Regime Templates · Open Library

Typed, parameterized, versioned regime templates for Zone operators

Every Zone on Axone is governed by a Regime — the Prolog artifact that decides who can act, under what conditions, and with what consequences. This library collects starter templates that ship as typed, parameterized, versioned, reproducible artifacts operators can drop into the Zone Builder and deploy today.

Three families of governance

Each template family answers a different operating question. Most production Zones compose templates from more than one family.

01 — Operational
Daily run-the-Zone rules
e.g. Tenant Onboarding
Operational regimes govern the steady state of a Zone — who can do what, under which quotas, with which rate-limits, and at which price. They are the templates every deployed Zone instantiates first: an identity surface, a resource envelope, and a pricing schedule. Most live Zones on axone-1 today are built on Operational regime templates composed with two or three sibling families.
02 — Audit
Evidence, logging, reproducibility
e.g. Audit-Log Feed
Audit regimes capture the second-by-second record of what happened in a Zone — who acted, what facts were checked, what regimes evaluated, and what state changed. They are designed for evidence export: every act emits a structured event, every event carries the regime version and slot values it was evaluated against. Audit templates are the substrate regulators, courts, and partners ask for when a Zone goes into production under any non-trivial compliance regime.
03 — Juridical
Disputes, opposability, IBC settlement
e.g. Opposable Dispute
Juridical regimes give acts their opposability — the property that makes them contestable across organizations and across chains. They define the dispute surface, who can challenge an act, which evidence rules apply, and how settlements are routed through IBC to counterparties on other Zones. Pactum Solidity contracts and the oppowser rule layer sit in this family.

Starter templates

Drop-in regime templates that ship today. Each template is a typed Prolog package — fill the slots, instantiate the Zone, get a reproducible on-chain regime hash.

🏥
Beta
Federated Clinical Inference Zone
Cross-site clinical AI under a single regime: jurisdiction-bound inference, RBAC for clinicians, and IRB-style review gates. Anchored to the healthcare Zone Builder case study.
healthcare RBAC IRB-gates
🎮
Beta
GPU Marketplace SLA Zone
SLA enforcement and on-chain dispute resolution for GPU marketplaces. Provides the provider_eligible Prolog rule plus reputational consequences Vast.ai, Akash, and Render do not.
compute SLA dispute
☁️
Live
Multi-Cloud AI Inference Zone
Wraps AWS, GCP, and Azure under a single governance layer with jurisdiction-aware routing, spot-arbitrage, and on-chain SLA settlement. 78% of enterprises run multi-cloud AI inference — this template is the missing governance surface.
multi-cloud spot-arbitrage jurisdictional-routing
📜
Draft
Audit-Grade Act Logger Zone
Evidence-export regime for production deployments. Captures immutable act logs, exports W3C-RDF provenance records, and integrates with Cognitarium for downstream compliance tooling.
evidence immutable-log w3c-rdf
⚖️
Beta
Opposable Dispute Settlement Zone
Cross-org opposability for acts of consequence. Pairs Pactum Solidity contracts with IBC-routed settlement so a Zone on axone-1 can challenge, contest, and settle acts against counterparts on any IBC-connected chain.
pactum opposability ibc

How to instantiate a template

Three steps from a typed artifact to a running Zone on axone-1. Reproducibility is a chain-level invariant: an operator can prove the Zone in production is the Zone the auditors reviewed, without trusting a build server.

STEP 01
Pick a template
Choose from the library above, or fork a published template into your organization's regime registry. The template ships with a typed slot list and an explicit regime-hash contract.
STEP 02
Fill the typed slots
Each slot is a typed Prolog term: slot(zone_id, atom), slot(quorum, integer), slot(jurisdictions, list). Mismatched types are rejected at compile time, not at runtime.
STEP 03
Zone ships with on-chain regime hash
The Zone is not "running" until its template reference, version, and slot values are recorded against the template hash on Layer 1. Every deployed instance is reproducible from the registry — rollouts, audits, and rollbacks all share one canonical artifact.

Ship your first governed Zone

Pick a template, fill the slots, deploy. The regime-template pattern is how AxoneOS becomes operable at enterprise scale.