Receipt chain
Canonical bbs.receipt.v2 semantics, deterministic hashing, sequence/linkage checks and independent chain verification.
Implemented
Request accessR&D RECORD
The program is exercised against failure, migration, verification and adversarial conditions before broader readiness is claimed.
Canonical bbs.receipt.v2 semantics, deterministic hashing, sequence/linkage checks and independent chain verification.
ImplementedSerialized append, chain-head allocation, advisory process locking, fsync durability and torn-tail handling.
ImplementedEd25519 signing and public-key verification separated from the originating runtime.
ImplementedReceipt construction, signing and durable append under one chain-head lock and append unit.
Implemented; activation remains boundedDeclared ZIP payload universe, self-hashed manifests, optional detached signatures and embedded receipt verification.
Implemented; packet integration remains in progressNon-destructive boundary records preserve exact legacy bytes and canonical-row digests without pretending old history was retroactively chained.
Implemented preparation pathFour independently receipted 250,000-case segments covering exactness, custody/failure truth, portability and independent verification.
Canonical 1,000,000-case target where technically meaningful; target is not a claim of completionAuthorized backend, API, configuration, tenant-isolation and AI-agent security validation with evidence and retest proof.
Scoped operation onlyBounded BLACKBOX investigation and deterministic receipt runtime used inside the controlled estate.
Private machinery; public claim is bounded investigation capability