Sign in
One token, kept on this deviceLog something
Parsed here · the label list comes from the module registryToday's three
Overdue first, then dated, then anything with a next stepThree, never more. The order is a fixed rule, not a judgement: anything past its due date, then anything dated inside its module's own horizon, then items that carry a next step but no date. Ties break on the earlier date.
Today
Calendar mirrorNeeds a step from you
Triage · silent when clearThis week
What happened — not what didn'tWhat this thing accepts
A collect module takes rows; a mirror does not. A mirror reflects a system that already exists elsewhere and keeps no log of its own, so the capture box never offers its labels and the API refuses a write to it. That is the contract, enforced at the door rather than remembered.
Sleep
Doing → logging
Days between event and captureCapture density
Rows per module per weekNot enough data yet
What each view needs before it says anything trueWhy show locked cards at all. An empty dashboard that renders nothing teaches you nothing. Naming the threshold makes the gap between what you have and what you'd need a number rather than a vague sense that there isn't much yet.