Claude Design pack — Software Factory¶
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-SOFTWARE-FACTORY · reads with the master brief · 11 screens.
1. Alignment¶
This pack covers the Software Factory 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 Software Factory 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.htmldestinationsblueprints,dsl,tplstudio,entities,devops,devops,devops,runtime,healthops,products,orchestration;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 |
| Lena | AssetMaintainer | Take an agent, skill or template from Draft to Published with evidence; Act on learning proposals |
| Omer | Operator | Keep the Factory and operated products within objectives; Resolve incidents with evidence |
| Screen | Route | Layout |
|---|---|---|
blueprints — Blueprints |
/factory/blueprints |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
dsl-studio — DSL and descriptor studio |
/factory/dsl |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
recipes — Generation recipes |
/factory/recipes |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
generated-outputs — Generated outputs and provenance |
/factory/projects/{projectId}/outputs |
read-only list or detail; no action rail |
proposals — Change proposals |
/factory/proposals |
read-only list or detail; no action rail |
pipeline-runs — Pipeline runs |
/factory/pipelines |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
promotions — Promotions |
/factory/promotions |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
provisioning — Provisioning |
/factory/provisioning |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
inventory — Runtime inventory and drift |
/factory/environments/{environmentId}/inventory |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
generated-products — Generated products |
/factory/products |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
workflow-run-graph — Workflow run graph |
/factory/runs/{runId}/graph |
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: recover-run. 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 |
|---|---|---|
blueprints |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | Requester, AssetMaintainer, Observer |
dsl-studio |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | AssetMaintainer, Requester |
recipes |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Approval (Pending, Approved, Rejected, Expired, Superseded) | Requester, Reviewer, AssetMaintainer, Observer |
generated-outputs |
Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack) | Requester, Reviewer, Operator, Observer |
proposals |
Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack) | Requester, Reviewer, Operator, Observer |
pipeline-runs |
Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack); Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, Operator, Observer |
promotions |
Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack); Approval (Pending, Approved, Rejected, Expired, Superseded) | Operator, Reviewer, WorkspaceAdmin, Observer |
provisioning |
Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack); Approval (Pending, Approved, Rejected, Expired, Superseded) | Operator, PlatformAdmin, Observer |
inventory |
Freshness (Fresh, Stale, Degraded, Unknown); Approval (Pending, Approved, Rejected, Expired, Superseded) | Operator, WorkspaceAdmin, Observer |
generated-products |
Fleet (Provisioning, Running, Degraded, Upgrading, Suspended, Offboarding); Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack) | WorkspaceAdmin, Operator, Observer |
workflow-run-graph |
Run (Accepted, Resolving, Running, WaitingApproval, Paused, Completed, Failed, Cancelled); Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Operator, 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.