Every priority carries one of four states: Ready, Building, Shipped, Shared. They're how Annsa tracks the loop — Ready while the spec waits, Building when work starts, Shipped when it lands, Shared once the customers who asked have heard back.
01Four states, one loop
02Setting a state
The status button on any priority or spec moves it. The header pills count each state at a glance — the same four counts appear on account panels, so you can see where one customer's asks stand.
03Shipped is not the end
Mark a priority Shipped and Share Back is the natural next click — choose the recipients, send, and the priority moves to Shared. The state exists because "we built it" and "they know we built it" are different facts, and the second one is the one customers feel.
04Parked is a flag, not a state
Parking sets a priority aside without pretending it moved. A parked priority keeps its state and wears a Parked badge; restore it and it's exactly where it was. See Parking priorities.
05States on the roadmap
The roadmap board runs Backlog → Later → Next on the planning side, then Building → Shipped → Shared. The planning columns are yours to arrange; the delivery columns mirror the states.
06States from your coding tool
Over MCP, annsa.act moves states without opening the app — "mark the export priority shipped" from Claude Code or Cursor does exactly what the status button does, and it's attributed to whoever did it.