Preview framework pin integrity controls
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
The producer already required FRAMEWORK_COMMIT from
tools/release_evidence.py (repository access required). The preview
verifier only checked whether the manifest and generation record agreed with
each other. A self-consistent retargeting could therefore pass verification
with a foreign framework claim.
control.zip is an explicitly synthetic metadata fixture. retargeted.zip
was copied from it and changed only the two framework claims and the outer
hash/size binding for generation.pb. Both archives retain identical source
and Turtle payloads. Neither contains actual Lean compilation or framework
build evidence; their synthetic source commit is forty a characters.
The before-repair CLI accepted both archives. The focused regression suite failed on two retargeting controls: a foreign 40-character pin and a noncommit string. The verifier now independently checks the producer’s existing shared pin. The control still passes, both retargeting cases fail, and disagreement between the manifest and generation record remains rejected. CI runs these three focused tests before preview packaging.
evidence.textproto uses
proto/validation_evidence.proto (repository access required)
to bind the source commit, relevant source and fixture bytes, terminal command
results, and combined logs. Old verifier bytes resolve from the recorded Git
base; repaired verifier bytes have their own command-input bindings. Expected
failures document rejection controls, not normative conformance.
This correction changes no framework pin, normative identity, semantic mapping, proof body, obligation, AST contract, or release policy. It aligns the verifier with the existing producer contract. The existing normative release blockers remain; these controls do not run or replace those gates. No framework compilation, full preview generation, deployment, or external write was performed for these synthetic controls.