# Air-gap bundles and formats

Air-gapped deployments use signed bundles with deterministic manifests. Bundles
are verified before import and tracked by mirror generation.

Bundle types
- Mirror and bootstrap bundles (images, charts, plugins).
- Advisory and VEX bundles with AOC guardrails.
- Risk and EPSS bundles for scoring.
- Symbol bundles for reachability overlays.
- Evidence bundles for findings and decisions.
- Revocation bundles for Authority token and key revocations.

Bundle format (offline bundles)
- Archive: .stella.bundle.tgz with deterministic tar settings.
- manifest.json lists entries with sha256 hashes and sizes.
- DSSE envelope signs the manifest payload.
- Optional receipt.json records import verification and audit metadata.

Manifest rules
- Sorted keys and stable ordering.
- SHA-256 digests for every entry.
- root_hash over all entries for quick validation.

Time anchors and staleness
- Time anchors are signed snapshots of time source state.
- Staleness checks gate use of bundles in sealed mode.
- Offline bundles should include time anchor and staleness metadata.

Sealed mode expectations
- Deny-all egress; only registered bundles are accepted.
- Imports emit audit events and are tracked by mirrorGeneration.
- UI displays sealed-mode banner with manifest hash and time anchor status.

Verification workflow
- Verify archive hash and DSSE signature.
- Validate manifest and any schema-specific entries.
- Reject bundles with missing provenance or invalid hashes.

Related references
- docs/airgap/overview.md
- docs/airgap/offline-bundle-format.md
- docs/airgap/staleness-and-time.md
- docs/airgap/portable-evidence.md
- docs/airgap/symbol-bundles.md
- docs/security/revocation-bundle.md