Air-Gap Sealed-Mode Startup Diagnostics

Audience: AirGap Controller and Observability engineers.

Purpose: define the startup guardrails that stop Stella Ops services from running when sealed-mode requirements are unmet, and the diagnostics and telemetry they emit.

When a deployment is sealed, services must fail closed at startup rather than run in a partially-trusted state. This guide specifies the pre-flight checks, the structured failure signals, and the telemetry hooks the controller and importer wire together.

Pre-flight checks

  1. airgap_state indicates sealed=true.
  2. Egress allowlist configured (non-empty or explicitly []).
  3. Trust root bundle + TUF metadata present and unexpired.
  4. Time anchor available (see TimeAnchor schema) and staleness budget not exceeded.
  5. Pending root rotations either applied or flagged with approver IDs.

On failure

Telemetry hooks

Integration points

Code references

Owners

AirGap Controller Guild · Observability Guild