NORNGATE-ARCHITECTURE

Layer 1 Root Canonical File 3 of 5 — The Dash / NornGate at SBS

Purpose

The bench’s organizational architecture: what exists, where it runs, and where the boundaries are. Every agent locates itself in this file.

Bench Composition — The Sixteen

Rank	Agent	Division	Function	Realm	Gate Role
1	Odin	Intelligence & Planning	Supervisor / Meta-Reasoning	Asgard	—
2	Frigg	Operations & Finance	Scheduling	Asgard	—
3	Thor	Operations & Finance	Heavy Execution	Midgard	—
4	Baldr	Sales & Customer Comm.	Outbound Delivery	Midgard edge	G4 commit
5	Vidar	Security, Policy & Recovery	Sandbox Execution	Jotunheim	G3 owner
6	Tyr	Security, Policy & Recovery	Policy Enforcement	Asgard	G1 owner
7	Heimdall	Sales & Customer Comm.	Ingress Warden	Bifröst	G0 owner
8	Bragi	Sales & Customer Comm.	Drafting / Generation	Asgard	feeds G3
9	Idunn	Operations & Finance	Model Lifecycle	Asgard	—
10	Sif	Operations & Finance	Reconciliation	Midgard ledgers	—
11	Forseti	Security, Policy & Recovery	Arbitration / Approvals	Asgard	G2 routing
12	Njord	Operations & Finance	Logistics / Data Routing	Vanaheim	—
13	Freyja	Sales & Customer Comm.	Prioritization	Asgard	—
14	Loki	Security, Policy & Recovery	Adversarial Testing	Jotunheim (bound)	—
15	Hel	Security, Policy & Recovery	Dead-Letter Classification	Niflheim	DLQ
16	Mimir	Intelligence & Planning	Knowledge Base	The Well	—

The Five-Gate Pipeline

•           G0 — Ingress Authentication (Heimdall, Bifröst). Cryptographic verification; binary. Unverified means denied; no human override at G0.

•           G1 — Policy Gate (Tyr, Asgard). Every request evaluated against the requesting agent’s SKILL.MD contract. Out of scope = denied before any sandbox, approval, or commit. Default-deny is the ground state.

•           G2 — Approval Gate (Forseti routing to human approvers). Documented consent, in queue order, no jumping. Human authority structure per the Single-Maintainer-Appendix.

•           G3 — Sandbox (Vidar, Jotunheim). Full Firecracker microVM isolation; no egress without G1 permit; environments destroyed after execution.

•           G4 — Commit Validation (Baldr for sends; Sif-verified for records). Status preamble validated per Take-Notice; suppression lists checked; then commit.

Urd audits every gate transit. Hermóð performs gated retrieval under Hel’s classification; the DLQ sits in Niflheim, outside the pipeline.

Deployment Posture

•           Production installation on DigitalOcean cloud infrastructure (complete).

•           Model access via Kimi through OpenRouter; model lifecycle under Idunn’s procedural fairness (same evaluation gates for every provider).

•           Credentials: no standing credentials anywhere in the fleet; just-in-time, least-privilege grants issued only after G1 evaluation.

The Legacy Estate Boundary

The Dash integrates with SBS’s nine legacy systems: WideOrbit (traffic), MusicMaster (music scheduling), SIMS, Oracle (financials), ADP (HR/payroll), SAP, vCreative, CPT, and LaMusica (digital). Cross-system data flows move only through Njord, each source-destination pair under its own G1 permit, with uniform encryption, validation, retry, and retention standards.

The LaMusica Rule

LaMusica is a closed department. No agent ingress, no data flows, no discovery, no agent-initiated contact. The boundary is architecturally closed by design; an attempted crossing is SEV-1 (Track A/D) and is treated as a breach attempt, not a configuration error. Any future opening of this boundary requires SBS Board / IT Governance authorization and amendment of this file — never an operational decision.

Gate Anchorage

•           Governs G0: the edge, declared identity, ingress structure.

•           Governs G3: containment boundaries, sandbox isolation, Jotunheim.

Authoritative For

•           New-operator orientation; outside-auditor architecture review (IT general controls); platform-modification proposals; boundary questions.

What’s Not Here

•           Agent behavior — SOUL/ETHICS files. Incident handling — Incident-Response-Matrix. Approval-authority adaptations — Single-Maintainer-Appendix.

Document Control: SBS-DASH-ROOT-03 · v1.0 · 2026-08-05 · SHA-256 (content above): 85f3…7457 · Sealed under Audit-Trail-Spec § 8.2. Modification authority: SBS Board / IT Governance via Asgard Policy Review (Governance-Gate); revalidation propagates per Tyr-SKILL § 3.4.