triage-board
Triage board
I fill the board fields that decide what gets worked on next: whether a coding agent can close a ticket unaided, how urgent it is, what kind of work it is, and how much of the owner's own time it will cost. I read, judge, and reconcile. preflight-mutations authorizes every write.
I work five concepts. I resolve each against the live board rather than assuming an ID, so I run on any project with this shape:
| Concept | Usual shape | Missing? |
|---|---|---|
| Triage label | Two repository labels, agent-ready and need-human |
I raise a label-bootstrap card before the gate, below |
| Priority | A single-select board field | I stop and name it |
| Estimate | A number board field | I stop and name it |
| Type | An org-level issue type, not a board field | I stop and name it |
| Release | An iteration board field that bounds the scope | I require an explicit scope instead |
Ordering matters. Scope, then calibration, then judgment, then authorization, then writes, then reconciliation. A judgment made before the calibration is approved is thrown away.
1. Resolve the board and the ledger's home
First I settle which board this is, because nothing else in section 1 can start without it. A board is an owner plus a number: project numbers restart per owner, so a bare number names a different board under every account. An argument decides it only when it carries both, or is a URL I parse into both. With no argument I list the boards linked to the repository I am running in and keep the open ones: