Implementation Plan: GovernedSpeed™ Runtime (Consolidated)

Consolidation Notice: This plan unifies P007 (Governed Execution), P021 (CALM Governance), and P030 (Governance Invariants) per ADR-031, which adopts GovernedSpeed™ as the integrated governance substrate.

Supersession: SDS-042 (Policy Gateway) and SDS-043 (Risk & Evidence) are superseded by SDS-047 (GovernedSpeed™ Governance Runtime). See REF-012 §10 for the Active Invariant Catalog.

Purpose

Deliver the unified governance plane for SEA-Forge™: runtime policy enforcement (Policy Gateway), evidence collection (Risk & Evidence), architectural validation (CALM), and system-wide invariant enforcement — all operating as a single cohesive substrate per the GovernedSpeed™ integration strategy.

Pre-Flight Validation

ADR Validation

PRD Validation

SDS Validation

REF-012 Validation

Provenance & Traceability

Architectural Decisions (ADRs)

Product Requirements (PRDs)

Software Design Specifications (SDS)

Reference Documents

Provenance Chain

graph TD
  ADR31[ADR-031: GovernedSpeed™ Integration] --> PRD10[PRD-010: AI Governance Runtime]
  ADR31 --> PRD21[PRD-021: GovernedSpeed™ Platform]
  ADR28[ADR-028: LLMOps] --> PRD10
  ADR05[ADR-005: CALM] --> PRD04[PRD-004: Architectural Compliance]
  ADR05 --> PRD05[PRD-005: Transparency]

  PRD10 --> SDS47[SDS-047: GovernedSpeed™ Runtime]
  PRD21 --> SDS47
  PRD04 --> SDS39[SDS-039: CALM CLI]
  PRD05 --> SDS39

  SDS47 --> SDS42[SDS-042: SUPERSEDED]
  SDS47 --> SDS43[SDS-043: SUPERSEDED]

  ADR01[ADR-001: Core Principles] --> REF12[REF-012 §10: Invariant Catalog]
  ADR14[ADR-014: CRL] --> REF12
  REF12 --> SDS35[SDS-035: SUPERSEDED]

  subgraph "Target Specs (Active)"
    SDS47
    SDS39
    REF12
  end

  subgraph "Superseded (Do Not Reference)"
    SDS42
    SDS43
    SDS35
  end

  style SDS42 fill:#ffcccc
  style SDS43 fill:#ffcccc
  style SDS35 fill:#ffcccc

Architecture and Design

Component Overview

Design Principles Applied

• Isomorphism: Policies, decision records, and evidence artifacts remain schema-identical across spec → generated contracts.
• Invariants: Fail-closed enforcement (PRD-010 REQ-GS-001), no silent overrides (REF-012 §10 + SDS-031).
• Idempotency: Decision logging and evidence submission dedupe by event/artifact IDs (SDS-047).
• Compliance-as-Code: Regulatory requirements (NIST AI RMF, ISO 42001, EU AI Act) are machine-readable OSCAL schemas validated in CI.

Dependency Justification

GovernedSpeed™ Runtime Dependencies

CALM Ecosystem Dependencies

Compliance-as-Code Dependencies

Expected Filetree

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
/
├── docs/specs/shared/sds/
│   ├── 047-governedspeed-governance-runtime.sds.yaml  # PRIMARY SPEC
│   ├── 039-calm-cli-service.md
│   ├── 046-governedspeed-integration.md
│   ├── 031-authority-ownership-boundaries.md
│   ├── 042-policy-gateway-service.md       # SUPERSEDED marker only
│   └── 043-risk-evidence-service.md        # SUPERSEDED marker only
├── docs/specs/.internal/
│   └── 012-invariant-regime.md             # REF-012 with §10 Active Catalog
├── schemas/
│   ├── events/governance/
│   │   ├── governance-decision.schema.json
│   │   ├── evidence-artifact.schema.json
│   │   └── waiver-record.schema.json
│   └── compliance/
│       ├── oscal/
│       │   ├── eu-ai-act.profile.json
│       │   ├── nist-ai-rmf.profile.json
│       │   └── iso-42001.profile.json
│       └── opa/
│           ├── bias-threshold.rego
│           └── training-transparency.rego
├── infra/
│   └── compliance/
│       └── lula-validation.yaml
└── .github/workflows/
    └── governance-gate.yml

Proposed Cycles (Worktree-First)

Task Breakdown

Wave 1: Contract Definitions (Parallel)

• C1A: Finalize SDS-047 GovernedSpeed™ Runtime contracts
  • Implements: PolicyGateway, RiskEvidenceService, FilterDecision, EvidenceArtifact entities
  • Satisfies: PRD-010 REQ-GS-001..005
  • Files: schemas/events/governance/*, docs/specs/shared/sds/047-governedspeed-governance-runtime.sds.yaml
  • Validation: just sds-validate docs/specs/shared/sds/047-governedspeed-governance-runtime.sds.yaml
• C1B: Finalize CALM CLI service contract
  • Implements: Validation, visualization, compliance commands
  • Satisfies: PRD-004/PRD-005
  • Files: docs/specs/architectural-governance/sds/039-calm-cli-service.md
• C1C: Finalize Invariant Regime §10 Active Catalog
  • Implements: Active invariant catalog schema + 15 system invariants from ADR-001
  • Satisfies: ADR-001, ADR-014, ADR-016
  • Files: docs/specs/.internal/012-invariant-regime.md §10

Wave 2: Compliance Infrastructure (Depends on Wave 1)

• C2A: Create OSCAL compliance profiles
  • Implements: EU AI Act, NIST AI RMF, ISO 42001 → technical controls mapping
  • Satisfies: REF-020 IAGPM-GenAI Framework
  • Files: schemas/compliance/oscal/*.profile.json
  • Tool: Trestle for profile management
• C2B: Create OPA policy rules
  • Implements: Bias threshold validation, training data transparency checks
  • Satisfies: PRD-010 (AI governance metrics)
  • Files: schemas/compliance/opa/*.rego

Wave 3: Integration (Depends on Wave 2)

• C3A: Integrate evidence with governance runtime
  • Implements: Giskard evidence artifacts hashed to IFL, SDS-047 submission API
  • Satisfies: PRD-021, SDS-047
  • Files: Adapter implementations in libs/shared/adapters/evidence/
• C3B: Wire authority and separation-of-duties hooks
  • Implements: SDS-031 RBAC model, non-delegable approvals, waiver workflow
  • Satisfies: SDS-031, REF-012 §governance
  • Files: docs/specs/shared/sds/031-authority-ownership-boundaries.md

Wave 4: CI Enforcement (Depends on Wave 3)

• C4A: Create governance CI gate
  • Implements: GitHub Actions workflow using Lula + OPA validation
  • Satisfies: PRD-010, PRD-004 (fail-on-non-compliant)
  • Files: .github/workflows/governance-gate.yml, infra/compliance/lula-validation.yaml
  • Gate Behavior: Fail-closed for critical invariants; warn-only for performance invariants

Validation & Verification

Spec Validation

• SDS-047 schema validates: just sds-validate docs/specs/shared/sds/047-governedspeed-governance-runtime.sds.yaml
• REF-012 §10 references correct invariant IDs from ADR-001
• SDS-039 CALM CLI contract complete with validation/visualization modes
• No references to superseded SDS-042, SDS-043, or SDS-035 in active plans

Implementation Validation

• Policy Gateway sidecar intercepts LLM calls and evaluates policies
• Evidence artifacts are SHA256 hashed and persisted to Risk & Evidence ledger
• CALM validation runs in CI and fails on architectural violations
• Invariant regime violations block merges in production environments
• Waiver workflow requires approvals per SDS-031 and produces audit records

Determinism Check

1
2
3
just pipeline governance-runtime
just regen-check docs/specs/governance-runtime/governance-runtime.manifest.json
git diff --exit-code  # Must be clean

Open Questions

1. OSCAL Profile Sourcing: Should we use existing NIST OSCAL catalogs or create SEA-specific mappings? → Prefer existing + overlay
2. Waiver Storage: Where should waiver records be stored? → SDS-047 Risk & Evidence Service + IFL anchor
3. Invariant Enforcement Mode: Which invariants are warn-only in staging? → Performance + experimental, NEVER safety

Risks & Mitigation

Rollback Strategy

1. Disable CI governance gate via feature flag (SEA_GOVERNANCE_GATE_ENABLED=false)
2. Temporarily downgrade non-critical invariants to warnings
3. Critical (safety) invariants remain fail-closed always

Related Documents

Active Specifications

Superseded Specifications (Do Not Reference)

Archived Plans