Skip to content

Claude Design pack — Governance & administration

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-GOVERNANCE-ADMINISTRATION · reads with the master brief · 14 screens.

1. Alignment

This pack covers the Governance & administration 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 Governance & administration 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.html destinations governance, governance, governance, security, security, integrations, intake, contractreg, tenants, admin, saasbase, admin; ConnectSoft Design System.dc.html, ConnectSoft Component Catalog.dc.html, ConnectSoft Developer Handoff.dc.html in C:/Git/ConnectSoft/ConnectSoft.DesignPrototypes/.
  • Alignment decisions: prototype alignment.

4. Personas, routes and layout

Persona Role Enters this area for
Noa WorkspaceAdmin Onboard projects and people under the tenant's policy; Control budgets, retention and residency
Eli PlatformAdmin Publish policies, profiles and templates that tenants may only tighten; Certify publishers and connectors
Screen Route Layout
policies — Policies /governance/policies list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
approval-policy — Approval policy /governance/approval-policy list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
audit — Audit search /governance/audit list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
findings — Findings and classifications /governance/findings list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
secrets-references — Secret references /governance/secrets list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
connections — Connections /governance/connections list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
connectors — Connectors and deliveries /governance/connectors list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
topic-registry — Topic registry /governance/topics read-only list or detail; no action rail
stores — Stores /governance/stores read-only list or detail; no action rail
retention-residency — Retention and residency /governance/retention list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
governance-orders — Governance orders /governance/orders list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
users-roles — Users and roles /governance/users list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
editions-billing — Editions and billing /governance/billing list or detail with an action rail; commands open confirmation sheets that name the class and, for gated classes, the approval
notification-preferences — Notification preferences /settings/notifications 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: govern-knowledge-and-usage, manage-editions-and-billing, 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
policies Asset readiness (Draft, InReview, Published, Deprecated, Revoked) PlatformAdmin, WorkspaceAdmin, Observer
approval-policy Asset readiness (Draft, InReview, Published, Deprecated, Revoked) PlatformAdmin, WorkspaceAdmin, Observer
audit Freshness (Fresh, Stale, Degraded, Unknown) PlatformAdmin, WorkspaceAdmin, Observer
findings Freshness (Fresh, Stale, Degraded, Unknown) PlatformAdmin, Operator, Observer
secrets-references Freshness (Fresh, Stale, Degraded, Unknown) PlatformAdmin, WorkspaceAdmin
connections Deployment availability (Registered, Evaluating, Approved, Active, Degraded, Retired) WorkspaceAdmin, PlatformAdmin, Observer
connectors Deployment availability (Registered, Evaluating, Approved, Active, Degraded, Retired); Freshness (Fresh, Stale, Degraded, Unknown) PlatformAdmin, Operator, Observer
topic-registry Freshness (Fresh, Stale, Degraded, Unknown) PlatformAdmin, Operator, Observer
stores Freshness (Fresh, Stale, Degraded, Unknown) PlatformAdmin, Operator, Observer
retention-residency Freshness (Fresh, Stale, Degraded, Unknown) WorkspaceAdmin, PlatformAdmin
governance-orders Approval (Pending, Approved, Rejected, Expired, Superseded); Freshness (Fresh, Stale, Degraded, Unknown) WorkspaceAdmin, PlatformAdmin, Operator
users-roles Freshness (Fresh, Stale, Degraded, Unknown) WorkspaceAdmin, PlatformAdmin
editions-billing Usage (Estimated, Reserved, Observed, Reconciled, Uncertain); Approval (Pending, Approved, Rejected, Expired, Superseded) WorkspaceAdmin, PlatformAdmin
notification-preferences Freshness (Fresh, Stale, Degraded, Unknown) Requester, Reviewer, AssetMaintainer, Operator, WorkspaceAdmin, PlatformAdmin, 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.