feat(ui): ship offline operations cutover
This commit is contained in:
55
docs/modules/ui/offline-operations/README.md
Normal file
55
docs/modules/ui/offline-operations/README.md
Normal file
@@ -0,0 +1,55 @@
|
||||
# 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.
|
||||
- `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`
|
||||
Reference in New Issue
Block a user