From 10105c37130871a47237fbb8860614fd97f7b84e Mon Sep 17 00:00:00 2001 From: wshallwshall Date: Wed, 5 Aug 2026 06:43:12 -0500 Subject: [PATCH] docs(plan): the dispatch document still said "ready to dispatch" with ten of its items shipped MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit SCHEDULABLE-BACKLOG-MULTISESSION-PLAN.md is read by sessions deciding WHAT TO BUILD, which is what makes this worse than an ordinary stale line: it does not misinform a reader about a fact, it misroutes work. The failure is already on record for this exact file -- a session dispatched from it this morning and inherited a SUPERSEDED section D RULE 1, whose ownership clause the owner had amended on 2026-08-04. Verified before writing, not transcribed: all ten claimed-shipped items (#233, #322, #324, #326, #330, #334, #335, #336, #341, #347) are closed or archived; the ledger is 108 open; 26 open items are numbered >=1000 and were filed after the plan existed. NO RUNNING COMPLETION COUNT, deliberately. Per CLAUDE.md section 11 a count embedded in prose is a liability -- it would go stale the moment the next lane lands, which is exactly how the line being fixed here got wrong. What is stated instead is the AUTHORING BASELINE as fixed history (92 open items at authoring) plus a dated snapshot of what has shipped, and a pointer to the ledger as the live record. Same reasoning as the docs/SECURITY.md PHI-route rewording in #204: stop asserting a count rather than correct one. The planning gap is recorded, not closed: 77 open items have no wave assignment and file contention has not been re-derived across the combined set, so scheduling from this document alone would both miss work and under-count collisions. Re-planning is a genuine multi-agent pass and an owner call. ⚠️ NOTE this file sits inside docs/releases/, which ADR 0160 Phase 1 proposes removing from the public repo. Fixing it anyway: Phase 1 is unratified, and a dispatch document that misroutes work does so TODAY. If Phase 1 lands, nothing is lost. --- docs/releases/SCHEDULABLE-BACKLOG-MULTISESSION-PLAN.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/releases/SCHEDULABLE-BACKLOG-MULTISESSION-PLAN.md b/docs/releases/SCHEDULABLE-BACKLOG-MULTISESSION-PLAN.md index cbb0cf9b..a90e114a 100644 --- a/docs/releases/SCHEDULABLE-BACKLOG-MULTISESSION-PLAN.md +++ b/docs/releases/SCHEDULABLE-BACKLOG-MULTISESSION-PLAN.md @@ -1,6 +1,6 @@ # MessageFoundry — Multisession Execution Plan: the schedulable backlog (2026-08-03) -**Clearing the 41 schedulable items from the 2026-08-03 re-score into 37 parallel-safe sessions across 5 waves, grouped so that no two sessions in the same wave ever co-own a file** (two deliberate exceptions — `docs/BACKLOG.md` **banner regions**, line-disjoint per banner; and the four-file share between W5's `private-paths-ignore-control` and `merge-gate-negative-controls`, line-disjoint and merge-ordered — both mitigated in §C). Method: **coordinator + one worker per session in its own worktree (`scripts/worktree/new.ps1 -Name plan-`) branched off `origin/main` @ `1cf04732`; workers build + verify + local-commit; the owner opens and approves every PR.** Every item below was file-mapped against the code at HEAD (`857a70d4`) with Glob/Grep/Read — the map corrections, missed seams and phantom references found during that pass are recorded in §D, because a *missed* shared file is the failure this plan exists to prevent. Status: **AUTHORED (2026-08-03), adversarially reviewed and revised (2026-08-03) — ready to dispatch.** What the review found and what moved is recorded in *Adversarial review* at the end; the two `docs/BACKLOG.md` surfaces it exposed are now owner-only (§C, §D RULE 1). +**Clearing the 41 schedulable items from the 2026-08-03 re-score into 37 parallel-safe sessions across 5 waves, grouped so that no two sessions in the same wave ever co-own a file** (two deliberate exceptions — `docs/BACKLOG.md` **banner regions**, line-disjoint per banner; and the four-file share between W5's `private-paths-ignore-control` and `merge-gate-negative-controls`, line-disjoint and merge-ordered — both mitigated in §C). Method: **coordinator + one worker per session in its own worktree (`scripts/worktree/new.ps1 -Name plan-`) branched off `origin/main` @ `1cf04732`; workers build + verify + local-commit; the owner opens and approves every PR.** Every item below was file-mapped against the code at HEAD (`857a70d4`) with Glob/Grep/Read — the map corrections, missed seams and phantom references found during that pass are recorded in §D, because a *missed* shared file is the failure this plan exists to prevent. Status: **AUTHORED (2026-08-03), adversarially reviewed and revised (2026-08-03). PARTIALLY DISPATCHED — this is no longer a plan to execute as written.** ⛔ **Read the ledger, not this file, for what remains.** Wave 1 has effectively completed and **ten of the 41 items have shipped** (#233, #322, #324, #326, #330, #334, #335, #336, #341, #347, verified closed 2026-08-05). Deliberately **no running completion count** beyond that dated snapshot, per CLAUDE.md §11: a count embedded in a dispatch document goes stale the moment the next lane lands, and this document is read by sessions deciding *what to build*, so a stale status does not merely misinform — **it misroutes work**. The authoring baseline is fixed history and safe to state: it was written against **92 open items**. ⚠️ The ledger is **108** today, and **26 open items numbered ≥1000 were filed after this plan existed** — several of them, including #1014 and #1025-#1027, produced *by the very lanes this plan dispatched*. **77 open items have no wave assignment and file contention has not been re-derived across the combined set**, so scheduling from this document alone will both miss work and under-count collisions. Re-planning is owed and is an owner call, not a gap to paper over here. What the review found and what moved is recorded in *Adversarial review* at the end; the two `docs/BACKLOG.md` surfaces it exposed are now owner-only (§C, §D RULE 1). > **The 52 DEMAND-GATE items are not here — by the rule, not by oversight.** They are excluded because the project refuses to build speculative connectors, codecs and parity knobs before a real feed/adopter/deployment fires their trigger, and because the demand-gate triage protocol requires a pause-explain-ask before any of them is scheduled. They are planned separately in [`DEMAND-GATE-BACKLOG-MULTISESSION-PLAN.md`](DEMAND-GATE-BACKLOG-MULTISESSION-PLAN.md); their banners and triggers live in `docs/BACKLOG.md`. **Do not pull one into a wave here.**