REIGN · ARCHITECTURE REFERENCE
Reign Architecture. The technical reference.
Continuous Operational Assurance for Enterprise AI. Reign sits between probabilistic autonomous systems and deterministic enterprise infrastructure. This page is the architecture reference for technical readers.
What the spine guarantees by construction
Properties of the architecture itself, present in every deployment mode. Layered enforcement and defense in depth are the operating model; assurance is the artifact the spine produces.
- Runtime enforcement. Every AI and agent call gated at the boundary, identity-bound, policy-evaluated, and recorded.
- Independent validation. Approved-model registry, validation harnesses, drift detection, predetermined change-control plans, executed outside the build pipeline.
- Tamper-evident attestation. Append-only ledger of every AI and agent decision, with cryptographic chain-of-custody for downstream evidence.
- Deployment-mode parity. Identical control plane across SaaS, Dedicated, Customer Cloud, and Air-Gapped. Sovereignty is a deployment property, not a separate codebase.
Mapped to the frameworks regulated industries answer to
Four components. One technical reference.
Each component is a discrete control surface with its own API, identity model, data plane, and deployment topology. Together they form a layered enforcement and attestation pipeline. Click through for component-level reference.
Runtime enforcement
AI Gateway
Identity-bound policy decision point at the boundary. MCP-native. Every AI and agent call evaluated against policy and logged before it reaches the model or the tool.
Independent validation
Model Risk Validation
Approved-model registry, validation harnesses, drift detection, predetermined change-control plans. Executed independently of the team that built or trained the system.
Tamper-evident attestation
Audit Ledger (CAVR)
Append-only, cryptographically chained record of every AI and agent decision. Continuous Audit, Validation and Reporting. Source of truth for downstream evidence.
Independent assurance
Assurance Packs
Regulator-facing evidence bundles assembled from ledger artifacts and mapped to the framework your industry answers to. Submission-ready output of the spine.
Where Reign sits, and what it is not
Reign is a control plane for AI and agent execution. It is not an MLOps platform, not a SIEM, not a GRC tool, and not a model-serving runtime. It sits between probabilistic systems (models, agents, copilots) and the deterministic systems they have to operate inside (identity, data, change control, audit). The spine is what makes that boundary enforceable, observable, and attestable in the same control surface.
Three Lines of Defense terminology shows up at the audit and assurance boundary, but it is not the dominant view here. For that framing see Reign for Audit and the Three Lines of Defense reference. This page is the engineering view.
The Autonomy Assurance Maturity Model describes the trajectory from ad-hoc oversight to continuous operational assurance. The Reign Architecture is what you deploy to operate at the upper levels.
Read this reference alongside the capability pages
The four components map to three operational capabilities. Read up into those for the buyer-level view, or down into Forge AI Substrate for the operating layer Reign deploys onto.
Capability
Pre-action Assurance
Gateway-level policy evaluation before any AI or agent action commits.
Capability
Outcome Validation
Independent validation of model and agent outcomes against approved behaviour.
Capability
Residual Risk
What the ledger and assurance packs surface about the risk the system still carries.
Take this reference into a technical conversation
Reign is being hardened with a small set of Tier 1 design partners through 2026. Limited intake. Ninety-day pilots. Audit-grade evidence. Engineering conversations are open before that.