diff --git a/docs/SESSIONS.md b/docs/SESSIONS.md index 88eeaa67..3c506346 100644 --- a/docs/SESSIONS.md +++ b/docs/SESSIONS.md @@ -421,3 +421,4 @@ are never rewritten or removed; corrections are new entries. 2026-09-27T00:11:29Z | Filbert (T3 Claude Code, thread 9cb9731e) | CHAT-03 brief R2 review (#1507 row 5), BRIEF-r2 5c5b45a2 | changes requested: F1 extension turn can overlap Mosaic preflight (spurious agent_settled, order-based attribution unsound), F2 empty clear_queue omits extension custom messages; B2-B6 and N1-N12 closed; review agents/filbert/work/chat-03-brief-review-r2-2026-09-26.md d149e8cc 2026-09-27T00:21:33Z | Sage (T3 Claude Code, thread 1ef1e4f8) | goals review, SetSpark deploy decision | Jason: decide. Deploy of shared-signals cc74d92 handed to the stack operator seat (12fe8cda). Goals review page written from ledger evidence (47.7, 33.0 human msgs per closed issue vs <10); CHAT-03 source held for rescope; two-round brief budget. Lead decision 27. North star to Jason for ratification. 2026-09-27T00:24:20Z | Sage (T3 Claude Code, thread 1ef1e4f8) | SetSpark deploy outcome | Operations seat deployed shared-signals cc74d92 to VM 1022 00:23Z, verified; survey: DEC-009 only bad row, 0 Accepted over 16. DEFERRED entry moved to Done; lead decision 28 (DEC-009 stays as stored). Caddy recreate side effect sent to operations. +2026-09-27T00:28:13Z | Sage (T3 Claude Code, thread 1ef1e4f8) | goal 1, close what is open | Closed #1503, #1509 and #1511 on evidence; QUEUE rows 1, 6, 23, 24, 25 done; Gate F recorded not passed (ledger: 2 human msgs in filbert thread, pre-T3 period unmeasurable), Gate G carries it; rows 9-13 unblocked. Lead decision 29. Open: #1507, #1508. diff --git a/docs/plans/2026-09-26_lead-decisions.md b/docs/plans/2026-09-26_lead-decisions.md index 59765c36..49717f96 100644 --- a/docs/plans/2026-09-26_lead-decisions.md +++ b/docs/plans/2026-09-26_lead-decisions.md @@ -343,3 +343,27 @@ which stay with him. Each item names who decided it and what happened. `depends_on`, about 20 s of edge downtime. I suggested `--no-deps setspark-api` to the operations seat. The procedure is theirs to change. +29. **Open items closed (goal 1).** Jason said on 2026-09-27 that Sage had + been distracted from mosaic-stack. Sage closed what the evidence + supports: + - #1511 closed. af4203ca is pushed, Filbert approved R2, and Jason + confirmed the live display on 2026-09-15. + - #1503 closed. D-001's MVP was one page of running Pi sessions with a + waiting-on-Jason flag. Gate A passed, and the attention status fix is + operator-accepted (row 22). Cross-harness board work is Gate E's. + - Row 25 is done (item 19). Row 23 is done on its live write with web + calls recorded. Its outside-root refusal rests on the offline suite. + - Row 24 is done without a live use. The Discord Sage has never called + commit or push. Records now go through row 25, and SetSpark cutover + freezes `vault/`, so another Discord check from Jason isn't worth + asking for. First real use is the check, and a failure opens a new + issue. + - #1509 closed. Gate H passed on 2026-09-13, and rows 14 to 25 are done. + Its gaps stay in DEFERRED. + - Row 6 closed, and Gate F is recorded as not passed. The ledger counts 2 + human messages in Filbert's T3 thread during #1512's life. One is + Jason's 09-26 takeover message. The item's first 11 days also predate + the T3 source, so a zero was never provable. Gate G (row 9) tests the + same thing on the queue, so it carries the test and Gate F isn't + rerun. Rows 9 to 13 no longer wait on row 6. + Still open: #1507 (Gate E, row 5) and #1508 (Gate G, A2 in progress). diff --git a/docs/plans/QUEUE.md b/docs/plans/QUEUE.md index 1ab37974..bd65ded8 100644 --- a/docs/plans/QUEUE.md +++ b/docs/plans/QUEUE.md @@ -28,22 +28,22 @@ Lead: Sage from 2026-09-26 (Jason's ruling); Darkwing is a collaborating seat. Jason is preparing the target for the next phase; until it arrives, the priority below stands. -Current owner priority: row 6, the next already-briefed coordination item after -Jason accepted row 18. His newer standing continuation instruction supplies the +Current priority: Sage's goal order from the 2026-09-27 goals review (close +what is open, queue as data, Gate E), pending Jason's ratification. Earlier: row 6, after Jason accepted row 18. His newer standing continuation instruction supplies the start; the earlier row-18-only priority is complete. Jason requires automatic continuation to the next authorized item after each accepted iteration; no routine next-step prompt. Explicit dependencies and protected-action gates remain. Use the five internal agents, not fleet seats. No -`~/.mosaic` changes or live fleet migration. Rows 9-13 still depend on row 6; -this does not waive those dependencies or authorize publication/access changes. +`~/.mosaic` changes or live fleet migration. Row 6 closed 2026-09-27 (lead decision 29), +which clears rows 9-13 to proceed; it does not authorize publication/access changes. | # | Piece | Owner | Issue | State | Gate | Brief | |---|-------|-------|-------|-------|------|-------| -| 1 | Control board MVP (scanner + page) | darkwing | #1503 | targeted status correction fully operator accepted in row 22; broader MVP ruling remains separate | A passed 2026-09-12 | plan page, top | +| 1 | Control board MVP (scanner + page) | darkwing | #1503 | done 2026-09-27 (Sage, lead decision 29): D-001 MVP delivered, Gate A passed 2026-09-12, attention status operator-accepted (row 22), relaunch activity, attribution and Host guard landed; #1503 closed; cross-harness board work belongs to Gate E (row 5) | 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 | CHAT-00/01/01C contracts published (370823b3, 28d4e98a, b023841c); CHAT-02 done: backend a5beb6d9, Console c9e771cf, live check passed 2026-09-26; CHAT-03 chartered 2026-09-26 (Jason approved); after brief r3, source work waits for Sage to rescope against Gate E (lead decision 27), Dewey writes the brief, Filbert reviews, Rocko adversarial, source author named by Darkwing after brief approval; CHAT-04..08 not chartered; Gate E blocked | E: all-seat interactive demonstration then Jason workday ruling; live cutover separately approved | `2026-09-13_webui-session-chat.md`, CHAT-00..08 | -| 6 | Darkwing on point: darkwing assigns and gates filbert's work (piece 5 on the plan page) | darkwing; filbert authors pilot; darkwing/dewey review | #1511 code phase; #1512 pilot | #1511 and #1512 committed locally in af4203ca (with rows 18 and 22), not pushed; #1512 re-run against 21e3e908 passed the serial acceptance command 397/397 three times; failures under concurrency are #1509 engine tests, reproduced on clean HEAD, filed in DEFERRED; #1512 closes after Sage's records commit; board restart for live #1512 and the Gate F live assignment wait on Jason | F: filbert's item closes with zero human messages from Jason; code phase does not claim Gate F | `2026-09-15_relaunch-activity.md`; `2026-09-14_task-attribution.md`; plan page Piece 5 | +| 6 | Darkwing on point: darkwing assigns and gates filbert's work (piece 5 on the plan page) | darkwing; filbert authors pilot; darkwing/dewey review | #1511 code phase; #1512 pilot | done 2026-09-27 (Sage, lead decision 29): #1511 and #1512 landed in af4203ca (pushed) and are closed; Gate F not passed: the ledger counts 2 human messages in filbert's T3 thread during #1512 (one is Jason's 09-26 seat takeover) and its first 11 days predate the T3 source; Gate G (row 9) now carries the zero-human-message test | F: filbert's item closes with zero human messages from Jason; code phase does not claim Gate F | `2026-09-15_relaunch-activity.md`; `2026-09-14_task-attribution.md`; plan page Piece 5 | | 7 | Weekly ledger run and rails number | sage (lead decision 27); Jason reads | — | recurring, every Monday; 09-13..19: 47.7, 09-20..26: 33.0 human messages per closed issue | 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 | — | parked by current owner direction; no `~/.mosaic` changes during internal bootstrap | Jason's call | none yet | | 9 | Queue as data: `docs/plans/queue.json`, `mosaic queue` is the only writer | darkwing; filbert reviews | #1508 | required; A1 (journal, lock, CLI, verify) committed 34a72af9 2026-09-27, Filbert approved; A2 (migration, render, dispatch) in progress, then genesis and hook install by Sage | G: a fresh seat told only "run `mosaic queue next` and do it" starts its piece with zero human messages | `2026-09-13_queue-as-data.md`, Piece A | @@ -60,9 +60,9 @@ this does not waive those dependencies or authorize publication/access changes. | 20 | Discord connector: per-user channel allowlist in the binding and Carmen enrolled (all listed rooms except #sage-admin) (MVP iteration 5) | coordinator | #1509 | done: caaef941 (`users[].channels` allowlist, `channel-not-for-user` drop); Carmen enrolled live by reload 00:03 UTC; her first message is the remaining check | Carmen gets a reply in #general and silence in #sage-admin; Jason unchanged | `2026-09-13_discord-connector-pilot.md` section 11 | | 21 | Discord connector: read-only tools for the Discord Sage through a Mosaic pi extension confined to declared roots (MVP iteration 6) | coordinator; reviewer per Q12 | #1509 | approved: rev-code-02 round 2 verdict 26276 (tree 43f0329b); committed locally; live check in #sage-admin with Jason next; Jason ruled R1–R7 2026-09-14 (roots docs/ and agents/sage/, Carmen included) | Sage answers a question from a file under a declared root with the reads in the turn record; a read outside the roots is refused and recorded | `2026-09-14_discord-readonly-tools.md` | | 22 | Board attention status: completed replies idle, explicit human input waiting | darkwing; filbert reviews | #1503 | source approved, receipt 26248; reviewer 193 per copy, author union 213 pass; actual Researcher scan idle | operator accepted full targeted status sequence: explicit request waiting, Seen hides attention but preserves waiting, completion returns idle; broader MVP/cross-harness acceptance and publication separate | `2026-09-13_board-attention-status.md` | -| 23 | Discord connector: writes confined to the `shared-signals` root plus web fetch and search for the Discord Sage (MVP iteration 7) | coordinator; reviewer per Q12 | #1509 | committed and pushed 1685deb4 (2026-09-18); operator check pending. Earlier: parts 1 and 2 (writes, web fetch and search) built 2026-09-16, suite 52/52, node 128; round 3 pinned for rev-code-02 on #1509 comment 26361 (supersedes rounds 1–2; adds the engine held-prompt fix); part 3 done live 2026-09-17 (SearXNG container on loopback, binding web key, restart; first live turn searched, fetched and wrote vault/Businesses/naming.md); Jason ruled D1–D4 2026-09-16 (SearXNG, Jason and Carmen write, any https host, rev-code-02) | Sage writes a naming shortlist into the repository from #ideas with the write and web calls in the turn record; a write outside the root is refused | `2026-09-16_discord-write-and-web-tools.md` | -| 24 | Discord connector: git verbs (status, commit, pull ff-only, push) for the Discord Sage on the `shared-signals` root, seat identity through the existing credential helper (MVP iteration 8) | coordinator; reviewer per Q12 | #1509 | committed 1949ed8d, pushed 2026-09-26; binding change and live check pending. Earlier: done 2026-09-18: built (src/git.mjs, bin/git-credential.mjs, extension params, envelope requester, context paragraph, vault protocol via reserve_id and per-write locks); suite 58/58, node 143; rev-code-02 APPROVED round 1 (#1509 comment 26375, tree 82ab962f); D5 mechanism changed: the fleet helper declines github.com, so the package ships its own credential helper reading the 0600 seat token file; binding change and live check next | Sage commits and pushes a decision file from #ideas; GitHub shows Sage as author with a Requested-by trailer; no token in any record | `2026-09-16_discord-git-tools.md` | -| 25 | Discord connector: SetSpark record client for the Discord Sage, fixed verbs against setspark-api, connector-verified approvals (MVP iteration 9) | coordinator; reviewer per Q12 | #1509 | rev-code-02 approved round 1 (#1509 comment 26467); committed 43d7574d, pushed 2026-09-26; live check pending. Earlier: in progress 2026-09-20: Jason's go relayed by the SetSpark coordinator (plan v3.2, shared-signals 55b2515); part 2a built (config, key read per call, HTTP core, approval ledger, Approve button and `approve` reply resolution, bind and approval submission with restart retry); part 2b built against shared-signals a5425a2 (eight model verbs, connector client, button evidence by confirmation message); node 162 pass, suite 63 passed; next: rev-code-02 review on #1509, local commit | Sage creates one work item from #sage-admin and the API shows it with revision 1; a proposal is approved by the Approve button and the audit row carries Sage's key id and Jason's Discord id separately; rev-code-02 approves on #1509 | `2026-09-20_discord-setspark-client.md` | +| 23 | Discord connector: writes confined to the `shared-signals` root plus web fetch and search for the Discord Sage (MVP iteration 7) | coordinator; reviewer per Q12 | #1509 | done 2026-09-27 (Sage, lead decision 29): committed and pushed 1685deb4; live turns wrote `vault/Businesses/naming.md` with web_search and web_fetch in the turn record; the outside-root refusal rests on the offline suite, not a live turn | Sage writes a naming shortlist into the repository from #ideas with the write and web calls in the turn record; a write outside the root is refused | `2026-09-16_discord-write-and-web-tools.md` | +| 24 | Discord connector: git verbs (status, commit, pull ff-only, push) for the Discord Sage on the `shared-signals` root, seat identity through the existing credential helper (MVP iteration 8) | coordinator; reviewer per Q12 | #1509 | done 2026-09-27 (Sage, lead decision 29): committed and pushed 1949ed8d; live-configured 2026-09-18, never used from Discord; records now go through row 25 and SetSpark cutover freezes `vault/`, so first real use is the check and a failure opens a new issue | Sage commits and pushes a decision file from #ideas; GitHub shows Sage as author with a Requested-by trailer; no token in any record | `2026-09-16_discord-git-tools.md` | +| 25 | Discord connector: SetSpark record client for the Discord Sage, fixed verbs against setspark-api, connector-verified approvals (MVP iteration 9) | coordinator; reviewer per Q12 | #1509 | done 2026-09-26: committed and pushed 43d7574d, live check passed (DEC-010, request 2, approved by button at 21:38:58Z, lead decision 19); approver rule enforced by the service since shared-signals cc74d92 (lead decisions 24 and 28) | Sage creates one work item from #sage-admin and the API shows it with revision 1; a proposal is approved by the Approve button and the audit row carries Sage's key id and Jason's Discord id separately; rev-code-02 approves on #1509 | `2026-09-20_discord-setspark-client.md` | 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 @@ -144,3 +144,4 @@ Gate F or when blocked." - 2026-09-26 — sage (lead): row 5 State: Jason approved CHAT-03. Dewey writes the brief; Filbert and Rocko review; the source author slot waits for Darkwing after A1/A2. No other row changed. - 2026-09-27 — sage (lead): rows 9 and 11 State: queue A1 committed (34a72af9) with the brief template; A2 in progress. No other row changed. - 2026-09-27 — sage (lead): row 5 State: CHAT-03 source work waits after brief r3 for a rescope against Gate E. Row 7: Sage runs the ledger each Monday. Weeks 09-13..19 and 09-20..26 came to 47.7 and 33.0 human messages per closed issue, against a target under 10. See `docs/plans/2026-09-27_goals-review.md`, lead decision 27. No other row changed. +- 2026-09-27 — sage (lead): rows 1, 6, 23, 24 and 25 done (lead decision 29). #1503, #1509 and #1511 closed with evidence comments. Gate F recorded as not passed; Gate G carries its test. No other row changed.