Claude Design pack — Quality & releases¶
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-QUALITY-RELEASES · reads with the master brief · 6 screens.
1. Alignment¶
This pack covers the Quality & releases 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 Quality & releases 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.htmldestinationsqa,devops;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 |
|---|---|---|
| Yoav | Reviewer | Decide on the exact proposal I was shown, never a stale one; See evidence before I approve |
| Lena | AssetMaintainer | Take an agent, skill or template from Draft to Published with evidence; Act on learning proposals |
| Maya | Observer | See state and evidence without acting |
| Screen | Route | Layout |
|---|---|---|
evaluation-runs — Evaluation runs |
/quality/evaluations |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
release-evidence — Release evidence |
/quality/evidence/{releaseId} |
read-only list or detail; no action rail |
feedback — Feedback |
/quality/feedback |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
datasets — Evaluation datasets |
/quality/datasets |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
learning-proposals — Learning proposals |
/quality/proposals |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
product-releases — Product releases |
/quality/releases |
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: publish-asset. 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 |
|---|---|---|
evaluation-runs |
Approval (Pending, Approved, Rejected, Expired, Superseded); Freshness (Fresh, Stale, Degraded, Unknown) | AssetMaintainer, Reviewer, PlatformAdmin, Observer |
release-evidence |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | AssetMaintainer, Reviewer, Observer |
feedback |
Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, Operator |
datasets |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked) | AssetMaintainer, PlatformAdmin |
learning-proposals |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Approval (Pending, Approved, Rejected, Expired, Superseded) | AssetMaintainer |
product-releases |
Delivery (Proposed, PullRequestOpen, Merged, Candidate, Released, Promoting, Verified, RolledBack) | 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.