Users experience the conductor model: conversational team room, visible agent roster, artifacts alongside chat, conflict surfacing, clarifications, decisions, and cross-artifact navigation tied to one scope state.
As a user, I want the left rail to show the entire Quorum pipeline (PRD steps) while I work, So that I always see the real process—not a dumbed-down mystery track.
Maps to: UX-DR1, UX-DR12, UX-DR14, FR7 (container for interaction).
Acceptance Criteria:
Given a desktop viewport (≥1280px)
When I open a workspace
Then I see pipeline rail (~256px), team room (fluid), artifacts (~360px) per Figma/wireframe alignment
And the pipeline rail lists all canonical steps from ux-design-specification.md §4.2.1 (1 → 2a → 2b → 2c → 3 → … → 12), scrollable or grouped-expandable, with completed / current / upcoming states
And step 3 is labeled per PRD (Three-pillar analysis, not “Filter” alone) and expands to show Desirability → Feasibility → Viability as nested items while in that phase
And there are no top-level rail steps invented outside the PRD (e.g. not “Conflict resolution” or “Sync” as fake methodology)
And below 1024px, rail is reachable via drawer/tab without losing access to the same full step list
And Figma file link is referenced for visual QA
As a user, I want to see which agents are active for this step, So that the team feels real and legible.
Maps to: FR8, UX-DR2.
Acceptance Criteria:
Given a pipeline step configuration
When the session loads
Then active personas are highlighted and inactive ones are subdued with tooltip “Joins in [step]”
And avatars + role labels match PRD roster naming policy
As a user, I want to read and send messages in the team room, So that I can run sessions with my AI team.
Maps to: FR7, NFR-P2 (streaming indicators).
Acceptance Criteria:
Given an active session
When I send a message
Then it appears in the transcript with correct ordering
When an agent responds with latency >2s
Then a streaming or step label indicator appears before full content (UX-DR3)
As a user, I want to list and open workspace artifacts next to chat, So that I can context-switch without losing the conversation.
Maps to: FR9, FR32.
Acceptance Criteria:
Given artifacts of multiple types exist
When I select an artifact
Then preview or detail opens without leaving the team room layout
And artifact list reflects a single underlying scope version; version chip when viewing non-current snapshot (if implemented)
As a user, I want structured conflict presentation when agents disagree, So that I can decide with clarity.
Maps to: FR10, UX-DR4 (reuse card visual language).
Acceptance Criteria:
Given orchestration emits a conflict structure
When the UI receives it
Then a trade-off panel shows positions, evidence links, and recommended resolution path
And the user can acknowledge or proceed to decision capture
As a user, I want to ask for clarification on agent reasoning, So that I trust the analysis.
Maps to: FR11.
Acceptance Criteria:
Given an agent message with expandable rationale
When I use “Clarify” (or equivalent)
Then the orchestration requests deeper explanation and renders it in-thread
And rate limiting or empty responses are handled gracefully (NFR-P2)
As a user, I want decisions on contested recommendations stored, So that audit and resume are possible.
Maps to: FR12, FR25 (feeds override/decision log).
Acceptance Criteria:
Given a contested recommendation
When I choose accept / reject / override with rationale
Then the decision is persisted with actor, timestamp, workspace, and references to messages
And the decision appears in a filterable Decision log minimal view or export hook
As a returning user, I want to resume from my last meaningful checkpoint, So that I don’t redo work.
Maps to: FR13, UX-DR6, ARCH-4.
Acceptance Criteria:
Given a saved checkpoint exists
When I reopen the workspace
Then a resume banner shows what is already complete and a CTA “Continue here”
And orchestration state reloads from persisted checkpoint without corrupting scope