The thread that usually dies the moment you switch tabs.
It holds the commitment, brings it back at the right moment, and keeps the work moving between conversations - because the open loop is the job.
Follow-ups
It holds the commitment, brings it back at the right moment, and keeps the work moving between conversations - because the open loop is the job.
What holds
Why this is the job
An agent that answers and forgets is an assistant.
The difference between a tool and a chief of staff is what happens after the answer. What was owed to somebody, what has gone quiet, what you said you would do on Thursday - held, and brought back beside the work rather than filed on a list you have to remember to open. (episode.ts, recurring.ts, when.ts)
It remembers what was owed
To a customer, a vendor, a candidate, a board member - and to whom, since a promise without a person is a note.
It notices silence
Nine days without a reply is a fact. It is treated as one rather than waiting for you to notice.
It comes back at the moment
Not at 9am with everything. Next to the thing that needs it, when it needs it.
Its routine is a line you can edit
What it does unasked is written in plain words in the command centre, not buried in a schedule table. (heartbeat.ts, from PicoClaw)
How it goes
From the mention to the return, in four moves.
You mention it once
"Chase them, and remind me Thursday if they stay quiet."
It holds the loop
With the person, the thing, and the moment it should come back.
It acts up to the line
Drafts the chase, lines up the context, prepares the decision.
It returns it to you
And anything irreversible still waits for your yes.
When nothing is outstanding
Nothing being carried. Which is either a quiet week or a new one.
This is the one list here that is not obviously good when it is empty. Either every loop got closed, or none has been picked up yet - so it says which, rather than showing you a tick and letting you assume.
Nothing is being carried
Mention something with a loose end and it gets picked up, appearing here with the date it will come back to you on.
What it holds to
Four ways a loop will not be closed. Quietly least of all.
It never quietly closes a loop
A thread it could not move is reported, not dropped.
It never sends the chase itself
Outbound is outbound. The draft is ready; the send is yours.
It never runs a schedule you cannot read
If it does something unasked, that instruction is legible and editable in your own words.
It never mistakes a plan for a mission
"Add a step: book a van" is a plan; "book the van" is an errand. Confusing the two is how an agent does something you were still thinking about.
The rest of the workbench.
Decisions arrive with the work done, not the questions still open.
Context that stays warm after the meeting, the email, and the tab close.
Meet the chief of staff your company never had.