Process the capture inbox on a schedule
Decides which actions to take, in what order, toward a goal.
You might say…
“By the time I get to my inbox the notes are so old I've forgotten why I captured them.”
What it does
Runs on a schedule to sweep new captures, apply tagging and filing judgement, and present a ready-to-confirm batch — keeping the inbox from accumulating.
Trigger: Use when the capture rate consistently outpaces manual processing sessions and the inbox is a chronic source of guilt rather than a useful queue.
I/O: Newly captured fragments since last run → batch of proposed tags, locations, and discard flags ready for one-click confirmation
Autonomy: Acts with approval — does the work, checks in on the exceptions.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation