Skip to content

Freeze the V4 focused confirmation protocol - #3532

Open
joshlf wants to merge 1 commit into
Gavvgvuiorzpz3yzrmmlq5zb5inu3nazbfrom
Gpt2gxvx72macbs3xnoxkx7o3k5mtekib
Open

Freeze the V4 focused confirmation protocol#3532
joshlf wants to merge 1 commit into
Gavvgvuiorzpz3yzrmmlq5zb5inu3nazbfrom
Gpt2gxvx72macbs3xnoxkx7o3k5mtekib

Conversation

@joshlf

@joshlf joshlf commented Aug 3, 2026

Copy link
Copy Markdown
Member

Freeze a 50-report blind evaluation of V4 against V3: five focused modes, two
conditions, and five fresh replicates per cell. The modes test proof-kernel
completeness, Boolean configuration semantics, length and arithmetic reasoning,
quantifier-sensitive verdicts, and abstraction redesign.

Seal the condition map, prompts, fixtures, frozen skill packages, authority
allowlists, atom rubrics, canonical output schema, scoring packets, retry rules,
and preregistered gates before collection. Require V4 to pass every required
atom in every replicate, with zero hard errors, TCB or authority defects,
proposal laundering, semantic noncompletion, scope failures, or budget
failures. Treat V3 only as a diagnostic comparator.

Retain exact package digests, reviewer records, validation tools, and an
append-only event protocol so collection, scoring, and unblinding can be
distinguished. No candidate reports exist at freeze time.


Latest Update: v2 — Compare vs v1

📚 Full Patch History

Links show the diff between the row version and the column version.

Version v1 Base
v2 vs v1 vs Base
v1 vs Base
⬇️ Download this PR

Branch

git fetch origin refs/heads/Gpt2gxvx72macbs3xnoxkx7o3k5mtekib && git checkout -b pr-Gpt2gxvx72macbs3xnoxkx7o3k5mtekib FETCH_HEAD

Checkout

git fetch origin refs/heads/Gpt2gxvx72macbs3xnoxkx7o3k5mtekib && git checkout FETCH_HEAD

Cherry Pick

git fetch origin refs/heads/Gpt2gxvx72macbs3xnoxkx7o3k5mtekib && git cherry-pick FETCH_HEAD

Pull

git pull origin refs/heads/Gpt2gxvx72macbs3xnoxkx7o3k5mtekib

Stacked PRs enabled by GHerrit.

Freeze a 50-report blind evaluation of V4 against V3: five focused modes, two
conditions, and five fresh replicates per cell. The modes test proof-kernel
completeness, Boolean configuration semantics, length and arithmetic reasoning,
quantifier-sensitive verdicts, and abstraction redesign.

Seal the condition map, prompts, fixtures, frozen skill packages, authority
allowlists, atom rubrics, canonical output schema, scoring packets, retry rules,
and preregistered gates before collection. Require V4 to pass every required
atom in every replicate, with zero hard errors, TCB or authority defects,
proposal laundering, semantic noncompletion, scope failures, or budget
failures. Treat V3 only as a diagnostic comparator.

Retain exact package digests, reviewer records, validation tools, and an
append-only event protocol so collection, scoring, and unblinding can be
distinguished. No candidate reports exist at freeze time.

gherrit-pr-id: Gpt2gxvx72macbs3xnoxkx7o3k5mtekib
@codecov-commenter

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.85%. Comparing base (bd3c8b8) to head (e57a8d4).

Additional details and impacted files
@@                        Coverage Diff                         @@
##           Gavvgvuiorzpz3yzrmmlq5zb5inu3nazb    #3532   +/-   ##
==================================================================
  Coverage                              91.85%   91.85%           
==================================================================
  Files                                     20       20           
  Lines                                   6093     6093           
==================================================================
  Hits                                    5597     5597           
  Misses                                   496      496           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

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.

2 participants