Claude Design pack — Intelligence¶
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-INTELLIGENCE · reads with the master brief · 6 screens.
1. Alignment¶
This pack covers the Intelligence 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 Intelligence 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.htmldestinationsknowledge,knowledge,context,artifacts;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 |
| Screen | Route | Layout |
|---|---|---|
knowledge-sources — Knowledge sources |
/intelligence/sources |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
knowledge-search — Knowledge search and graph |
/intelligence/search |
read-only list or detail; no action rail |
memory — Memory and promotion |
/intelligence/memory |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
repository-intelligence — Repository intelligence |
/intelligence/repositories |
list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval |
context-snapshot — Context snapshot |
/intelligence/context/{snapshotId} |
read-only list or detail; no action rail |
artifacts — Artifacts and lineage |
/intelligence/artifacts |
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, govern-knowledge-and-usage. 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 |
|---|---|---|
knowledge-sources |
Freshness (Fresh, Stale, Degraded, Unknown) | AssetMaintainer, WorkspaceAdmin, Observer |
knowledge-search |
Freshness (Fresh, Stale, Degraded, Unknown) | Requester, AssetMaintainer, Observer |
memory |
Asset readiness (Draft, InReview, Published, Deprecated, Revoked); Approval (Pending, Approved, Rejected, Expired, Superseded) | AssetMaintainer, WorkspaceAdmin, Reviewer, Observer |
repository-intelligence |
Freshness (Fresh, Stale, Degraded, Unknown) | AssetMaintainer, Operator, Observer |
context-snapshot |
Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, Observer |
artifacts |
Freshness (Fresh, Stale, Degraded, Unknown) | Requester, Reviewer, 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.