The Five Aira Sub-Products
Settlements, Estate, Evidence, Compliance Bundles, Compliance Reports — what each one is, who buys it, and which problem it solves.
Aira ships five distinct sub-products on top of the same core primitives (receipts, signatures, the policy engine). Different buyers, different moments of use. This page is the canonical reference — every dashboard subtitle, every landing-page card, and every SDK example uses the same one-liner from the table below.
The taxonomy
| Sub-product | One-line tagline | Primary buyer | When you reach for it |
|---|---|---|---|
| Settlements | Tamper-evident batches that anchor recent receipts to a public, queryable log. | Engineers, technical auditors | Continuous, automatic — Aira does it for you |
| Estate | Lifecycle for individual agents — wills, ownership transfers, certified shutdowns. | Agent operators, governance teams | When an agent retires, transfers ownership, or sunsets |
| Evidence | Curated bundles of specific receipts assembled for a single legal request. | Legal teams (reactive, on subpoena) | When someone formally asks for proof of a specific incident |
| Compliance Bundles | Cryptographic snapshot of every receipt in a period, mapped to a regulatory framework. Machine-readable, offline-verifiable. | Compliance officers, internal auditors | Periodic — month-end, quarter-end, year-end |
| Compliance Reports | Same data as a bundle, rendered as a regulator-ready PDF. The document a regulator opens. | Regulators, board members, external auditors | When you need to hand someone a document they can read |
The conceptual split
Settlements → infra-level proof (batch anchoring of receipts)
Estate → agent lifecycle (wills, succession, shutdowns)
Evidence → legal discovery (one request, specific receipts)
Compliance ─┬─ Bundles → cryptographic evidence (machine-readable JSON)
└─ Reports → human-readable document (PDF)How they relate
Receipts are the atomic unit. Every other sub-product is a different view or lifecycle layer over receipts:
- Settlements group receipts into batches and anchor each batch. Every receipt eventually belongs to exactly one settlement.
- Compliance Bundles select receipts by date range and framework, then commit the set to a Merkle root that auditors can verify offline.
- Compliance Reports take the same selected set and render it as a PDF for human readers. Reports and Bundles are two views of the same data — bundles for machines, reports for humans. Most teams produce both.
- Evidence Packages select receipts by case (a specific lawsuit, inquiry, internal investigation) — not by date range. They're curated by an operator, sealed, and exported.
- Estate records agent-lifecycle events as their own receipts so the audit trail covers wills, ownership transfers, and shutdowns the same way it covers tool calls.
Which one do you need?
| If you're being asked… | Reach for |
|---|---|
| "Prove these receipts haven't been tampered with" | Settlements (built-in continuously) |
| "We're being sued — give us all decisions related to customer X" | Evidence |
| "Auditors are coming next week — they want the full Q1 record" | Compliance Bundles |
| "The regulator wants a document for this period" | Compliance Reports |
| "Agent retired — sign the death certificate" | Estate |
| "What's the audit history of this one agent's lifecycle?" | Estate |
Ship-of-Theseus rule
If you only ever produce one of these, your audit trail is incomplete. Most regulated deployments end up using all five at different cadences:
- Settlements runs continuously — you don't think about it.
- Compliance Bundles is generated monthly and stored as your internal record.
- Compliance Reports is generated on-demand from the same data when a regulator or board asks for the human-readable version.
- Evidence is generated reactively when legal requests it.
- Estate is updated when agents transition (rare but high-stakes).
The dashboard surfaces all five as siblings under the Agents section of the sidebar. Each has its own page; each page has the canonical one-liner above as its subtitle.