yoi/.yoi/tickets/open/20260606-215403-explicit-ticket-workflow-state/thread.md

Created

Created by LocalTicketBackend create.

---

Plan

Created from design discussion about removing inferred panel Ticket state.

Decision recorded:

• stop treating panel heuristics from labels/title/thread events as authoritative workflow state;
• add an explicit durable Ticket workflow state: intake -> ready -> queued -> inprogress -> done;
• intake -> ready is completed through Intake Pod conversation/materialization;
• ready -> queued is the normal human panel action, replacing the current Go action with Queue;
• review/rework stay inside inprogress;
• blocked/user-attention is an overlay such as attention_required, not a workflow state;
• transient activity should be derived from live Pod/session/thread state and not persisted in Ticket frontmatter.

---

Decision

Updated per user direction:

• Ticket row should not expose priority/action/status/phase as separate permanent columns; they are redundant once explicit workflow state exists.
• Ticket rows should be essentially state + slug/id + title.
• Pod rows should likewise be essentially pod-state + pod-name.
• Operations such as Queue/Defer/Open/Send should move to selected-row actionbar/key hints instead of row columns.
• Composer/status bar should be kept concise; verbose target/help/diagnostic text should move to actionbar or detail/diagnostic areas.

---