Technology · verification path
Verification path
Verification focuses on proving that reconstructed state is pure, deterministic, and complete. Critical failures preserve counterexample artifacts rather than silently repairing history. Public inspection lives on the Trust Console, Proof Registry, Evidence Explorer, Challenge Lab, and Auditor handoff.
Public check surface
What you can inspect today
Replay parity
Identical inputs and event order yield matching terminal hashes for sealed capsules.
Open →
Illegal-transition rejection
Unauthorized lifecycle edges reject without state mutation — sealed rejection receipts.
Open →
Cross-implementation parity
Independent Node and Python pure verifiers agree on frozen capsule hashes.
Open →
Audit completeness
Evidence records and provenance labels for claims on the public surface.
Open →
Ordering & adversarial fixtures
Challenge Lab probes for mismatch, altered receipts, and illegal edges.
Open →
Lineage consistency
Append-only chain integrity as documented (DEMONSTRATION until broader sealed scope).
Open →
After verification review
Reproduce offline via Auditor handoff. Commercial scope follows Limitations and written pilot boundaries.