Claude Design pack — Workspace¶
Generated from the architecture model
This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Pack id AIF-UX-WORKSPACE · reads with the master brief · 8 screens.
1. Alignment¶
This pack covers the Workspace work area of the Factory Studio. Design the screens below as high-level pages, flows and states; do not design element-level components beyond the design-system catalog. Every simulated action is fixture behaviour and says so.
2. Design prompt¶
Produce an interactive prototype of the Workspace work area: the screens, their states from the state families, the flows that pass through them with their adverse branches, in light and dark, LTR (en, ru) and RTL (he), keyboard-first, WCAG 2.2 AA.
3. Sources¶
- Screens: screens catalog · states: states catalog · permissions: permissions catalog
- Prototype references:
ConnectSoft AI Software Factory.dc.htmldestinationscommand,newproduct,runcenter,reviews,reviews,projects,runtime;ConnectSoft Design System.dc.html,ConnectSoft Component Catalog.dc.html,ConnectSoft Developer Handoff.dc.htmlinC:/Git/ConnectSoft/ConnectSoft.DesignPrototypes/. - Alignment decisions: prototype alignment.
4. Personas, routes and layout¶
| Persona | Role | Enters this area for |
|---|---|---|
| Dana | Requester | Submit work with the right scope, profile and limits and see it progress; Know what waits on me |
| Yoav | Reviewer | Decide on the exact proposal I was shown, never a stale one; See evidence before I approve |
| Screen | Route | Layout |
|---|---|---|
my-work — My work |
/work |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
run-submit — Submit a run |
/work/runs/new |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
run-detail — Run detail |
/work/runs/{runId} |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
approvals-list — Approvals waiting |
/work/approvals |
read-only list or detail; no action rail |
approval-card — Approval card |
/work/approvals/{approvalId} |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
project-overview — Project overview |
/projects/{projectId} |
read-only list or detail; no action rail |
project-settings — Project settings |
/projects/{projectId}/settings |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
environment-board — Environment board |
/projects/{projectId}/environments |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
5. Interaction¶
Flows passing through this area: submit-assessment, review-exact-proposal, publish-asset, onboard-project, offboard-and-export. A command returns the server's outcome (202, 403, 409, 412, 422) rendered in words; the BFF never retries; a 412 re-renders the newer proposal.
6. Mock data¶
Use the shared fixtures of the fixtures page only; label every number as fixture data; never real customer data.
7. State and permission matrix¶
| Screen | State families | Roles |
|---|---|---|
my-work |
Run (Accepted, Resolving, Running, WaitingApproval, Paused, Completed, Failed, Cancelled); Approval (Pending, Approved, Rejected, Expired, Superseded); Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, AssetMaintainer, Operator, WorkspaceAdmin, PlatformAdmin, Observer |
run-submit |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Usage (Estimated, Reserved, Observed, Reconciled, Uncertain) | Requester |
run-detail |
Run (Accepted, Resolving, Running, WaitingApproval, Paused, Completed, Failed, Cancelled); Usage (Estimated, Reserved, Observed, Reconciled, Uncertain); Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, Operator, Observer |
approvals-list |
Approval (Pending, Approved, Rejected, Expired, Superseded) | Reviewer, Operator, PlatformAdmin |
approval-card |
Approval (Pending, Approved, Rejected, Expired, Superseded); Run (Accepted, Resolving, Running, WaitingApproval, Paused, Completed, Failed, Cancelled) | Reviewer |
project-overview |
Usage (Estimated, Reserved, Observed, Reconciled, Uncertain); Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, Operator, WorkspaceAdmin, Observer |
project-settings |
Freshness (Fresh, Stale, Degraded, Unknown) | WorkspaceAdmin |
environment-board |
Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack); Freshness (Fresh, Stale, Degraded, Unknown) | Operator, WorkspaceAdmin, Observer |
| Global states on every screen: loading skeleton; empty with the permitted next action; validation error; dependency degraded with freshness; permission denied with explanation; stale version conflict with the newer version rendered; success with scope and version. |
8. Accessibility criteria¶
Keyboard-only operation; visible focus; landmarks; live regions for realtime updates; 24×24 targets; contrast 4.5:1 text and 3:1 UI in both schemes; RTL mirrored for he with identifiers LTR; reduced motion honoured; status by text and icon, never colour alone (see localization and accessibility).
9. Expansion instructions¶
Screens marked missing in the prototype are new designs; generic placeholders become dedicated views; keep the design-system tokens and the seven-status palette; do not invent destinations outside the screens catalog. Future-phase screens stay designed with a Proposed badge.