# PM · Agent Agency — Desktop UX Rework Handoff DRAFT

Status: **WAITING OWNER PROTOTYPE APPROVAL**
Do not dispatch implementation yet.
Do not restart Agent Agency from scratch.
Preserve and rebase existing Target v004 work after Owner approval.

## Product decisions fixed in prototype

- Desktop-first Owner reference for 1366–1920.
- Outside Project: Projects / Employee Library / New Project.
- Inside Project: Overview / Roadmap / Team.
- Task, Mission, Run, Result, Decision, technical evidence are contextual surfaces.
- Roadmap tells a human stage journey; delivery epochs remain metadata.
- Task inspector is Owner summary first, technical evidence second.
- Results are human actions, not raw locators.
- Team separates Employee identity, membership, responsibility and observed execution.
- Library is staffing discovery with Profession → Reuse/Create → Membership.
- Bootstrap is Sources → Interview → Proposal → Approval → Provisioning → Project Control.
- Execution separates PM recommendation / Owner preference / Mission request / Actual Run.
- Discuss routes to external collaboration; Hub does not become chat.
- Global and project-local Drive workspaces remain distinct.

## Work packages after Owner approval

### WP0 — Data/truth reconciliation (P0)
Repair single current-stage/status projection, Team membership/responsibility truth, Employee version adoption truth and Result locator integrity.
Dependency: domain/data review before visual polish can claim truth.
Acceptance: Projects/Overview/Roadmap agree; Team and Task assignments agree; no accepted/unaccepted contradiction.

### WP1 — Desktop shell + Projects + Overview (P1)
Rebase current v004 UI into approved desktop hierarchy and Owner vocabulary.
Acceptance: human project descriptions, NOW/NEXT/ATTENTION in 3–5 sec, no engineering import/SHA on primary layer, no horizontal overflow at 1366/1920.

### WP2 — Roadmap + Task inspector (P1)
Implement meaningful stages, completed-stage story, task drill-down and collapsed Technical details.
Acceptance: history/current/next/future readable; Owner layer first; drawer never widens page.

### WP3 — Results / Artifacts (P0/P1)
Create human Result component and safe actions.
Acceptance: one-click Open Result/GitHub/Artifact/Handoff where available; raw locator secondary; broken/unavailable state explicit.

### WP4 — Team + Drive workspaces (P1)
Implement project member cards around responsibility and observed execution.
Acceptance: why-here, responsibilities, accepted version, global/project Drive links, truthful unknown activity.

### WP5 — Employee Library + staffing flow (P1)
Add human taxonomy, aliases, search/filter, My Employees, project team tab, profession detail, Reuse/Create/Add flow.
Acceptance: PM/Product/Architect/Developer/QA/Content/Marketing/Research found in ≤3 meaningful actions; no duplicate Employee by default.

### WP6 — New Project Bootstrap (P1)
Implement Target v004 bootstrap UX using existing architecture contracts.
Acceptance: Sources → Interview → Proposal → exact Owner approval → Provisioning; Automatic/Waiting Owner/Blocked/Ready without transaction jargon.

### WP7 — Execution selection + Discuss (P1)
Implement PM recommendation, Owner override, Mission preview, runtime option descriptors, Actual Run observation and Discuss routing.
Acceptance: Automatic/Preferred/Exact; unavailable option disabled with reason; requested config never shown as actual; Discuss does not mutate canonical state.

### WP8 — Auth / trusted device completion (P2)
Preserve current reload/new-tab persistence and complete full-browser/session-expiry/logout QA.

### WP9 — Independent QA (gate)
Re-run live browser QA against approved spec and viewport 1366/1920, then regression-check narrow/mobile separately after desktop acceptance.

## Data repair vs frontend

Data/domain first: status contradictions, Team membership/responsibility mismatch, Employee version disagreement, stale/invalid Result locators.
Frontend/product: hierarchy, copy, Roadmap rendering, inspector order, Result cards, Library discovery, Bootstrap, execution controls, Discuss.
Both: progress derivation, current-stage projection, availability/readiness rendering.

## Preserve / rebase

Keep existing Target v004 architecture, runtime provisioning work, bootstrap contracts, Drive workspace model, collaboration endpoints, execution preference fields and existing verified auth/session work.
Do not discard production Hub implementation. Adapt/rebase it to the approved Product/UX specification.

## QA requirements

- no page-level horizontal overflow at 1366 and 1920
- long URL/title/Employee names safe
- inspector width bounded
- technical details collapsed by default
- empty/unavailable/inconsistent states explicit
- no fake runtime/model observation
- source-data contradictions surfaced, not cosmetically hidden

## Dispatch rule

Wait for Human Owner walkthrough and explicit prototype approval.
After approval, PM converts these work packages into bounded implementation assignments using Codex/current approved developer surface as applicable.

STATUS: **WAITING OWNER PROTOTYPE APPROVAL**