# U1 — Project High-Fidelity Brief

**Date:** 2026-08-20  
**Status:** **OWNER-APPROVED FINAL U1 — binding visual authority**  
**Canonical HTML:** [`../mockups/i1/u1-project.html`](../mockups/i1/u1-project.html)  
**Page behavior authority:** [`../specs/ui/project.md`](../specs/ui/project.md)

## Approval

The owner-supplied final U1 reference on 2026-08-20 is approved and has been realized as deterministic repository HTML/CSS.

This supersedes earlier generated U1 mockups and earlier draft U1 compositions where they conflict visually.

```text
VISUAL AUTHORITY
  docs/mockups/i1/u1-project.html
  docs/mockups/i1/u1-final.css

SEMANTIC AUTHORITY
  Project / Goal / Plan / Task / Queue / Factory domain specs
```

Generated images are reference/history only after this point. Implementation must follow the deterministic HTML unless a later explicit owner design Decision amends U1.

## Final Five-Second Scan

U1 answers:

```text
What are the current Goals?
What needs my attention?
What is blocked?
Which Plans are active?
What FactoryRuns are running now?
What was recently completed?
What is queued next / later / waiting / blocked?
Is Project health current?
```

## Final Shell

### Global top bar

```text
WORK / Projects / AWP
Search projects, plans, tasks, runs, decisions…   ⌘K
notifications
help
current user / role
```

### Left navigation

```text
HOME
  Overview
  Needs your attention

WORK
  Projects
  Plans
  Work Items
  Queue (Next Up)
  Saved views

EXECUTION
  FactoryRuns
  Agents
  CI

DELIVERY
  Releases / Changes
  Deployments

OPERATIONS
  Queues
  Health

INTELLIGENCE
  Reports
  Analytics

SETTINGS
  Project Settings
```

The final U1 shell intentionally presents the complete product destination map. Increment activation controls behavior/availability; visual implementation should not arbitrarily relocate these destinations.

## Final Project Header

```text
AWP
Agentic Software Delivery Control Plane
platform-modules/awp
Owner: Platform Team
Created May 18, 2025

New Plan
Connections
Decisions
```

Project tabs:

```text
Overview
Vision
Goals
Plans
Work
FactoryRuns
Reviews
Decisions
CI
Delivery
Settings
```

`Overview` is selected.

## Final Overview Composition

The approved composition is three horizontal layers plus the Project status footer.

### Layer 1 — Goals / Attention / Blockers

```text
Current Goals
Needs Your Attention
Blockers
```

#### Current Goals

Compact, immediately scannable rows:

```text
Goal name                         status
Dogfood the first lifecycle       On Track
Secure & compliant baseline       On Track
Platform UX v1 – ship U1 screens  At Risk
FactoryRuns automation MVP        On Track
U1 polish & usability             On Track
```

Do not add a row of generic numeric KPI cards above these Goals.

#### Needs Your Attention

Each item has:

```text
severity marker
short actionable label
priority
one direct action
```

Final reference items include visual-design approval, runtime-pin confirmation and planning-default acceptance.

#### Blockers

Each blocker has:

```text
severity
short title
compact explanation
explicit Next action
priority
direct Resolve action
```

Blocker copy is operational, not a generic warning banner.

### Layer 2 — Active / Running / Completed

Three peer panels:

```text
Active Plans
FactoryRuns (What's running now)
Recently Completed
```

#### Active Plans

Columns:

```text
Plan
Progress
Status
Next milestone
```

The Plan row itself is the navigation target in implementation. No redundant `Open Plan` button is required.

#### FactoryRuns

Columns:

```text
Run ID
Plan / Task
Status
Model / Account
Started
```

Running and planned rows can coexist. This section answers **what is being done now**.

#### Recently Completed

Columns:

```text
Run ID
Plan / Task
Completed
```

This section answers **what was done recently**.

### Layer 3 — Queue / Next Up

The approved Project Overview includes a full-width compact Queue summary rather than only a single “next candidate” card.

Columns:

```text
Now (Ready)
Next
Later
Waiting (External)
Blocked
```

Each column shows count and ordered work items with owning Plan/context. `View full queue` opens the dedicated dependency-aware Queue/Graph surface.

This Project-level queue summary does **not** replace the canonical dependency DAG or server-side legality rules. Manual ordering remains constrained by hard prerequisites/policy.

### Project status footer

```text
Project Health: Healthy
Last updated: Just now   [refresh]
Project timezone: Asia/Singapore (UTC+8)
Customize
```

## Visual Language

Final U1 characteristics:

- dark, dense professional control-plane UI;
- slim fixed left navigation;
- global top search;
- compact project header and tab row;
- subtle blue/black panels and borders;
- violet product/action accent;
- green/amber/red operational state accents;
- tables and compact lists rather than oversized cards;
- no giant hero;
- no glassmorphism;
- no decorative gradients as content;
- no equal-size metric-card dashboard strip;
- no emoji/iconography that changes text layout unpredictably.

## Responsive / Implementation Requirements

Desktop high-fidelity reference is the owner-approved 1536×1024 composition. Implementation should preserve hierarchy at smaller widths rather than merely scaling the entire desktop canvas.

- do not cut words in the middle;
- no horizontal overflow in primary Project content at supported breakpoints;
- tables may switch to semantic stacked rows where required;
- queue columns may collapse to scrollable/stacked responsive presentation while preserving ordering labels;
- keyboard focus must be visible on nav, tabs, rows and actions;
- status is always communicated in text, not only color.

## Binding Corrections to Earlier Drafts

The owner-approved final U1 supersedes these earlier draft assumptions:

- the Overview uses the full five-column compact Queue summary at the bottom;
- Current Goals use compact rows rather than large criteria cards;
- Active Plans, live FactoryRuns and Recently Completed are peer panels on the same layer;
- Intelligence destinations (`Reports`, `Analytics`) are present in the left navigation;
- Project tabs are visible directly below the header;
- the final U1 reference does not require a floating Project Manager launcher in this screen composition;
- Search occupies the final top-bar position without a large `Planned I3` label inside the field.

These are visual-placement decisions. Activation/authorization semantics remain controlled by the increment/domain specifications.

## Change Control

The U1 HTML is now binding implementation reference. A material change to section hierarchy, navigation placement, Queue summary structure, Project header/tab placement, or major interaction location requires an explicit owner-approved design amendment.