Claude Design pack — Operations & usage¶
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-OPERATIONS-USAGE · reads with the master brief · 13 screens.
1. Alignment¶
This pack covers the Operations & usage 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 Operations & usage 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.htmldestinationsruns,exectrace,observability,healthops,observability,cost,runtime,products,products,installruns,runbooks;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 |
|---|---|---|
| Omer | Operator | Keep the Factory and operated products within objectives; Resolve incidents with evidence |
| Noa | WorkspaceAdmin | Onboard projects and people under the tenant's policy; Control budgets, retention and residency |
| Maya | Observer | See state and evidence without acting |
| Screen | Route | Layout |
|---|---|---|
run-list — Runs |
/operations/runs |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
run-timeline — Run timeline |
/operations/runs/{runId} |
read-only list or detail; no action rail |
overview — Operations overview |
/operations |
read-only list or detail; no action rail |
status-objectives — Status and objectives |
/operations/status |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
alerts — Alerts |
/operations/alerts |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
usage-cost — Usage and cost |
/operations/usage |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
capacity — Capacity and quotas |
/operations/capacity |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
fleet-board — Fleet board |
/operations/fleet |
read-only list or detail; no action rail |
product — Operated product |
/operations/fleet/{productId} |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
rollouts — Rollouts |
/operations/rollouts |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
incidents — Incidents |
/operations/incidents |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
on-call — On-call |
/operations/on-call |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
offboardings — Off-boardings |
/operations/offboardings |
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, recover-run, govern-knowledge-and-usage, operate-fleet, manage-editions-and-billing, 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 |
|---|---|---|
run-list |
Run (Accepted, Resolving, Running, WaitingApproval, Paused, Completed, Failed, Cancelled); Usage (Estimated, Reserved, Observed, Reconciled, Uncertain); Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, Operator, Observer |
run-timeline |
Run (Accepted, Resolving, Running, WaitingApproval, Paused, Completed, Failed, Cancelled); Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, Operator, Observer |
overview |
Freshness (Fresh, Stale, Degraded, Unknown); Usage (Estimated, Reserved, Observed, Reconciled, Uncertain) | WorkspaceAdmin, Operator, Observer |
status-objectives |
Freshness (Fresh, Stale, Degraded, Unknown) | Operator, WorkspaceAdmin, PlatformAdmin, Observer |
alerts |
Freshness (Fresh, Stale, Degraded, Unknown) | Operator, WorkspaceAdmin, PlatformAdmin, Observer |
usage-cost |
Usage (Estimated, Reserved, Observed, Reconciled, Uncertain) | WorkspaceAdmin, Operator, Observer |
capacity |
Freshness (Fresh, Stale, Degraded, Unknown) | Operator, WorkspaceAdmin, PlatformAdmin, Observer |
fleet-board |
Fleet (Provisioning, Running, Degraded, Upgrading, Suspended, Offboarding); Freshness (Fresh, Stale, Degraded, Unknown) | Operator, PlatformAdmin, Observer |
product |
Fleet (Provisioning, Running, Degraded, Upgrading, Suspended, Offboarding); Freshness (Fresh, Stale, Degraded, Unknown) | WorkspaceAdmin, Operator, Observer |
rollouts |
Fleet (Provisioning, Running, Degraded, Upgrading, Suspended, Offboarding); Approval (Pending, Approved, Rejected, Expired, Superseded) | Operator, Reviewer, PlatformAdmin, Observer |
incidents |
Fleet (Provisioning, Running, Degraded, Upgrading, Suspended, Offboarding) | Operator, Observer |
on-call |
Fleet (Provisioning, Running, Degraded, Upgrading, Suspended, Offboarding) | PlatformAdmin, Operator |
offboardings |
Fleet (Provisioning, Running, Degraded, Upgrading, Suspended, Offboarding); Approval (Pending, Approved, Rejected, Expired, Superseded) | WorkspaceAdmin, PlatformAdmin, Operator |
| 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.