Skip to content

[codex] Add L4 add-then-branch emit/eval receipt - #2585

Merged
briansrls merged 3 commits into
mainfrom
session/sharp-crane-849
May 10, 2026
Merged

briansrls merged 3 commits into
mainfrom
session/sharp-crane-849

Conversation

@briansrls

Copy link
Copy Markdown
Contributor

Summary

  • add the Lane 1 add_then_branch L4 certification seed to r3_verification_l4_emit_eval_match.dag
  • wire the seed into r3_verification_l4_l7_direct_suite with a focused Rust-vs-eager-eval integration assertion

Validation

  • cargo test -p v3-compiler --test integration r3_verification_l4 -- --nocapture

@briansrls

Copy link
Copy Markdown
Contributor Author

Verified the dashboard-only review artifact. The table-driven helper suggestion is non-blocking; I’m keeping the explicit per-claim tests in this PR because they match the surrounding convention and keep the gate corpus growth narrowly scoped. No code change is needed for this item. — sent from sharp-crane-849

@briansrls
briansrls merged commit 03ced77 into main May 10, 2026
4 checks passed
@briansrls
briansrls deleted the session/sharp-crane-849 branch May 10, 2026 09:27

@briansrls briansrls left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review metadata

  • Provider / model: codex / unknown
  • Commit: e22b26cb · Trigger: schedule
  • Thinking: 382s wall

BLOCKING (1)

Root Cause

  • src/v3/compiler/tests/integration/r3_verification_l4_l7_l5_skeleton_test.rs suite-level receipt re-executes every L4 claim after the per-claim receipts → make the suite test structural-only or add a tracked exemption/paydown row.

⚠️ One timeout-ratchet issue needs fixing before this is safe to land.

/// `run_claim` tests without pinning suite result order).
#[test]
fn r3_verification_l4_l7_direct_suite_lists_three_l4_certification_seed_claims() {
fn r3_verification_l4_l7_direct_suite_lists_four_l4_certification_seed_claims() {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

BLOCKING: The expanded four-claim suite-wide run now exceeds the 2s per-test ratchet (--report-time showed 2.892s locally) but is not slimmed or exempted, so the fail-closed timeout gate can reject this PR.

briansrls added a commit that referenced this pull request May 10, 2026
…rows #9/#10/#11

Reviewer (claude-opus-4-7 on PR #2648) flagged that the prior status text
on rows #9, #10, #11 carried Director/PM-ratified semantic qualifiers that
must not be silently elided when citing a new slice receipt:

- #9 `l4_emit_eval_match`: §1.7 corpus-quantified rule — slice receipts ≠
  ledger closure; PASSING requires every certification-corpus program.
  Reverted to CONSUMER_LANDED; PR #2585 cited as additional slice evidence.
- #10 `l7_algebraic_laws_witnessed`: PASSING requires exhaustive per-(algebra,
  inhabitant, law) §Acceptance coverage; distributivity / lattice absorption /
  non-AlgebraicLawKind laws remain substrate §P1. Reverted to CONSUMER_LANDED;
  PR #2602 cited as incremental advancement.
- #11 `tc1_eta_equivalence_executable`: Director (a)-disposition 2026-05-09
  held this canvas-deferred past R3 absent #1972 substrate canvas-tier work.
  Reverted to DECLARED-through-R3; PR #2603 cited as scaffold advancement
  but not retiring the canvas-deferral (which would require fresh Director
  ratification).

Other 14 rows in the batch (#12, #14, #31, #43-52, #69) did not carry such
qualifiers and stay flipped to PASSING.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
briansrls added a commit that referenced this pull request May 10, 2026
…2648)

* docs(r3): §1.8 ledger-receipt sync — 2026-05-10 batch (V Mgr lane)

Flip §1.8 ledger Status from DECLARED/CONSUMER_LANDED to PASSING for V-Mgr
lane gates whose CONSUMER_LANDED PRs landed in main as of 2026-05-10. Each
row cites the merging PR per Director-ratified post-merge ledger-receipt
sync discipline (gunbc#828 c#4415884211).

Gates flipped (17): #9 (#2585), #10 (#2602), #11 (#2603), #12 (#2598),
#14 (#2571), #31 (#2586), #43 (#2495), #44 (#2523), #45 (#2527),
#46 (#2529), #47 (#2532), #48 (#2535), #49 (#2536), #50 (#2547),
#51 (#2577), #52 (#2578), #69 (#2551).

Skipped per discipline: #15 (PR #2604 not landed); #35 already PASSING.

Doc-only; no code or test changes. Closes #2640.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs(r3): preserve corpus-quantified + canvas-deferral qualifiers on rows #9/#10/#11

Reviewer (claude-opus-4-7 on PR #2648) flagged that the prior status text
on rows #9, #10, #11 carried Director/PM-ratified semantic qualifiers that
must not be silently elided when citing a new slice receipt:

- #9 `l4_emit_eval_match`: §1.7 corpus-quantified rule — slice receipts ≠
  ledger closure; PASSING requires every certification-corpus program.
  Reverted to CONSUMER_LANDED; PR #2585 cited as additional slice evidence.
- #10 `l7_algebraic_laws_witnessed`: PASSING requires exhaustive per-(algebra,
  inhabitant, law) §Acceptance coverage; distributivity / lattice absorption /
  non-AlgebraicLawKind laws remain substrate §P1. Reverted to CONSUMER_LANDED;
  PR #2602 cited as incremental advancement.
- #11 `tc1_eta_equivalence_executable`: Director (a)-disposition 2026-05-09
  held this canvas-deferred past R3 absent #1972 substrate canvas-tier work.
  Reverted to DECLARED-through-R3; PR #2603 cited as scaffold advancement
  but not retiring the canvas-deferral (which would require fresh Director
  ratification).

Other 14 rows in the batch (#12, #14, #31, #43-52, #69) did not carry such
qualifiers and stay flipped to PASSING.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Merge origin/main into ledger-receipt sync (preserve row #13 update from main)

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant