Skip to content

V3 redesign status

Designed Implemented (partial)

Source: doc/product/V3_*.md (12 V3-specific design docs) · doc/product/ux-mocks/product-redesign-v3/

The V3 redesign is in flight. /v3 is the design mock; /v3-prod and the active production routes are the shipped implementation built from it. This page summarizes status by V3 doc.

V3 doc inventory

flowchart TB
    classDef d fill:#fff3cd,stroke:#332701

    V1[V3_Action_Lifecycle_Closure_Plan_v1]:::d
    V2[V3_Admin_Workbench_Consistency_Plan_v1]:::d
    V3[V3_Admin_Workbench_Model_v1]:::d
    V4[V3_Cutover_Route_Map_v1]:::d
    V5[V3_E2E_Testing_Contract_v1]:::d
    V6[V3_Migration_Execution_Tracker_v1]:::d
    V7[V3_Mock_To_Production_Data_Parity_v1]:::d
    V8[V3_Navigation_Journey_Contract_v1]:::d
    V9[V3_Operator_Admin_IA_Restructure_v1]:::d
    V10[V3_Resource_Lifecycle_Evidence_Pattern_v1]:::d
    V11[V3_Scheduler_Runtime_Node_Lifecycle_Audit_v1]:::d
    V12[V3_Storage_Sharing_v1]:::d
    V13[V3_Surface_Row_Intent_and_Useful_Data_Audit_v1]:::d
    V14[V3_User_Workflow_Demo_Runbook]:::d
    V15[V3_V1_Retirement_Guardrails_v1]:::d
    V16[V3_V1_Workflow_Parity_Audit_v1]:::d
    V17[V3_Workbench_Consistency_Plan_v2]:::d
    V18[V3_Workflow_Consolidation_Plan_v1]:::d

V1 → V3 migration model

flowchart LR
    classDef v1 fill:#ffebee,stroke:#c62828
    classDef v3 fill:#e8f5e9,stroke:#2e7d32

    V1["/api/v1/*<br/>frozen demo + internal continuity"]:::v1
    V3["/api/v1/v3/*<br/>read models + new flows"]:::v3
    V3PROD[v3-prod routes<br/>shipped from mocks]:::v3
    V3MOCK["/v3 mock HTML"]:::v3

    V1 -.feature-by-feature retire.-> V3PROD
    V3 -.read-model isolation until<br/>target domain route is clear.-> V3PROD
    V3MOCK -.design source.-> V3PROD

From AGENTS.md §1b (project rule):

v3 is the long-term product and code organization model. Current v1 routes are only a frozen demo/internal-user continuity surface while the migration is in progress; do not treat v1 as a public backward-compatibility contract.

Cutover route map

→ Read source: V3_Cutover_Route_Map_v1.md.

The cutover plan defines which routes migrate first, what their v3 equivalents look like, and the guardrails for retiring v1.

What's not migrating to v3

→ Read source: V3_V1_Retirement_Guardrails_v1.md.

Some v1 routes remain in routes_v1_frozen.go as durable demo/internal surfaces. New product routes should go to v3 domain route files (routes_provisioning_*.go, routes_platform_*.go, routes_access_*.go).

Mock-to-production parity

→ Read source: V3_Mock_To_Production_Data_Parity_v1.md.

Parity rules:

  • Mocks define visual layout and intent.
  • Production must implement the journeys, not the literal layout.
  • Mock copy that explains design rationale is removed in production — page copy serves the user's task, not the reviewer.
  • Permanent section subtitles are a warning sign that the page is still talking to design reviewers.

Admin workbench model

→ Read source: V3_Admin_Workbench_Model_v1.md.

Admin workbench uses the focused-detail + operation-drawer + acknowledgement/suppression pattern. Governs every /admin/* page family.

Testing contract

→ Read source: V3_E2E_Testing_Contract_v1.md, E2E_Selector_Contract.md.

E2E tests rely on stable selectors, not text. Mocks and production share the same selector vocabulary so tests run against either.

Where to look next