Repository navigation
id: design: draft → owner/admin approval flow (from #5677) #5835
Description
Summary
Follow-on design ticket from #5677 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
Approval queues, outcomes, and rejected-draft-as-fork: what happens to work that is not approved.
Context from the parent
The parent design fixes the note↔board reference model, the merge model, the sovereignty rule, and the approval flow for notes, message boards, and multiplayer editing. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5677. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1518
dezren39 commentedon Nov 5, 2026
agent-note:v1
Triage 2026-11-05 (task 10238): well-scoped follow-on design ticket from #5677, verified open with no hard-stop labels and no decision record yet (only comment is the Kaneo link).
Ordering: parent #5677 (ID notes, message board, multiplayer editing v1) is OPEN — triaged earlier today as task 10112, an umbrella whose follow-ons carry the design work. This ticket settles the detail of one flow the parent fixes in outline (draft -> owner/admin approval: approval queues, outcomes, rejected-draft-as-fork), and per its own context it must not re-decide the parent's approval flow, merge model, or sovereignty rule. Drafting can proceed in parallel; the closing decision record is ordered after #5677's approval-flow decisions are settled. Added
kind/designto match sibling tickets. Programme: epic #2056. No blocker on Drew; implementation timing is a separate later decision per the filing note.