proof / signed history
journal cryptography.
ZERO uses hash-chained entries, Ed25519 signatures, daily roots, and external anchors so autonomous decisions can be replayed against durable evidence.
zero.journal.v1entry envelope
Ed25519entry signature
root hashdaily commitment
Hash-chained envelopeEvery zero.journal.v1 entry carries seq, payload_hash, prev_hash, entry_hash, signing_key_id, and signature.Signed daily rootsjournal-root-YYYY-MM-DD.json commits to the final stream tips for each day and becomes the compact public proof handle.External anchorsOpenTimestamps, Sigstore-style logs, or later public-chain anchors make root timing independently checkable.Replay bindingA decision replay should cite the stream, sequence, payload hash, entry hash, daily root, and anchor when available.Postmortem evidenceIncidents involving live decisions, refusals, or journal anomalies must cite a journal root or explain why it is unavailable.Failure behaviorHash mismatch, missing sequence, invalid signature, anchor failure, and concurrent append conflicts all have explicit degraded states.What it provesThe payload was present in an append-only stream, signed by a configured key, and later committed by a daily root.What it does not proveIt does not prove a model was right, reveal private material, or replace settlement evidence for executed venue orders.