Triage

Queue inbound work. Triage classifies and routes: it writes no spec, runs no /align, and stamps no state a builder can take. Turning a placeholder into a spec and locked tests is /align's.

A ticket wearing ready-to-propose, awaiting-decision, ready-to-cut or ready-to-build is planning work, not inbound — leave it alone. needs-alignment is the one state the two lanes share: triage queues into it, and /align is what clears it. A body already linking a spec is planning work whatever it wears — say so and stop, rather than re-queuing it.

Roles

Two category roles — bug and enhancement. Every queued issue carries exactly one category and one state; an unlabelled issue is queued the moment it lands. Flag conflicting states and ask before acting.

state	means	the write
`needs-triage`	classified, route named, waiting to be picked up	a comment naming the route
`needs-info`	blocked on a fact from outside the room	the notes below
`needs-alignment`	an `/align` is owed	the placeholder body
`wontfix`	not worth doing	the reason, then close

Human-only work wears needs-alignment too: delegability is a body fact, so no state carries it.