Protocol
Local verification before public claims.
The CLE Protocol connects canonical data, record hashes, archived snapshots, typed ProofGraphs, browser verification, and an optional challenge-capable contract. It makes integrity and claim boundaries inspectable without turning a hash into a truth claim.
Protocol Components
- Canonical JSON and CSV artifacts in
data/. - Record hashes and dataset hashes regenerated from the current source files.
- Snapshot manifests archived in
data/snapshots/. - Release verification artifacts that record the commands and limits for each public package.
- ProofGraph compiles every record into typed source, claim, response, limitation, and certification nodes.
- A snapshot-wide Merkle registry proves that each record graph belongs to the published registry root.
- The optional smart contract records commitments, registered attestations, permissionless challenges, responses, and supersession lineage.
Verification Commands
npm run hash:dataregenerates record and snapshot hashes.node scripts/hash-dataset.mjs --checkchecks committed hashes against current data.npm run validate:datavalidates canonical data and schema consistency.npm run checkruns the broader local release gate.npm run proofgraph:verify -- --allrecomputes every graph and registry inclusion proof.