And why that pattern became Axiom.
AI.FO was a production CFO-reasoning system. 2,000+ assertions. Sealed snapshots. Audit-independent verification. No hallucinations in the audit trail. This is how it worked — and what Axiom learned shipping it.
When Claude writes a journal entry, it produces an artifact. That artifact needs to be auditable — but it should not be mixed into human-authored records without a clear boundary.
AI.FO's sealed snapshot architecture generates a cryptographic receipt at the moment every automated task completes. The receipt is sealed before the artifact enters any human-facing system. Human commits and auto-generated artifacts are kept in separate git scopes, with the snapshot serving as the provenance record.
[Claude writes artifact]
↓
[Artifact sealed at generation time]
↓
[HMAC receipt generated]
skill | timestamp | inputs_hash | output_hash
↓
[Artifact enters human-audit scope — provenance verified]
↓
[Human commits only provenance metadata, not raw data]
Most audit processes are retrospective — you run the audit after the quarter closes. AI.FO ran a continuous audit harness: every night, the system executed the full close checklist against live data and produced a signed Engine Check Audit report.
The report was structured for a Federal Single Audit reviewer. If a reconciliation failed, it failed publicly and in real-time. By the time the auditor arrived, the evidence was already sealed and verified.
| Assertion | Logic | Failure condition | Last run |
|---|---|---|---|
| Balance sheet zero-check | Assets − Liabilities = 0 | Non-zero balance | 2026-05-26 23:00 |
| AP aging under 30 days | Invoices > 30 days = 0 | Any balance > 30 days | 2026-05-26 23:00 |
| Grant expenditure ≤ budget | Σ grant spend ≤ budgeted | Overage | 2026-05-26 23:00 |
| JE sequence unbroken | JE count = last − first + gaps | Gap detected | 2026-05-26 23:00 |
| Foreign entity FX rate valid | Rate date ≤ statement date | Stale rate | 2026-05-26 23:00 |
2,000+ assertions. Every one deterministic. Every one traceable. Every one signed.
AI.FO's architecture never sent financial data to the LLM. Not a policy choice — a structural one. The LLM received structured metadata and produced structured instructions. Financial data moved through deterministic logic paths only.
Financial Data
↓
[Deterministic assertion layer — no LLM]
↓
[Structured metadata only → LLM]
↓
[LLM reasoning on metadata, not data]
↓
[Result sealed → receipt generated → audit trail]
Every assertion is a provable statement about the data. No guesswork.
Every AI.FO primitive has a direct Axiom equivalent. Here's the mapping.
| AI.FO primitive | What it did | Axiom equivalent | What it does |
|---|---|---|---|
| Sealed snapshot | Receipt generated at artifact creation, before human review | HMAC receipt | Cryptographic attestation generated at invocation time, before output is returned |
| Audit-independent harness | Nightly signed test run — verifiable without auditor present | /verify endpoint | Any compliance team or regulator verifies receipts without Axiom's infrastructure online |
| Deterministic assertion layer | Financial data never reaches the LLM — structural isolation | Timing-safe HMAC verification | Receipt signature verified with constant-time comparison — no timing oracle exposure |
| Regulated DNA | Federal Single Audit, GAAP, multi-entity treasury, ITGC controls | EU AI Act / SOC 2 / HIPAA mapping | Structured regulatory control mappings: CC7.2, CC7.3, Art 12, Art 13, §164.312(b) |
| 2,000+ assertions | Every close-cycle check provable and traceable | Per-receipt execution trail | Every skill invocation produces a signed, queryable receipt |
AI.FO's approach attracted inbound from organizations that needed what Axiom now delivers as a product:
Names withheld under NDA. Letter counts and sector exposure are the only specifics that can be disclosed.
90-day pilot. Full cryptographic receipt infrastructure from day one.
If you're deploying AI agents in a regulated environment — finance, healthcare, legal, critical infrastructure — you need this. Not as a feature. As a structural requirement.