Receipts-Native Architecture
Logs are mutable. Receipts are anchored. When autonomous systems make life-or-death decisions, mutable logs do not satisfy FRE 901(b)(9) evidentiary standards. Liability disputes cost millions. Insurance carriers underwrite blind. Defense procurement stalls.
FAA Part 108, EU AI Act Article 12, DoD 3000.09, and expanding FRE 901(b)(9) case law are converging on one requirement: unforgeable audit trails. Receipts-native architecture becomes the infrastructure standard before agentic AI reaches critical mass. The window is 18–24 months.
Dual-hash provenance, anchored to an append-only Merkle ledger, offline-capable and designed to meet FRE 901(b)(9)
NIST standard plus cryptographic diversity. SHA-256 for compliance; BLAKE3 for speed and hash-width diversity. Combined collision probability effectively zero.
Every receipt anchors to a Merkle chain. Any modification after the fact is detectable. Verification is constant-time regardless of chain length.
Every receipt carries an Ed25519 signature. Authority is provable, not asserted. RACI chains and approval chains cannot be falsified after the fact.
Incumbent observability stacks cannot retrofit this. They are built for post-hoc analysis, not inference-time cryptographic provenance. Rewriting takes 18–24 months and is cost-prohibitive at scale.
I had questions before I built anything. The Inquiry is where I answered them, plainly, with receipts. Open to anyone who wants to understand the machine before they use it.
Enter The InquiryFive questions in under thirty seconds. An honest read on whether your decision trail holds up to a court, a regulator, or an underwriter.
Take the diagnosticA live, dual-hashed, signed receipt for any decision you name. The Merkle chain is open to verify. This is what compute-time compliance looks like.
Generate a receiptAI Flight Recorder deploys receipts-native architecture with insurance carriers underwriting BVLOS operations. Beachhead: the $2.3B drone-insurance market requires cryptographic proof-of-compliance before BVLOS scales. Expansion: the $850B DoD budget and $1–2T space-infrastructure buildout. Category lock window: 18–24 months before enterprise AI governance becomes table stakes.