Home

The gated runtime for AI agent fleets. Every consequential action is verified before any side effect occurs — deterministically, fail-closed, and fully audited.

This wiki is the map. NornGate is a deterministic, fail-closed control plane that sits in front of agent tool execution. Most agent systems let actions happen immediately — a retrieval hits storage, a message reaches an API, a workflow mutates state — and control, if it exists at all, is post-hoc. NornGate inverts this: every consequential action an agent attempts must clear a five-gate pipeline before it is committed.

Core thesis — the runtime is the product. Inference is COGS. NornGate does not resell tokens; it sells verified outcomes. Billing is per G4-verified outcome, never per token — you pay for actions that provably cleared every gate, not for the model calls behind them.

Silence means no. If any gate cannot explicitly approve an action, the action stops. Default-deny is the ground state of the runtime, not a setting you turn on.

---

Navigate

	Section	What is inside
ᛟ	Introduction	What NornGate is, and why the gated model exists.
ᚱ	Getting Started	Install, Quickstart, and your first project.
ᚲ	Core Concepts	The five pillars, the Spine, the Nine Worlds, the five gates, determinism, fail-closed.
ᛏ	Guides	Configuring gates, subdomains (realms), integrating agents, observability, the Ragnarök drill.
ᛗ	Reference	API, configuration, glossary, error codes, CLI.

---

ᚨ Sources

Eddic corpus (naming doctrine). Snorri Sturluson, Prose Edda (Gylfaginning — the Norns, Yggdrasil, Baldr, Ragnarök); the Poetic Edda (Völuspá — cosmology and the Nine Worlds). The rune meanings above follow the Elder Futhark tradition. The mapping from these sources to platform controls is maintained as a first-class artifact, not flavor text.

Internal design docs. CORE-STRUCTURE.md (naming doctrine, realm→subdomain mapping, god→agent registry, Norn telemetry triad) and the platform white paper / light paper (gate taxonomy, per-outcome billing model).