diff --git a/docs/plans/CURRENT.md b/docs/plans/CURRENT.md index 5c64402c..11e1eeb2 100644 --- a/docs/plans/CURRENT.md +++ b/docs/plans/CURRENT.md @@ -1,6 +1,11 @@ -# CURRENT — single source of "what happens next" +# CURRENT — narrative log of the work in flight -This file always names exactly one next action. Any "continue" / "next" / +The task list is `docs/plans/QUEUE.md`: one table, one row per piece, with +owner, state and gate. Read that first; it says what is next for you. This +file holds the narrative behind the rows and the completed log, and it does +not always name one action any more. If the two disagree, QUEUE.md wins. + +This file historically named exactly one next action. Any "continue" / "next" / "proceed" message means: execute the action below, fully (implement → test → verify against its acceptance criteria → commit → push → close the issue → update this file to the next action). No ambiguity, no re-planning. diff --git a/docs/plans/DEFERRED.md b/docs/plans/DEFERRED.md index 77cfa1af..a09f00ea 100644 --- a/docs/plans/DEFERRED.md +++ b/docs/plans/DEFERRED.md @@ -60,14 +60,9 @@ at every gate. Started 2026-09-12 during the control board MVP. but unowned). Fix candidates: per-seat worktrees, or shared files edited only by the seat named in CURRENT.md. (2026-09-12) -## Queue (Jason's order) +## Queue -1. WebUI on Dewey's Console design absorbs the board as its first screen - (piece 4, MOSAIC-STACK-D-002, Gate E on Monday 2026-09-14). -3. Darkwing on point (piece 5, briefed on the plan page; starts Sunday - 2026-09-13 on Jason's message; Gate F: filbert's item closes with zero - human messages to filbert). Closes the "set by" gap. -4. Fleet launch through `mosaic launch`: the stress test. +Moved to `docs/plans/QUEUE.md` on 2026-09-13. This file holds only gaps. ## Done diff --git a/docs/plans/QUEUE.md b/docs/plans/QUEUE.md new file mode 100644 index 00000000..79b60979 --- /dev/null +++ b/docs/plans/QUEUE.md @@ -0,0 +1,54 @@ +# QUEUE — the one task list + +Read this first. One row per piece. Nobody needs to read the prose plans to +know what is next; the Brief column says which section to open only when you +are the owner of that row. + +How to find your next thing: + +- **Jason**: the first row whose State starts with `Jason:`. +- **A seat**: the first row where Owner is you and State is `in progress`, + `in review` or `briefed`. If there is none, you have nothing; say so on the + board and stop. +- **Coordinator (Claude session)**: update this table at every gate, before + anything else is written. CURRENT.md is the narrative log; this table wins + if they disagree. + +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. + +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. + +## Pieces (in order) + +| # | Piece | Owner | Issue | State | Gate | Brief | +|---|-------|-------|-------|-------|------|-------| +| 1 | Control board MVP (scanner + page) | darkwing | #1503 | Jason: rule whether the page answers "who is waiting on me" without a terminal; then close #1503 and mark MOSAIC-STACK-D-001 completed | A passed 2026-09-12 | plan page, top | +| 2 | Seat registration and `mosaic seat task` | darkwing | #1504 | done 2026-09-13 | B passed 2026-09-12 | plan page, Step 3 | +| 3 | Reply-from-board (piece 2 on the plan page) | darkwing | #1505 | done 2026-09-12 | C passed 2026-09-12 | plan page, "Piece 2: reply-from-board" | +| 4 | Ledger (piece 3 on the plan page) | darkwing | #1506 | done 2026-09-13 | D: 18.9 human messages per closed issue, week of 2026-09-06 | plan page, "Piece 3: ledger" | +| 5 | WebUI first screen on the Console design (piece 4 on the plan page) | dewey; filbert reviews | #1507 | in review (WEBUI-1507-R1 waiting on filbert) | E: Jason works Monday 2026-09-14 from the WebUI without the terminal | plan page, "Piece 4: WebUI first screen (Console)" | +| 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 | + +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 +point", and execute it. Start with the first assignment for filbert. Report at +Gate F or when blocked." + +## Parked (not in order, needs Jason to reopen) + +| Item | Why parked | Where | +|------|------------|-------| +| Registry increment 3 (headless identity-env leak) | #1500 closed on increment 2; Jason has not asked for 3 | CURRENT.md, "#1500 increment 2 (historical)" | +| Auth/provider/harness registry review | Paused for owner alignment | `docs/plans/2026-09-03_auth-provider-harness-registry.md` | +| CI runners, second real adapter, push automation | Deferred by owner 2026-09-03 | `docs/plans/ROADMAP.md`, "Explicitly deferred" | +| Console screens beyond the first (launch, observe, stop, transcript, palette) | Needs a new brief after Gate E | DEFERRED.md | +| Open gaps from the MVP work | Fixed only when a gate needs them | DEFERRED.md, "Open" | + +## Log of table changes + +- 2026-09-13 — created; rows 1 to 8 taken from CURRENT.md, DEFERRED.md and the plan page.