Offline Operations

Purpose

Keep offline and air-gap workflows as a first-class operational capability without reviving a second product tree.
Make Offline Kit, Feeds & Airgap, and evidence export handoffs usable from the active Ops > Operations shell.

Owner shell: Ops > Operations
Primary routes:
- /ops/operations/offline-kit
- /ops/operations/offline-kit/dashboard
- /ops/operations/offline-kit/bundles
- /ops/operations/offline-kit/verify
- /ops/operations/offline-kit/jwks
- /ops/operations/feeds-airgap
- /setup/trust-signing/transparency for Attestor transparency schedule/import exchange
Secondary linked destinations:
- /evidence/exports
- /evidence/verify-replay
- /setup/trust-signing

Preserve old bookmarks and stale menu links by redirecting:
- /ops/offline-kit/*
- /ops/feeds/*
- /platform-ops/*
- /platform/ops/*
Redirects must preserve query params and fragments so tab or action state survives the handoff.

Offline Kit owns bundle management, offline verification, and trust-material inspection.
Feeds & Airgap owns mirror freshness, version-lock posture, and air-gap entry actions.
Feeds & Airgap links to the Trust & Signing transparency workflow for external mirror schedule/import exchange instead of duplicating certificate and target controls.
Feeds & Airgap must expose a direct advisory/VEX source-management handoff in the page header so operators can correct stale or disconnected source state from the owner surface.
Evidence Exports remains Evidence-owned, but Offline Kit must link into it for portable bundle generation.
Single actions like Import Bundle and Export Bundle should not become standalone products; they route into a tabbed or action-aware owner page.

Keep:
- offline bundle loading and activation
- offline verification history and report export
- trust-anchor inspection and export
- feed freshness and version-lock context
- evidence export and replay handoffs
Why:
- offline and air-gap operation is a real product differentiator, not a prototype branch
- release evidence, trust material, and feed provenance all need an operator home when the site is disconnected

Canonical Ops > Operations routes and stale alias repair for deep offline links.
Route-aware Feeds & Airgap tab state and action banners.
Direct Transparency Exchange handoff to /setup/trust-signing/transparency.
Working Offline Kit shortcuts into Evidence and Trust surfaces.
Bundle export, verification detail drill-in, verification report export, and trust-anchor inspection/export.