MEMO 03 · HUMAN LOCK
NEEDS: the router file (Memo 01) · the morning stack (Memo 02) · your chat and shared documents, connected (Spec Sheet 02) or pasted in and attached
Memo 02 ended on the item waiting on you. On Ambervale’s* desk, it’s a message the executive director sent at 5:40 Wednesday evening, with five calls for Thursday and one instruction: “Come with positions, not summaries.”
Those five calls are buried in 51 messages across six channels and three direct threads, four documents and two forms. A decision queue reads it all and returns each call with a recommended position.
HUMAN LOCK
Your AI can sort and price every call in the week, and each one is still made by the person who answers for it.
51 messages read, five calls returned, one recommendation overruled.
The setup
The queue holds the calls you make and the ones you owe a recommendation on.
OPTIONS
Two to four real choices, including doing nothing when waiting is one of them.
RECOMMENDED
One pick and its strongest reason. It’s the position you take into the room, or strike.
COST IF WRONG
Hours, dollars or a relationship, and whether it can be undone. It sets the order, so the call you can’t take back comes first.
NOT MINE
Calls that belong to someone else, with the owner from your router file’s WHO DECIDES WHAT.
NOT DECISIONS
Updates and plain tasks, one line each, so you can see what it set aside.
Save these fields in a file next to your router file, and attach both when you start the queue.
The queue reads the week where it happened: your chat channels and shared documents, through the same one-time sign-in as your calendar and inbox. Some of those connections can post or edit as well as read. The queue only reads, so set anything that writes to ask first. For now you start it yourself; scheduled runs come in Memo 04.
The queue also works without any connection. If you aren’t ready to connect, aren’t sure how yet (check out Spec Sheet 02), or your work account doesn’t allow it, paste the week’s messages into the chat and attach the documents and forms as files. The queue reads pasted text and attached files the same way. What changes is the gathering: you collect the week yourself, and each run needs a fresh copy.
THE OVERRIDE
The top call in the video is a five-year lease the board must approve, and the landlord wants an answer four weeks before the board meets. The queue recommends a special vote. I strike it and ask the landlord to hold, knowing he may walk. The reason is one line no file holds: Ambervale’s chair takes multi-year commitments only at regular meetings. It goes into the router file, dated.
The close
The queue spares you the second pass through the week, the one spent hunting for what needs deciding. On Ambervale’s desk, that attention goes to the lease, the one call that turned on knowing the chair. That’s the queue thinking with you: it put the hold on the list of options and gave you a recommendation worth arguing with.
What’s the oldest call on your desk right now, and what would it cost to be wrong about it?
* Ambervale is a fictional nonprofit I use in these memos so I can show real workflows without showing anyone’s real inbox.