mosaicstack/stack
25
0
Fork 1
Code Issues 341 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

Queue as data: one machine-readable task registry, single writer, ledger checks #1508

New Issue
Open
opened 2026-09-13 00:41:17 +00:00 by jason.woltje · 1 comment
jason.woltje commented 2026-09-13 00:41:17 +00:00
Owner
Copy Link
Copy Source

Required after piece 5 (darkwing on point). Not parked. Rows 9-13 in docs/plans/QUEUE.md.

  1. Queue as data: QUEUE.md rows become a JSON file under the data root or repo; scripts/mosaic queue is the only writer (list, add, move, assign). Hand edits to shared plan files stop.
  2. AGENTS.md cadence: read the queue first; CURRENT.md is narrative only.
  3. Brief template: goal, gate, owner, out of scope, files owned; one page; linked from the row.
  4. Reviews and receipts go through the board/comms channel or issue comments, not files under docs/plans/reviews/.
  5. Ledger checks weekly: every open issue has a row; every in-progress row has a live registered seat; every done row has a closed issue; violations listed next to the human-messages number.

Gate G: a fresh seat launched with no prior context finds and starts its next piece from the queue alone, with zero human messages.

Why: the process goes off the rails every time because the entry point is prose and nobody enforces state. Jason, 2026-09-13: I want this iron-clad.

Required after piece 5 (darkwing on point). Not parked. Rows 9-13 in docs/plans/QUEUE.md. 1. Queue as data: QUEUE.md rows become a JSON file under the data root or repo; `scripts/mosaic queue` is the only writer (list, add, move, assign). Hand edits to shared plan files stop. 2. AGENTS.md cadence: read the queue first; CURRENT.md is narrative only. 3. Brief template: goal, gate, owner, out of scope, files owned; one page; linked from the row. 4. Reviews and receipts go through the board/comms channel or issue comments, not files under docs/plans/reviews/. 5. Ledger checks weekly: every open issue has a row; every in-progress row has a live registered seat; every done row has a closed issue; violations listed next to the human-messages number. Gate G: a fresh seat launched with no prior context finds and starts its next piece from the queue alone, with zero human messages. Why: the process goes off the rails every time because the entry point is prose and nobody enforces state. Jason, 2026-09-13: I want this iron-clad.
jason.woltje commented 2026-09-13 00:45:14 +00:00
Author
Owner
Copy Link
Copy Source

Plan page with decomposition and gates: docs/plans/2026-09-13_queue-as-data.md (pieces A to E, Gate G). QUEUE.md rows 9 to 13 link to it. Starts after piece 5 (row 6) reaches Gate F or blocks.

Plan page with decomposition and gates: docs/plans/2026-09-13_queue-as-data.md (pieces A to E, Gate G). QUEUE.md rows 9 to 13 link to it. Starts after piece 5 (row 6) reaches Gate F or blocks.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
Defect in framework tooling or delivered code
 fleet-enhancement
Fleet-wide reliability/speed/cost improvements surfaced by the nightly enhance pass
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
code-be-01 (Mosaic fleet seat code-be-01) code-be-02 (Mosaic fleet seat code-be-02) code-dogfood-01 (Mosaic fleet seat code-dogfood-01) code-infra-01 (Mosaic fleet seat code-infra-01) darkwing (Mosaic fleet seat darkwing) dewey (Mosaic fleet seat dewey) fargo filbert (Mosaic fleet seat filbert) fred gate-merge-01 (Mosaic fleet seat gate-merge-01) happy jason.woltje (Jason Woltje) marcie merge-gate ops-01 (Mosaic fleet seat ops-01) ops-02 (Mosaic fleet seat ops-02) ops-03 (Mosaic fleet seat ops-03) ops-ci-01 (Mosaic fleet seat ops-ci-01) ops-deploy-01 (Mosaic fleet seat ops-deploy-01) orch-01 (Mosaic fleet seat orch-01) pepper resume rev-code-01 rev-code-02 rev-security-01 rev-security-02 rev-security-03 (Mosaic fleet seat rev-security-03) rocko (Mosaic fleet seat rocko) sanity scooby (Scooby) scrappy shaggy tiny topher (Mosaic fleet seat topher) velma veronica (Mosaic fleet seat veronica) vision woodpecker
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaicstack/stack#1508