# AWP I1 Deterministic High-Fidelity Prototypes

**Status:** **U1–U6 OWNER-APPROVED / FINAL — I1 VISUAL DESIGN COMPLETE**

These repository HTML/CSS/JS files are the binding deterministic visual/interaction references for Increment 1. Generated-image attempts are not canonical once an approved deterministic realization exists.

## Journey

1. [`u1-project.html`](u1-project.html) — **FINAL / OWNER-APPROVED** Project Overview: Current Goals, Needs Your Attention, Blockers, Active Plans, current FactoryRuns, Recently Completed, five-column Queue / Next Up and Project status footer.
2. [`u2-factory-active.html`](u2-factory-active.html) — **FINAL / OWNER-APPROVED** active FactoryRun, reconciled to the final U2 reference and [`../../plans/AWP-U2-FACTORYRUN-HIGH-FIDELITY-BRIEF.md`](../../plans/AWP-U2-FACTORYRUN-HIGH-FIDELITY-BRIEF.md).
3. [`u3-waiting-failure-retry.html`](u3-waiting-failure-retry.html) — **FINAL / OWNER-APPROVED** failure/waiting/retry state preserving U2 FactoryRun identity and emphasizing WIP safety/recovery.
4. [`u4-review.html`](u4-review.html) — **FINAL / OWNER-APPROVED** exact-candidate ChangeSet/Review state with realistic diff, blocking finding, evidence and MergeGate.
5. [`u5-ready-to-merge.html`](u5-ready-to-merge.html) — **FINAL / OWNER-APPROVED** same Review surface advanced to protected ready-to-merge state.
6. [`u6-completed.html`](u6-completed.html) — **FINAL / OWNER-APPROVED** same lifecycle advanced to read-only merged/completed outcome, provenance and next work.

## Styling / interaction

- U1 final: [`u1-final.css`](u1-final.css)
- U2–U6 final execution/review system: [`awp-i1-final.css`](awp-i1-final.css)
- U2–U6 lightweight mockup interactions: [`awp-i1-final.js`](awp-i1-final.js)
- Legacy [`awp.css`](awp.css) is non-authoritative and must not override final U1–U6 behavior/visual language.

## Owner Approval — 2026-08-20

The owner explicitly approved all six lifecycle mockups and authorized transition from design/specification finalization into implementation.

```text
U1  APPROVED / FINAL
U2  APPROVED / FINAL
U3  APPROVED / FINAL
U4  APPROVED / FINAL
U5  APPROVED / FINAL
U6  APPROVED / FINAL
```

Approval freezes the material I1 hierarchy, information architecture, state presentation and primary-action semantics. Implementation-local CSS/component technique may differ only if rendered behavior remains faithful.

## Visual Parity Invariants

Across the approved set:

```text
near-black/navy application background
restrained purple primary/selected accents
thin blue/navy borders
compact operational typography and high information density
human-readable identity first; IDs secondary
small semantic status pills
one dominant primary action per decision context
secondary/destructive actions separated
no generic KPI-card hierarchy
no giant hero or marketing composition
no glassmorphism
raw provider/log/Kubernetes details are secondary evidence
waiting/failure states explain recovery and WIP safety before logs
```

## Binding U1 Rules

- ProjectVision != Goal != Plan; `GOLIVE` is not a primitive.
- U1 layout is: Current Goals / Attention / Blockers -> Active Plans / FactoryRuns / Recently Completed -> five-column Queue / Next Up -> Project health/footer.
- Current Goals are compact operational rows.
- Plan and Task rows are navigation targets; no redundant routine open buttons.
- Queue summary exposes Now / Next / Later / Waiting / Blocked while hard dependency legality remains authoritative in the Work/Queue domain.
- Search stays in the global top bar.
- Project tabs sit under the compact Project header.

## Binding U2/U3 FactoryRun Rules

- U2 and U3 are the I1 FactoryRun visual authorities.
- Header: Plan title + FactoryRun ID, state, elapsed time, Plan, Goal and Scope; View Plan / overflow / separated Cancel Run.
- Tabs: Overview / Tasks / AgentRuns / Timeline / ChangeSet.
- Main hierarchy: Task Progress & Topology + Active AgentRuns, followed by Latest Activity + WIP/Checkpoint Safety + ChangeSet/Review + Current/Next/Attention.
- Multi-agent concurrency and Task dependencies are visible.
- AgentRun cards expose Attempt/model/account/Workspace/activity/checkpoint without making provider provenance the primary identity.
- U3 preserves the same FactoryRun page and changes state hierarchy for failure/recovery; it does not redesign the page.
- Failure answers: what failed, what AWP did, whether work is safe, what happens next, whether the user must act.

## Binding U4/U5/U6 Review Rules

- U4 -> U5 -> U6 are one ChangeSet/Review surface advanced through lifecycle states.
- exact base/candidate identity is always visible;
- changed files + real diff are primary review evidence;
- findings identify severity/location/status;
- verification evidence binds to the exact candidate;
- U4 changes-requested state cannot Merge and has one correction action;
- U5 MergeGate explains why the exact candidate is safe before the one Merge action;
- trusted control plane owns Merge; AgentRun cannot merge;
- U6 is read-only terminal outcome and exposes resulting commit, provenance, Task/Plan/Goal effect, dependency re-evaluation and next work;
- Merge does not imply Release/Deployment; those activate later.

## Implementation Authority

Implementation agents must read the matching UI/domain specs together with these final artifacts. Material visual relocation or lifecycle-semantic change requires an explicit owner-approved design/spec amendment.

The I1 Design Complete gate is now **GREEN**.