From cbf24b01b00b5df0e05a4a7a02308bad6b506667 Mon Sep 17 00:00:00 2001 From: Jason Woltje Date: Sat, 12 Sep 2026 19:41:56 -0500 Subject: [PATCH] QUEUE rows 9-13 (#1508): process becomes data, one writer, ledger checks; AGENTS.md cadence reads QUEUE.md first Jason: the process goes off the rails every time because the entry point is prose. Rows 9-13 are marked required and cannot be parked. Co-Authored-By: Claude Fable 5.1 --- AGENTS.md | 10 ++++++---- docs/plans/QUEUE.md | 9 ++++++++- 2 files changed, 14 insertions(+), 5 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index dbf555ef..896df4e8 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -51,9 +51,10 @@ green at every step. Not production software — a proven foundation. - **Register** your session in `docs/SESSIONS.md` — one append-only line (date, actor, scope, outcome). Never rewrite or remove entries. -- **Cadence**: read `docs/plans/CURRENT.md` → execute its single next action - fully (implement → test → verify against acceptance criteria → commit → - push → close issue) → update CURRENT.md → register in SESSIONS.md. +- **Cadence**: read `docs/plans/QUEUE.md` first; your next piece is the first + row you own that is briefed, in progress or in review, nothing else. Open only + the brief that row links to. Execute it fully (implement → test → verify against acceptance criteria → commit → + push → close issue) → move your QUEUE.md row → register in SESSIONS.md. - "next" means one action. A batch mandate ("run the queue") repeats the loop until green or blocked. Blocked means stop and report, never improvise. - Substantial work gets a Gitea issue and a BUILD-LOG phase entry @@ -99,7 +100,8 @@ Full reference — usage, fields, exit codes, safety notes: ## Pointers (depth lives here) -- `docs/plans/CURRENT.md` — THE next action (single source of "what now") +- `docs/plans/QUEUE.md` — THE task list (one row per piece; read first) +- `docs/plans/CURRENT.md` — narrative log behind the queue rows - `docs/plans/ROADMAP.md` — agreed milestone path (M16+) - `docs/plans/CONDUCTOR.md` — orchestration protocol and guardrails - `docs/plans/2026-09-02_atomic-mosaic-foundation.md` — architecture, invariants diff --git a/docs/plans/QUEUE.md b/docs/plans/QUEUE.md index 0de09b50..34abeaed 100644 --- a/docs/plans/QUEUE.md +++ b/docs/plans/QUEUE.md @@ -16,7 +16,8 @@ How to find your next thing: States: `queued` (no brief yet) → `briefed` (brief written, not started) → `in progress` → `in review` → `Jason: ` → `done`. `parked` -means not before the rows above it and not without Jason's say. +means not before the rows above it and not without Jason's say. `required` +means it cannot be parked or reordered below `queued` rows; only Jason moves it. Brief locations: "plan page" is `docs/plans/2026-09-12_control-board-mvp.md`. Gaps found while working go to `docs/plans/DEFERRED.md`, not here. @@ -33,6 +34,11 @@ Gaps found while working go to `docs/plans/DEFERRED.md`, not here. | 6 | Darkwing on point: darkwing assigns and gates filbert's work (piece 5 on the plan page) | darkwing | none yet | briefed; Jason: send the start message from the board on Sunday 2026-09-13 | F: filbert's item closes with zero human messages from Jason | plan page, "Piece 5: darkwing on point" | | 7 | Weekly ledger run and rails number | Jason | — | recurring, end of Monday 2026-09-14 | under 10 human messages per closed issue for the week of 2026-09-13 | `packages/ledger/README.md` | | 8 | Fleet seats (`~/.mosaic`) onto `mosaic launch` | unassigned | — | queued; not before row 6 is done | Jason's call | none yet | +| 9 | Queue as data: JSON registry, `mosaic queue` is the only writer (list, add, move, assign) | darkwing | #1508 | required; starts when row 6 is done, before row 8 | G: a fresh seat with no prior context finds and starts its piece from the queue alone, zero human messages | #1508 | +| 10 | AGENTS.md cadence reads the queue first; CURRENT.md is narrative only | coordinator | #1508 | done 2026-09-13 (AGENTS.md cadence and pointer lines) | — | #1508 | +| 11 | Brief template: goal, gate, owner, out of scope, files owned; one page, linked from the row | darkwing | #1508 | required; with row 9 | rows 9 and 12 use it | #1508 | +| 12 | Reviews and receipts through the board or issue comments, not files in `docs/plans/reviews/` | darkwing | #1508 | required; after row 9 | one review round with no new file under reviews/ | #1508 | +| 13 | Ledger checks: open issue has a row; in-progress row has a live seat; done row has a closed issue | darkwing | #1508 | required; after row 9 | violations printed with the weekly number, first run Monday 2026-09-21 | #1508 | Start message for row 6, sent from the board to darkwing: "Read docs/plans/QUEUE.md, then the plan page section "Piece 5: darkwing on @@ -52,5 +58,6 @@ Gate F or when blocked." ## Log of table changes - 2026-09-13 — created; rows 1 to 8 taken from CURRENT.md, DEFERRED.md and the plan page. +- 2026-09-13 — rows 9 to 13 added (#1508): the process itself becomes data with one writer and ledger checks. Jason: "I want this iron-clad." Required, not parked; rule: these rows cannot be moved to parked, only to done. - 2026-09-13 — dewey: WebUI row advanced to Jason-owned Gate E after Filbert approval, exact committed-tree 208/208 and remote-verified ea00ec66 publication. No other row changed.