DEPLOYMENT-PLAYBOOK

Layer 2 Procedural File 3 of 6 — The Dash / NornGate at SBS Implements: 00-NornGate-Architecture.md. Constraint: Phase 2 deploys only after Phase 1 is complete and Phase 2 is approved, inside the approved 30–45-day deployment window.

Purpose

The deterministic deployment sequence for Phase 2 — taking The Dash from approved plan to production across the Sales, Finance, and Traffic silos. Integration order is fixed: the legacy systems integrate first; silo workflows come after. Every phase has gate checkpoints, evidence requirements, and rollback criteria. A phase that cannot evidence its checkpoint does not advance.

The Nine Phases

Phase 0 — Readiness & Baseline Capture. System inventory verified against NornGate-Architecture; data samples pulled from each legacy system; approval roster and Delegation Map confirmed; Tyr’s policy baseline loaded; Freyja’s value framework signed off by the business owners. Checkpoint: baseline package sealed in Urd’s ledger.

Phase 1 — Provisioning & Genesis. DigitalOcean production environment verified; agent containers staged; genesis records written across Urd’s hash-chain; Heimdall’s G0 edge configured; Vidar’s Jotunheim pools tested. Checkpoint: genesis verification report.

Phase 2 — Per-Agent Configuration Load. Each agent’s SKILL contract registered at G1; realm assignments confirmed; credential brokering tested just-in-time with TTL; Take-Notice preambles verified on sample artifacts. Checkpoint: sixteen registered SKILL manifests, G1-evaluated clean.

Phase 3 — Legacy Connectors (first, before any silo workflow). Njord’s connectors to WideOrbit, MusicMaster, SIMS, Oracle, ADP, SAP, vCreative, and CPT — each source-destination pair under its own G1 permit (category 10, DA-class). LaMusica: no connector, no exception — the LaMusica Rule stands throughout. Checkpoint: per-pair flow verification, sent vs. received reconciled.

Phase 4 — Initial Reconciliation Cycles (read-only). Sif runs shadow reconciliation: accounting vs. CRM, orders vs. invoices, invoices vs. deposits. No correction authority — flags only. Tolerances declared and human-set. Checkpoint: first clean tie-out or a classified exception register.

Phase 5 — Governance Configuration. G2 category matrix loaded (10-Governance-Gate-Spec); authorization roles assigned; Break-Glass Roster named and rehearsed; timeout rules armed. Checkpoint: roster rehearsal record; matrix sign-off by IT Director.

Phase 6 — Dry-Run (shadow mode). Full pipeline against synthetic environments and shadow copies: Odin plans, Valkyries-style dispatch simulated, Thor executes to shadow targets, Baldr stages sends without release, Loki runs baseline probes inside Jotunheim, Hel catalogs every induced failure. Checkpoint: dry-run evidence package, including Loki’s findings closed or accepted.

Phase 7 — Production Cutover (narrow → wide). Limited live scope first: one silo, one workflow (recommended: the WideOrbit order-to-cash flow), PAWF classes only. Widening by G2 decision after each clean cycle. Checkpoint: two clean live cycles, Sif-verified.

Phase 8 — Deployment Audit Package. Delivered to the IT Director and board: integrity report, configuration manifest, dry-run evidence, first-cycle reconciliation summary, open-items register. This package is the reference baseline for all future oversight packages. Checkpoint: human acceptance recorded in the ledger. Phase 2 is done when the package is accepted, not when the software runs.

Rollback Doctrine

Every phase is reversible to the prior checkpoint. Rollback triggers are declared per phase before entry; Thor’s idempotency and Urd’s chain make rollback an execution problem, not a data-recovery problem.

Authoritative For

Phase 2 execution; board visibility into deployment posture; auditor review of change management.

What’s Not Here

Ongoing operations (10-Operating-Rhythm); approval categories (10-Governance-Gate-Spec); incident handling during deployment (00-Incident-Response-Matrix applies throughout).

Modification Protocol

Proposal drafted by the responsible agent → legal/sufficiency review where statutory interpretation is implicated → Odin staffs the synthesis pass → G2 request with full evidence package → human decision per the Single-Maintainer-Appendix authority structure. Approved modifications are versioned (1.0 → 1.1 minor; 1.x → 2.0 material) and captured in Urd’s ledger as policy_change-class records. Layer 1 files are not modified by this protocol — they require SBS Board / IT Governance authorization via Asgard Policy Review.

Document Control: SBS-DASH-PROC-03 · v1.1 · 2026-08-05 · SHA-256 (content above): 7eef…4fd7 · 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.