Detects modification after sealing. It does not establish that a measured value is meaningful.
VERIFICATION
Every visible state
needs a visible proof path.
Integrity evidence answers a narrow question: can the current V5 state be traced through knowledge admission, atomic Present, 100 ms microblocks and replay? It does not turn integrity into predictive value or external validation.
RUNTIMEREALTIME V5AXES7/7MMR ROOTdcff7e1e6b32EXTERNAL VALIDATIONNOT_PRESENT
01 · SEALED HISTORY
The record is append-only.
newest sealed block80455
02 · WHAT EACH CHECK MEANS
Strong evidence.
Narrow claims.
Ed25519 + ML-DSA-65 bind the published artefact to this system. They do not prove the system is right.
The output can be recomputed from its inputs. It does not certify that the inputs were the right ones.
Commits to one history. It makes no statement about a future market outcome.
03 · CURRENT EVIDENCE STATE
What is closed.
What is still open.
LIVE SEALED PRESENT—ratified sealed cells; gaps not imputed
MARKET EDGENOT ESTABLISHEDprospective economic evidence required
EXTERNAL AUDITNOT PRESENTaudit package prepared, review not completed
EXTERNAL AUTHORITY0/7cannot be granted by CMM.X itself
ACTION GATE0no action authority
AUTHORITY STATUSNONAUTHORITATIVEseparate from measurement
04 · REPRODUCE IT
Verify before you trust.
1Take the state
/api/system2Check the seal/api/attestation3Replayre-derive from inputsIf replay disagrees with the published state, the publication itself becomes evidence of the failure. That is the intended fail-closed behavior.
Open evidence handling rules and statement classes
Measured, reproducible and open to refutation.
Architecture and semantics chosen by the protocol.
What the system is built toward but has not reached.
Missing data stays undetermined; superseded records are appended, never rewritten; unrunnable checks fail closed.