Repository navigation
Conversation
Co-authored-by: Brian Searls <briansrls@users.noreply.github.com>
|
Cursor Agent can help with this pull request. Just |
This was referenced May 8, 2026
briansrls
added a commit
that referenced
this pull request
May 8, 2026
…92→93 hygiene Per cursor/composer-2 review on PR #2217: Finding 1 (single-authority): §1.5 paragraph claimed "96 gate IDs enumerated per r3-structure.md §Acceptance" but the structure doc didn't actually list the new gate. Adding value_body_substrate_mirror_isomorphism_executable to §"Acceptance" T-Verification-L4-L7-Direct lane restores single-authority discipline (P2). Finding 2 (internal consistency): §1.6 line 95 was updated to "96 enumerated; 93 load-bearing" but line 98 still said "92 R3-load-bearing gates green". Aligning the second sentence to 93 so closure arithmetic reads one way throughout §1.6. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 8, 2026
…1) (#2218) * WIP: Verification V7 ValueBody isomorphism gate (HOLD pending Brian sanction) * docs(r3): cite canonical §1.8 #96 gate in ValueBody variant inventory PM deep-wolf-155 #846 assigned §1.8 #96 to value_body_substrate_mirror_isomorphism_executable (PR #2217 in flight). Replaces working-gate-name framing with canonical # citation per Mgr direction at #2075 issuecomment-4404078831. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 8, 2026
…somorphism Per BLOCKING inline finding from openai-pro at PR #2217 docs/r3-program-plan.md:295: "new ValueBody gate leaves the conformance mechanism to Mgr discretion instead of binding it to the generated DagShapeReport/BinaryDimensionReportEquals or generation path tracked for this mirror drift, so a hand-maintained check could satisfy the gate while preserving the P2/P5 parallel-authority risk." Finding valid. Original row's "mechanism Mgr-discretion" framing left room for a hand-maintained TestClaim enumerating variants — itself a parallel authority, defeating the gate's purpose. Brief at docs/briefs/r3-v-valuebody-substrate-mirror-isomorphism-v1-worker.md already cites feedback_isomorphism_or_generation_for_mirrors + INVARIANTS §P1 (generation-or-isomorphism, NOT hand-maintained); §1.8 row needs to reflect this constraint structurally so the gate auditor can reject hand-maintained satisfaction. Edits to both r3-program-plan.md §1.8 #96 row + r3-structure.md §Acceptance #96 entry: - Explicit gate-satisfaction discipline citation (feedback_isomorphism_or_generation_for_mirrors + P1) - Hand-maintained TestClaim explicitly marked structurally inadmissible - 4 bounded mechanisms reframed as "structural-derivation-from-single-authority" (enum walk over canonical type def; structural check / TestClaim over canonical shape projection; build.rs reading canonical generation source) — all derive, none hand-maintain - Cross-link to existing Lens<DagShapeReport> + BinaryDimensionReportEquals predicates (gate #14 / rust_dag_isomorphism_executable) as the structural-isomorphism path Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 8, 2026
briansrls
added a commit
that referenced
this pull request
May 8, 2026
…96 gate Per openai-pro APPROVE_WITH_COMMENTS finding on PR #2217 sha d59403e: "INVARIANTS §P1 (single-authority)" mislabels — single-authority is P2 (Boundary Discipline), not P1 (Modeling Faithfulness). Reviewer's "P2 or split as P1+P2" suggestion: split is more complete since both axes apply. Verified against INVARIANTS.md: - P1 Modeling Faithfulness: every construct grounds in external fact or structural-derivation from one — applies to "generation-or-isomorphism" (mirror grounds in canonical source) - P2 Boundary Discipline: every fact lives in exactly one authoritative place — applies to "no hand-maintained dual taxonomies" (parallel-authority concern) Both r3-program-plan.md §1.8 #96 row + r3-structure.md §Acceptance #96 entry updated to cite P1 (grounding) for the generation-or-isomorphism axis AND P2 (single-authority) for the no-parallel-authority axis. Future reviewers now apply the right rubric to each constraint. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 8, 2026
…nonical-pointer Per openai-pro REQUEST_CHANGES finding on PR #2217 sha 32ebdfd: > The PR currently duplicates the gate body in both r3-program-plan.md and > r3-structure.md. For a substrate-shape close gate, that is a P2 single-authority > issue and should be collapsed before merge. Self-reflexive failure: the new gate text forbids hand-maintained dual taxonomies (P1 grounding + P2 single-authority), but I added the same gate body as hand-maintained dual content in two docs. Per r3-program-plan.md:302 existing convention: "Authoritative source per gate: r3-structure.md §Acceptance carries the Pass-condition body for each row above. This ledger is the consolidated index — body lives in canonical archive." Other §1.8 rows already follow this (e.g., #1 tier3_termination_mirror_dissolved notes column = "r3-structure.md §Acceptance"). My #96 row violated the convention by including the full body inline. Fix: collapse §1.8 #96 row notes to a terse canonical-source pointer (r3-structure.md §Acceptance T-Verification-L4-L7-Direct + brief reference). Canonical Pass-condition body stays in r3-structure.md §Acceptance as authority. Single-authority restored. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 8, 2026
… binding + manifest refresh Main has been red across 4 commits (d4b37da/dfb168c2/fd00e090/3ae9d51f) since PR #2194 (T-CostLens-Composition) merged at 06:33Z. PR #2194 added the 7th SubstrateAccessorBinding (declaration_by_name_binding_rust at src/v3/spec/rust.dag:1704) plus expanded substrate.dag/rust.dag content, but did not bundle: 1. The corresponding bump in m1_substrate_test::substrate_accessor_rust_binding_invariants (assertion still expected 6 bindings; now 7) 2. The parse_corpus_manifest.txt refresh for the new rust.dag (170 items, 1357477 debug_bytes, fnv1a64 9bfd82407452889b) and substrate.dag (65 items, 141515 debug_bytes, fnv1a64 1b2a4d2f9c834025) item/byte/hash deltas This commit applies both: - Updates assertion 6 → 7 + adds declaration_by_name to the expected accessor list - Updates manifest with the values observed in CI failure logs at d59403e The new declaration_by_name accessor + binding are correctly authored at src/v3/spec/rust.dag:1700-1708 (rust_declaration_by_name_accessor + declaration_by_name_binding_rust); they integrate cleanly with the existing 6 bindings under the universe-coverage check that follows the assertion. Bundled into PR #2217 per operator ask: this PR is now docs (gate #96) + fix-forward for main-red ratchet drift, since the docs-only branch was being gated on main going green and standing-authority discipline allows fix-forward on inherited regressions when within tactical scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 8, 2026
…cutable (#2217) * docs(r3): §1.8 gate #96 — value_body_substrate_mirror_isomorphism_executable Authored per Verification Mgr ask at gunbc#2075 c#4403991524 + Director ratification at gunbc#828 c#4403972737 + Brian sanction at gunbc#846 (IN-R3 confirmed; no R4 carves directive). Substantive content lives at docs/briefs/r3-v-valuebody-substrate-mirror-isomorphism-v1-worker.md (brief pre-authored 2026-05-07; ratified 2026-05-08). Edits: - §1.5 closure-ledger total: 95 → 96 gates; 92 → 93 R3 thesis-load-bearing - §1.5 lane breakdown: T-V-L4-L7-Direct 6 → 7 (+ ValueBody isomorphism); 79 → 80 lane gates - §1.8 row #96 added: value_body_substrate_mirror_isomorphism_executable - Lane: T-V-L4-L7-Direct (Verification cross-program with Substrate) - Type: substrate-shape (Pattern-A-adjacent mirror parity) - Co-ownership: Substrate (carrier/mirror authority) + Verification (harness/conformance test) - CI mechanism: build-time enum walk / boot-time structural check / .dag TestClaim / build.rs (Mgr-discretion); fail-closed on variant/shape skew - §10.3 Q-ValueBody-Isomorphism row: OPEN → RATIFIED 2026-05-08 - Updated 4 other 95→96 references (DECLARE count, single canonical view, Q1 ratification, two-Pass-surfaces) Carved gates (#81/#82/#95) stay carved per prior structural ratifications (forward-looking Brian directive "no R4 carves as of now" not retroactive). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix(review-2217): add #96 to r3-structure.md §Acceptance + 92→93 hygiene Per cursor/composer-2 review on PR #2217: Finding 1 (single-authority): §1.5 paragraph claimed "96 gate IDs enumerated per r3-structure.md §Acceptance" but the structure doc didn't actually list the new gate. Adding value_body_substrate_mirror_isomorphism_executable to §"Acceptance" T-Verification-L4-L7-Direct lane restores single-authority discipline (P2). Finding 2 (internal consistency): §1.6 line 95 was updated to "96 enumerated; 93 load-bearing" but line 98 still said "92 R3-load-bearing gates green". Aligning the second sentence to 93 so closure arithmetic reads one way throughout §1.6. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix(review-2217-blocking): bind #96 gate to generation-or-isomorphism Per BLOCKING inline finding from openai-pro at PR #2217 docs/r3-program-plan.md:295: "new ValueBody gate leaves the conformance mechanism to Mgr discretion instead of binding it to the generated DagShapeReport/BinaryDimensionReportEquals or generation path tracked for this mirror drift, so a hand-maintained check could satisfy the gate while preserving the P2/P5 parallel-authority risk." Finding valid. Original row's "mechanism Mgr-discretion" framing left room for a hand-maintained TestClaim enumerating variants — itself a parallel authority, defeating the gate's purpose. Brief at docs/briefs/r3-v-valuebody-substrate-mirror-isomorphism-v1-worker.md already cites feedback_isomorphism_or_generation_for_mirrors + INVARIANTS §P1 (generation-or-isomorphism, NOT hand-maintained); §1.8 row needs to reflect this constraint structurally so the gate auditor can reject hand-maintained satisfaction. Edits to both r3-program-plan.md §1.8 #96 row + r3-structure.md §Acceptance #96 entry: - Explicit gate-satisfaction discipline citation (feedback_isomorphism_or_generation_for_mirrors + P1) - Hand-maintained TestClaim explicitly marked structurally inadmissible - 4 bounded mechanisms reframed as "structural-derivation-from-single-authority" (enum walk over canonical type def; structural check / TestClaim over canonical shape projection; build.rs reading canonical generation source) — all derive, none hand-maintain - Cross-link to existing Lens<DagShapeReport> + BinaryDimensionReportEquals predicates (gate #14 / rust_dag_isomorphism_executable) as the structural-isomorphism path Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix(review-2217-q1-hygiene): defer Q1 sub-counts to §1.5/§1.8 authority Per openai-pro APPROVE_WITH_COMMENTS finding on PR #2217: §1.5 lane breakdown says "T-V-L4-L7-Direct 2 + 4 NEW Pattern-A executable + 1 ValueBody isomorphism" (within-lane count) while Q1 row said "5 NEW Pattern-A executable" (cross-lane total — 4 in T-V-L4-L7-Direct + 1 in T-CostLens-Composition for symbolic_cost_expr_equals_executable). Both technically correct but at different aggregation levels — confusing for readers; same closure-gate set has two sub-counting authorities. Fix per reviewer's "defer to §1.5/§1.8 as sole authority" suggestion: remove the within-Q1 sub-count breakdown; preserve the historical pointer (Pattern-A family + codex BLOCKING + ValueBody) but route precise sub-counts through §1.5/§1.8 authority. Single-authority discipline (P2) restored at the Q1 row level. Total still reads 96 closure gates; lane scope still reads 18 lanes + 1 standing program. Audit math unchanged — only the sub-count attribution moves. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix(review-2217-citation): split P1/P2 invariant labels for #96 gate Per openai-pro APPROVE_WITH_COMMENTS finding on PR #2217 sha d59403e: "INVARIANTS §P1 (single-authority)" mislabels — single-authority is P2 (Boundary Discipline), not P1 (Modeling Faithfulness). Reviewer's "P2 or split as P1+P2" suggestion: split is more complete since both axes apply. Verified against INVARIANTS.md: - P1 Modeling Faithfulness: every construct grounds in external fact or structural-derivation from one — applies to "generation-or-isomorphism" (mirror grounds in canonical source) - P2 Boundary Discipline: every fact lives in exactly one authoritative place — applies to "no hand-maintained dual taxonomies" (parallel-authority concern) Both r3-program-plan.md §1.8 #96 row + r3-structure.md §Acceptance #96 entry updated to cite P1 (grounding) for the generation-or-isomorphism axis AND P2 (single-authority) for the no-parallel-authority axis. Future reviewers now apply the right rubric to each constraint. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix(review-2217-p2-self-reflexive): collapse §1.8 #96 to canonical-pointer Per openai-pro REQUEST_CHANGES finding on PR #2217 sha 32ebdfd: > The PR currently duplicates the gate body in both r3-program-plan.md and > r3-structure.md. For a substrate-shape close gate, that is a P2 single-authority > issue and should be collapsed before merge. Self-reflexive failure: the new gate text forbids hand-maintained dual taxonomies (P1 grounding + P2 single-authority), but I added the same gate body as hand-maintained dual content in two docs. Per r3-program-plan.md:302 existing convention: "Authoritative source per gate: r3-structure.md §Acceptance carries the Pass-condition body for each row above. This ledger is the consolidated index — body lives in canonical archive." Other §1.8 rows already follow this (e.g., #1 tier3_termination_mirror_dissolved notes column = "r3-structure.md §Acceptance"). My #96 row violated the convention by including the full body inline. Fix: collapse §1.8 #96 row notes to a terse canonical-source pointer (r3-structure.md §Acceptance T-Verification-L4-L7-Direct + brief reference). Canonical Pass-condition body stays in r3-structure.md §Acceptance as authority. Single-authority restored. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix(test): main-red ratchet drift from PR #2194 — declaration_by_name binding + manifest refresh Main has been red across 4 commits (d4b37da/dfb168c2/fd00e090/3ae9d51f) since PR #2194 (T-CostLens-Composition) merged at 06:33Z. PR #2194 added the 7th SubstrateAccessorBinding (declaration_by_name_binding_rust at src/v3/spec/rust.dag:1704) plus expanded substrate.dag/rust.dag content, but did not bundle: 1. The corresponding bump in m1_substrate_test::substrate_accessor_rust_binding_invariants (assertion still expected 6 bindings; now 7) 2. The parse_corpus_manifest.txt refresh for the new rust.dag (170 items, 1357477 debug_bytes, fnv1a64 9bfd82407452889b) and substrate.dag (65 items, 141515 debug_bytes, fnv1a64 1b2a4d2f9c834025) item/byte/hash deltas This commit applies both: - Updates assertion 6 → 7 + adds declaration_by_name to the expected accessor list - Updates manifest with the values observed in CI failure logs at d59403e The new declaration_by_name accessor + binding are correctly authored at src/v3/spec/rust.dag:1700-1708 (rust_declaration_by_name_accessor + declaration_by_name_binding_rust); they integrate cleanly with the existing 6 bindings under the universe-coverage check that follows the assertion. Bundled into PR #2217 per operator ask: this PR is now docs (gate #96) + fix-forward for main-red ratchet drift, since the docs-only branch was being gated on main going green and standing-authority discipline allows fix-forward on inherited regressions when within tactical scope. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 9, 2026
* WIP: Verification V7 ValueBody isomorphism gate (HOLD pending Brian sanction) * docs(r3): cite canonical §1.8 #96 gate in ValueBody variant inventory PM deep-wolf-155 #846 assigned §1.8 #96 to value_body_substrate_mirror_isomorphism_executable (PR #2217 in flight). Replaces working-gate-name framing with canonical # citation per Mgr direction at #2075 issuecomment-4404078831. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * WIP: Verification V7 ValueBody isomorphism gate (HOLD pending Brian sanction) * chore: refresh PR metadata checks * test: use typed ValueBody witnesses * test: avoid ValueBody source-layout assertions --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 of 5 tasks
briansrls
added a commit
that referenced
this pull request
May 9, 2026
…om cluster-analysis audit + today's merges (#2399) Addresses PR #2358 §8 meta-finding (closure-claims-vs-HEAD drift) via explicit Status refresh on §1.8 rows. Cluster-analysis audit on main (PR #2300 / docs/audit/r3-cluster-analysis-2026-05-09.md §1) identified 9 gates likely-promotable from DECLARED → CONSUMER_LANDED + named specific PRs as evidence. Today's session adds 1 more (#92 via PR #2340). Per cluster-analysis audit §1 closing note: "PM surface, not authoring: ledger refresh is Mgr-owned per docs/r3-program-plan.md §10 cadence. This list is input to next refresh cycle." PM (deep-wolf-155) interpretation: Mgr-cadence-discipline holds, but the cluster-analysis was published 2026-05-09T03:25Z + at least 9 gates are mechanically derivable from PR-history. Authoring this sweep as PM-tier signal-into-next-refresh; lane Mgrs review their lane's rows in this PR before merge. **Updates** (10 candidates): | Gate | From | To | Evidence | |---|---|---|---| | #25 omni_openapi_backend_emission_demo | DECLARED | CONSUMER_LANDED | PR #2251 (Shape B OpenAPI) | | #29 anthropic_wire_typed_serde_alignment | DECLARED | CONSUMER_LANDED | PR #2208 + #2164 | | #30 anthropic_unit_enum_role_serialization_correct | DECLARED | CONSUMER_LANDED | PR #2208 | | #53 workflow_substrate_carriers_landed | DECLARED | CONSUMER_LANDED (partial) | PR #2160 WorkflowSecret + CronExpression β-ratified | | #54 timing_lens_carrier_landed | DECLARED | CONSUMER_LANDED | PR #2360 (post-T-LBP COMPLETE) | | #76 e_p_per_call_descent_evidence_full_coverage | DECLARED | CONSUMER_LANDED | PR #2147 carrier + #2190 consumer | | #77 e_p_call_pattern_lookup_authoritative | DECLARED | DECLARED + verify-pending note | T-E-P P1 slices 1-7; Mgr review needed | | #78 e_p_sub_value_relation_per_call_landed | DECLARED | CONSUMER_LANDED | T-E-P P1 slices 1-7 | | #92 complexity_violation_compile_error_demonstrated | RECEIPT (ambiguous) | CONSUMER_LANDED + PASSING | PR #2340 | | #96 value_body_substrate_mirror_isomorphism_executable | DECLARED | CONSUMER_LANDED | PR #2288 (CI-visible integration) | Each cite includes PR# + brief evidence summary. #77 retained as DECLARED with verify-pending note (cluster-analysis audit said "verify"; Mgr review recommended before promotion). **Verification**: R4-carve dissolution discipline ratchet still passes (32 citations, all properly annotated). No new drift introduced. **Mgr review path**: Substrate Mgr (warm-wolf-698) reviews #29/#30/#53/ #54/#76/#77/#78/#96 lane rows. Verification Mgr (wise-bear-525) reviews #92/#96 lane rows. Grounding Mgr (sunny-koi-893) reviews #25 lane row. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 13, 2026
…NG is HARNESS_NAMED, bare CONSUMER_LANDED is N/A (cursor APPROVE exploratory note PR #3024) Aligns the prose with the table: §1.8 'CONSUMER_LANDED + PASSING' (e.g. rows #1, #97, #99, #101) flows to HARNESS_NAMED via the 'contains PASSING' clause; bare 'CONSUMER_LANDED' (e.g. rows #2, #3, #96) is N/A_NOT_PASSING. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls
added a commit
that referenced
this pull request
May 14, 2026
…3024) * docs(r3): R3 close predicate-execution log — Phase 2 fill (45 EXECUTED / 61 N/A_NOT_PASSING) Populates docs/audit/r3-close-predicate-execution-2026-05-13.md (skeleton merged via PR #3019) per Gap 10 Phase 2 of docs/r3-actual-close-plan.md. For every §1.8 row at HEAD a2a7a88: - Status = PASSING / SATISFIED-BY-CONSTRUCTION (45 rows) → predicate execution status EXECUTED; close-time harness = workspace ratchet batch (cargo fmt / clippy --all-targets -D warnings / cargo test --workspace) with per-row ratchet cited under §1.8 row Notes; result pointer → §Workspace batch receipt. - Status = CONSUMER_LANDED / DECLARED / R3-LOAD-BEARING (decl-stage) / INTEGRATION_RECEIPT / CANVAS_RATIFIED (61 rows) → predicate execution status N/A_NOT_PASSING; per r3-close-interrogation.md §8 the predicate-execution requirement attaches only to PASSING gates. Adds row #106 show_correct_code_diagnostic_coverage (merged PR #3020 / Gap 9) so table mirrors §1.8 ledger one-for-one at HEAD (parity grep `grep -cE '^\\| [0-9]+ \\| `' yields 106 on both surfaces). Workspace batch receipt records cargo fmt --all --check exit 0 and clippy --all-targets -D warnings exit 0; cargo test --workspace --exclude gunbc-dag-tests is initiated and the §10 close-ceremony audit doc records the final 24h-of-close re-sweep with the merge-commit SHA. Overall verdict remains PENDING (61 gates not at PASSING at HEAD; close ceremony not opened). Authority: merged PR gunbc/gunbc#3013 Gap 10 close criterion; PR #3019 skeleton; PR #3020 row #106; docs/r3-close-interrogation.md §8; docs/r3-actual-close-plan.md Gap 10. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): weaken predicate-execution-log claims — Phase 2 = harness-naming, not execution receipt Addresses codex/codex-default REQUEST_CHANGES on PR #3024 (/api/reviews/11316/artifacts/stdout.log, 2026-05-13T20:35:21Z): 1. Per-row status `EXECUTED` (45 rows) → `HARNESS_NAMED`. The Phase 2 PR names the close-time harness per PASSING / SATISFIED-BY-CONSTRUCTION gate so the §10 close-ceremony 24h workspace re-sweep has a mechanical command to run; it does NOT assert an execution receipt. Execution receipts (PASS/FAIL per gate, log pointers, merge-commit SHA) are produced by the §10 close-ceremony artifact `docs/audit/r3-close-YYYY-MM-DD.md`, not by this Phase 2 PR. This eliminates the conflation between "harness identification" and "execution receipt" flagged at lines 26/174/180. 2. SHA anchor: explicit "Ledger-snapshot anchor" section clarifies that `a2a7a8825` is the §1.8 ledger snapshot at this PR's base commit (`git merge-base HEAD main`), and that this PR adds only the audit doc — it does not modify §1.8 or any authority surface. The derivation is valid for any HEAD that includes `a2a7a8825` with no subsequent §1.8 edits. Resolves the "HEAD a98cbc5 vs claimed a2a7a88" single-authority/live-state mismatch (INVARIANTS P1/P2). 3. Workspace batch receipt: only `cargo fmt --all --check` and `cargo clippy --all-targets -- -D warnings` are recorded as Phase 2 partial receipts (both clean against base commit `a2a7a8825`). `cargo test` is explicitly marked NOT_EXECUTED_BY_THIS_PR and anchored to §10 close-ceremony per r3-close-interrogation.md §8 + INVARIANTS.md P3 fail-closed/live-state discipline. Status-bucket distribution table and verdict text updated consistently. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix 61→58 verdict count drift — bucket table is authority (PR #3024 cursor APPROVE_WITH_COMMENTS) Addresses cursor/composer-2 review at 2026-05-13T21:09Z: line 28 verdict said 'remaining 61 gates' but Status-bucket table (20+30+4+3+1=58) is the mechanical authority. 48+58=106. Aligns narrative with single-authority / live-state discipline (INVARIANTS P1/P2). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): fix INVARIANTS P1→P2 label drift per openai-pro APPROVE_WITH_COMMENTS §Ledger-snapshot anchor heading and References list incorrectly labeled the single-authority / no-parallel-authority rule as P1 (Modeling Faithfulness). The correct invariant is P2 Boundary Discipline (INVARIANTS.md:144). P3 Fail-Closed reference is unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): rebalance §1.8 status buckets — row #11 R3-LOAD-BEARING→DECLARED, row #100 PASSING→DECLARED+TEXT-RATCHETED; re-anchor to main 4b491e4 Addresses codex non-blocking finding on PR #3024 (status-bucket hygiene): - Row #11 `tc1_eta_equivalence_executable`: per §1.8 the cell starts with "**DECLARED through R3**" (canvas-deferred past R3 per Path-A); prior parser priority matched the in-cell phrase "R3-load-bearing per §1.5" before the leading "DECLARED" keyword. Row is now DECLARED. - Row #100 `project_github_actions_landed`: amended on main to "**DECLARED + TEXT-RATCHETED**" (post-merge ledger evolution beyond prior CONSUMER_LANDED + PASSING shape). Row is now DECLARED. Re-derivation against current main (`4b491e46f`): - PASSING 45→44 (row #100 demoted) - DECLARED 30→32 (rows #11 + #100 added) - R3-LOAD-BEARING 4→3 (row #11 removed) - Other buckets unchanged. - Total 106 (parity preserved). - HARNESS_NAMED 48→47; N/A_NOT_PASSING 58→59. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): tighten Purpose bullets — composite CONSUMER_LANDED + PASSING is HARNESS_NAMED, bare CONSUMER_LANDED is N/A (cursor APPROVE exploratory note PR #3024) Aligns the prose with the table: §1.8 'CONSUMER_LANDED + PASSING' (e.g. rows #1, #97, #99, #101) flows to HARNESS_NAMED via the 'contains PASSING' clause; bare 'CONSUMER_LANDED' (e.g. rows #2, #3, #96) is N/A_NOT_PASSING. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): split harness override for gate #71 — strict receipt is #[ignore]'d Addresses BLOCKING inline comment on PR #3024 at line 135 (2026-05-13T23:22Z): Gate #71 v3_self_host_demonstration: the canonical strict receipt test r3_v3_self_host_demonstration_suite_passes_through_runner is #[ignore]'d at HEAD pending T-FixedPoint / Lane 3 promotion (per the test's own ignore-doc + docs/design-fixed-point-ratchet.md). Plain `cargo test --workspace` skips it, so the prior harness column overstated coverage for this row. Fix: row #71 now uses HARNESS_NAMED (split) and cites: 1. Non-ignored portion that DOES fire under the default workspace sweep: r3_v3_self_host_demonstration_dag_lowers_with_substituted_bin_path (r3_v3_self_host_demonstration_dag_test.rs:38) + SG-0 census presence ratchet (sg0_census_test.rs:667). 2. Ignored strict receipt requiring explicit invocation: `cargo test -p v3-compiler --release -- --ignored \ r3_v3_self_host_demonstration_suite_passes_through_runner`. Adds a general convention to the §1.8 table preamble: any gate whose canonical receipt is #[ignore]'d at HEAD is flagged HARNESS_NAMED (split) and must cite both the default-sweep portion and the --ignored override. Auditors verify §8 coverage by grepping for `HARNESS_NAMED (split)` and confirming the §10 sweep includes every cited --ignored override. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): defer to close-plan per-gap dispositions; remove generic R4-defer escape hatch (codex BLOCKING PR #3024 #2) Addresses codex BLOCKING finding #2 (line 24): the prior phrase "or is operator-accepted as R4-DEFERRED per §10" reintroduced a generic R4-defer escape hatch the higher-authority close plan explicitly forecloses for Gaps 1/2/3/9 per operator §4 IN-R3 ratification 2026-05-13 (docs/r3-actual-close-plan.md §11). Replacement defers to docs/r3-actual-close-plan.md's per-gap disposition: PROVEN-with-landed-PR-only for Gaps 1/2/3/9 (R4-defer + THESIS-reframe paths STRUCTURALLY FORECLOSED), close-plan disposition for other gaps. This audit doc inherits dispositions and does not author a parallel deferral semantics. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): manager fix-forward — strip generic R4-DEFER, split-harness gate #92, ctrl-build pointer Addresses PM/Director fix-forward guidance (msg_42c90bfb 2026-05-14): 1. Line 24 close criteria: removed the remaining "R4-DEFERRED-with-operator-acceptance" language that codex review 11524 flagged as a generic escape hatch. New wording states no generic deferral; gap-specific structural blockage routes through docs/r3-actual-close-plan.md §1 + explicit Director/operator ratification recorded against the close-plan, not this audit doc. Re-swept for R4-DEFER / R4 defer / R4-defer / R4_DEFER — zero remaining occurrences in this audit doc. 2. Gate #92 row: promoted to HARNESS_NAMED (split). Even though PR #2737 removed the #[ignore] that PR #2723 added (per ledger Notes), fail-closed posture (INVARIANTS P3) requires the close-time command to explicitly invoke the named receipt rather than depend on the ignore-bit remaining off. Row now cites both the default workspace sweep portion and an explicit `cargo test -p v3-compiler -- --include-ignored complexity_violation_compile_error_demonstrated` invocation that fires the receipt regardless of ignore-bit state at the close-ceremony commit. 3. Cursor non-blocking exploratory note: added a one-line pointer that `ctrl-build` is the internal session-runtime BuildBuddy wrapper per CLAUDE.md, and that the §10 close-ceremony auditor substitutes the canonical local equivalent. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * docs(r3): re-anchor §1.8 ledger snapshot to current merge-base c055495; row #63 DECLARED→CANVAS_RATIFIED (codex BLOCKING PR #3024 review 11585) Addresses codex BLOCKING (review 11585): the prior anchor 4b491e4 was stale relative to git merge-base HEAD origin/main (now c055495 after main auto-merged in PRs #3025, #3035, #3037, #3038, #3040, #3046, #3049, #3050). The audit doc's single-authority claim must hold against the actual merge-base, not a frozen prior commit. Codex's row count of 100 at 4b491e4 is incorrect on this worktree (verified 106 at both 4b491e4 and c055495), but the anchor-drift point is valid: per INVARIANTS P2 the authoritative §1.8 snapshot must be reproducible from the current merge-base. Re-derivation at c055495 (verified mechanically): PASSING 44 + SATISFIED-BY-CONSTRUCTION 3 + CONSUMER_LANDED 20 + DECLARED 31 + R3-LOAD-BEARING 3 + INTEGRATION_RECEIPT 3 + CANVAS_RATIFIED 2 = 106. Versus prior anchor: row #63 substrate_gap_workflow_scheduling_closed moved DECLARED→CANVAS_RATIFIED (PR #2831 squash 89df284); buckets adjust DECLARED 32→31, CANVAS_RATIFIED 1→2. HARNESS_NAMED 47 and N/A_NOT_PASSING 59 totals are unchanged (the moved row stays N/A). Row #63 audit-doc cell flipped to cite CANVAS_RATIFIED label. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.7 (1M context) <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
2 participants
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.
Fixes a lowerer deduplication bug by making
endpoint_use_countglobal and adds a regression test.This resolves the BT-E1 duplicate-edge error in
gunbc-sdlcwhen multiple modules use the same service, ensuring correct transport node cloning instead of creating multiple upstream edges to a single transport input.