What this repository intends to do, published the way facts are and never allowed to go stale quietly.
The workflow emits `backlog/1` from `.backlog/items.json` — where items are actually filed — and checks the two rules that carry the format: expiry is derived from an item’s kind and refused as input, and nothing reaches the public projection until a named human promotes it.
Items decay on purpose, which is why the run is also daily: a fragment a month old under-reports how much of the plan has quietly stopped claiming to be current. A backlog that cannot decay is a lie told at increasing volume.
The fragment is a generated artifact emitted from the source and never hand-edited, and `paths-ignore` stops the commit it makes from triggering it again.
That no intention was published without a human, and that nothing claims to be current past its derived deadline. Re-emit from the same `.backlog/items.json` and the fragment matches; an item nobody promoted is absent, and an expired one reports as decayed.
An agent backlog is the future tense of a record: one item per intention, filed by the agent doing the work in the repository that owns it, decaying on a deadline derived from its kind, and promoted to public only by a named human.
agent backlog →