Technologies rotate every funding round. Institutions move on geological time. AI decisions that touch patient records, audit logs, and identity cannot wait for a stable wire format — they need a chain of authority, a regime, and an opposable trail, all of which Axone provides for the institutional data layer.
Every cloud, every model provider, every chat-middleware factory churns through AI vendor stacks in 18-month cycles. Hospitals, courts, and regulators carry 30-year record-retention obligations. The substrate that bridges the two — the part that has to outlast any single cloud or model — is the institutional data layer, and that is the layer Axone is built to serve.
Axone treats data custody as the durable primitive. Axone adds the institution: Zones as the jurisdiction-bound rule registry the data custodian operates, Pactum as the on-chain opposable settlement arm that turns a data-access agreement into a verifiable chain of custody, and an IBC-anchored auditable trail that outlives any model vendor or cloud. For the full foundation framing, see the foundation thesis and the developer surface at docs.axone.xyz.
Models move in and out of rotation. Clouds get renegotiated. The audit, retention, and identity obligations around a patient record or a court filing do not. Below: the institutional-data-sovereignty primitives the Axone layer provides.
Zones are the jurisdiction-bound rule registry the data custodian operates and that audit and governance bodies can verify. A Zone's rules are decided by the regime — not by the model that happens to be calling through it — and they are the boundary any data access must respect.
Pactum is the Solidity contract family that turns a data-access agreement into a verifiable chain of custody. Disputes are not a chat between subscribers and a model vendor; they are a verification against the published rule and the on-chain trail, with a settled outcome.
The IBC-anchored auditable trail records who saw which record, under which Zone, with which justification. Replace any cloud or model tomorrow and the trail still answers who is accountable for a 30-year retention obligation.
Transport is incidental: MCP or any alternative is just the wire that carries the call. The architecture assumes the wire churns — the institutional data layer does not. For the developer surface and reference SDKs, see docs.axone.xyz.
The supporting case study shows how a custody layer can outlive any single model or cloud.
The blog is the public research surface for governance and architecture on Axone. Continue with the case study above — or browse the wider blog.