Do the public bytes match the declared release?
The public delivery exposes a manifest, market-state artifact, acceptance record and consumer verifier.
PASSInspect delivery →PROOF EXPLORER / READ ONLY
Do not trust
the rendered state.
Verify the release identity, chain state, signatures and independent reproduction separately. A pass in one layer never substitutes for a failure or limitation in another.
PROOF MAP
Four layers. Four separate checks.
Visual orientation only. Each node carries its current real public status and links to the underlying machine evidence.
01 · RELEASEPASSSELF_CONSISTENT_ONLY
02 · CHAIN75470FRESH
03 · ATTEST75470HYBRID SIGNATURES
04 · REPRODUCE93.06%0 MISMATCH
AUTHORITY≠ ACTIONACTION_GATE 0
RELEASEBYTES
IDENTITYHASH
DERIVATIONREPLAY
ATTESTATIONPROOF
≠
AUTHORITYACTION
CHAIN FRESHNESS21sFRESH
ATTESTATION44sseq 75470
REPRODUCTION93.06%0 mismatches
RELEASEseq_75239_20260908T202900+0000SELF_CONSISTENT_ONLY
CURRENT VERIFICATION OBJECT
RELEASEseq_75239_20260908T202900+0000
MANIFEST SHA-256aa4ca02f62b0bbcbd3d4c2dd206770de8bbfb1829ef8e9006fa563080814924e
ACCEPTANCE SHA-256962b58678dca0e2c578b97b2fff495aff7a4472994de5221479e65314ee68889
CLAIM BOUNDARYDESCRIPTIVE_STATE_EVIDENCE_ONLY
Is the state anchored in the current append-only chain?
Frontier 75470 · blocks 56969 · MMR root 5481a21c27d7bd15….
Are signatures present over the canonical payload?
Ed25519 fingerprint 2001f57eee4a7a56 · ML-DSA-65 fingerprint a3e323f0640c5fa9.
What can a separate code path actually reproduce?
67 reproduced leaves · 93.06% of derived content · mismatches 0.
Reproduction is intentionally not all-or-nothing.
The public report distinguishes reproduced content from constants, declared inputs, metadata and known non-deterministic or undeclared-input gaps. Zero mismatches does not mean every leaf is independently reproducible.
93.06% derived content reproduced39 float-exact checks0 mismatches5 undeclared-input gaps
Open reproduction gaps · 5
axis_payload.statusrequires an input/rule not declared in the artifact (e.g. undeclared status map or u0-rebuilder input); honest gap, never fabricated.
axis_payload.tf.1d.statusrequires an input/rule not declared in the artifact (e.g. undeclared status map or u0-rebuilder input); honest gap, never fabricated.
axis_payload.tf.1h.statusrequires an input/rule not declared in the artifact (e.g. undeclared status map or u0-rebuilder input); honest gap, never fabricated.
axis_payload.tf.4h.statusrequires an input/rule not declared in the artifact (e.g. undeclared status map or u0-rebuilder input); honest gap, never fabricated.
axis_payload.u0.u0_meanrequires an input/rule not declared in the artifact (e.g. undeclared status map or u0-rebuilder input); honest gap, never fabricated.
INDEPENDENT CHECK
Verification procedure
Use separate tools for separate claims. The rendered interface itself is never the evidence source.
- ResolveFetch
/api/deliveryand record the release identity. - HashFetch the manifest and referenced artifacts; recompute SHA-256 locally.
- VerifyRun the delivered consumer verifier outside the CMM.X implementation tree.
- AttestVerify Ed25519 and ML-DSA-65 over the canonical attestation payload if that layer is required.
- Respect boundaryA valid package still does not imply direction, edge, MARKET_GO or action permission.
Established by this surface
- Current public release identity
- Append-only chain visibility
- Presence of hybrid signature material
- Independent reproduction result and its gaps
Not established by this surface
- No external source authenticity
- No directional prediction or alpha
- No professional-pilot evidence
- No MARKET_GO or action authority
TECHNICAL DEPTH
Need the full research verification view?
The legacy research surface remains available separately so the Enterprise proof path stays concise without deleting technical detail.