# UI v2 Rewire Source of Truth

Status: Active
Date: 2026-02-18
Working directory: `docs/modules/ui/v2-rewire`

## 1) Hard Rules

1. For overlapping guidance, higher pack number wins.
2. If a higher pack is partial, keep the latest lower-pack detail for uncovered screens.
3. Inside one pack, interpret in this order: `Now/New location` statements, menu/screen graphs, then ASCII/rationale text.
4. Canonical planning references must come from this file plus `authority-matrix.md`, not raw packs alone.

## 2) Canonical IA (v2)

### 2.1 Root domains

Canonical root domains are:
- `Dashboard` (release mission board)
- `Release Control`
- `Security & Risk`
- `Evidence & Audit`
- `Integrations`
- `Platform Ops`
- `Administration`

Rationale:
- `Dashboard` is last explicitly upgraded as a release-centric entrypoint in Pack 16.
- Root domain framing is explicit in Pack 21 and remains the governing top-level grouping.

### 2.2 Ownership decisions resolved by higher-pack precedence

These are authoritative for planning and replace older conflicting placements:
- `Policy Governance` belongs to `Administration` (Pack 21 overrides Packs 5/9/11).
- `Trust & Signing` belongs to `Administration`, with consumption links from Evidence/Security (Pack 21 overrides Packs 9/11/20 on ownership).
- `System` belongs to `Administration` with operational drilldowns into `Platform Ops` (Pack 21 overrides Packs 9/11 alternatives).
- Legacy `Settings -> Security Data` is split:
  - source connectivity/freshness in `Integrations` plus `Platform Ops` mirror operations
  - advisory impact on gating in `Security & Risk` (Pack 21 mapping).

### 2.3 Domain ownership vs nav rendering

`Releases`, `Approvals`, `Deployments`, `Regions & Environments`, and `Bundles` are Release Control domain capabilities.

If implementation keeps direct nav shortcuts for `Releases`/`Approvals`, treat that as a rendering convenience only. Domain ownership and contracts remain Release Control-owned.

## 3) Canonical screen authorities

Use the following packs as the latest valid source per domain.

### 3.1 Release Control + Bundle lifecycle

Authoritative packs:
- Pack 21 for `Release Control` root positioning and setup/admin migration
- Pack 12 for full Bundle Organizer data model and flows
- Pack 13 for release promotion flows anchored on bundle versions
- Pack 14 for run/timeline, checkpoints, rollback, replay hooks
- Pack 18 for standardized environment detail shell/tabs

Superseded for this domain:
- Packs 1, 4, 8, 11 (historical drafts)

### 3.2 Dashboard

Authoritative pack:
- Pack 16 (`Dashboard` mission board, env risk + SBOM + hybrid reachability + Nightly/Data signals)

Superseded:
- Packs 1, 4, 8, 11 (dashboard/control-plane variants)

### 3.3 Approvals

Authoritative packs:
- Pack 17 for upgraded approval queue/detail tabs and decision-ready context
- Pack 13 for base release/approval flow coupling

Superseded:
- Packs 1, 4, 8, 13 sections overlapped by Pack 17 detail model

### 3.4 Security & Risk

Authoritative packs:
- Pack 19 for consolidated decision-first Security screen model
- Pack 21 for top-level `Advisory Sources` mapping statement

Superseded:
- Packs 3, 7, and earlier security layouts

Known gap:
- `Advisory Sources` detailed screen spec is not fully expanded in raw packs and must be sprinted as a first planning task.

### 3.5 Evidence & Audit

Authoritative pack:
- Pack 20 for evidence chain structure (`Evidence Home`, packs/bundles/export/proof/replay/audit)

Override:
- `Trust & Signing` ownership moved to `Administration` by Pack 21. Keep bidirectional deep links.

Superseded:
- Packs 3, 9, 11 evidence structures

### 3.6 Platform Ops and data confidence

Authoritative packs:
- Pack 15 for `Data Integrity` operating model and bubble-up wiring
- Pack 10 for feeds/airgap operational screen specifics where still needed
- Pack 21 for top-level Platform Ops taxonomy and admin drilldown links

Superseded:
- Packs 3, 6, 9, 11 operations variants

### 3.7 Integrations

Authoritative packs:
- Pack 21 for Integrations taxonomy and settings split
- Pack 10 for hub/detail/add + feed-source operational ties

Superseded:
- Packs 2, 5, 9 integration placement drafts

### 3.8 Administration

Authoritative pack:
- Pack 21 (`A0` ... `A7` including Policy, Trust, System)

Superseded:
- Packs 2, 5, 9, 11 admin/settings decompositions

## 4) Normalized terminology (canonical names)

Use these terms in sprint tickets/specs:
- `Control Plane` -> `Dashboard`
- `Packets` -> `Evidence Packs`
- `Evidence Bundles` remains `Evidence Bundles`
- `Feed Mirror & AirGap Ops` under `Platform Ops` (connectivity still surfaced in `Integrations`)
- `Hybrid Reachability` stays second-class (visible in context views, not a standalone product root)

## 5) Planning gaps to schedule first

Create early sprints for these spec-completion items before broad implementation starts:
- `Security & Risk -> Advisory Sources` full screen definition and contracts
- final nav rendering decision for Release Control-owned capabilities (direct shortcuts vs strictly nested)
- Trust ownership transition rules between Administration and Evidence workflows (route aliases + breadcrumbs + redirects)
- route deprecation map from legacy `Settings/*` and older aliases to final IA paths