Version and Provenance Register
Cryptographic Chains, Release Histories, and Name Crosswalks
Review the cryptographic provenance chain, release history (Version 1 to Version 14), and Windows filename-length mitigation crosswalks. Demonstrates how predecessors are preserved as immutable evidence and successors are promoted solely by checksum-distinct verification.
Claim Boundary & Exclusions Audit
What Is Claimed (Within Scope)
- •Complete release genealogy across BNP, ETP-CPR, POST-BNP, OIRP, and CP4.R2C synchronization gates.
- •Transparent crosswalk mapping 28 Windows-safe short names (FA-*) to original descriptive manuscript filenames.
- •Release-control rule: Recency, renaming, or storage location does not create scientific authority.
What Is NOT Claimed (Prohibited Inferences)
- •Checksum verification guarantees artifact identity; it does not replace scientific peer review of claim validity.
Technical Exposition & Formulation
Per FA-AUTH-01: 'Any future change in authority requires: a named predecessor; a checksum-distinct successor; a revision manifest; a complete claim and dependency audit; render and accessibility verification; and an update to this register.'
Assumptions & Input Data
- SHA-256 hashes are cryptographic invariants.
Declared Complete Carrier (K3)
REBUILD_VERIFICATION.json and FILENAME_MAP.json.
Source Provenance & Verification Hashes
ETP_MANUSCRIPT_AUTHORITY_REGISTER_Truth_First_V14...
Challenge This Claim Ceiling
Identified an unstated carrier or a counterexample? Submit a formal challenge.