Repository navigation
docs(close/receipt): P3-B fresh M1 rustc probe + tail reclassification post-SG-1 (8 active classes) - #4086
Merged
Conversation
…n post-SG-1 Per PM forced dispatch 2026-05-31: fresh measurement after SG-1 #3956 (78b9698) + SG-7 #4014 systemic fixes, not stale baseline reuse. Two files: 1. docs/audit/v4-rustc-error-catalog-2026-05-31.md — fresh classification 2. docs/audit/v4-rustc-error-catalog-2026-05-31.m1-probe-summary.txt — raw probe output verbatim Headline (vs 2026-05-29 pre-SG-1 baseline): - v2 diagnostics: 24 → 0 (SG-7 cleared via #4014) - rustc errors: 7951 → 6991 (-960, -12%) - E0423 (SG-1): 2978 → 0 (SG-1 closed at structural failure mode) - Dominant code: E0423 → E0308 (2862) SG-1 partial dissolution analysis (§3): 1317 of the 2862 E0308 errors carry "expected String, found Symbol" — SG-1 emitter now produces Symbol values but the generated function signatures still annotate -> String. This is a SG-1-FOLLOWON class needing function-signature realization amendment. Two NEW dominant classes surfaced from the type-mismatch tail (§4): - SG-RC-LAYERING (~700 errors): Rc/Box/raw inconsistency at function boundaries. Missing modeled fact = per-use-site ownership realization. NEW §10.0 WORKSHEET REQUIRED. - SG-COLLECTION-PROJECTION (~170 errors): FreeMonoid vs Vec<Rc<T>> at consumer boundaries. EXTEND SG-5/SG-6 or new sub-worksheet (proud-pike's call). P3-D elastic core count (§5): - CLOSED: 2 (SG-1, SG-7) - EXISTS — amendment/extension/worker-only: 5 (SG-1-FOLLOWON, SG-2, SG-8, SG-3-CASCADE, SG-5/SG-6) - NEW WORKSHEET REQUIRED: 1 (SG-RC-LAYERING) - OPTIONAL NEW vs extend: 1 (SG-COLLECTION-PROJECTION) - Bounded long tail: 1 class (~58 errors) TOTAL: 8 active receipt-producing classes. §8 explicit NOT-list: not a worker dispatch, not a P1 amendment, not a MW-D8 amendment, not a SG-1 reopening. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
changed the title
briansrls
marked this pull request as ready for review
May 31, 2026 04:38
Cursor: §1 named 17a9ac4 as HEAD/downstream of W2.3+W1.5, but git log shows 17a9ac4 is the PARENT of 78b9698 (SG-1 squash). The probe ran with 78b9698 as `git rev-parse HEAD`, not 17a9ac4. Rewrote the reference line to name 78b9698 as the actual probe SHA explicitly, with 17a9ac4 named correctly as its parent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 31, 2026
6 of 7 tasks
6 tasks
briansrls
added a commit
that referenced
this pull request
May 31, 2026
Merged
3 tasks
briansrls
added a commit
that referenced
this pull request
May 31, 2026
… snapshot + #4091 anchor (#4094) * docs(planning): v4 dep graph refresh 2026-05-31T06:30Z — post-cascade snapshot + #4091 anchor Forward-projection update to docs/planning/v4-predicate-dependency-graph-2026-05-30.md (#4058) for the 2026-05-31 wave-collapse window. Captures: P2 scope (a) PROVEN via P2-A probe (44-source compiler closure, 0 diagnostics, no bridge); P3 7951→6991 rustc with 8 receipt-producing classes routed per #4086 catalog; P5-PROVEN 2/3 gates closed (Wa-1 #4079 + P5-D tranche-2 #4089 LANDED); Wave 1 EXIT achieved via #4082. Names Path A (P5 final-flip) as shortest critical path forward; identifies P2-B bridge deletion + structural-bridge replacement as latent operator gates. References #4091 elastic CI redesign exploration at §3.5 / §6 / §8 / §9 / §10 so any structural-bridge replacement authoring aligns with the in-flight design rather than being re-shaped post-ratification. Definitions cited per src/v4/TASKS.md:806-817. Authoritative state defers to merry-badger burn-down, sharp-otter MW-D8 ledger + P1 roster + post-SG-1 catalog (#4086), and quick-tern's tranche state. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4094 tightening per operator feedback — P5 two-layer split + dispatch board + watchlist Applies operator feedback on the dep graph refresh: - §1 top table: P2 row renamed "TECHNICAL-PROVEN / AUTHORITY-BLOCKED" so the split between technical proof and authority deletion is visible at the top; P5 row reframed as two-bundle ("fixture/law" + "authority gate") to prevent "Wa-2 LANDED → P5 GREEN" misreads. - §3.2 P2: explicit Layer 1 / Layer 2 framing matching the top table; P2-B authorization listed as decision-node. - §3.3 P3 table: adds `state` column (routed / worksheet-needed / authoring / in-review / route-pending) + explanatory note on the 9-rows-for-8-classes structure cursor flagged on the prior commit. - §3.5 P5: Layer 1 fixture/law bundle 3/3 CLOSED (Wa-2 #4080 dca5ce7 LANDED while operator was writing feedback); Layer 2 authority gate OPEN; explicit anti-misread sentence. - §4 Path A: step 1 marked complete; structural-bridge step references #4091 §3. - §6.5 NEW Current Dispatch Board: priority-ordered table per operator suggestion (Wa-2 done; structural-bridge DFS unstaffed; P2-B operator-gated; SG-RC-LAYERING authoring; SG-6 #4085 in cursor RC; SG-1b routed; #4091 ratification posture). - §7: inverted "no dispatches needed" framing to name the two authoring blockers (SG-RC-LAYERING + structural-bridge replacement) as active items to monitor/escalate; operator-gated decisions surfaced. - §8: removed Wa-2 risk (closed); added explicit "first concrete CiUpsertStep replacement under #4091" framing for the structural bridge. - §10 renamed "Forecast (pre-bed read)" → "Watchlist (receipt-state, not time-based)" per operator's no-timeline discipline; consolidated PM-actionables into "decisions blocking forward progress" so it reads as receipt-state rather than time-adjacent. No code paths changed; docs-only. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
4 of 5 tasks
briansrls
added a commit
that referenced
this pull request
May 31, 2026
## Summary - Add approved §10.0 DFS worksheet for SG-RC-LAYERING (~700 E0308 Rc/Box band). - Single authority: `TargetUseSiteOwnershipRealization` in `v4.std.target_model`. - READY-FOR-WORKER-DISPATCH after merge (Modeling DFS §8 proud-pike-680). ## Test plan - [x] docs-only; CI fmt/discipline/affected/ci green on d59f8c5 - [x] dashboard reviews: claude + cursor APPROVE
briansrls
added a commit
that referenced
this pull request
May 31, 2026
…cement) — +184 delta vs #4086 Per PM dispatch 2026-05-31: re-run full-tree M1 probe + per-class delta vs PR #4086 baseline. Substrate landings since #4086: #4099 SG-1b worksheet, #4100 SG-RC worksheet, #4102 R3-internal, #4105 + #4107 substrate (compute_fabric + cache_interface), #4115 P5 bridge replacement. Headline (origin/main at d015b76): - v2 emit diagnostics: 0 (SG-7 stays closed; confirms #4115 didn't regress) - .rs files emitted: 345 (was 335; +10 substrate growth) - rustc errors: 7175 (was 6991; +184 / +2.6%) - E0423 (SG-1 closure check): 0 (stays closed across all 6 substrate PRs) Delta concentration: - E0107 (SG-2): +125 — biggest single delta; new compute_fabric/cache_interface carriers need type-arg projection; SG-2 worksheet path #3962 absorbs without shape change. - E0308 (mixed): +43 — SG-1-FOLLOWON +13 (1317 → 1330 'expected String, found Symbol') + SG-RC-LAYERING +24 on TestClaim row + minor others. - Other codes: ±0 to +6 each; long tail completely pinned. No new SG-class signatures emerged. P3-D elastic core count UNCHANGED from #4086: 8 active receipt-producing classes + 2 closed. All routing from proud-pike-680 (msg_6db2dc9e) absorbs the delta: - SG-1b worksheet #4099 absorbs the +13 SG-1-FOLLOWON. - SG-RC-LAYERING worksheet #4100 absorbs the +80 SG-RC. - SG-COLLECTION-PROJECTION (~170, no Δ) stays on SG-5/SG-6 amendment plan. - SG-2 / SG-8 / SG-3-CASCADE: existing worksheet routings. §6 includes a spot-correction of #4086's SG-3-CASCADE arithmetic (was 1191; actual sum is 761). §7 explicit reads: P5 bridge replacement (#4115) did NOT regress v2 emit; this catalog's 0-diagnostic line is the implicit non-regression receipt. §8 NOT-list: not a worker dispatch (proud-pike's routing surface); not a SG-1/SG-7 reopening; not a P5 bridge receipt (#4097 owns that); not a P1/ MW-D8 amendment. Two files: catalog + raw probe summary verbatim. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 31, 2026
…4086 (no new SG classes) (#4122) * WIP: Close/Receipt Manager — authority over close predicates, two-axis dispos * docs(close/receipt): fresh M1 rustc probe post-#4115 (P5 bridge replacement) — +184 delta vs #4086 Per PM dispatch 2026-05-31: re-run full-tree M1 probe + per-class delta vs PR #4086 baseline. Substrate landings since #4086: #4099 SG-1b worksheet, #4100 SG-RC worksheet, #4102 R3-internal, #4105 + #4107 substrate (compute_fabric + cache_interface), #4115 P5 bridge replacement. Headline (origin/main at d015b76): - v2 emit diagnostics: 0 (SG-7 stays closed; confirms #4115 didn't regress) - .rs files emitted: 345 (was 335; +10 substrate growth) - rustc errors: 7175 (was 6991; +184 / +2.6%) - E0423 (SG-1 closure check): 0 (stays closed across all 6 substrate PRs) Delta concentration: - E0107 (SG-2): +125 — biggest single delta; new compute_fabric/cache_interface carriers need type-arg projection; SG-2 worksheet path #3962 absorbs without shape change. - E0308 (mixed): +43 — SG-1-FOLLOWON +13 (1317 → 1330 'expected String, found Symbol') + SG-RC-LAYERING +24 on TestClaim row + minor others. - Other codes: ±0 to +6 each; long tail completely pinned. No new SG-class signatures emerged. P3-D elastic core count UNCHANGED from #4086: 8 active receipt-producing classes + 2 closed. All routing from proud-pike-680 (msg_6db2dc9e) absorbs the delta: - SG-1b worksheet #4099 absorbs the +13 SG-1-FOLLOWON. - SG-RC-LAYERING worksheet #4100 absorbs the +80 SG-RC. - SG-COLLECTION-PROJECTION (~170, no Δ) stays on SG-5/SG-6 amendment plan. - SG-2 / SG-8 / SG-3-CASCADE: existing worksheet routings. §6 includes a spot-correction of #4086's SG-3-CASCADE arithmetic (was 1191; actual sum is 761). §7 explicit reads: P5 bridge replacement (#4115) did NOT regress v2 emit; this catalog's 0-diagnostic line is the implicit non-regression receipt. §8 NOT-list: not a worker dispatch (proud-pike's routing surface); not a SG-1/SG-7 reopening; not a P5 bridge receipt (#4097 owns that); not a P1/ MW-D8 amendment. Two files: catalog + raw probe summary verbatim. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(close/receipt): #4122 — fix §6 arithmetic per openai-pro (long-tail 58 → 115; SG-3-CASCADE includes E0308 mop-up) openai-pro found that §6 published a contradictory long-tail count: §2 already lists E0391=29, E0599=28, other=58 separately, but §6's 'Long tail (E0391 / E0599 / + 12 other codes)' said 58 — should be 29+28+58 = 115. Separately, SG-3-CASCADE row totaled only E0277+E0573+E0560+E0369+E0121 (765), omitting the E0308 mop-up that the cascade definition is supposed to soak up by construction. Fixes: - Long tail row: 58 → 115 (E0391 + E0599 + other 12 codes, sum verified). - SG-3-CASCADE row: 765 → ~1,390 (adds unclassified-E0308 mop-up ~625 = 2905 total E0308 minus SG-1-FOLLOWON 1330 minus SG-RC-LAYERING ~780 minus SG-COLLECTION-PROJECTION ~170). - Added an explicit arithmetic-reconciliation sub-table showing each bucket × code coverage × count, summing to ~7,175 ± 1 rounding band. - Footnote on the probe-summary top-25 histogram summing to 7,174 vs §1's 7,175 — single error in a code beyond top-25 (probe script truncates display at top-25; rustc log carries full population). Catalog now publishes a single self-consistent residual count usable as the live ratchet meter. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * WIP: Close/Receipt Manager — authority over close predicates, two-axis dispos --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Merged
3 tasks done
briansrls
added a commit
that referenced
this pull request
May 31, 2026
…ksheet (per #4086) (#4126) * docs(receipt): SG-3-CASCADE cascade-only determination — no §10.0 worksheet (per #4086) SG-3-CASCADE (trait/field/binary mop-up: E0277/E0573/E0560/E0369/E0121 + residual-E0308) carries no independent missing modeled fact. Each band is the rustc-visible consequence of a fact already owned by a primary class (SG-1-FOLLOWON #4099, SG-2 #3962, SG-RC-LAYERING #4100, SG-8, SG-COLLECTION- PROJECTION). A §10.0 worksheet's DFS-path / canonical-home fields would be empty or duplicate a primary's — so no worksheet is warranted; authoring one would invent substrate work that does not exist. - New: docs/audit/v4-sg3-cascade-only-receipt-2026-05-31.md §0 determination, §2 per-band traceability (each → owning primary/worksheet), §4 falsifiable monotonic-dissolution criterion for the next post-primary probe. - Resolves predicate-dependency-graph §3.3 ambiguity: SG-3-CASCADE row was "extend existing worksheet" (unnamed); now "retired (no worksheet)" — bands fan across five primaries, no single host to extend. Docs-only; no code/substrate/.dag touched. Grounded in the committed #4122 live ratchet meter (SG-3 bands pinned, zero-Δ vs #4086); no re-probe (would regenerate identical numbers). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * WIP: SG-3-CASCADE §10.0 worksheet or cascade-only receipt — trait/field/binar * docs(receipt): fix §1 measurement-basis wording — E0560 +4 is primary-driven, not "zero Δ" (openai-pro #4126) §1 claimed the SG-3 named bands are "pinned (zero Δ)" and "the only motion is residual-E0308," contradicting the adjacent table's E0560 +4 / named-subtotal +4. Corrected: 4 of 5 named bands are zero-Δ; E0560 ticked +4, and that tick is itself primary-driven (new SG-2 field-projection sites from #4105/#4107 substrate, per §2) — not independent SG-3 growth, which strengthens the cascade-only thesis rather than weakening it. The −46 total is net of the +4 E0560 tick. No count changed; wording made internally faithful. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 31, 2026
…ss all dispatch/count surfaces (codex + inline RC on #4126) #4126 retired SG-3-CASCADE as cascade-only but only updated the §3.3 row + state legend, leaving SG-3 still represented as dispatchable elsewhere in the same planning artifact — two authorities for "is SG-3 dispatchable" (INVARIANTS P2 single-authority). Resolved across all surfaces: - §Path C (line 98): dropped SG-3 from "Workers extend ..." dispatch list; added explicit "SG-3 is NOT a dispatch target — retired cascade-only" note. - Count surfaces (§P3 row line 11, §2 #4086 entry line 21, §3.3 header line 44, §3.3 footnote line 60): "8 active receipt-producing classes routed" → "8 receipt-producing classes — 7 dispatchable + SG-3-CASCADE cascade-residual." Keeps the #4086-catalog reconciliation (still 8 receipt-producing) while removing the dispatchability contradiction. Follow-up to merged #4126; receipt unchanged. Docs-only — no code/substrate/.dag. Closes #4086 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 31, 2026
… precise count (openai-pro RC on #4130) openai-pro flagged that "7 dispatchable" introduced a new dispatch-count contradiction: of the 7 non-SG-3 classes, several are not worker-dispatchable under the table's own legend (SG-1b=worksheet-needed, SG-RC-LAYERING=authoring, SG-COLLECTION-PROJECTION=route-pending). Reworded all four count surfaces (§P3 row, §2 #4086 entry, §3.3 header, §3.3 footnote) to "7 active across routing states + SG-3-CASCADE retired cascade-residual" — the only binary fact the count asserts is retired-vs-active, which matches the per-row state column exactly. No claim that all 7 are dispatchable. Docs-only — no code/substrate/.dag. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 31, 2026
…4126 (#4130) * docs(receipt): SG-3-CASCADE cascade-only determination — no §10.0 worksheet (per #4086) SG-3-CASCADE (trait/field/binary mop-up: E0277/E0573/E0560/E0369/E0121 + residual-E0308) carries no independent missing modeled fact. Each band is the rustc-visible consequence of a fact already owned by a primary class (SG-1-FOLLOWON #4099, SG-2 #3962, SG-RC-LAYERING #4100, SG-8, SG-COLLECTION- PROJECTION). A §10.0 worksheet's DFS-path / canonical-home fields would be empty or duplicate a primary's — so no worksheet is warranted; authoring one would invent substrate work that does not exist. - New: docs/audit/v4-sg3-cascade-only-receipt-2026-05-31.md §0 determination, §2 per-band traceability (each → owning primary/worksheet), §4 falsifiable monotonic-dissolution criterion for the next post-primary probe. - Resolves predicate-dependency-graph §3.3 ambiguity: SG-3-CASCADE row was "extend existing worksheet" (unnamed); now "retired (no worksheet)" — bands fan across five primaries, no single host to extend. Docs-only; no code/substrate/.dag touched. Grounded in the committed #4122 live ratchet meter (SG-3 bands pinned, zero-Δ vs #4086); no re-probe (would regenerate identical numbers). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * WIP: SG-3-CASCADE §10.0 worksheet or cascade-only receipt — trait/field/binar * docs(receipt): fix §1 measurement-basis wording — E0560 +4 is primary-driven, not "zero Δ" (openai-pro #4126) §1 claimed the SG-3 named bands are "pinned (zero Δ)" and "the only motion is residual-E0308," contradicting the adjacent table's E0560 +4 / named-subtotal +4. Corrected: 4 of 5 named bands are zero-Δ; E0560 ticked +4, and that tick is itself primary-driven (new SG-2 field-projection sites from #4105/#4107 substrate, per §2) — not independent SG-3 growth, which strengthens the cascade-only thesis rather than weakening it. The −46 total is net of the +4 E0560 tick. No count changed; wording made internally faithful. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(planning): purge SG-3 single-authority conflict — retire it across all dispatch/count surfaces (codex + inline RC on #4126) #4126 retired SG-3-CASCADE as cascade-only but only updated the §3.3 row + state legend, leaving SG-3 still represented as dispatchable elsewhere in the same planning artifact — two authorities for "is SG-3 dispatchable" (INVARIANTS P2 single-authority). Resolved across all surfaces: - §Path C (line 98): dropped SG-3 from "Workers extend ..." dispatch list; added explicit "SG-3 is NOT a dispatch target — retired cascade-only" note. - Count surfaces (§P3 row line 11, §2 #4086 entry line 21, §3.3 header line 44, §3.3 footnote line 60): "8 active receipt-producing classes routed" → "8 receipt-producing classes — 7 dispatchable + SG-3-CASCADE cascade-residual." Keeps the #4086-catalog reconciliation (still 8 receipt-producing) while removing the dispatchability contradiction. Follow-up to merged #4126; receipt unchanged. Docs-only — no code/substrate/.dag. Closes #4086 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(planning): "7 dispatchable" → "7 active across routing states" — precise count (openai-pro RC on #4130) openai-pro flagged that "7 dispatchable" introduced a new dispatch-count contradiction: of the 7 non-SG-3 classes, several are not worker-dispatchable under the table's own legend (SG-1b=worksheet-needed, SG-RC-LAYERING=authoring, SG-COLLECTION-PROJECTION=route-pending). Reworded all four count surfaces (§P3 row, §2 #4086 entry, §3.3 header, §3.3 footnote) to "7 active across routing states + SG-3-CASCADE retired cascade-residual" — the only binary fact the count asserts is retired-vs-active, which matches the per-row state column exactly. No claim that all 7 are dispatchable. Docs-only — no code/substrate/.dag. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 31, 2026
… single-authority fix (follow-up to #4130) (#4131) * docs(planning): rebase P3 error-count surfaces on #4122 live ratchet (7,175), not stale #4086 6,991 (codex + inline RC on #4130) The predicate-graph reported #4086's 6,991-error meter as current P3 state at three surfaces (§1 P3 row :11, §3.3 SG-1b row :50, §8 watchlist :159), but #4122's post-#4115 catalog explicitly declares itself the live ratchet at 7,175 ("replaces #4086 as the live meter; #4086 kept as the post-SG-1 baseline"). That left two P3 count authorities (INVARIANTS P2). All three surfaces now cite #4122 7,175 as the live count; the 6,991 figure is retained only where explicitly labeled as the post-SG-1 delta baseline. Single P3 count authority restored. Follow-up to merged #4126/#4130. Docs-only — no code/substrate/.dag. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs(planning): align SG-1b routing state to #4122 (worksheet #4099 LANDED) — single-authority (codex + inline RC on #4131) #4131 rebased the SG-1b row's count to #4122's 7,175 meter but left its routing STATE stale ("worksheet-needed / NEW sibling worksheet"), while the same #4122 catalog (§6) and merged #4099 say the SG-1b worksheet has LANDED and only TR-lane worker dispatch remains — two authorities for SG-1b state. Aligned all live SG-1b state surfaces to #4122 §6 ("worksheet #4099 landed; TR worker dispatch is next-step receipt"): §3.3 row :50 (state worksheet-needed → routed), §5 owner table :113, §6 sequence row :138. Dropped now-unoccupied `worksheet-needed` from the §3.3 footnote's active-states enumeration (kept in the legend definitions). Action step :97 and timestamped historical notes :125/:185 unchanged. Docs-only — no code/substrate/.dag. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Merged
6 tasks
briansrls
added a commit
that referenced
this pull request
May 31, 2026
…E0432/E0433 per #4086) (#4127) * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * WIP: SG-8 §10.0 worksheet — module graph + carrier re-exports (~796 E0425/E04 * docs(sg-8): align worksheet dispatch with docs-only #4127 Drop co-delivery claims; split worksheet PR from implementation worker per SG-RC #4100 pattern so merge gate and falsification probes match the actual diff. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(sg-8): single authority for post-merge implementation gate Replace "merge unblocks implementation worker" with dispatch-binding language and explicit §8-before-merge + §8-before-implementation ordering so the status table cannot contradict the OPEN §8 checklist. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(sg-8): fix 03_name_resolve DFS path to compiler/ Align worksheet authority map with landed src/v4/compiler/03_name_resolve.dag (TASKS.md T-28-B); src/v4/03_name_resolve.dag does not exist on main. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(sg-8): anchor worksheet to committed main authorities Cite catalog (#4086) and ladder (#4120) with main URLs; drop volatile probe counts from worksheet authority (implementation PR evidence). Co-authored-by: Cursor <cursoragent@cursor.com> * docs(sg-8): require executable F4 falsification receipt Replace ambiguous "v4 manual claim" with hermetic TestClaim or src/v2/tests fixture plus rg receipt per TESTING.md discipline. Co-authored-by: Cursor <cursoragent@cursor.com> * docs(sg-8): tighten F2 receipt to wrong-module pattern Match F2 grep to forbid CarrierKind via v4_compiler_target_carriers only, not blanket absence of CarrierKind (pipeline import may be correct). Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
briansrls
added a commit
that referenced
this pull request
Jun 1, 2026
…1.8 self-compile runway, §8.5 resolutions) Per operator 2026-06-01T01 approval-with-edits: 1. **Class B wording tightened** (§11.7.2): "required if already modeled" → "Only if part of current §11.7.1 safety floor OR selected by trusted affected-set/testgen". Prevents required surface from silently growing back. 2. **Explicit Rust emit pick** (§11.7.1 gate #3): chose `M1 v4 full-tree rust emit probe` (NOT both M1 + T-22 corpus rust). Rationale: M1 drives the residual-count catalogs (#4086/#4122/#4140) that inform dispatch; T-22 corpus rust duplicates same closure compile with no unique signal → demoted to Class C scheduled. 3. **§11.8 NEW: Language self-compile runway** with explicit rungs L0-L4 per language: - L0 leaf-model verification - L1 compiler-subset emit - L2 compiler-subset execution - L3 self-output fixed point - L4 full self-compile Per-language manager scope tabled: Rust (critical path, L1 in progress); Go (release-minimum, L0; clean external verifier advantage); Python (release-minimum, L0 complete via #4117); TypeScript (alpha/preview); C++ (capacity-permitting matrix only). Mechanical rules preserved (worksheet single-authority-fact gate, shared facts through Modeling DFS Arbiter). 4. **§8.5 operator decisions resolved** per operator sign-off: - P5 runtime gate: option (ii) authorized as WORKSHEET (not impl) in parallel with P3 - SG-8 / Modeling DFS succession: dedicated manager to spawn; PM does NOT act as DFS; keen-heron stays TR - TypeScript: authorized as alpha/preview language lane - Go/Python: authorized for self-compile runway per §11.8 - CI Coverage Bankruptcy Wave 1: APPROVED; spawn CI Manager - stern-lynx closeout (c): still pending (low-priority; role reconstituting anyway) INVARIANTS P2 single-authority preserved throughout: §8.5 canonical for sign-off state; §11.7 + §11.8 reference operator framing without claiming alternate authority. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
Jun 1, 2026
* docs(planning): v4 dep graph Jun 1 release-day EOD — post-cascade snapshot Successor to docs/planning/v4-predicate-dependency-graph-2026-05-31.md (#4096) capturing the 2026-05-31 P3+P5 cascade end-of-day state on Jun 1 release day. Summary of today's predicate state movement: - P5 dep-graph-framing: Layer 1 + Layer 2 BOTH CLOSED via #4115 structural-bridge implementation (positive-Y CiUpsertStep replaces shell, bridge deleted); strict TASKS.md reading still has runtime-gate upward debt at adhoc-f8699326-d69 (operator decision pending). - P3: 8 of 9 routed classes closed/retired today (SG-1/7/5/6/1b/2/RC-LAYERING/SG-3-cascade-retired) + SG-8 worksheet on main (impl gated on §8). Residual rustc count stale at 7175 (#4122 catalog); fresh probe needed. - P2: scope (a) PROVEN; bridge deletion 14-day window starts today via #4097 M2 probe. Operator decision OR window completion gates full P2 GREEN. - T-38-PR2 verdict-surface migration LANDED #4120. Org change: proud-pike-680 archived mid-day; Modeling DFS lane consolidated under keen-heron-687 de facto. §8 sign-off authority for SG-8 impl needs operator routing. Tree health: 0 active subtree work at 00:30Z 2026-06-01. All 5 overnight PRs merged; #4112 operator-landed. Managers idle. Operator decisions pending (block forward progress): - P5 runtime gate (i) M1 cargo-clean subset vs (ii) bootstrap-evaluator corpus path (load-bearing per SELF_HOSTING) - P2-B bridge deletion authorization (or 14-day window wait) - SG-8 §8 sign-off authority routing post-proud-pike-archival No code paths changed; docs-only. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex RC fix — P5 canonical predicate single-authority Addresses codex REQUEST_CHANGES on #4137: §10 "P5 fully GREEN today" framing violated single-authority discipline against canonical TASKS.md predicate "TestClaim suite passes". Same snapshot at §3.5 / line 102 correctly named the runtime-execution gate as still open (adhoc-f8699326-d69), creating parallel dep-graph definition risk where a worker could treat P5 as done. Fix: §10 rewritten to lead with "P5 (canonical 'TestClaim suite passes' per TASKS.md): NOT fully GREEN today" — Layer 1+2 closed but runtime-execution gate remains open; explicit "do NOT treat as done" anti-misread phrasing. INVARIANTS P2/P3 single-authority + fail-closed documentation discipline preserved by aligning §10 with §3.5. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex RC fix 2 — eliminate "dep-graph framing P5 GREEN" alternate-authority phrasing Addresses codex second REQUEST_CHANGES on #4137: §8:156 "per dep-graph framing, P5 is GREEN (both layers closed)" was a second P5 status authority even in a risk/honesty section, despite §10 anchoring canonical TASKS.md status. A worker could read §8 as permission to close P5 before runtime-execution gate. Fix: §8 rewritten to lead with "P5 single authority: P5 is GREEN only when the canonical TASKS.md predicate 'TestClaim suite passes' is satisfied." Today's Layer 1+2 closures explicitly framed as "partial progress toward P5, not an alternate definition of GREEN." Adds explicit "Do not treat partial layer closure as P5 GREEN" anti-misread. INVARIANTS P2 single-authority discipline fully aligned: only the canonical predicate text in TASKS.md:816 defines what GREEN means for P5. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 expansion — operator sign-offs queue + remaining-7000 protocol + TS parallel ops Per operator request "tell me anything else that needs sign off up front + get this entire sheet fresh/ready": Added three new sections: - §8.5 Operator sign-offs queue (consolidated table; tracks all PM-waits-on-operator items including P2-B AUTHORIZED + fresh M1 probe AUTHORIZED that just dispatched) - §8.6 Remaining P3 residual cascade — explicit worksheet protocol clarity (probe → §10.0 → impl → repeat); names keen-heron as de facto manager pending routing decision - §8.7 TypeScript / cross-target parallel opportunities (TR-lane work feasible parallel to Rust residual; per Wave F F3 TS is v4-alpha-only; mirrors today's Python widening pattern) Also updated §1 P2 row: TECHNICAL-PROVEN / AUTHORITY-BLOCKED → TECHNICAL-PROVEN; DELETION IN FLIGHT (operator authorized 00:28Z; work-item adhoc-4cad7e9b-558 spawned to skip 14-day window). Pending operator decisions still in queue (per §8.5): - P5 runtime gate (i) M1 cargo-clean subset vs (ii) bootstrap-evaluator corpus path - SG-8 §8 sign-off authority routing - Modeling DFS Manager succession plan - TypeScript work plan authorization - stern-lynx closeout cond (c) Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex RC #3 + cursor RC fix — reconcile P2-B authorization state + correct ci.yml line citation Addresses combined codex (RC #3) and cursor (RC #1 on this PR) findings: 1. **P2-B authorization desync** (codex + cursor): §3.2, §4 Path B, §6, §6.5, §7, §10 all framed P2-B as pending operator decision, while §8.5 + §1 P2 row recorded the 00:28Z AUTHORIZED state. One snapshot, two authorities. Fix: every blocker/dispatch-board/watchlist mention of P2-B updated to "AUTHORIZED + in flight" with work-item URL adhoc-4cad7e9b-558. §8.5 is the single source of truth for sign-off state. 2. **ci.yml line citation wrong** (cursor): bridge step is at ci.yml:401-410 (the `v2 → v4 bootstrap resolve-posture gate` step); lines 378-385 are the unrelated phase1/nat_semiring gate (carried over from #4096 predecessor without verification). Fixed in §3.2. 3. **Fresh M1 probe also AUTHORIZED + in flight** (carried desync): §10 listed fresh M1 probe under "PM dispatches available pending operator authorization"; updated to reflect 00:28Z authorization + work-item adhoc-7b46e080-3cd in flight. INVARIANTS P2 (single authority) preserved: §8.5 is canonical for sign-off state; every other section now references or aligns with it. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex RC #4 + operator-blocking reviews fix — full single-authority cleanup Addresses three operator-blocking inline reviews + codex RC #4: 1. **TASKS.md line-number drift risk**: switched all `src/v4/TASKS.md:806-817` and `:816` citations to stable section anchor `src/v4/TASKS.md` "Definition of v4-done" (operator/codex flagged line-number cite as drift risk; using header anchor is robust against future renumbering). Note: current file content confirms predicates ARE at :813-817 under :805 header; operator's :572-584 suggestion doesn't match current main but the anchor switch sidesteps the issue entirely. 2. **ci.yml line-number drift risk**: switched all `.github/workflows/ci.yml:401-410` citations to step name `v2 → v4 bootstrap resolve-posture gate (CI emit-wall bridge)` (operator/cursor flagged 401-410 as not precisely the bridge step; step-name cite is robust + names exactly what gets deleted). 3. **Fresh M1 probe desync** (operator blocking on line 89): §6 listed as pending blocker owned by sharp-otter while §8.5 marked AUTHORIZED + in flight. §6 and §6.5 updated to reflect AUTHORIZED + work-item adhoc-7b46e080-3cd in flight (sleek-heron-13 spawned; PR #4140 7,724 errors +549 vs #4122). 4. **§7 PM-actionable contradiction** (codex RC #4): "No worker implementation dispatches blocked" contradicted SG-8 needing §8 routing. §7 rewritten to explicitly enumerate blocked items (SG-8, P5 runtime) referencing §6.5 dispatch board + §8.5 operator decisions queue. INVARIANTS P2 single-authority: §8.5 is the canonical sign-off state; §6 + §6.5 + §7 + §10 now all reference §8.5 rather than maintaining parallel state. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex/cursor RC #5+#6 fix — reconcile probe-result state + Path A no-overclaim Addresses two more blocking reviews: 1. **Probe-result state desync** (codex + cursor RC): §1 + §3.3 + §8 still framed "fresh probe needed" while §6.5/§8.5 recorded 7,724 result. Reconciled: §1 P3 row + §3.3 residual paragraph + §8 honesty bullet all now lead with the 7,724 result (sleek-heron-13 PR #4140) and note substrate-absorbed pattern; §8 final bullet clarifies per-class delta still pending review. 2. **§4 Path A overclaim** (codex RC): "Either flips strict P5 GREEN" was wrong — neither (i) nor (ii) flips P5 GREEN by routing decision alone. Rewrote Path A to make explicit: P5 GREEN requires TestClaim suite passes bullet satisfied by actual suite execution receipt; choice (i)/(ii) authorization unblocks dispatch toward that receipt. INVARIANTS P2 single-authority preserved: §8.5/§6.5 are canonical for state; every other section now references their 7,724 reading rather than maintaining parallel stale 7,175 references. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 §11 — proposed next-iteration management structure (operator-requested) Adds §11 covering operator-requested management redesign for post-Jun-1 next-iteration. Structural principle: fan out RCA + worksheet authoring; centralize single-authority approval per INVARIANTS P2. Roles defined (with scope / deliverable-by-end-of-tenure / exit criteria for each): - Modeling DFS Arbiter (fresh-spawn, NOT PM; single-authority gate) - 5 per-language RCA Managers: Rust, Python, Go, TypeScript (alpha/preview), C++ (later) - 6 shared substrate managers: ModuleGraph, TargetTypeExpression, TargetAtom, Collection/Algebra, Runtime/TestClaim, CI CI Manager scope captures post-cascade CI state: - substrate exists (ci.dag CiPipeline/CiJob/CiGate/CiUpsertStep) but runtime still YAML+shell - four-compile-redundancy in ci_v4 still unresolved per #4091 §1.2 - affected-set testing/building NOT yet via evaluator; weeks-to-months - deliverable: collapse 4 compiles to 1; YAML→CiUpsertStep; affected-set via evaluator; shell retirement; runtime ≤10min Coordination protocol + mechanical rule (no impl without §10.0 worksheet) preserved. PM scope under new structure: routing + escalation only; explicit DO NOT list (act as Arbiter, approve substrate, spawn impl without worksheet). Pending operator re-review per their message; if ratified, §11.4 lists immediate next-wave dispatch. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 §11.6 — concrete CI migration inventory per operator request Adds §11.6 with verified counts as of 2026-06-01T01:00Z post-#4139 main: Headline: - ci.yml: 73 YAML steps across 7 jobs - ci.dag: 47 modeled CiUpsertStep rows on main (W2.3 Buckets A+B+C+E + bankruptcy Tier-0 + #4115 P5) - scripts/: ~30 shell scripts (~22 production candidates for retirement; ~8 dev/test infra stays) Migration scope categorized (A-E): - A: Already modeled + receipt-parity (47 rows) - B: Pending modeling (gate/check steps, ~10): SG-0 net-shrink, R4-carve, fabrication sentinel, T-19 testgen, release-doc authority, install.sh pinned, manager-brief, test-timeout, rust toolchain, Gate #103 - C: Pending modeling (leaf-model boundaries, ~6): Phase 1 R1/R2a/R2b/R3-external for rust + python - D: Pending modeling (toolchain/cache, ~5): per-job duplication of isolation + rustup pin - E: Already retired (testclaim-corpus-gate.sh #4115, resolve-posture-gate.sh #4139, bankruptcy #4101) Shell retirement list enumerated (22 production scripts). Structural redundancies per #4091 §1.2: four-compile in ci_v4 (~14m savings), per-job HOME isolation (4× duplication), cache cleanup. Runtime authority migration coupled with P5 runtime gate (adhoc-f8699326-d69) — both are same SELF_HOSTING substrate work. Affected-set testing/building via evaluator: modeled substrate exists (ChangeSet → AffectedSet → AffectedSetProduced in src/v4/std/change.dag); runtime gap is same as P5 runtime gate. CI Manager near-term wins (executable without operator decision): migrate B+C, collapse D duplication, collapse four-compile redundancy. Long-pole: runtime authority migration (gated on P5 runtime decision). Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex RC fix — P2-B state DELIVERED (#4139 merged 00:50Z) Addresses codex RC: §11.6 line 324 said #4139 deleted the bridge script while §1/§3.2/§4/§6/§6.5/§7/§10 said "in flight" — inconsistent live state. Verified via git ls-tree origin/main: #4139 MERGED 2026-06-01T00:50:17Z (squash 12d1aa6); script + ci.yml step actually gone from main. All P2-B state references updated: - §1 P2 row: "TECHNICAL-PROVEN; DELETION IN FLIGHT" → "GREEN" - §3.2 section: header + body reflect #4139 MERGED with squash SHA - §4 Path B: "IN FLIGHT" → "DONE" - §6 blocker: "RESOLVED + DELIVERED" - §6.5 dispatch board priority 2: state "DONE 2026-06-01T00:50Z" - §7 PM dispatches: "DELIVERED via #4139 MERGED 00:50Z" - §8.5 sign-off queue: "DONE" with merge SHA - §10 watchlist: "P2: fully GREEN" INVARIANTS P2 single-authority restored: one accurate live-state authority across the doc; #4139 MERGED is the canonical fact. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 §11.7 — CI Coverage Bankruptcy: bare-minimum first + cut list + reframed CI Manager charter Per operator directive 2026-06-01T01: aggressive CI cut now, bare minimum survival floor, reframe CI Manager to "make affected-set + testgen the safety net" not "migrate every shell step". Restructured §11.7: §11.7.1 BARE MINIMUM SAFETY NET (what stays) — 5 required gates explicit: 1. fmt --check 2. bootstrap minimal viability (shell exception short-term) 3. ONE Rust emit/probe path (not four — collapse four-compile redundancy) 4. ci.dag structural receipt + CiUpsertStep schema checks 5. no-new-shell ratchet Target: cold PR ~5-10min (vs current 30-75min) §11.7.2 Four CI classes (A/B/C/D) for categorization. §11.7.3 AGGRESSIVE CUT LIST: now includes operator directive to PERMANENTLY delete all v3 integration tests (ci_integration Tier-0 I3 determinism_test, full v3 job: cargo test --lib --bins, clippy --features bootstrap-regen-fresh, etc) — DELETE not demote per project_spirit + #4101 bankruptcy. §11.7.4-6 unchanged (four-wave plan, cut rule, honesty ledger). §11.7.7 CI Manager REFRAMED charter: - Old: "migrate every shell step to CiUpsertStep" - New: "get the bare minimum safety net working in CI using affected-set + testgen" - Work lane prioritizes: bankruptcy cut → four-compile collapse → affected-set + testgen shadow → first active modeled skip → affected-set as Class A authority - Shell-to-CiUpsertStep migration becomes BACKGROUND/INCREMENTAL in service of affected-set needs, not a separate front - Explicit anti-patterns: don't migrate for completeness; don't maintain retired-lane ratchets; don't trust affected-set exclusively before Wave 3 proves it Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 — operator sign-off edits (Class B, M1 pick, §11.8 self-compile runway, §8.5 resolutions) Per operator 2026-06-01T01 approval-with-edits: 1. **Class B wording tightened** (§11.7.2): "required if already modeled" → "Only if part of current §11.7.1 safety floor OR selected by trusted affected-set/testgen". Prevents required surface from silently growing back. 2. **Explicit Rust emit pick** (§11.7.1 gate #3): chose `M1 v4 full-tree rust emit probe` (NOT both M1 + T-22 corpus rust). Rationale: M1 drives the residual-count catalogs (#4086/#4122/#4140) that inform dispatch; T-22 corpus rust duplicates same closure compile with no unique signal → demoted to Class C scheduled. 3. **§11.8 NEW: Language self-compile runway** with explicit rungs L0-L4 per language: - L0 leaf-model verification - L1 compiler-subset emit - L2 compiler-subset execution - L3 self-output fixed point - L4 full self-compile Per-language manager scope tabled: Rust (critical path, L1 in progress); Go (release-minimum, L0; clean external verifier advantage); Python (release-minimum, L0 complete via #4117); TypeScript (alpha/preview); C++ (capacity-permitting matrix only). Mechanical rules preserved (worksheet single-authority-fact gate, shared facts through Modeling DFS Arbiter). 4. **§8.5 operator decisions resolved** per operator sign-off: - P5 runtime gate: option (ii) authorized as WORKSHEET (not impl) in parallel with P3 - SG-8 / Modeling DFS succession: dedicated manager to spawn; PM does NOT act as DFS; keen-heron stays TR - TypeScript: authorized as alpha/preview language lane - Go/Python: authorized for self-compile runway per §11.8 - CI Coverage Bankruptcy Wave 1: APPROVED; spawn CI Manager - stern-lynx closeout (c): still pending (low-priority; role reconstituting anyway) INVARIANTS P2 single-authority preserved throughout: §8.5 canonical for sign-off state; §11.7 + §11.8 reference operator framing without claiming alternate authority. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 cursor RC fix — propagate §8.5 resolutions through §1/§4/§6/§6.5/§7/§10 Addresses cursor RC: §8.5 marked operator decisions #3-#8 RESOLVED at 01Z but §1/§4/§6/§6.5/§7/§10 still listed them as pending blockers / operator decisions. Single-authority violation per INVARIANTS P2. Reconciliation: - §1 P5 row: removed "operator decision pending"; added "option (ii) authorized as WORKSHEET per §8.5 #3" - §4 Path A: removed "operator decision required"; replaced with worksheet-authorized framing - §6 blockers table: P5 runtime gate + SG-8 §8 sign-off both struck-through with RESOLVED references - §6.5 dispatch board: P5 runtime gate + SG-8 §8 rows reframed to "RESOLVED; <next-step>" with Modeling DFS Arbiter as owner - §7 PM-actionable: SG-8 + P5 impl rephrased from "BLOCKED on operator decision" to "pending Modeling DFS Arbiter spawn + worksheet authoring" (sequenced post-resolution) - §10 watchlist: all 5 RESOLVED decisions struck-through with resolution summaries; added "Next dispatch actions" subsection listing the spawn-to-do queue (Modeling DFS Arbiter, CI Manager, language RCA Managers, P5 worksheet) INVARIANTS P2 single-authority restored: §8.5 is canonical; every other section now defers to §8.5 numbering with resolution status. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 operator-blocking RC fix — gate-vs-decision distinction + P2-GREEN propagation Addresses 3 operator-blocking inline reviews at lines 85/86/87: 1. **P5 runtime gate vs P5 routing DECISION** (operator line 86): §8.5 #3 conflated "routing decision resolved" with "gate resolved". The OPERATOR CHOICE between (i) and (ii) is resolved; the GATE itself (runtime executes + suite passes) is STILL OPEN. Reconciled: - §8.5 #3: "DECISION RESOLVED" not "RESOLVED"; explicit "gate itself remains OPEN" - §6 blockers: "(still OPEN)" qualifier on P5 runtime gate row - §6.5 dispatch board priority 1: "(gate OPEN; routing RESOLVED)" + exit-receipt sequence extended through ship+execute - §3.5 P5 + §10 + §1 P5 row unchanged (correctly already showed gate OPEN) 2. **SG-8 §8 sign-off authority routing vs §8 ratification** (operator line 87): §8.5 #4 conflated "authority routing resolved" with "§8 ratification resolved". The AUTHORITY question (who reviews) is resolved; the actual §8 RATIFICATION on SG-8 worksheet is a separate step that gates impl dispatch. Reconciled: - §8.5 #4: "ROUTING RESOLVED" with note that §8 ratification is separate post-Arbiter-spawn step - §6 blockers: "(authority routing resolved; ratification still open)" qualifier 3. **P2 stale-reference propagation** (operator line 85 related): §1 P4 row + §3.4 still said "hard-gated on P2 full PROVEN + P3 binary builds" — P2 is fully GREEN per #4139. Fixed both to reference only P3 binary builds as remaining gate. INVARIANTS P2 single-authority preserved: each predicate state distinguishes routing-decision-resolved vs gate-closure-pending; no parallel authorities for the same predicate state. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex RC fix — §3.5 P5 line 98 stale "decision pending" → reflect §8.5 #3 resolution Addresses codex RC at line 98: §3.5 still said "Operator decision pending" for (i) vs (ii) routing while §8.5 #3 records RESOLVED at 01Z with option (ii) WORKSHEET authorized. Single-authority violation per INVARIANTS P2. Fixed: §3.5 P5 paragraph now lead-frames the routing decision as RESOLVED (option (ii) WORKSHEET, per §8.5 #3) while preserving the canonical gate-OPEN reading (runtime ships + suite executes + passes). (i) noted as patient-wait alternative path downstream of P3 cascade. INVARIANTS P2 single-authority preserved: §8.5 canonical for sign-off state; §3.5 references it consistently. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * docs(planning): #4137 codex RC fix — §6.5 priority 3 SG-8 routing-vs-ratification rename Addresses codex finding on §6.5 priority 3: state column said "RESOLVED" but exit receipt still required "§8 ratification → SG-8 impl worker dispatchable", creating ambiguous live-state. Fix: rename title from "SG-8 §8 sign-off authority" to "SG-8 §8 sign-off **routing** (NOT the ratification itself)"; state column now explicit about what's resolved (routing) vs pending (ratification). Sequence noted: Arbiter spawn → §8 ratification → SG-8 impl. This was the codex review on sha 4242a83 (3 commits behind HEAD); line 98 fix at 21b0b35 + gate-vs-decision distinction at f246e9d also already address the broader pattern. This rename is the final piece on the §6.5 row itself. INVARIANTS P2 single-authority preserved: state column reflects only what's actually resolved (routing); exit-receipt column names the remaining dispatchability gate. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Per PM forced-dispatch 2026-05-31 ("fresh measurement after systemic fix, not stale baseline reuse"). Fresh M1 rustc probe on
origin/mainpost-SG-1 (78b9698asquash of #3956) + post-SG-7 (#4014 / #4050), reclassified by missing modeled fact.Two files under
docs/audit/:v4-rustc-error-catalog-2026-05-31.md— fresh classification (replaces the 2026-05-29 catalog as the live ratchet meter; 2026-05-29 stays as pre-SG-1 baseline).v4-rustc-error-catalog-2026-05-31.m1-probe-summary.txt— raw probe output verbatim.Headline (post-SG-1 vs 2026-05-29 baseline):
error[E####]linesE0423(SG-1 signature)E0308(2862)E0423(2978)SG-1 partial dissolution (§3): 1,317 of the 2,862 E0308 errors carry
expected String, found Symbol— SG-1 emits Symbol values but the generated function signatures still annotate-> String. SG-1-FOLLOWON (return-type realization amendment).Two NEW dominant classes (§4):
FreeMonoid<T>not lowered toVec<Rc<T>>at consumer sites. EXTEND SG-5/SG-6 or new sub-worksheet (proud-pike-680's call).§5 Class routing table — P3-D elastic-core count:
§8 NOT-list: not a worker dispatch (proud-pike-680 ratifies worksheets); not a P1 amendment (TASKS.md unaffected); not a MW-D8 amendment (gate-conditions independent of rustc population); not a SG-1 reopening.
Test plan
.dagtouched — docs-only classification + raw probe receipt.scripts/v4-m1-rust-emit-probe.shrun end-to-end).String/Symbolcascade) verified via the §7grep / sort | uniq -cpipeline againstrustc.log.