AWP · Planning & product design

Progress snapshot

Architecture is closed. The active work is Planning UX: planner-led guidance, quality/CI enforcement, delivery/deployment recommendations, external connections, and the decision workspace before implementation-grade specs and canonical mockups.

Now

D1 · Right Context rail

Decide what follows the current decision automatically versus what remains pinned/static.

4Complete

8Active

1Low-fi baseline

4Not started

Lifecycle position

Planning UX is current

Architecture complete Planning UX active Specs, mockups, implementation queued

Work areas

Architecture review
Broad review closed

COMPLETE

Architecture baseline
Canonical topology, boundaries, providers

COMPLETE

FOSS/provider decisions
Binding baseline selected

COMPLETE

Three-plane topology
Edge → control plane → K3s execution

COMPLETE

UX screen atlas
Useful low-fidelity input, not canonical high-fi design

BASELINE

Planning-module product design
Workflow, profiles, decisions, artifacts, launch

ACTIVE

Planning UX / launch model
Major direction captured

ACTIVE

Planner-led conversation UX
Planner owns agenda and next step

ACTIVE

Quality / CI planning
Risk/behavior driven, smallest meaningful verification

ACTIVE

Verification enforcement
Cross-agent gates and reusable evidence

ACTIVE

Delivery / deployment planning
CI + release + CD + rollback + promotion

ACTIVE

Integration / connection model
User-global connections, project-local bindings

ACTIVE

Engineering communication UX
Concise policy, references, aliases

ACTIVE

Architecture foundation specs
Starts after Planning UX closes enough

NOT STARTED

Page behavior specs
Required before canonical visual mockups

NOT STARTED

Approved high-fidelity mockups
Dark mode first

NOT STARTED

Implementation
Waits for specs and approved design

NOT STARTED

What is left

Ordered

D1
Right Context rail
Context-following vs pinned/static.

D2
Decision comparison UX
Compare 2–4 credible alternatives with recommendation, evidence and impact.

D3
Enough-to-proceed threshold
Handle accepted/deferred non-blocking uncertainty.

D4
Inferred Planning Profile UX
Auto-apply + Change vs explicit confirmation.

D5
Progressive disclosure depth
How much ExecutionPolicy / CI / Delivery detail appears by default.

D6
Connection setup UX
Inline setup, resource permissions, return to planning context.

D7
Foundation specs + ADRs
Freeze architecture into implementation-grade contracts.

D8
Page specs → mockups
Low-fi refinement, then approved dark-mode mockups.

Blocked now: 0
No current hard blocker is recorded. Specs and mockups are queued behind unresolved Planning UX decisions rather than blocked by an external dependency.

Durable design documents

AWP-PLANNING-MODULE-DESIGN.md

AWP-PLANNING-UX-DESIGN.md

AWP-PLANNER-LEADERSHIP-UX.md

AWP-QUALITY-CI-PLANNING-DESIGN.md

AWP-VERIFICATION-ENFORCEMENT-DESIGN.md

AWP-DELIVERY-CONNECTIONS-PLANNING-DESIGN.md

AWP-INTEGRATION-CONNECTIONS-ARCHITECTURE.md

AWP-ENGINEERING-COMMUNICATION-POLICY.md