A crew beside a backlog says why it stands still

An engine that reads idle next to open issues accounts for every one of them, and raises its hand when only a person can release the work.

The tick line. Each tick of a repository the crew works says how many issues are open and why the ones that are not ready wait, one count per reason:

[autonomy] tick repo=trevato/forge did=idle open=278 waiting="later=245 plan=17 blocked=6" ready=10 startable=0 held="open_pull=2 twin=1"

ready, startable, held and passed account for the rest, as before.

A closed blocker frees what waited for it. An issue whose only blocker closed is ready, whatever that blocker itself once waited for. Before, the closed blocker's own links still counted, so such an issue was never ready while Next up called it ready and the map called it blocked.

The planner's hold is named. When the owner's pause or open-issue ceiling holds the planner, the tick says so (planner not asked why="the planner is held by the open-issue ceiling: …") and gives the planner nothing.

The need. When a tick picks nothing, asks no planner, nothing can start, and open issues wait for a person (later, unconfirmed or unadopted), the needs stack carries one row for the repository, for whoever may write to it:

trevato/forge: the crew has nothing to start, and 278 issues are open. 245 wait behind the Later gate, 17 are

the plan's own, 6 wait for other open work.

Its one choice, "Open what is held", opens /:owner/:name/held, where held issues are lifted one at a time or closed in one approval (the terminal's held screen and the held and lift MCP tools do the same). The row is on the home page's needs count, /asks, the terminal and the MCP forge tool, and is gone on the next tick that starts something. Nothing is lifted without a person: which held work goes next is the owner's order.

Not done: the count is the last tick's, kept in memory, so the row appears a tick after a restart.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs