Files
git.stella-ops.org/docs/modules/ui/offline-operations/README.md
master 7943cfb3af chore(docs+devops): cross-module doc sync + sprint archival moves + compose updates
Bundled pre-session doc + ops work:
- docs/modules/**: sync across advisory-ai, airgap, cli, excititor,
  export-center, findings-ledger, notifier, notify, platform, router,
  sbom-service, ui, web (architectural + operational updates)
- docs/features/**: updates to checked excititor vex pipeline,
  developer workspace, quick verify drawer
- docs top-level: README, quickstart, API_CLI_REFERENCE, UI_GUIDE,
  code-of-conduct/TESTING_PRACTICES updates
- docs/qa/feature-checks/: FLOW.md + excititor state update
- docs/implplan/: remaining sprint updates + new Concelier source
  credentials sprint (SPRINT_20260422_003)
- docs-archived/implplan/: 30 sprint archival moves (ElkSharp series,
  misc completed sprints)
- devops/compose: .env + services compose + env example + router gateway
  config updates

File-level granularity preserved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-22 16:06:39 +03:00

57 lines
2.5 KiB
Markdown

# 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.
## Canonical Owner
- 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`
- Secondary linked destinations:
- `/evidence/exports`
- `/evidence/verify-replay`
- `/setup/trust-signing`
## Legacy Alias Policy
- 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.
## UX Rules
- `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` 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.
## Preserved Value
- 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
## Shipped In This Cut
- Canonical `Ops > Operations` routes and stale alias repair for deep offline links.
- Route-aware `Feeds & Airgap` tab state and action banners.
- Working Offline Kit shortcuts into Evidence and Trust surfaces.
- Bundle export, verification detail drill-in, verification report export, and trust-anchor inspection/export.
## Related Docs
- `docs/modules/ui/platform-ops-consolidation/README.md`
- `docs/features/checked/web/offline-operations-ui.md`
- `docs/modules/ui/component-preservation-map/RESTORATION_PRIORITIES.md`