Tasks blocked on human action. Each entry links to the originating BL item. Add an entry when you
set Status: blocked and the blocker is human-only — not waiting on another agent, not waiting on a
dependency an agent can resolve.
Per the methodology pattern, this is a passive registry: items land here via the blocked-item protocol, the human scans it when they check in, and the agent moves on to the next ready item instead of holding a lock.
recent/search queries at
the price of a C dependency in a “one-line install” CLI; JSONL keeps the install trivial and makes
P2 retrieval harder. The agent has written up both sides in the item body and has no basis to
choose between a distribution promise and a query capability. Blocks BL-0002 (which writes through
the storage layer). Added 2026-05-22.tinker on the package registry before the first publish.
Done 2026-05-18; item resumed and shipped.(Older unblocked items live in their epic’s ARCHIVE.md.)
Deps: field plus the lock.