ui fixes

docs/modules/ui/v2-rewire/source-of-truth.md

@@ -1,7 +1,7 @@
 # UI v2 Rewire Source of Truth
 
 Status: Active
-Date: 2026-02-20
+Date: 2026-02-21
 Working directory: `docs/modules/ui/v2-rewire`
 
 ## 1) Hard rules
@@ -15,6 +15,7 @@ Working directory: `docs/modules/ui/v2-rewire`
 4. Canonical planning references must come from this file plus `authority-matrix.md`, not raw packs alone.
 5. `pack-23.md` is the active Platform IA override for all conflicts with `pack-22.md` and lower packs.
 6. `pack-22.md` remains authority for non-Platform areas unless `pack-23.md` explicitly overrides them.
+7. Pre-alpha policy is canonical-only routing: no legacy redirects and no alias windows.
 
 ## 2) Canonical IA (v3)
 
@@ -26,8 +27,8 @@ Canonical top-level modules are:
 - `Releases`
 - `Security`
 - `Evidence`
-- `Topology`
-- `Platform`
+- `Ops`
+- `Setup`
 
 ### 2.2 Global context
 
@@ -39,7 +40,8 @@ Required global context controls:
 - Region multi-select
 - Environment multi-select scoped to Region selection
 - Time window selector
-- Status indicators (offline/feed/policy/evidence)
+- Stage selector
+- Status indicators (offline/feed/policy/evidence/live event stream)
 
 ### 2.3 Ownership decisions resolved by precedence
 
@@ -47,16 +49,17 @@ These are authoritative for planning and replace older conflicting placements:
 
 - `Release Control` root is decomposed:
   - release lifecycle surfaces move to `Releases`,
-  - inventory/setup surfaces move to `Topology`.
+  - inventory/topology surfaces move to `Setup -> Topology`.
 - `Bundle` is deprecated in operator IA and renamed to `Release Version`.
 - `Runs`, `Deployments`, `Promotions`, and `Hotfixes` are lifecycle views inside `Releases` and not top-level modules.
 - `VEX` and `Exceptions` remain distinct data models, but are exposed in one operator workspace:
   - `Security -> Disposition Center` tabs (`VEX Statements`, `Exceptions`, `Expiring`),
-  - feeds/source configuration lives in `Platform -> Integrations -> Feeds`.
+  - feeds/source configuration lives in `Ops -> Integrations -> Advisory & VEX Sources`.
 - SBOM Graph/Lake are one `Security -> SBOM` workspace with mode tabs.
 - Reachability is a first-class surface under `Security -> Reachability`.
-- `Policy Governance` remains administration-owned under `Platform -> Setup`.
-- Trust posture is visible in `Evidence`, while signing/trust mutation stays in `Platform -> Setup -> Trust & Signing`.
+- Topology ownership is setup-owned under `Setup -> Topology`.
+- Policy and former Platform ownership are consolidated under `Ops`.
+- Trust posture is visible in `Evidence`, while signing/trust mutation stays under `Ops` setup/policy surfaces.
 
 ## 3) Canonical screen authorities
 
@@ -95,11 +98,12 @@ Superseded:
 
 - Standalone menu treatment from earlier packs where runs/deployments/promotions/hotfixes were separate roots.
 
-### 3.4 Topology
+### 3.4 Setup + Topology
 
 Authoritative packs:
 
-- `pack-22.md` for module ownership and taxonomy.
+- `pack-22.md` for topology taxonomy and environment detail structure.
+- `pack-23.md` for platform ownership moves now consolidated under `Ops`.
 - `pack-18.md` for environment detail shell standards reused inside topology-aware views.
 
 ### 3.5 Security
@@ -120,11 +124,11 @@ Authoritative packs:
 - `pack-22.md` for evidence navigation framing and release linkage expectations.
 - `pack-20.md` for evidence chain structure (packs/export/proof/replay/audit).
 
-### 3.7 Operations
+### 3.7 Ops
 
 Authoritative packs:
 
-- `pack-23.md` for Platform Ops placement and workflow prioritization.
+- `pack-23.md` for Platform + Policy + Integrations consolidation under one root.
 - `pack-15.md` for data integrity operating model.
 - `pack-10.md` for feeds/airgap operational detail where still valid.
 
@@ -135,7 +139,7 @@ Authoritative packs:
 - `pack-23.md` for Platform Integrations placement and topology ownership split.
 - `pack-10.md` and `pack-21.md` for connector detail flows where not overridden.
 
-### 3.9 Platform Administration
+### 3.9 Setup Administration
 
 Authoritative packs:
 
@@ -153,10 +157,12 @@ Use these terms in sprint tickets/specs:
 - `Security & Risk` -> `Security`
 - `Evidence & Audit` -> `Evidence`
 - `Evidence Pack/Bundle` -> `Decision Capsule`
-- `Platform Ops` -> `Platform -> Ops`
-- `Integrations` root -> `Platform -> Integrations` (alias-window only at `/integrations`)
-- `Setup` root -> `Platform -> Setup` (includes administration-owned setup/governance)
-- `Regions & Environments` menu -> `Topology` module + global context switchers
+- `Platform Ops` -> `Ops`
+- `Policy` -> `Ops -> Policy`
+- `Integrations` -> `Ops -> Integrations`
+- `Administration` -> `Setup`
+- `Topology` root -> `Setup -> Topology`
+- `Regions & Environments` menu -> `Setup -> Topology` + global context switchers
 
 ## 5) Planning gaps to schedule first
 
@@ -164,6 +170,6 @@ Create first-wave dependency sprints for:
 
 - backend global context contracts and persistence (`Region/Environment` top-bar model),
 - releases read-model contracts for list/detail/activity/approvals queue,
-- topology inventory contracts and synchronization,
+- setup-owned topology inventory contracts and synchronization,
 - security disposition aggregation contracts (VEX + Exceptions UX join),
-- route deprecation map from `/release-control/*`, `/security-risk/*`, `/evidence-audit/*`, `/platform-ops/*` to canonical paths.
+- route retirement cleanup from legacy families to canonical pre-alpha roots with no redirect compatibility layer.