Files
git.stella-ops.org/docs/modules/ui/v2-rewire/pack-23.md
2026-02-20 23:32:20 +02:00

86 lines
2.6 KiB
Markdown

# Pack 23 - Platform Global Ops/Integrations/Setup Advisory Delta
Status: Active high-precedence authority for Platform IA and ownership
Date: 2026-02-20
Precedence: Overrides `pack-22.md` and lower packs for overlapping Platform navigation, ownership, and operator workflow behavior.
## 1) Intent
- Make `Platform` a global root and consolidate operability into one module shell.
- Keep three explicit Platform subdomains:
- `Ops`,
- `Integrations`,
- `Setup`.
- Reduce cognitive load by consolidating operations surfaces around decision impact.
## 2) Canonical Platform model
### 2.1 Platform as global root
- `Platform` is a top-level module.
- `Integrations` and `Setup` are no longer separate top-level roots.
- Canonical IA under Platform:
- `/platform/ops/*`
- `/platform/integrations/*`
- `/platform/setup/*`
### 2.2 Ops workflow priority
Ops primary workflows:
1. `Data Integrity`
2. `Jobs & Queues`
3. `Health & SLO`
Ops secondary tools:
- `Feeds & Airgap`
- `Quotas & Limits`
- `Diagnostics`
### 2.3 Ownership boundaries
- `Topology` owns hosts/targets/agents management.
- `Platform Integrations` owns external systems only:
- Registries,
- SCM,
- CI/CD,
- Runtimes / Hosts (connectors only),
- Advisory sources,
- VEX sources,
- Secrets.
- `Platform Setup` owns inventory and orchestration setup:
- Regions & Environments,
- Promotion Paths,
- Workflows & Gates,
- Gate Profiles,
- Release Templates.
- Feed Policy,
- Defaults & Guardrails.
## 3) Degraded/offline UX contract
Platform operator views must provide:
- explicit decision impact label (`BLOCKING`, `DEGRADED`, `INFO`),
- retry controls,
- copyable correlation ID,
- last-known-good/read-only context when live dependencies degrade.
## 4) Route mapping directives
- Keep legacy aliases for migration safety:
- `/integrations/*` -> `/platform/integrations/*`
- `/platform-ops/*` and `/operations/*` -> `/platform/ops/*`
- Legacy hosts/targets integration links must redirect to Topology:
- `/platform/integrations/hosts` -> `/topology/hosts`
- `/platform/integrations/targets*` -> `/topology/targets`
## 5) Planning and QA gates
- Platform nav and submenus reflect the Ops/Integrations/Setup split.
- Integrations screens do not present hosts/targets/agents as managed integration categories.
- Integrations include `Runtimes / Hosts` as connector category while inventory ownership remains in Topology.
- Setup routes render setup-owned pages, including `Feed Policy`, `Gate Profiles`, and `Defaults & Guardrails`.
- Focused FE route/nav/platform tests pass for changed surfaces before sprint closure.