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.
Each template family answers a different operating question. Most production Zones compose templates from more than one family.
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.
slot(zone_id, atom) and slot(quorum, integer) slots, RBAC buckets, and a hand-off to an operational resource envelope. Demonstrated in the regime-template walkthrough.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.
slot(zone_id, atom), slot(quorum, integer), slot(jurisdictions, list). Mismatched types are rejected at compile time, not at runtime.
Pick a template, fill the slots, deploy. The regime-template pattern is how AxoneOS becomes operable at enterprise scale.