01Canonical records
Deterministic representations of source, context, decision and release events.
EVIDENCE GOVERNANCE
Context that can be reviewed and verified.
A context record is stronger when its sources, transformations, decisions and release conditions can be independently examined.
EVIDENCE MODEL
Evidence is part of context, not an afterthought.
The evidence plane records what was known, what was missing, who or what assessed it, and which authority permitted the outcome.
02Integrity hashes
SHA-256 and SHA3-family profiles for controlled artefacts and manifests.
03Signature profiles
Compatibility and post-quantum signature profiles reported according to actual execution status.
04Timestamp receipts
Independent timestamping can anchor selected manifests without exposing confidential payloads.
05Disagreement records
Conflicting sources, models and agents remain visible for human review.
06Release receipts
Audience, reliance, confidentiality, licensing, expiry and revocation are bound to output release.
Cryptographic accuracy
Readiness, configuration and successful execution are different states. A system must not report a post-quantum signature, trusted timestamp or external verification unless the relevant operation actually ran and the result was retained.
Public/private separation
Public records can publish identifiers, hashes, verification instructions and high-level architecture while excluding private keys, confidential specifications, privileged legal material, customer information and unrestricted evidence payloads.
Legal limits
Hashes, signatures and timestamps may support integrity, chronology and custody. They do not by themselves determine inventorship, patent validity, admissibility, infringement, legal ownership or the truth of the underlying content.
Review this website’s release manifest.
The verification page provides the public manifest roots and local verification instructions.