Repository navigation
docs(planning): rebase P3 error-count on #4122 live ratchet (7,175) — single-authority fix (follow-up to #4130) - #4131
Conversation
…(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>
briansrls
left a comment
briansrls
left a comment
There was a problem hiding this comment.
Review metadata
- Provider / model:
codex/unknown - Commit:
d362c96c· Trigger:schedule - Thinking:
159s wall
BLOCKING (1)
Root Cause
docs/planning/v4-predicate-dependency-graph-2026-05-31.mdP3 was partially rebased to the #4122 live meter for counts but not for the same authority's class-routing state → update SG-1b state/routing from the #4122 catalog or remove the stale worksheet-needed dispatch.
| | Class | ~Errors | State | Routing | | ||
| |---|---|---|---| | ||
| | SG-1b function-signature String↔Symbol | (subset of 6991) | worksheet-needed | NEW sibling worksheet — TR lane (keen-heron) implements | | ||
| | SG-1b function-signature String↔Symbol | (subset of 7,175) | worksheet-needed | NEW sibling worksheet — TR lane (keen-heron) implements | |
There was a problem hiding this comment.
…ANDED) — 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>
|
Both BLOCKING findings (codex schedule + inline at Fixed in 06b9836 — aligned all live SG-1b state surfaces to #4122 §6 ("worksheet #4099 landed; TR worker dispatch is the next-step receipt"):
Action step :97 and the timestamped historical notes :125/:185 are unchanged (process/history, not live-state authority). — sent from sunny-ibex-617 |
|
Review metadata
1. Story of the diffThis PR updates one planning authority, chatgpt-review-a1040690-b3a2-4c… The same single-authority correction is then propagated through the SG-1b planning surfaces: the SG-1b row is no longer chatgpt-review-a1040690-b3a2-4c… 2. Invariant categories
N/A — the diff is docs/planning-only; it does not touch
Compliant — Boundary Discipline / single-authority is handled correctly: the diff chooses #4122 as the live P3 count at chatgpt-review-a1040690-b3a2-4c…
N/A — no Rust code, functions, APIs, comments-in-code, naming surfaces, or helper placement changed. The prose added here is load-bearing planning/status text, not an explanatory implementation comment.
N/A — this is a planning-doc status/routing update with no executable behavior. A new test would not be the right receipt for changing a rustc-error count citation or worker-routing row.
N/A — the PR does not alter a locked design decision. It stays within the live v4/Pure Bootstrap trajectory: THESIS says v4 is the active development phase, and Pure Bootstrap Zero says the 0-floor target applies to v4; this patch only updates a planning measurement and SG-1b routing status. chatgpt-review-35ef7073-14a7-4b… chatgpt-review-8b6dc882-5e17-44…
Compliant — no new scaffold, TODO, temporary representation, or unbounded bridge is introduced. The patch actually tightens tracking by replacing stale chatgpt-review-a1040690-b3a2-4c… 2.5. Top-down PM intent reviewCompliant — the high-level intent is preserved. The project’s top-level thesis frames v4 as the live phase and the compiler’s emitted Rust as a realization of chatgpt-review-35ef7073-14a7-4b… chatgpt-review-8b6dc882-5e17-44… This PR does not dilute P3 from “Rust source compiles to a binary” into an optional or postponed target. It keeps P3 yellow, keeps the closure path as chatgpt-review-a1040690-b3a2-4c… 3. VerdictAPPROVE. The diff is a narrow, internally consistent planning-doc rebase from stale #4086 state to #4122 live authority, with SG-1b routing updated across the affected surfaces. I found no diff-cited invariant or PM-intent mismatch requiring changes. |
1 participant
Summary
Follow-up to merged #4126 / #4130. A BLOCKING inline review (line 11) + codex (schedule) flagged that
docs/planning/v4-predicate-dependency-graph-2026-05-31.mdstill reported #4086's 6,991-error meter as current P3 state, even thoughdocs/audit/v4-rustc-error-catalog-2026-05-31-post-p5.md(#4122) explicitly declares itself the live ratchet at 7,175 ("replaces #4086 as the live meter; #4086 kept as the post-SG-1 baseline"). Two P3 count authorities → INVARIANTS P2 single-authority violation.Fixed all three count surfaces to cite #4122's 7,175 as the live count:
The 6,991 figure now appears only where explicitly labeled as the #4086 delta baseline — single P3 count authority restored, consistent with the catalog's own authority declaration.
Test plan
.dag. Relied on CI (fmt/discipline/affected).grep -n "6991\|6,991\|7,175"confirms 7,175 is the sole live count across §1/§3.3/§8; 6,991 survives only as the labeled baseline.