Receipt chains
Ordered event records preserve declared actor, event and subject identity.Order and linkage are recorded so a later reviewer can separate the event from its retelling.
Solutions
Evidence that can leave the runtime.
Receipts, provenance, custody, portable releases and independent verification for records that need to survive operational boundaries.
Digital evidence
Digital evidence fails quietly the moment it leaves the system that made it — provenance drops, order blurs, and a result decays into a claim. This solution keeps receipt state, cryptographic binding, portable release and independent verification as separate layers, so a record stays inspectable long after it moves.
Portable releases
A declared payload is frozen with the material needed to inspect it, so the evidence universe does not silently change when it travels.
Independent verification
Supported evidence can be checked without the private signing key or the originating runtime, which is what lets a third party review it at all.
Custody boundaries
Source, action and release state stay distinguishable, so nobody mistakes a derived artifact for the original record.
Current Evidence
Ordered V2 receipts preserve actor, event and subject identity across the record.
SHA-256 hashing and detached Ed25519 signatures bind evidence and release state.
Released evidence can be verified without the private key or the originating runtime.
Proof
Provenance that survives the handoff.
Blackbox Systems binds declared events and releases to receipts, hashes and detached manifests so evidence stays inspectable after it leaves the runtime. These are engineering evidence states, not a claim of certification or admissibility.