AIFACTORY-FEAT-076: Studio work area: 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.
A design artefact, not a tracker
This backlog is generated from model/backlog/ and validated against the architecture model. No work item exists in any tracker, and no item carries a date, an estimate or an assignee (ADR-0029).
Epic Factory Studio (PF-14) · Increment I3 Studio · State elaborated · Route frontend-developer · Build order 116 of 185 (Factory code)
The 14 screens of the Studio work area Governance & administration on the Blazor shell and microfrontends, bound to the read models and commands the model names for them, with their state families, roles, locales and accessibility contracts. Screens come from model/ux/screens.yaml and the prototype alignment.
| Delivers | — |
| Stubs | — |
| Realizes | ux work areas: Governance & administration |
| Requirements | — |
| Depends on | — |
| Sources | model/ux/screens.yaml, model/ux/prototype-alignment.yaml |
AIFACTORY-US-1394: Governance: I read the policy bundles in force and the decisions of a run, and validate a project override that may only tighten the tenant bundle¶
behavior · persona workspace-admin
As a workspace admin, I want to see which policy bundle governs my project, why a run was allowed or denied, and whether a stricter project override is valid before I propose it, so that I tighten the policy of a project with evidence and never loosen the platform ceiling by mistake.
A platform admin, a workspace admin or an observer opens the screen policies at /governance/policies. StudioBff composes it under the scope of the session from ListPolicyBundles and GetPolicyBundle of PolicyEngineService, reached through GovernanceHost, and from ListRunDecisions for a run the user picks, which lists the decisions recorded for that run with their effects, matched rules and reasons. In I3 the bundle in force for a tenant is the one the policy engine seeded itself at the first decision asked for that tenant, and until the publication gate of the fourth increment the seeded bundles are the only ones in force, as the amendment of ADR-0015 on the policy bundle of a new tenant records; the screen states that the bundle is seeded and shows no publication control. A role of the screen whose session holds factory.policies.write, the scope of ValidateProjectPolicy, validates a project override: the page sends it through ForwardCommand with an idempotency key, PolicyEngineService checks every rule against the tenant bundle and answers the findings, a rule that loosens the bundle being a finding, or 400 for a malformed override; the action is sandbox class and stores nothing. SimulatePolicy, the what-if evaluation of a candidate bundle against the recorded decisions of a period, is also sandbox class and takes the same scope, so it is offered to the same sessions. A session without factory.policies.write sees both controls disabled with the reason. A run of another tenant is answered 404 by ListRunDecisions like a run that does not exist and a missing scope inside the tenant 403, and the page says which. When GovernanceHost does not answer, the source is shown degraded with its last freshness and the commands are refused with 503, never queued. StudioBff consumes PolicyRevisionActivated and refreshes the policy bundle view of the open page.
Acceptance criteria
| AC1 | Given a workspace admin on policies, when StudioBff/GetScreenModel composes it, then the bundles and the bundle in force come from PolicyEngineService/ListPolicyBundles and PolicyEngineService/GetPolicyBundle, the page states that the bundle is the seeded one of the tenant as the amendment of ADR-0015 on new tenants records, and no publication control is shown in I3. |
| AC2 | Given a run of the scope, when the user opens its decisions, then PolicyEngineService/ListRunDecisions lists effects, matched rules and reasons, and a run of another tenant is answered 404 and a missing scope 403, each explained in words (ADR-0015, FUX-05). |
| AC3 | Given a session that holds factory.policies.write, when StudioBff/ForwardCommand forwards PolicyEngineService/ValidateProjectPolicy with an idempotency key, then every rule that loosens the tenant bundle is shown as a finding, a malformed override is answered 400 and nothing is stored; PolicyEngineService/SimulatePolicy is offered to the same sessions, because it takes the same scope, and a session without that scope sees both controls disabled with the reason (FUX-01). |
| AC4 | Given GovernanceHost does not answer, when the screen is open, then the source is shown degraded with its last freshness and a command is refused with 503 and not queued, and when PolicyEngineService/PolicyRevisionActivated is consumed by StudioBff the open page refreshes without a reload (model/services/factory-studio/StudioBff.yaml). |
| Traces: services | StudioBff, PolicyEngineService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, PolicyEngineService/ListPolicyBundles, PolicyEngineService/GetPolicyBundle, PolicyEngineService/ListRunDecisions, PolicyEngineService/ValidateProjectPolicy, PolicyEngineService/SimulatePolicy |
| Traces: events | PolicyEngineService/PolicyRevisionActivated |
| Traces: adrs | ADR-0015 |
| Traces: requirements | FUX-01, FUX-05 |
| Relates: screens | policies |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:policy-engine-service, feature:governance-host |
| Sources | model/ux/screens.yaml, model/services/factory-studio/StudioBff.yaml, model/services/governance/PolicyEngineService.yaml, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5630 Policies screen in the Governance microfrontend |
ui | The Governance microfrontend renders policies with the bundle in force marked as seeded, the decisions of a chosen run with effects, rules and reasons, a validation panel that lists every loosening rule as a finding, the simulation for a session that holds factory.policies.write, and both controls disabled with their reason for a session without it. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5631 Screen model and command routes of the policies screen in StudioBff |
contract | StudioBff composes policies through GovernanceHost from ListPolicyBundles, GetPolicyBundle and ListRunDecisions with the freshness of the source, forwards ValidateProjectPolicy and SimulatePolicy with an idempotency key and the scope of the session, refuses them with 503 while GovernanceHost does not answer, and refreshes the view on PolicyRevisionActivated. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5632 Verify the policies screen against a stubbed StudioBff |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving a seeded bundle, the decisions of a run, a loosening override, a session without factory.policies.write, a 404 of another tenant and an unreachable GovernanceHost; the tests prove AC1 to AC4 of AIFACTORY-US-1394 (PolicyEngineService/ValidateProjectPolicy). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5697 Verify the StudioBff side of the policies screen |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-governance-policies" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (composition through GovernanceHost with freshness), AC2 (the 404 and 403 of ListRunDecisions returned unchanged), AC3 (ValidateProjectPolicy and SimulatePolicy forwarded once with an idempotency key and the scope of the session) and AC4 (503 while GovernanceHost does not answer, nothing queued, refresh on PolicyRevisionActivated) of AIFACTORY-US-1394 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-1395: Governance: I search and export the audit evidence, resolve findings and set classifications, and keep secret references without ever seeing a secret value¶
behavior · persona platform-admin
As a platform admin, I want to search the evidence, act on findings and classifications and manage the references to secrets from the Studio, so that I govern data classes, evidence and credentials of the tenant without leaving the Studio and without a secret value on any screen.
Three screens of the Governance area read services delivered in the first increment through GovernanceHost. The screen audit reads SearchAudit of AuditService: the evidence by scope, kind, actor, run and time with its chain position. A platform admin or a workspace admin may export the evidence of a project with ExportAudit, an external-class action answered 202 that produces the export in open formats with chain proofs; the evidence is redacted and never purged, as ADR-0019 decision 3 keeps it. The screen findings reads ListFindings and ListClassifications; a platform admin resolves or accepts the risk of a finding with a reason through ResolveFinding, a shared-write action that needs no approval binding, and sets the data class, retention, redaction rules and residency of a resource type through SetClassification, a production-class action because retention and routing change, which carries the approval binding of its class and which the owning service answers 409 on a conflict. The screen secrets-references reads ListSecretReferences of SecretBrokerService, which the model documents for Platform admin under factory.secrets.admin, and ListRunIssuances, both metadata only. The controls of the screen are offered to a session that holds factory.secrets.admin: it registers a reference to a vault secret with owner, purposes, time to live and rotation policy through RegisterSecretReference, records a rotation with RotateSecret, which revokes the live issuances of the old version, and revokes a reference with RevokeSecretReference, all three production class. A workspace admin without that scope sees the controls disabled with the reason and the reference list refused with its reason, while the issuances of a run stay readable. No screen shows or posts a secret value: the value is written to the vault by its owner, never through the Studio. Every command goes through ForwardCommand with an idempotency key and the scope of the session and, for a production-class command, the approval binding the owning service requires; the gate is the owning service, never StudioBff. An observer or an operator without the scope sees the controls disabled with the reason, a resource of another tenant is answered 404 and a missing scope 403. StudioBff consumes FindingRaised, FindingResolved, ClassificationChanged and SecretReferenceRegistered and refreshes the open views.
Acceptance criteria
| AC1 | Given a platform admin on audit, when StudioBff/GetScreenModel composes it, then the evidence comes from AuditService/SearchAudit with its chain position, and AuditService/ExportAudit forwarded through StudioBff/ForwardCommand answers 202 and the page shows the export as requested, the evidence staying redacted as ADR-0019 decision 3 requires (FUX-06). |
| AC2 | Given a platform admin on findings, when they resolve a finding or set a classification, then AuditService/ResolveFinding is forwarded with an idempotency key and a reason, AuditService/SetClassification additionally carries the approval binding of its production class, a 409 of SetClassification is shown with the current classification, and the view refreshes on AuditService/FindingResolved and AuditService/ClassificationChanged (AuditService/ListFindings, AuditService/ListClassifications, FUX-01). |
| AC3 | Given the screen secrets-references, when it renders, then SecretBrokerService/ListSecretReferences and SecretBrokerService/ListRunIssuances show metadata only, no page shows or accepts a secret value, SecretBrokerService/RegisterSecretReference, SecretBrokerService/RotateSecret and SecretBrokerService/RevokeSecretReference are offered to a session that holds factory.secrets.admin and forwarded with the approval binding of the production class, a workspace admin without that scope sees them disabled with the reason, and the view refreshes on SecretBrokerService/SecretReferenceRegistered (NFR-03). |
| AC4 | Given an observer, a resource of another tenant or a missing scope, when a screen or a command is requested, then the controls are disabled with the reason for the observer, the answer is 404 for the other tenant and 403 for the missing scope, and AuditService/FindingRaised refreshes the findings of an open page without a reload (ADR-0015, ADR-0019). |
| Traces: services | StudioBff, AuditService, SecretBrokerService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, AuditService/SearchAudit, AuditService/ExportAudit, AuditService/ListFindings, AuditService/ListClassifications, AuditService/ResolveFinding, AuditService/SetClassification, SecretBrokerService/ListSecretReferences, SecretBrokerService/ListRunIssuances, SecretBrokerService/RegisterSecretReference, SecretBrokerService/RotateSecret, SecretBrokerService/RevokeSecretReference |
| Traces: events | AuditService/FindingRaised, AuditService/FindingResolved, AuditService/ClassificationChanged, SecretBrokerService/SecretReferenceRegistered |
| Traces: adrs | ADR-0015, ADR-0019 |
| Traces: requirements | FUX-01, FUX-06 |
| Relates: screens | audit, findings, secrets-references |
| Relates: nfrs | NFR-03 |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:audit-service-complete, feature:secret-broker-service, feature:governance-host |
| Sources | model/ux/screens.yaml, model/services/governance/AuditService.yaml, model/services/governance/SecretBrokerService.yaml, docs/architecture/adr/0019-data-governance.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5633 Audit, findings and secret reference screens in the Governance microfrontend |
ui | The Governance microfrontend renders audit, findings and secrets-references with the freshness family, the chain position of each evidence entry, the reason field of a finding resolution, the class of each command beside its control, metadata-only secret references with no field for a secret value, the secret controls disabled with their reason for a session without factory.secrets.admin, and other disabled controls with their reason. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5634 Screen models and command routes of the audit, findings and secret screens in StudioBff |
contract | StudioBff composes the three screens through GovernanceHost with the freshness of each source, forwards the seven commands with an idempotency key and the scope of the session, adds the approval binding of the production class to SetClassification and the three secret reference commands and none to ResolveFinding, returns the answer of the owning service unchanged, and refreshes the views on FindingRaised, FindingResolved, ClassificationChanged and SecretReferenceRegistered. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5635 Verify the audit, findings and secret screens by role |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving each screen to a platform admin, a workspace admin without factory.secrets.admin, an observer and a caller of another tenant, a 409 on a classification and a log capture that fails when a secret value appears; the tests prove AC1 to AC4 of AIFACTORY-US-1395 (AuditService/SetClassification, SecretBrokerService/RotateSecret). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5698 Verify the StudioBff side of the audit, findings and secret screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-governance-audit-findings-and-secret-references" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (composition through GovernanceHost and the 202 of ExportAudit returned unchanged), AC2 (ResolveFinding forwarded with a reason and no approval binding, SetClassification with the approval binding of its class, refresh on FindingResolved and ClassificationChanged), AC3 (no secret value in any composed model or log, the secret commands forwarded with their approval binding, refresh on SecretReferenceRegistered) and AC4 (404 and 403 returned unchanged, refresh on FindingRaised) of AIFACTORY-US-1395 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-1396: Governance: I register, verify and grant the Azure DevOps connection of a project and see its connector, within the thin scope of the integration services¶
behavior · persona workspace-admin
As a workspace admin, I want to register the one Azure DevOps connection of my project with its credential reference, verify it and grant its use, so that the project gets its source scope only when the connection is verified, and nothing is shown that the integration services do not yet deliver.
In I3 the integration services are delivered thin: IntegrationService holds one Azure DevOps connection per project with its credential reference, and ConnectorRegistryService holds the Azure DevOps connector for template feeds and for opening the change proposal. The screen connections reads ListConnections of IntegrationService through IntegrationHost: the connections of the scope with provider, state, health, rotation due and grant counts. A workspace admin or a platform admin registers the connection with RegisterConnection, naming provider, endpoint policy, credential kind and a Key Vault reference; the value is written to Key Vault by its owner or the Secret Broker flow and never posted through the Studio. VerifyConnection checks the credential through the Secret Broker and a provider health call and is answered with the result; SetGrant grants or narrows the use of the connection by a subject. A second connection for the same project is answered 409. When verification fails the project stays without source scope, as the flow onboard-project of model/ux/flows.yaml states, and the page says so. The screen connectors reads ListConnectors of ConnectorRegistryService, and a platform admin runs the conformance suite with CertifyConnector, a sandbox action answered 202 whose evidence is stored as an artifact. RotateCredential and RevokeConnection of IntegrationService and ListDeliveries, CreateSubscription and ReplayDelivery of ConnectorRegistryService arrive with the complete deliveries of the two services in I5: the screens offer none of them and show the deliveries source as unknown in the freshness family, named. Every command goes through ForwardCommand with an idempotency key and the scope of the session; an observer sees the controls disabled with the reason, a connection of another tenant is answered 404 and a missing scope 403. StudioBff consumes ConnectionRegistered, ConnectionStateChanged, ConnectionGrantChanged and ConnectorActivated and refreshes the open views.
Acceptance criteria
| AC1 | Given a workspace admin on connections, when they register the connection of the project, then StudioBff/ForwardCommand forwards IntegrationService/RegisterConnection with an idempotency key and a Key Vault reference, no field accepts a credential value, a second connection of the project is answered 409, and the list from IntegrationService/ListConnections shows the new connection after IntegrationService/ConnectionRegistered (FUX-01). |
| AC2 | Given a registered connection, when IntegrationService/VerifyConnection fails, then the page shows the failure and that the project stays without source scope as the flow onboard-project of model/ux/flows.yaml states, and IntegrationService/SetGrant narrows or grants use with the view refreshed on IntegrationService/ConnectionGrantChanged and IntegrationService/ConnectionStateChanged. |
| AC3 | Given a platform admin on connectors, when they certify the connector, then ConnectorRegistryService/CertifyConnector answers 202 and the certification state of ConnectorRegistryService/ListConnectors follows ConnectorRegistryService/ConnectorActivated, while deliveries, subscriptions, replay, rotation and revocation are not offered in I3 and the deliveries source is shown unknown (model/backlog/features/integration.yaml). |
| AC4 | Given an observer, a connection of another tenant or a missing scope, when a screen or a command is requested, then the controls are disabled with the reason, the answer is 404 for the other tenant and 403 for the missing scope, and StudioBff/GetScreenModel shows IntegrationHost degraded with its last freshness when it does not answer (ADR-0015). |
| Traces: services | StudioBff, IntegrationService, ConnectorRegistryService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, IntegrationService/ListConnections, IntegrationService/RegisterConnection, IntegrationService/VerifyConnection, IntegrationService/SetGrant, ConnectorRegistryService/ListConnectors, ConnectorRegistryService/CertifyConnector |
| Traces: events | IntegrationService/ConnectionRegistered, IntegrationService/ConnectionStateChanged, IntegrationService/ConnectionGrantChanged, ConnectorRegistryService/ConnectorActivated |
| Traces: adrs | ADR-0015 |
| Traces: requirements | FUX-01 |
| Relates: screens | connections, connectors |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:integration-service-thin, feature:connector-registry-service-thin, feature:integration-host |
| Sources | model/ux/screens.yaml, model/ux/flows.yaml, model/backlog/features/integration.yaml, model/services/integration/IntegrationService.yaml, model/services/integration/ConnectorRegistryService.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5636 Connection and connector screens in the Governance microfrontend |
ui | The Governance microfrontend renders connections and connectors with the deployment-availability and freshness families, a registration form that takes a Key Vault reference and no credential value, the verification result with the source-scope consequence, the grant editor, the certification state, and the deliveries source shown unknown with its name. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5637 Screen models and command routes of the connection and connector screens in StudioBff |
contract | StudioBff composes the two screens through IntegrationHost with the freshness of each source, forwards RegisterConnection, VerifyConnection, SetGrant and CertifyConnector with an idempotency key and the scope of the session, offers no route for the commands of the complete deliveries, and refreshes the views on the four consumed events. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5638 Verify the connection and connector screens in their thin scope |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub that serves a registered connection, a failed verification, a 409 on a second connection, a certification and a 404 of another tenant; the tests prove AC1 to AC4 of AIFACTORY-US-1396 (IntegrationService/VerifyConnection, ConnectorRegistryService/CertifyConnector). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5699 Verify the StudioBff side of the connection and connector screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-governance-connections-and-connectors-thin" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (RegisterConnection forwarded once with its idempotency key and a Key Vault reference, the 409 returned unchanged, refresh on ConnectionRegistered), AC2 (VerifyConnection and SetGrant forwarded, refresh on ConnectionGrantChanged and ConnectionStateChanged), AC3 (the 202 of CertifyConnector, refresh on ConnectorActivated, no route for the commands of the complete deliveries) and AC4 (404 and 403 returned unchanged, IntegrationHost degraded with its last freshness and commands answered 503) of AIFACTORY-US-1396 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-1397: Governance: I manage project membership and delegations through ProjectService and set my notification and Studio preferences¶
behavior · persona workspace-admin
As a workspace admin, I want to grant roles, delegate for a bounded period and revoke a delegation from the Studio, and every user to set how they are notified and how the Studio looks, so that people get exactly the role the Identity service records, and nobody misses an approval for lack of a notification.
The screen users-roles reads ListProjects and GetProject of ProjectService through ControlPlaneApi: the projects of the caller with memberships, delegations, source scope and environments. A workspace admin of the project or a platform admin grants or changes a project role with SetMembership, delegates the same or a lesser role for a bounded period with a reason through Delegate, and revokes a delegation at once through RevokeDelegation. The Identity service is the system of record of role assignments and delegations: ProjectService writes to it with its own workload token and names the acting member, and the Identity service decides from its own records whether that member may act, as the amendments of ADR-0015 for D114 and D115 record; the Studio states no role of its own. The role order of D114 applies: Observer is below every role, Requester, Reviewer, Asset maintainer and Operator are not comparable and each is below Workspace admin. Each refusal has its own answer. Delegate answers 400 for an invalid body, a delegation without an expiry among them, 409 for a role greater than the one the grantor holds, 404 for a project of another tenant, 403 for a token without factory.projects.delegate and 503 while the Identity service does not answer. SetMembership answers 400 for an invalid body, 403 for a token without factory.projects.admin, 404 for a project it does not find and 503 while the Identity service does not answer. RevokeDelegation answers 403 for a token without factory.projects.delegate, 404 for a delegation it does not find and 503 while the Identity service does not answer. In every refusal nothing changed and the page says so in words. The screen notification-preferences at /settings/notifications is open to all seven roles: it reads ListNotifications of StudioNotificationService, which StudioBff fronts, sets the channels per kind, the quiet hours and the digest through SetNotificationPreferences, and sets the locale (en, he, ru), theme, reduced motion and default work area through SetStudioPreferences of StudioBff; the next session starts with them. StudioBff consumes MembershipChanged and DelegationChanged and refreshes the project view.
Acceptance criteria
| AC1 | Given a workspace admin on users-roles, when they grant a role, delegate or revoke, then StudioBff/ForwardCommand forwards ProjectService/SetMembership, ProjectService/Delegate or ProjectService/RevokeDelegation with an idempotency key, and the page shows the role the project holds after ProjectService/MembershipChanged or ProjectService/DelegationChanged refreshes the view of ProjectService/GetProject (ADR-0015, FUX-01). |
| AC2 | Given a refused membership or delegation command, when it is sent, then ProjectService/Delegate answers 400 for an invalid body or a delegation without expiry, 409 for a role greater than the one the grantor holds, 404 for a project of another tenant, 403 for a token without factory.projects.delegate and 503 while the Identity service does not answer; ProjectService/SetMembership answers 400, 403, 404 or 503 for an invalid body, a token without factory.projects.admin, a project not found or an unavailable Identity service; ProjectService/RevokeDelegation answers 403, 404 or 503 for a token without factory.projects.delegate, a delegation not found or an unavailable Identity service; in each case nothing changes and the page explains the refusal in words (ADR-0015 amendments for D114 and D115). |
| AC3 | Given any of the seven roles on notification-preferences, when the user saves channels, quiet hours and digest and their locale, theme and reduced motion, then StudioNotificationService/SetNotificationPreferences and StudioBff/SetStudioPreferences record them, StudioNotificationService/ListNotifications shows the notifications with unread counts, and the next session starts with the saved preferences (docs/planes/experience/studio/localization-accessibility.md). |
| AC4 | Given an observer or a role other than workspace admin and platform admin on users-roles, when the screen renders, then StudioBff/GetScreenModel refuses it with 403 because the list of model/ux/screens.yaml does not name the role, and ProjectService/ListProjects shows only the projects of the caller. |
| Traces: services | StudioBff, ProjectService, StudioNotificationService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, StudioBff/SetStudioPreferences, ProjectService/ListProjects, ProjectService/GetProject, ProjectService/SetMembership, ProjectService/Delegate, ProjectService/RevokeDelegation, StudioNotificationService/ListNotifications, StudioNotificationService/SetNotificationPreferences |
| Traces: events | ProjectService/MembershipChanged, ProjectService/DelegationChanged |
| Traces: adrs | ADR-0015 |
| Traces: requirements | FUX-01 |
| Relates: screens | users-roles, notification-preferences |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:project-service, feature:control-plane-api, feature:studio-notification-service |
| Sources | model/ux/screens.yaml, model/services/control-plane/ProjectService.yaml, model/services/factory-studio/StudioNotificationService.yaml, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5639 Users and roles and notification preference screens |
ui | The Governance microfrontend renders users-roles with memberships, delegations with grantor, expiry and reason, a delegation form that requires an expiry and offers only the same or a lesser role, and each refusal answer in words with the statement that nothing changed; the settings route renders notification-preferences with channels per kind, quiet hours, digest, locale, theme and reduced motion. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5640 Screen models and command routes of the users and preferences screens in StudioBff |
contract | StudioBff composes users-roles through ControlPlaneApi and notification-preferences from StudioNotificationService with the freshness of each source, forwards SetMembership, Delegate and RevokeDelegation with an idempotency key and returns their answers unchanged, routes SetNotificationPreferences to StudioNotificationService and stores SetStudioPreferences on the session, and refreshes the project view on MembershipChanged and DelegationChanged. The Workspace area reuses these three membership routes. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5641 Verify the users, roles and preferences screens |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub that answers a granted role; for Delegate a delegation without expiry answered 400, a greater role answered 409, a token without factory.projects.delegate answered 403, a project of another tenant answered 404 and an Identity outage answered 503; for SetMembership an invalid body answered 400, a token without factory.projects.admin answered 403, a project not found answered 404 and an Identity outage answered 503; for RevokeDelegation a 403, a 404 and a 503; and saved preferences applied to the next session; the tests prove AC1 to AC4 of AIFACTORY-US-1397 (ProjectService/Delegate, StudioBff/SetStudioPreferences). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5700 Verify the StudioBff side of the users, roles and preferences screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-governance-users-roles-and-notification-preferences" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (the three membership commands forwarded once with an idempotency key, refresh on MembershipChanged and DelegationChanged), AC2 (every 400, 403, 404, 409 and 503 of Delegate, SetMembership and RevokeDelegation returned unchanged with nothing queued), AC3 (SetNotificationPreferences routed to StudioNotificationService and SetStudioPreferences stored for the next session) and AC4 (403 of GetScreenModel for a role the screen does not name) of AIFACTORY-US-1397 (StudioBff/ForwardCommand, StudioBff/SetStudioPreferences). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-130: The Governance & administration work area of the Studio is bound to the model¶
behavior · persona workspace-admin
As a workspace admin, I want the Governance & administration work area of the Studio (14 screens) bound to the read models, commands, state families and roles the model names for it, so that I can onboard projects and people under the tenant's policy from one place, with every control reflecting what I may do and how fresh what I see is.
This is the integration PBI of the Governance and administration area. The Governance microfrontend is generated from the microfrontend library template, composed into the Studio shell through its registry and holds the fourteen screens of model/ux/screens.yaml with their routes, read models, commands, state families and roles; it calls StudioBff only. A screen is offered to the roles its list names; for any other role it is absent from the navigation and GetScreenModel refuses it with 403. Eight screens are delivered by AIFACTORY-US-1394 to AIFACTORY-US-1397. Six read services delivered after I3: approval-policy reads ApprovalPolicyService, topic-registry EnvelopeRegistryService, stores StoreProfileService, and retention-residency and governance-orders RetentionResidencyService, all delivered in I4; editions-billing reads FactoryCommercialService, delivered in I7. In I3 each of these is registered, offered to its roles and shows its sources as unknown in the freshness family, named, never hidden and never filled from a fake; none of its commands is offered, so the refusal of a retention longer than the platform ceiling and the edition changes wait for those increments. Every screen subscribes through Realtime.Subscribe of StudioRealtimeGateway; when the channel drops the page marks its data stale and when it returns the page reloads the screen model. A command needing the approval binding of its class carries it to the owning service, whose gate decides; StudioBff and the Studio hold no approval of their own. Every screen renders in English, Russian and Hebrew right to left and is built to the accessibility contract of docs/planes/experience/studio/localization-accessibility.md; the area evidence that follows this PBI checks it on the finished area.
Acceptance criteria
| AC1 | Given the shell with the Governance microfrontend, when each of the 14 screens of model/ux/screens.yaml opens for a role its list names, then it renders from StudioBff/GetScreenModel only, and for a role its list does not name the screen is not offered and StudioBff/GetScreenModel answers 403 (ADR-0007, ADR-0015). |
| AC2 | Given approval-policy, topic-registry, stores, retention-residency, governance-orders and editions-billing, when they open in I3, then each shows its sources as unknown in the freshness family of model/ux/states.yaml with the source named, shows no invented value and offers none of its commands (FUX-12). |
| AC3 | Given an open screen and its subscription through StudioRealtimeGateway/Realtime.Subscribe, when the channel drops, then the page marks the data stale and never presents it as current, and when the channel returns the page reloads StudioBff/GetScreenModel and shows the current state without a browser reload (FUX-01). |
| AC4 | Given a command of a delivered screen, when a role issues it, then it is forwarded once through StudioBff/ForwardCommand with an idempotency key, the scope of the session and the approval binding its class requires, a role without the right sees the control disabled with the reason, and the screens render in en, ru and he right to left under docs/planes/experience/studio/localization-accessibility.md. |
| Traces: services | StudioBff, StudioRealtimeGateway, PolicyEngineService, AuditService, SecretBrokerService, IntegrationService, ConnectorRegistryService, ProjectService |
| Traces: apis | StudioBff/GetStudioSession, StudioBff/GetScreenModel, StudioBff/ForwardCommand, StudioRealtimeGateway/Realtime.Subscribe |
| Traces: adrs | ADR-0007, ADR-0015 |
| Traces: requirements | FUX-01, FUX-12 |
| Relates: screens | approval-policy, topic-registry, stores, retention-residency, governance-orders, editions-billing |
| Depends on | AIFACTORY-US-1394, AIFACTORY-US-1395, AIFACTORY-US-1396, AIFACTORY-US-1397, feature:studio-bff, feature:studio-realtime-gateway, feature:component-blazor-shell |
| Sources | model/ux/screens.yaml, model/ux/states.yaml, model/ux/prototype-alignment.yaml, docs/planes/experience/studio/screens/governance-administration.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-436 Screens of the work area Governance & administration: Policies, Approval policy, Audit search, Findings and classifications, Secret references, Connections, Connectors and deliveries, Topic regist ... |
ui | The Governance microfrontend is composed into the shell through the registry with one navigation group and the fourteen routes of model/ux/screens.yaml; each screen renders from StudioBff only, and the six screens of later sources render their sources as unknown with the source named and no command. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-437 Commands of the work area Governance & administration |
implementation | The commands of the eight delivered screens are forwarded through StudioBff with an idempotency key, the scope of the session and the approval binding their class requires, and the commands of the six screens of later sources (approval rules, retention, residency, governance orders, subscriptions) are not offered in I3. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-438 States, roles, locales and accessibility of the work area Governance & administration |
implementation | Each screen shows the state families the model names for it, hides or disables what the role may not do with the reason, marks stale data on a dropped channel and reloads on its return, renders in every supported locale including right-to-left, and passes the accessibility checks of the UX model. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-743 Verify studio-governance-administration-work-area by running the declared command |
verification | Run dotnet build -c Release, dotnet test -c Release --no-build and npx playwright test --project=chromium; they pass and prove AC1 to AC4 of AIFACTORY-US-130 (StudioBff/GetScreenModel, StudioRealtimeGateway/Realtime.Subscribe). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-US-1398: Governance and administration area evidence: every screen passes the accessibility and phone-width checks and an end-to-end walk of the area through StudioBff is recorded¶
evidence · persona observer
As an observer, I want proof that every screen of the Governance and administration area is usable by keyboard, in every locale and at phone width, and that a walk of the area reads only StudioBff, so that the area is accepted on a recorded check.
This PBI is the proof of the Governance and administration area and comes after its integration PBI AIFACTORY-US-130, which registers the fourteen screens. The accessibility and phone-width check opens each of the fourteen screens of the area for a role its list in model/ux/screens.yaml names and asserts the rules of docs/planes/experience/studio/localization-accessibility.md: WCAG 2.2 AA by the automated checks, keyboard operation with a visible focus ring and focus returned to the triggering control after a dialog, validation messages tied to their fields and refusals explained in words, reduced motion honoured, in English, Russian and Hebrew rendered right to left, light and dark, at 1440 by 900 and at 390 by 844 with no horizontal scroll. The end-to-end walk follows the part of the flow onboard-project of model/ux/flows.yaml that I3 delivers, as a workspace admin: the policy bundle in force and the validation of a stricter override, the registration and verification of the Azure DevOps connection, a role granted and a bounded delegation, and the notification preferences; then, as a platform admin, an audit search, a finding resolved with a reason and a secret reference registered; and as an observer, the same screens without commands. The screens whose sources arrive in I4 or I7 show their sources as unknown and are listed by name. The record holds per screen and role the expected and observed result and the network log, which shows no address other than StudioBff and StudioRealtimeGateway; no secret value appears in the record or the log.
Acceptance criteria
| AC1 | Given each of the 14 screens of the area in model/ux/screens.yaml, when the accessibility check runs in the three locales, both schemes and the two viewports of docs/planes/experience/studio/localization-accessibility.md, then every screen passes the automated WCAG 2.2 AA checks and keyboard operation, renders Hebrew right to left and has no horizontal scroll at 390 by 844 (NFR-15, FUX-12). |
| AC2 | Given the walk as a workspace admin, a platform admin and an observer, when it runs on the acceptance estate, then every screen renders from StudioBff/GetScreenModel, every command it issues goes through StudioBff/ForwardCommand, the offered commands match the roles of model/ux/screens.yaml, and every screen of a later source is listed by name (ADR-0007). |
| AC3 | Given the record and the network log of the walk, when they are read, then the browser called no address other than StudioBff and StudioRealtimeGateway and no secret value appears in either (NFR-03, FUX-12). |
| Traces: services | StudioBff |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand |
| Traces: adrs | ADR-0007 |
| Traces: requirements | FUX-12 |
| Relates: screens | policies, approval-policy, audit, findings, secrets-references, connections, connectors, topic-registry, stores, retention-residency, governance-orders, users-roles, editions-billing, notification-preferences |
| Relates: nfrs | NFR-15, NFR-03 |
| Depends on | AIFACTORY-US-1394, AIFACTORY-US-1395, AIFACTORY-US-1396, AIFACTORY-US-1397, AIFACTORY-US-130, feature:studio-bff, feature:component-blazor-shell |
| Sources | model/ux/screens.yaml, model/ux/flows.yaml, docs/planes/experience/studio/localization-accessibility.md, docs/planes/experience/studio/screens/governance-administration.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5642 End-to-end walk of the Governance and administration area |
fixture | A browser-driven walk in the Studio repository that signs in as a workspace admin, a platform admin and an observer, follows the delivered part of the flow onboard-project and the audit, findings and secret screens, and records per screen and role the rendered state, the offered commands, the answers and the addresses the browser called, with a check that fails when a secret value appears. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5643 Accessibility and phone-width check of the Governance screens |
verification | Run dotnet test -c Release --filter Category=Accessibility, npx playwright test --project=chromium at 1440 by 900 and npx playwright test --project=phone-390x844, the Playwright project of the Studio at 390 by 844, on the fourteen screens in en, ru and he, light and dark; the results prove AC1 of AIFACTORY-US-1398 against docs/planes/experience/studio/localization-accessibility.md. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5644 Verify the walk record of the Governance area |
verification | Run the walk of AIFACTORY-TASK-5642 on the acceptance estate; its record and network log prove AC2 and AC3 of AIFACTORY-US-1398 (StudioBff/GetScreenModel, StudioBff/ForwardCommand) and are kept with the evidence of increment I3. | ConnectSoft.AI.SoftwareFactory.Studio |