Freeze the V4 focused confirmation protocol

[joshlf]

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.

---

• 　  Harden V5 staged runtime and recovery #3607
• 　  Bind V5 review evidence and identities end to end #3604
• 　  Make the V5 diagnostic harness executable and fail closed #3603
• 　  Draft the V5 diagnostic-prequalification harness #3601
• 　  Harden V5 evaluation and terminal confirmation #3537
• 　  Require evidence-bearing proof kernels in unsafe Rust V5 #3536
• 　  Analyze why the V4 focused gate failed #3535
• 　  Blind-score and aggregate the V4 focused evaluation #3534
• 　  Collect all V4 focused audit reports #3533
• 👉 Freeze the V4 focused confirmation protocol #3532
• 　  Revise the unsafe Rust skill after the V3 evaluation #3531
• 　  Analyze the V3 targeted confirmation failures #3530
• 　  Blind-score the V3 targeted confirmation #3529
• 　  Collect the V3 targeted confirmation reports #3528
• 　  Freeze the V3 targeted confirmation protocol #3527
• 　  Revise unsafe Rust skill around domain and verdict certificates #3524
• 　  Evaluate V2 against V1 and the V1 core ablation #3523
• 　  Revise unsafe Rust skill to V2 after V1 evaluation failures #3522
• 　  Evaluate the V1 abstraction-design workflow #3521
• 　  Replay V1 against the predecessor pilot #3608
• 　  Add unsafe Rust skill V1 and preserve predecessor pilot #3520

Latest Update: v5 — Compare vs v4

📚 Full Patch History

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

Version	v4	v3	v2	v1	Base
v5	vs v4	vs v3	vs v2	vs v1	vs Base
v4		vs v3	vs v2	vs v1	vs Base
v3			vs v2	vs v1	vs 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.

[codecov-commenter]

Codecov Report

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

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.