Active
FRE 901(b)(9): Federal Rules of Evidence
Machine-generated evidence must be authenticated as accurate and unaltered
Mutable logs fail this standard. Any post-hoc modification produces inadmissible evidence in federal court.
2026
DoD 3000.09: Autonomous Weapons Systems
Procurement updates require provable human-in-the-loop governance
$850B defense budget. Contractors without verifiable decision provenance face disqualification from major programs.
2026-2027
FAA Part 108: BVLOS Drone Operations
Verifiable audit trails required for insurance underwriting and regulatory compliance
No verifiable logs means no insurance. No insurance means no commercial BVLOS. $2.3B drone insurance market by 2029.
2026-2027
EU AI Act Article 12: High-Risk AI Logging
Decision-making traceability required. Deterministic replay becomes regulatory baseline.
Fines up to 7% of global annual turnover. Brussels effect means EU standards become global standards.
The category lock window
Between 2026-2028, the standard for autonomous systems governance will be established. The first platform that satisfies all four regulatory frameworks becomes the default. Receipts-Native Architecture is the only approach that meets FRE 901(b)(9), DoD 3000.09, FAA Part 108, and EU AI Act Article 12 with a single cryptographic foundation.
Now to Q2 2026
Foundation
AI Flight Recorder deployed with insurance carriers. Prove architecture with BVLOS operations before rulemaking finalizes.
Q3 2026 to Q2 2027
Expansion
Defense contractor integrations for DoD 3000.09 compliance. EU AI Act enforcement creates demand pull. Cross-regulatory proof becomes competitive moat.
Q3 2027 to 2028
Category Lock
Regulatory frameworks finalized with receipts-native as the reference implementation. First-mover advantage converts to category ownership.
Compliance matrix
| Requirement | Mutable Logs | Receipts-Native |
|---|---|---|
| FRE 901(b)(9): Evidence authenticity | ✗ Fails. Logs can be modified post-hoc. | ✓ Passes. Cryptographic signatures prove authenticity. |
| DoD 3000.09: Human oversight proof | ✗ Fails. No verifiable human-in-loop record. | ✓ Passes. RACI chain with cryptographic timestamps. |
| FAA Part 108: Verifiable audit trails | ⚠ Partial. Timestamps are operator-modifiable. | ✓ Passes. Merkle chain integrity from takeoff to landing. |
| EU AI Act Art. 12: Traceability | ⚠ Partial. Logs exist but lack tamper-evidence. | ✓ Passes. Complete traceability with append-only ledger. |
| Tamper detection | ✗ None. Modifications undetectable. | ✓ Any modification breaks Merkle chain. Instant detection. |
| Cross-jurisdiction compliance | ✗ Requires separate implementations per framework. | ✓ Single cryptographic foundation satisfies all four. |