Audit ledger
Verify privileged history through a BLAKE3-linked event chain with optional entropy provenance.
Each record carries the previous state forward
Linked records
Each privileged event includes the prior record hash, making retroactive changes detectable. Verification can cover the complete chain or a selected slice.
Entropy and anchoring
MAGIC-sourced entropy may salt ledger records while retaining provider provenance. Chain anchoring can publish a checkpoint beyond the local database.
Cryptographic boundary
The current ledger uses classical BLAKE3 hashing and Ed25519 attestations. Post-quantum signatures are explicitly future work.
Verification and evidence
Verification recomputes each record hash with the previous link and reports the first mismatch. Privileged events correlate approval, capability, worker, and XP evidence so an operator can reconstruct why an action ran.
Post-quantum roadmap
The repository separates current cryptography from planned migration work. Future releases explore NIST-selected post-quantum primitives; current deployments should be evaluated against the documented classical boundary rather than future claims.