# Home / Work Command Center UI **Status:** Approved target-state behavior — AWP Advisor/Search extension integrated **First realization:** I1 minimal; deepens every increment. ## Page Job Answer in one screen: ```text What is happening across my work? What needs me? What is blocked or unhealthy? What changed recently? Where should I go next? ``` After I4, Home also provides the natural entry to ask the system-wide AWP Advisor questions such as `Which Project needs me most?` without requiring a Project selection first. This is an operational/project-management command center, not an analytics landing page. ## Information Hierarchy 1. **Needs Your Attention** — blocking OwnerRequired/PolicyRequired decisions, Approvals, failed/degraded work requiring human action. 2. **In flight** — active Plans/FactoryRuns/Agents/CI/Deployments grouped by Project and lifecycle. 3. **Project progress** — GOLIVE/readiness, active Plan progress, blocked/queued items. 4. **Execution / infrastructure health** — active agents and Cluster/AWP health summary. 5. **Recent outcomes** — merged, released, deployed, resolved incidents. Dashboard metrics are secondary and clickable to source primitives. ## Desktop Layout Direction Target after later Search/Advisor activation: ```text Header: Work Search… ⌘K [Ask AWP] [New Project] Attention strip / cards (only if non-empty) ┌──────────────────────────┬─────────────────────────────┐ │ In flight │ Health / capacity │ │ Project -> Plan -> work │ Agents / Cluster / CI/CD │ ├──────────────────────────┼─────────────────────────────┤ │ Projects / GOLIVE │ Recent outcomes/activity │ └──────────────────────────┴─────────────────────────────┘ ``` `Ask AWP` is visible on Home once the I4 system advisor activates because portfolio/system advice is a primary Home job. Before activation it is omitted, not shown disabled as permanent dead chrome. Avoid dozens of small KPI tiles. Use summaries that lead to decisions/work. ## AWP Advisor Entry I4 target: ```text [Ask AWP] -> AdvisorShell -> persona: AWP Advisor -> scope: all Projects/resources visible to Principal -> page context: Home filters/time range ``` Typical questions: ```text Which Project needs me most? Which Projects are falling behind? Where are recurring CI/deployment failures? Which Plans/Decisions appear stale? Where are agents/CI capacity being consumed? ``` The advisor answer links to Project/Attention/Plan/etc. sources. It does not replace Home Attention or mutate Projects invisibly. ## Search Entry I3 target shows visible `Search…` with Cmd/Ctrl+K hint. It opens the global Search/Command palette. Search finds/navigates exact entities; `Ask AWP` remains a distinct command/advisor mental model. ## Data Sources Project/Plan/Task/Factory/Agent/CI/Deployment/Incident projections and Attention items. No independent dashboard state. AWP Advisor queries the same canonical/read-model sources through its authorized query layer. ## Actions Primary action when no urgent attention: `New Project` or resume highest-priority work based on context. Attention cards carry their own focused primary action. Secondary: filter/search/project selection. `Ask AWP` is an advisory secondary action, not a competing primary task button. ## States - **Empty:** clear product start with New Project / Connect existing Project; do not show empty dashboard chrome. - **Loading:** preserve shell and skeleton major regions; no layout jumps. - **Error:** partial data can render with source-specific degraded callout; avoid replacing whole page when one health source fails. - **Populated:** attention first, then work/health/progress. - **Stale/disconnected:** last-updated indicator + retry/realtime reconnect; authoritative state refresh action. Advisor/Search have their own complete states in dedicated UI specs and do not blank Home when unavailable. ## Responsive / Accessibility At medium/small widths, stack Attention then In flight then Project/Health/Recent. Keyboard order matches visual priority. Status never relies on color alone. Cards/rows have descriptive accessible names including primitive/status. Search and Ask AWP remain keyboard accessible. On small screens advisor opens as full-height sheet/page rather than squeezing Home. ## URL Truth Filters/project/status/time-range are URL-restorable where useful. Opening a primitive has its own stable route. Home filters/time range are passed as visible advisor context after I4, not hidden into thread state only. ## Increment Realization I1 shows Project/Plan/Factory/Review/Merge activity. I3 adds global Search/Command palette. I4 adds richer Agent metrics and system-wide `Ask AWP`. I5 CI, I6 delivery, I7 cluster, I8 incidents. I9 may add organization selector/reliability only when productized. ## High-Fidelity Requirements Before I1: populated dogfood command-center state and meaningful Empty/Attention variant if shipped. Later cards fit the same layout without redesigning the shell. Before I4: Home with visible Search + `Ask AWP`, system-scope advisor open, cross-Project answer with source links, partial-data and narrow-screen state. ## Target State Home is the owner-facing work command center. It projects canonical AWP state into the shortest path from “what is happening?” to the one item that most needs inspection or action. It never becomes a second workflow database or a vanity KPI dashboard. The AWP Advisor adds interpretation over that state, not another source of truth. ## Primary Users / Jobs - owner/operator: find the highest-impact work or attention item and continue it; - project/product manager: scan cross-project progress, blockers and recent outcomes and ask portfolio questions; - technical operator: detect degraded AWP/Cluster/CI/CD state and drill into the authoritative primitive. ## Entry / Exit Points Entry: default authenticated landing page, global `HOME -> Work`, notification/attention return, or browser restore. Exit: Project, Plan, Task, FactoryRun, Agent, Review, CIExecution, Deployment, Incident, Cluster or Attention detail. `New Project` exits into Project onboarding. Search exits to the selected entity/command. `Ask AWP` keeps Home as context unless the user opens a cited source. Back navigation restores filters/scroll/selection where practical. ## User Journeys ### J1 — Resume the most important work ```text Open Home -> Attention/In-flight sorted by consequence -> identify current state + last + next -> open Project/Plan/Task primitive -> perform work there -> return to Home with view state preserved ``` ### J2 — Resolve an attention item ```text Attention item -> read why / consequence / owner / blocking gate -> open canonical Decision/Approval/failure context -> act with policy/revision checks -> immediate acknowledgement + durable operation state -> item resolves or shows next wait/failure -> Home projection updates ``` ### J3 — Diagnose partial degradation ```text Health summary degrades -> source section remains readable with freshness -> open Cluster/CI/Connection/AWP-health source -> inspect reason/recovery -> return to Home -> unaffected work remained usable throughout ``` ### J4 — Ask AWP across Projects ```text Home -> Ask AWP -> system scope + Home filter/time context visible -> ask portfolio question -> answer cites accessible Project/Plan/Attention sources -> open selected Project or close advisor -> Home state preserved ``` ## Data / Source of Truth Home reads projections over canonical Project, Plan, Task, FactoryRun, AgentRun, CIExecution, Deployment, Incident, Decision/Approval and Cluster state. Realtime is only freshness transport; a disconnect never invents state. Telemetry can enrich health/analytics but cannot override durable lifecycle truth. AWP Advisor thread/persona state is conversation state only; factual portfolio claims query these same sources. ## Authorization / Action Hierarchy Read/drill-down follows the authenticated Principal's project/resource access. `New Project`, Decision/Approval actions, retries/cancels and protected operational actions use the same control-plane capability/policy checks as their canonical destination page. Home never grants authority by aggregating an item. AWP Advisor system scope is all **authorized** Projects/resources, not administrator-by-default visibility. ## Async / Duplicate-Mutation Safety Home should prefer navigation to canonical action contexts for consequential mutations. Any inline action must acknowledge immediately, carry revision/idempotency protection, disable accidental duplicate submit, expose durable progress and survive navigation. High-risk actions are never queued while disconnected. Advisor proposal execution and Search mutation commands inherit their canonical command safeguards. ## Invariants From Day 1 - attention is actionable product state, not generic notification count; - Home never owns duplicate lifecycle state; - waiting/blocked summaries always explain why and next owner/action; - partial source failure does not blank unrelated work; - every card/metric can be traced to its authoritative primitive; - no high-risk mutation executes from stale cached state; - Search and AWP Advisor remain distinct; - advisor can prioritize/explain Home state but cannot hide or replace canonical Attention. ## Current Implementation State Target page specification only. I1 U1 is the first visual/implementation slice. Search/Advisor are intentionally absent from I1 product chrome. ## Deferred Realization Global Search activates I3; AWP Advisor and richer Agent analytics I4; full CI/CD/Cluster/Incident summaries activate in mapped increments. Their future placement is designed now; dead panels/controls are not shipped early. ## Temporary Dogfood Behavior I1 may show only Project/Plan/Factory/Review/Merge and basic execution health. Missing future domains/Search/Advisor are omitted rather than represented by fake zero-value widgets or disabled permanent controls. ## Related Contracts / Decisions - [`INDEX.md`](INDEX.md) — product shell and goal-oriented navigation; - [`../domains/projects.md`](../domains/projects.md), [`../domains/work.md`](../domains/work.md), [`../domains/approvals-decisions.md`](../domains/approvals-decisions.md); - [`../domains/advisory-personas.md`](../domains/advisory-personas.md); - [`../workflows/task-to-merge.md`](../workflows/task-to-merge.md); - [`advisory-chat.md`](advisory-chat.md), [`search-command-palette.md`](search-command-palette.md); - global Attention semantics from `approval.md`; - six-group target IA and Last/Current/Next/Attention interaction rules are binding. ## Visual Mockup Authority No exploratory image is canonical. The I1 populated/attention/empty Home frames require explicit owner approval before implementation and are then linked/embedded from the human HTML spec. Later I3/I4 Search/Ask AWP frames receive separate approval. ## Acceptance A user can identify the most consequential active/blocking work in under one scan and navigate directly to it without opening several dashboards; after advisor activation they can also ask AWP a portfolio question with explicit scope and source-linked answer.