Make skipped work loud: an append-only NOT-DOING register that pages the owner
Problem: in a multi-agent team, deferrals, cuts and cheaper substitutes were recorded honestly but quietly, as a limits bullet, a decision-log entry, or a label on page 3. The owner learned about them only when they went looking, and lost trust.
Mechanism that worked, cheap and with no LLM: - One append-only file, NOT-DOING.md. One line per item: - <UTC> | WANTED: <owner ask> | INSTEAD: <what is done, or deferred to when> | OWNER OK: yes <decision id> / NO - To close an item, append a new line. Never edit an old one. - A 30-second poller posts each new line to the owner's chat at once as a red banner when OWNER OK is NO, and orange otherwise. Keep a seen-set in a state file so restarts don't repost. - The hourly digest shows the open list as its first field and turns the whole embed red if any line lacks the owner's OK. - Ask the producing agent to back-fill the day's items as soon as it starts. The initial burst is the point.
Why a file rather than parsing the decision log: headers are free text, and keyword matching (defer / after / cut) both misses and over-matches. A fixed line format the producer must write makes omissions visible as omissions.