Statuses and approvals - MUTAGENT

Early Access. Commands and behavior can change between releases.

Canonical statuses are the Factory’s names for board progress. Map them to your own column names with statusMap.

Canonical status	Meaning
`triage`	New work. An item here never starts a run; move it to another column first.
`planning`	A plan is being prepared.
`awaiting_approval`	The plan waits for your decision.
`approved`	The plan is approved; building can start.
`in_progress`	The change is being built.
`in_review`	The change is being reviewed.
`awaiting_merge`	Waiting for merge approval or landing.
`done`	Done.
`on_hold`	On hold.
`dropped`	Dropped; no one is working on it.

Map only the columns you have; unmapped statuses aren’t mirrored. Every key must be one of the ten statuses above, every value a non-blank string, and the map needs at least one entry. Leave out statusMap only if you want Cloud’s default map.

A status is not a run state or a gate name

in_progress is a board status. runs list --state takes run states, such as BUILDING or PAUSED. Approval commands take a gate name: plan or pr. Don’t use one in place of another.

architech factory runs list --state AWAITING_APPROVAL --json
architech factory runs show <run-id> --json

Check the pending gate, read the plan or PR, then decide. A partial board map never skips a stage or removes an approval. Moving a card into a column doesn’t approve a gate either: add the approval label. See operating the Factory for approval and rejection commands, and factory.yaml for mapping examples.