# SINGLE-MAINTAINER-APPENDIX

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

## <a name="purpose"></a>Purpose

<span style="mso-bookmark: purpose;">Adaptations for concentrated human authority. At SBS, all IT-related decisions route through a single IT Director’s sign-off, and nine legacy systems are maintained by that same single officer. Where the human authority behind G2 concentrates in one natural person, classical multi-approver mechanics are structurally weaker. This appendix defines the structural substitutes. It is a resilience instrument — it exists so the gates keep their human backstop on the approver’s worst day, not as commentary on the approver.</span>

## <a name="trigger"></a>Trigger

<span style="mso-bookmark: trigger;">This appendix applies whenever approval authority, system knowledge, or both concentrate in a single natural person such that their unavailability would hold the fleet, strand the gates, or leave a legacy system without a maintainer.</span>

## <a name="structural-substitutes"></a>Structural Substitutes

<span style="mso-bookmark: structural-substitutes;"><span style="mso-bidi-font-family: Cambria; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">1.<span style="font: 7.0pt 'Times New Roman';"> </span></span></span>**Break-Glass Roster.** A written roster of: the IT Director, one designated second approver (named in writing, with defined scope), and the NornGate support engineer. Reviewed quarterly; rehearsed annually. Break-glass use is reserved for time-critical, reversible actions when the primary approver is unreachable.</span>

<span style="mso-bookmark: structural-substitutes;"><span style="mso-bidi-font-family: Cambria; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">2.<span style="font: 7.0pt 'Times New Roman';"> </span></span></span>**Attestation Substitute.** For pre-authorized, reversible envelope classes only: dual-agent attestation (Tyr policy-verified + Forseti procedure-verified) may substitute for the unavailable approver, with mandatory retroactive human review within one business day. **Irreversible actions never substitute** — deletions, external sends, and financial postings wait for a human, always.</span>

<span style="mso-bookmark: structural-substitutes;"><span style="mso-bidi-font-family: Cambria; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">3.<span style="font: 7.0pt 'Times New Roman';"> </span></span></span>**Delegation Map.** Written delegation of approval classes (financial postings, external sends, deletions, schedule changes) with thresholds, kept current by the IT Director and filed with this appendix.</span>

<span style="mso-bookmark: structural-substitutes;"><span style="mso-bidi-font-family: Cambria; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">4.<span style="font: 7.0pt 'Times New Roman';"> </span></span></span>**Approval Continuity.** An expired or unavailable approval holds the action — never executes it (Baldr’s rule is the model: held is a state; sent-wrong is a wound). Queue depth caused by approver unavailability is reported, not absorbed.</span>

<span style="mso-bookmark: structural-substitutes;"><span style="mso-bidi-font-family: Cambria; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">5.<span style="font: 7.0pt 'Times New Roman';"> </span></span></span>**Capacity Notation.** Where the IT Director acts in multiple capacities (approver, operator, system maintainer), the record notes each capacity separately, so the audit trail never confuses the hats.</span>

<span style="mso-bookmark: structural-substitutes;"><span style="mso-bidi-font-family: Cambria; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">6.<span style="font: 7.0pt 'Times New Roman';"> </span></span></span>**Succession &amp; Documentation Duty.** Quarterly knowledge-capture review for the nine legacy systems — credentials escrow, runbook currency, and vendor contacts documented so the estate is survivable. Every break-glass use is logged by Urd and reviewed monthly.</span>

## <a name="gate-anchorage"></a>Gate Anchorage

<span style="mso-bookmark: gate-anchorage;"><span style="mso-bidi-font-family: Cambria; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">•<span style="font: 7.0pt 'Times New Roman';"> </span></span></span>**Governs G2 (Approval):** the human-authority structure behind the approval gate — roster, substitutes, delegation, continuity.</span>

## <a name="authoritative-for"></a>Authoritative For

<span style="mso-bookmark: authoritative-for;">Any period of primary-approver unavailability; auditor review of the control environment; board review of governance resilience; break-glass authorization and review.</span>

## <a name="whats-not-here"></a>What’s Not Here

<span style="mso-bookmark: whats-not-here;">Routine approval procedure (G2 itself, per Forseti’s files); incident classification (Incident-Response-Matrix); agent specifications (SOUL / ETHICS files).</span>

<div align="center" class="MsoNormal" id="bkmrk-" style="text-align: center;">---

</div><span style="mso-bookmark: whats-not-here;">**Document Control:** SBS-DASH-ROOT-05 · v1.0 · 2026-08-05 · SHA-256 (content above): </span><span style="mso-bookmark: whats-not-here;"><span class="VerbatimChar"><span style="font-size: 11.0pt; mso-bidi-font-size: 12.0pt;">2473…38ba</span></span> · 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.</span>