zerocopy — Engineering Performance

Collect the V3 targeted confirmation reports (#3528) Generate and preserve all 80 canonical reports under the frozen blind protocol, without inspecting the hidden condition map or changing prompts, fixtures, skill packages, rubrics, or gates. Retain raw attempts and validation records so operational failures are distinguishable from semantic outcomes. Three interrupted orchestration attempts, r033 through r035, are recorded and replaced according to the preregistered retry rules; their existence does not alter the canonical sample or scoring criteria. This phase establishes only that the preregistered corpus was collected. It performs no semantic comparison, blind scoring, adjudication, unblinding, or release conclusion. gherrit-pr-id: Gxgsta5jm3iasu652ow7bfbefe3c2r6nb Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Introduce `doc(hidden)` `derive(Project)` (#3492) This factors out the `derive(TryFromBytes)` into `project.rs`, and exposes this machinery as a doc-hidden `derive(Project)`. The implementation of `is_bit_valid` on enums is now fully safe, and a soundness issue of mutable enum tag projection is resolved by permitting only immutable tag projection. gherrit-pr-id: Gcc56a15ce65387a017464947e8c2f25dc9e8c737

Evaluate V2 against V1 and the V1 core ablation (#3523) Run a preregistered 150-report forward evaluation: ten modes, three frozen conditions, and five fresh replicates per cell, with two blind scorers per mode and adjudication before unblinding. V2 versus V1 is the primary comparison; the V1 core ablation is only a historical bridge. V2 passes every whole-execution, exact Rust-1.79/1.80 boundary, producer-quantifier, ticket, configuration, and published-contract atom. It produces no proposal laundering and retains strong reconstructed-proof behavior. The release gate still fails with 16 atom misses and five hard errors. Four of five V2 reports contract an inclusive stable-release interval by omitting Rust 1.80.1, then assert exhaustive closure. Another report assembles every fact needed for a valid empty-slice UB witness but dilutes the conclusion to UNPROVED by continuing to seek a universal positive lemma. Sparse-version interval claims cause two more misses; one omitted alias route exposes an oracle-granularity issue rather than a clear skill defect. The evidence shows that recovering the quantified domain must itself be a proof obligation and that verdicts need explicit logical certificates. It motivates V3's Required/Covered model, domain-transformation obligations, multi-release proof bases, and existential UB certificate. Preserve the failed gate unchanged. Differences between coherent conditions are mixed, modes are heterogeneous, five replicates are an engineering screen, and procedural isolation and unavailable model/seed identity preclude a broad causal or population-level claim. gherrit-pr-id: Gthyz3viupsc7cxzrbqaql6qitqmx2ews Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Blind-score and aggregate the V4 focused evaluation (#3534) Complete blind scoring, adjudication, aggregation, condition unblinding, and the official preregistered V4 decision. Preserve the scoring ledger, packets, events, integrity checks, machine-readable summaries, and unblinding artifacts. V4 improves proof-kernel coverage to 135 of 135 atoms from V3's 124 of 135 and Boolean-configuration reasoning to 25 of 75 from 8 of 75. Quantifier-sensitive verdict reasoning remains 25 of 25, abstraction redesign improves to 27 of 35 from 23 of 35, and length and arithmetic reasoning regresses to 40 of 55 from 46 of 55. Across all modes, V4 produces no proposal laundering, scope or budget defect, semantic noncompletion, or confirmed novel finding. The absolute gate still fails. V4 does not pass every required atom, and hard errors plus TCB or authority defects remain. The dominant pattern is not a bad high-level verdict but an incomplete semantic bridge: visible source syntax is treated as if it directly established execution semantics, types, arithmetic, control flow, or caller obligations. The official outcome is therefore failure, irrespective of comparative gains. Detailed root-cause interpretation belongs to the following analysis phase. gherrit-pr-id: G4gcidwygjqjb3gwg5fcikcvz4chrkvix Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Draft and validate the V5 diagnostic-prequalification harness (#3601) Add an explicitly DRAFT/UNSEALED eight-mode, three-condition, five-replicate-per-cell diagnostic design. After independent review, correct and validate the 115-atom, 35-control oracle, including F's unavailable-root and fan-out separation and Q's invalid-str invariant escape and later-UB semantics. Bind exact fixture surfaces, frozen skill packages, V4 lineage, authority propositions and quotations, deterministic schedules, schemas, projection contracts, and strict-JSON semantic validators. Preserve synthetic self-tests for schedule generation, atom and gate composition, attempt lifecycles, projection, scoring, consistency, and aggregation data structures. Keep the design conspicuously non-executable as release evidence: blocking integration hooks and a static-integrity failure prevent promotion, and no reports, scores, adjudications, condition maps, seeds, lock, or result are recorded. gherrit-pr-id: Ghh32fbkyuqkrndyfjzwwarkb4dmfosug Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Freeze the V3 targeted confirmation protocol (#3527) Freeze a blind 80-report evaluation of V3 against V2 after independent review and preregistration refinement: eight modes, two conditions, and five fresh replicates per cell. Seal condition maps, prompts, fixtures, frozen skill packages, rubrics, allowed authority, expected atoms, and report and scoring schemas before generation begins. Exercise symbolic release domains, nonlinear policy composition, configuration products, existential unsoundness certificates, whole-execution behavioral claims, positive multi-version proofs, abstraction-design firewalls, and regression breadth. Require V3 to pass every required atom in every replicate with zero hard errors, authority defects, proposal laundering, semantic noncompletion, and scope or budget failures. Add an append-only event ledger and explicit attempt lifecycle so generation, validation, retries, blind scoring, adjudication, and unblinding remain auditable. At freeze time the report count is zero, so later results cannot have influenced the protocol or success criteria. gherrit-pr-id: G5k3oylk4nmllritz5hdpiksvqbp24ffs Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Evaluate the V1 abstraction-design workflow (#3521) Run a 54-report treatment/core-ablation study over nine abstraction-design modes. Preserve the fixtures, frozen packages, manifests, raw reports, blind scores, adjudications, and limitations needed to reproduce the comparison. No treatment report certifies an unimplemented proposal, while 16 of 27 core-ablation reports do. Treatment matches or exceeds every adjudicated mode and produces parsimonious designs such as checked construction, real sealing, safe slice splitting, and receiver-bound lifetimes. The preregistered gates nevertheless fail. Four treatment reports use executions containing UB as behavioral counterexamples, and two incorrectly prove a Rust-1.70 empty-slice pointer loop by promoting producer facts into a universal invariant. These failures motivate V2's whole-execution verdict, exact-domain, boundary-case, and producer-quantifier rules. The study remains exploratory: isolation is procedural, model identity and sampling seed are unavailable, modes are heterogeneous, and one replicate per cell cannot establish release readiness. gherrit-pr-id: G3y45zv35fuuyeejc26bftqdd33lqz2oh Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Collect all V4 focused audit reports (#3533) Generate and preserve the complete 50-report canonical corpus under the frozen blind protocol. Keep condition identities sealed and leave the packages, prompts, fixtures, rubrics, authority sets, and release gates unchanged. Record 54 total attempts. Four infrastructure failures are retried under the preregistered rules; every canonical report validates and remains within its output cap. Preserve the raw reports, attempt metadata, validator output, and collection integrity records so later scoring can distinguish model behavior from orchestration behavior. This commit closes report collection only. It contains no scoring result, unblinding, semantic interpretation, or revision to the skill. gherrit-pr-id: Gowcssqoviioleh66rgjls4bafqwd4l5n Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Make the V5 diagnostic harness executable and fail closed (#3603) The first V5 draft described the intended diagnostic study but could not safely execute it. Review found that READY promotion was impossible, several CLI routes had stale arities, padded report IDs disagreed with their validators, host-specific paths destroyed prompt equality, evaluator packets named only digests rather than readable evidence, materiality had no runnable lifecycle, and DRAFT/READY schemas and runtime-state rules contradicted one another. Replace that draft boundary with an authenticated prepare-snapshot, private-review, and finalize lifecycle. The production lock now binds the trusted source declaration, both skill packages, every target, the harness programs, the staged word counter, 120 report prompts/plans/launches, 43 evaluator assignments, hook-specific review contracts and receipts, empty pre-lock runtime state, and a separately custodied external commitment. Synthetic paths carry an authenticated test-only kind and cannot mint production artifacts. Adversarial review exposed further trust failures: executing an unverified candidate verifier, source-copy TOCTOU, ambiguous line-oriented manifests, arbitrary review claims and evaluator launches, stale receipts, unreviewed runtime state, irrelevant schema leakage, optional or crash-unsafe external commitments, and a coherent attack that rebound an F report to target E and a V5 condition to the V4 package. Use injective framed commitments, trusted in-process regeneration, exact artifact/check/evidence inventories, private review copies, atomic no-replace publication, explicit custody-bound recovery, and exact target/condition/package joins to close those failures. Preserve each attack as a negative self-test. Complete the execution protocol around those locked inputs: readable content-addressed packets, two independent consistency reviews, conditional adjudication, materiality review and ledger reconstruction, exact projection and control joins, deterministic aggregate rebuilding, production state authentication, canonical path checks, leases and seals with crash recovery, and fail-closed bound gate evaluation. Unbound caller data cannot make D-STATIC pass. Validation covers prepare, integration, protocol, and draft-verification self-tests; hostile temporary paths; all CLI help surfaces; all JSON parsing and schemas; adversarial provenance, packet, lease, gate, commitment, and assignment mutations; whitespace; and cache hygiene. This remains diagnostic infrastructure: G-ISOLATION and G-OUTPUT-FINALIZATION deliberately remain FAIL, so the commit cannot support a release or terminal-VN claim. gherrit-pr-id: Ghchu3g3fkri2ofhgm5addjto4rfkyvyi Agent-Authored-By: AI agent acting on Josh Liebow-Feeser's behalf

Introduce unstable `#[zerocopy(invariant(...))]` library invariant checking (#3681) Makes progress on #1330. gherrit-pr-id: G2cef62dbb236b18953ded9a3d514bf0913c0e49c