Skip to content

AIFACTORY-FEAT-081: Studio work area: Workspace

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 121 of 185 (Factory code)

The 8 screens of the Studio work area Workspace 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: Workspace
Requirements —
Depends on —
Sources model/ux/screens.yaml, model/ux/prototype-alignment.yaml

AIFACTORY-US-1412: Workspace: I land on my work with my runs, approvals and notifications in my scope, switch the scope, and read the overview of a project

behavior · persona requester As a requester, I want one landing page with the runs and approvals that concern me and my notifications, a scope I can switch, and an overview of a project, so that I see what waits on me and how a project stands without searching for it.

Any user with a Studio role opens the screen my-work at /work. StudioBff composes it from GetStudioSession with the user, the roles in each scope and the current tenant and project, from ListNotifications of StudioNotificationService with unread counts by importance, and from ListRuns and ListApprovals of RunControlService, reached through ControlPlaneApi, filtered to the trusted scope of the session. The user switches the current tenant or project with SetStudioScope of StudioBff; a scope the user holds no role in is answered 403, and every screen model after the switch is composed for the new scope. A requester, a reviewer, an operator, a workspace admin or an observer opens project-overview at /projects/{projectId}, composed from GetProject of ProjectService with memberships, delegations and source scope, ListEnvironments of EnvironmentService, GetProjectUsage of CostUsageService and ListRuns for the project. The run, approval, usage and freshness families of model/ux/states.yaml govern the display; uncertain usage is shown apart and never folded into a total. A project of another tenant is answered 404 like one that does not exist, and a project in the tenant the user holds no scope in is answered 403 (ADR-0015). StudioBff consumes RunStateChanged and ApprovalRequested of RunControlService and refreshes the lists, and the realtime gateway pushes NotificationCreated, so a new approval or notification appears on the open page without a reload. When ControlPlaneApi does not answer, the run and project sources are shown degraded with their last freshness while the notifications stay current.

Acceptance criteria

AC1 Given a user on my-work, when StudioBff/GetScreenModel composes it, then it shows the session from StudioBff/GetStudioSession, notifications from StudioNotificationService/ListNotifications and runs and approvals from RunControlService/ListRuns and RunControlService/ListApprovals in the trusted scope, with the freshness of each source (FUX-01).
AC2 Given a user with roles in two projects, when they switch the scope through StudioBff/SetStudioScope, then every screen model is composed for the new scope, a scope without a role is answered 403, and RunControlService/ApprovalRequested or StudioNotificationService/NotificationCreated show on the open page without a reload (FUX-04).
AC3 Given project-overview, when it opens, then it renders from ProjectService/GetProject, EnvironmentService/ListEnvironments, CostUsageService/GetProjectUsage and RunControlService/ListRuns with uncertain usage apart, and a project of another tenant is answered 404 like an unknown one (ADR-0015, FUX-08).
Traces: services StudioBff, StudioNotificationService, RunControlService, ProjectService, EnvironmentService, CostUsageService
Traces: apis StudioBff/GetStudioSession, StudioBff/SetStudioScope, StudioBff/GetScreenModel, StudioNotificationService/ListNotifications, RunControlService/ListRuns, RunControlService/ListApprovals, ProjectService/GetProject, EnvironmentService/ListEnvironments, CostUsageService/GetProjectUsage
Traces: events RunControlService/RunStateChanged, RunControlService/ApprovalRequested, StudioNotificationService/NotificationCreated
Traces: adrs ADR-0015
Traces: requirements FUX-01, FUX-04, FUX-08
Relates: screens my-work, project-overview
Depends on feature:studio-bff, feature:component-blazor-shell, feature:studio-notification-service, feature:run-control-service, feature:project-service, feature:environment-service, feature:cost-usage-service-complete, feature:control-plane-api
Sources model/ux/screens.yaml, model/ux/states.yaml, model/services/factory-studio/StudioBff.yaml, model/services/control-plane/RunControlService.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-5681 My work and project overview screens in the Workspace microfrontend ui The Workspace microfrontend renders my-work with the scope switcher, the runs and approvals of the scope and the notifications with unread counts, and project-overview with memberships, delegations, source scope, environments, usage by status with uncertain amounts apart and the runs of the project, each with its freshness. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5682 Screen models and scope route of the landing screens in StudioBff contract StudioBff composes my-work and project-overview from the session, StudioNotificationService and ControlPlaneApi with the freshness of each source, applies SetStudioScope to every later composition, answers 404 for a project of another tenant and 403 for a scope without a role, and refreshes the lists on RunStateChanged and ApprovalRequested. ConnectSoft.AI.SoftwareFactory.StudioBff
AIFACTORY-TASK-5683 Verify the landing screens across a scope switch verification Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving a user with roles in two projects, a pushed approval and notification, a project of another tenant and an unreachable control plane; the tests prove AC1 to AC3 of AIFACTORY-US-1412 (StudioBff/SetStudioScope, RunControlService/ListApprovals). ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5710 Verify the StudioBff side of the landing screens verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-workspace-my-work-and-project-overview" 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 of my-work from the session, StudioNotificationService and ControlPlaneApi in the trusted scope with the freshness of each source), AC2 (SetStudioScope applied to every later composition, 403 for a scope without a role, refresh on ApprovalRequested and RunStateChanged) and AC3 (composition of project-overview, the 404 of another tenant, the run and project sources degraded while ControlPlaneApi does not answer) of AIFACTORY-US-1412 (StudioBff/GetScreenModel, StudioBff/SetStudioScope). ConnectSoft.AI.SoftwareFactory.StudioBff

AIFACTORY-US-1413: Workspace: I submit a run by alias with its limits and follow it in the run detail with its steps, receipts, artifacts and usage, and cancel it

behavior · persona requester As a requester, I want to submit a vision as a run with its scope and limits and follow it step by step with what it called, produced and consumed, so that I see progress, what waits on me and what the run cost without reloading the page.

A requester opens the screen run-submit at /work/runs/new. StudioBff composes it from GetProjectUsage of CostUsageService, so the requester sees the budget left before submitting, and from ListModelProfiles of ModelRouterService for the profiles a run may use. The list of asset releases, ListReleases of AgentRegistryService, is delivered in I4; in I3 that source is shown unknown, named, and the run is submitted by alias. The requester submits the vision with its scope and limits through ForwardCommand, which forwards SubmitRun of RunControlService once with an idempotency key; the page shows the run only once RunAccepted is consumed. Every 409 is explained in words: a key reused with another body, which is the adverse branch of the flow submit-assessment of model/ux/flows.yaml, a suspended or closed project, an alias that points at a deprecated or revoked release, a retired target environment, and a production target whose pinned release is not Published; a body that carries a parent field is answered 400. When CostUsageService denies the budget reservation of the run, StudioBff consumes BudgetReservationDenied, and run-detail names the limiting budget or quota without a reload and does not present the run as progressing, which is the adverse branch of the same flow for an exhausted budget. A requester, a reviewer, an operator or an observer opens run-detail at /work/runs/{runId}, composed from GetRun with steps, attempts, the current lease and pending approvals, ListRunReceipts of ModelRouterService and ListRunToolReceipts of ToolAdapterService by hash and never by content, ListRunArtifacts of ArtifactService with their validation state and GetRunUsage with usage by status, uncertain amounts apart. The run timeline of DashboardService is delivered in I4 and shown unknown. A failed step shows its failure class and recorded outcome. A run of another tenant is answered 404 by GetRun like one that does not exist. The requester or an operator cancels a run with CancelRun; the page says that cancellation is requested and shows the run cancelled only once RunCancelled is consumed. StudioBff follows the run through RunControl.WatchRun and refreshes the run view on RunStateChanged, RunCompleted, RunFailed and RunCancelled, and the page updates without a reload; after the realtime channel returns the screen reloads its model, and a model older than its freshness limit is marked stale with its age and never shown as current.

Acceptance criteria

AC1 Given a requester on run-submit, when they submit, then StudioBff/ForwardCommand forwards RunControlService/SubmitRun once with an idempotency key, the run appears only once RunControlService/RunAccepted is consumed, every 409 is explained in words (a key reused with another body as the flow submit-assessment of model/ux/flows.yaml states, a suspended or closed project, an alias of a deprecated or revoked release, a retired target environment and a production target whose pinned release is not Published), a body that carries a parent field is answered 400, and the release list is shown unknown with submission by alias (ADR-0014, FUX-03).
AC2 Given run-detail, when StudioBff/GetScreenModel composes it, then it renders from RunControlService/GetRun, ModelRouterService/ListRunReceipts, ToolAdapterService/ListRunToolReceipts, ArtifactService/ListRunArtifacts and CostUsageService/GetRunUsage, receipts by hash only, uncertain usage apart, a failed step shows its failure class and outcome, and a run of another tenant is answered 404 by RunControlService/GetRun like an unknown one (FUX-06, FUX-08).
AC3 Given a running run followed through RunControlService/RunControl.WatchRun, when RunControlService/RunStateChanged, RunControlService/RunCompleted or RunControlService/RunFailed is consumed, then the page shows the new state without a reload, and after a dropped channel returns the page reloads StudioBff/GetScreenModel and marks nothing stale as current (FUX-04, FUX-07).
AC4 Given a running run, when the requester or an operator cancels it through RunControlService/CancelRun, then the page says the cancellation is requested and shows the run cancelled only once RunControlService/RunCancelled is consumed (ADR-0024).
AC5 Given a run whose budget reservation is denied, when CostUsageService/BudgetReservationDenied is consumed by StudioBff, then run-detail names the limiting budget or quota without a reload and does not present the run as progressing, as the flow submit-assessment of model/ux/flows.yaml states for an exhausted budget (FUX-08).
Traces: services StudioBff, RunControlService, ModelRouterService, ToolAdapterService, ArtifactService, CostUsageService
Traces: apis StudioBff/GetScreenModel, StudioBff/ForwardCommand, RunControlService/SubmitRun, RunControlService/GetRun, RunControlService/CancelRun, RunControlService/RunControl.WatchRun, ModelRouterService/ListModelProfiles, ModelRouterService/ListRunReceipts, ToolAdapterService/ListRunToolReceipts, ArtifactService/ListRunArtifacts, CostUsageService/GetProjectUsage, CostUsageService/GetRunUsage
Traces: events RunControlService/RunAccepted, RunControlService/RunStateChanged, RunControlService/RunCompleted, RunControlService/RunFailed, RunControlService/RunCancelled, CostUsageService/BudgetReservationDenied
Traces: adrs ADR-0014, ADR-0024
Traces: requirements FUX-03, FUX-04, FUX-06, FUX-07, FUX-08
Relates: screens run-submit, run-detail
Depends on feature:studio-bff, feature:component-blazor-shell, feature:run-control-service, feature:control-plane-api, feature:model-router-service, feature:model-gateway-host, feature:tool-adapter-service, feature:tool-executor-host, feature:artifact-service, feature:knowledge-host, feature:cost-usage-service-complete
Sources model/ux/screens.yaml, model/ux/flows.yaml, model/services/control-plane/RunControlService.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-516 Run submission screen ui The Workspace microfrontend renders run-submit, which collects the vision, the scope, the alias and the limits, shows the budget left and the model profiles, marks the release list unknown, forwards one command with an idempotency key and shows the run once it is accepted, with each 409 explained in words. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-517 Run detail with live step states ui The Workspace microfrontend renders run-detail with steps, attempts, the lease and pending approvals, model and tool receipts by hash, artifacts with their validation state, usage by status, the run timeline source marked unknown, the failure class of a failed step, and a cancel control that waits for the observed state. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-518 Reconnect and freshness implementation The screen reloads its model after a reconnect and marks a model older than its freshness limit as stale with its age. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5694 Run following and run view refresh in StudioBff implementation StudioBff follows the run through RunControl.WatchRun and refreshes the run view on RunStateChanged, RunCompleted, RunFailed and RunCancelled, and the reservation view on BudgetReservationDenied. ConnectSoft.AI.SoftwareFactory.StudioBff
AIFACTORY-TASK-5684 Verify submission and the live run detail verification Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving an accepted run, each 409 of submission including a retired target environment, a 400 for a body with a parent field, a run of another tenant answered 404 by GetRun, a denied budget reservation pushed live, steps changing live, a failed step, a dropped and returned channel and an observed cancellation; the tests prove AC1 to AC5 of AIFACTORY-US-1413 (RunControlService/SubmitRun, RunControlService/CancelRun). ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5711 Verify the StudioBff side of submission and the run detail verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-workspace-run-submit-and-detail" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (SubmitRun forwarded once with its idempotency key, its 409 and 400 returned unchanged, refresh on RunAccepted, the release list source marked unknown), AC2 (composition of run-detail from the five sources with receipts by hash only and the 404 of GetRun returned unchanged), AC3 (RunControl.WatchRun followed and refresh on RunStateChanged, RunCompleted and RunFailed), AC4 (CancelRun forwarded once, refresh on RunCancelled) and AC5 (refresh of the reservation view on BudgetReservationDenied) of AIFACTORY-US-1413 (StudioBff/ForwardCommand, RunControlService/RunControl.WatchRun). ConnectSoft.AI.SoftwareFactory.StudioBff

AIFACTORY-US-1414: Workspace: I administer a project's members, delegations, source scope and budget, and create, freeze and unfreeze its environments

behavior · persona workspace-admin As a workspace admin, I want to grant roles, delegate for a bounded period, set the source scope and budget of a project, and manage its environments, so that a project is onboarded and governed from the Studio with every refusal explained.

A workspace admin opens the screen project-settings at /projects/{projectId}/settings, composed from GetProject of ProjectService through ControlPlaneApi. Through ForwardCommand with an idempotency key they grant or change a role with SetMembership, delegate the same or a lesser role for a bounded period with a reason with Delegate, revoke a delegation with RevokeDelegation, replace the repositories, collections and tools a run may touch with SetSourceScope, and set the budget with SetProjectBudget of CostUsageService. The adverse branches of the flow onboard-project of model/ux/flows.yaml are explained in words: a delegation without an expiry is refused, a source scope outside the connected repositories is refused, and a threshold above the platform one is answered 409. Identity is the system of record of roles, so a role change answers 503 while Identity is unavailable and the page says that nothing changed (D114). An operator, a workspace admin or an observer opens environment-board at /projects/{projectId}/environments, composed from ListEnvironments of EnvironmentService and GetCurrentRelease of EnvironmentPromotionService for each environment. A workspace admin creates an environment with a policy class with CreateEnvironment, and freezes or unfreezes one with FreezeEnvironment and UnfreezeEnvironment, production-class commands that carry the approval binding of their class; the page says that a production environment needs its baseline provisioned under an approval. A project of another tenant is answered 404. The delivery and freshness families of model/ux/states.yaml govern the display. StudioBff consumes MembershipChanged, DelegationChanged, EnvironmentCreated and EnvironmentStateChanged and refreshes the open page without a reload.

Acceptance criteria

AC1 Given a workspace admin on project-settings, when they grant a role, delegate, revoke or set the source scope, then StudioBff/ForwardCommand forwards ProjectService/SetMembership, ProjectService/Delegate, ProjectService/RevokeDelegation or ProjectService/SetSourceScope, and the page shows the change only once ProjectService/MembershipChanged or ProjectService/DelegationChanged is consumed (FUX-01).
AC2 Given the adverse branches of the flow onboard-project of model/ux/flows.yaml, when a delegation has no expiry, a source scope is outside the connected repositories, a threshold sent through CostUsageService/SetProjectBudget is above the platform one or Identity is unavailable, then each refusal is explained in words and nothing changes (ADR-0015).
AC3 Given environment-board, when StudioBff/GetScreenModel composes it, then it renders from EnvironmentService/ListEnvironments and EnvironmentPromotionService/GetCurrentRelease, and EnvironmentService/CreateEnvironment, EnvironmentService/FreezeEnvironment and EnvironmentService/UnfreezeEnvironment are offered to a workspace admin with the approval binding of their class and disabled with the reason for other roles (FUX-02, FUX-05).
Traces: services StudioBff, ProjectService, CostUsageService, EnvironmentService, EnvironmentPromotionService
Traces: apis StudioBff/GetScreenModel, StudioBff/ForwardCommand, ProjectService/GetProject, ProjectService/SetMembership, ProjectService/Delegate, ProjectService/RevokeDelegation, ProjectService/SetSourceScope, CostUsageService/SetProjectBudget, EnvironmentService/ListEnvironments, EnvironmentService/CreateEnvironment, EnvironmentService/FreezeEnvironment, EnvironmentService/UnfreezeEnvironment, EnvironmentPromotionService/GetCurrentRelease
Traces: events ProjectService/MembershipChanged, ProjectService/DelegationChanged, EnvironmentService/EnvironmentCreated, EnvironmentService/EnvironmentStateChanged
Traces: adrs ADR-0015
Traces: requirements FUX-01, FUX-02, FUX-05
Relates: screens project-settings, environment-board
Depends on feature:studio-bff, feature:component-blazor-shell, feature:project-service, feature:environment-service, feature:cost-usage-service-complete, feature:control-plane-api, feature:environment-promotion-service, feature:delivery-host, feature:studio-governance-administration, feature:studio-operations-usage, feature:studio-software-factory
Sources model/ux/screens.yaml, model/ux/flows.yaml, model/services/control-plane/ProjectService.yaml, model/services/control-plane/EnvironmentService.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-5685 Project settings and environment board screens in the Workspace microfrontend ui The Workspace microfrontend renders project-settings with members, delegations with their expiry and reason, source scope and budget forms, and environment-board with environments by class and state and the current release of each, the create, freeze and unfreeze controls with the class of the action, and each refusal of the flow onboard-project explained in words. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5686 Screen models and command routes of the project administration screens in StudioBff contract StudioBff composes project-settings and environment-board through ControlPlaneApi and DeliveryHost with the freshness of each source, forwards SetSourceScope and the environment commands CreateEnvironment, FreezeEnvironment and UnfreezeEnvironment with an idempotency key and the approval binding of their class, and refreshes the views on EnvironmentCreated and EnvironmentStateChanged. It adds no second route for what earlier tasks deliver: it reuses the routes of SetMembership, Delegate and RevokeDelegation and the refresh on MembershipChanged and DelegationChanged of AIFACTORY-TASK-5640, the route of SetProjectBudget of AIFACTORY-TASK-5655 and the composition of GetCurrentRelease of AIFACTORY-TASK-5673. ConnectSoft.AI.SoftwareFactory.StudioBff
AIFACTORY-TASK-5687 Verify project onboarding refusals and environment commands verification Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving a delegation without expiry, a source scope outside the connected repositories, a threshold above the platform one, an Identity outage, a frozen production environment and an observer session; the tests prove AC1 to AC3 of AIFACTORY-US-1414 (ProjectService/Delegate, EnvironmentService/FreezeEnvironment). ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5712 Verify the StudioBff side of the project administration screens verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-workspace-project-settings-and-environments" 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 membership, delegation and source scope commands forwarded once with an idempotency key, refresh on MembershipChanged and DelegationChanged), AC2 (the refusals of Delegate, SetSourceScope and SetProjectBudget and the 503 of an unavailable Identity service returned unchanged with nothing queued) and AC3 (composition of environment-board through ControlPlaneApi and DeliveryHost, the environment commands forwarded with the approval binding of their class, refresh on EnvironmentCreated and EnvironmentStateChanged) of AIFACTORY-US-1414 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). ConnectSoft.AI.SoftwareFactory.StudioBff

AIFACTORY-US-034: I decide approvals on the exact proposal I was shown

behavior · persona reviewer As a reviewer, I want an inbox of the approvals that wait for me, each with the exact proposal version and its evidence, so that I never approve something other than what I reviewed.

A reviewer, an operator or a platform admin opens the screen approvals-list at /work/approvals, composed from ListApprovals of RunControlService through ControlPlaneApi, with the pending and decided requests visible to the roles of the caller. A reviewer opens approval-card at /work/approvals/{approvalId} with the exact proposal version and its hash, the run from GetRun and the evidence from ListRunArtifacts of ArtifactService. The approval family of model/ux/states.yaml governs the display: Pending, Approved, Rejected, Expired and Superseded. The reviewer approves, rejects or requests changes through ForwardCommand, which forwards DecideApproval with the proposal hash and the request version, and the card shows the decision only once ApprovalDecided is consumed. Each answer of DecideApproval is shown in words. A request whose version changed after the card was opened is answered 409 and the card offers the current version, which is the flow review-exact-proposal of model/ux/flows.yaml. A request that expired while it was read is answered 410; the card shows Expired and says that a new request is needed, the adverse branch of the same flow. A request for changes on a spend approval is answered 409 and explained. A 503 means that nothing was recorded, and the card offers to send the decision again. The requester of the run, and the author of the proposal, see the card without the decision controls and with the reason, and a decision they send anyway is answered 403. The production approval of a promotion appears here too: it is the one approval a person gives for a production promotion, the gate of EnvironmentPromotionService bound to the release and the environment, and the Studio adds no approval of its own (D133). When an approval is requested, StudioBff consumes ApprovalRequested, the eligible reviewers receive a notification that the realtime gateway pushes as NotificationCreated, and the request appears in their open inbox without a reload.

Acceptance criteria

AC1 Given an approval request, when RunControlService/ApprovalRequested is consumed, then it appears in approvals-list of the eligible reviewers from RunControlService/ListApprovals without a reload and each of them receives StudioNotificationService/NotificationCreated listed by StudioNotificationService/ListNotifications (FUX-05).
AC2 Given an approval card, when the reviewer opens it, then the exact proposal version and its hash are shown with the run from RunControlService/GetRun and the evidence from ArtifactService/ListRunArtifacts, and a production promotion approval shows the release and the environment it is bound to (FUX-06).
AC3 Given a decision sent through StudioBff/ForwardCommand to RunControlService/DecideApproval, when the request version changed after the card was opened, then the answer is 409 and the card offers the current version as the flow review-exact-proposal of model/ux/flows.yaml describes; when the request expired, the answer is 410 and the card shows Expired and says a new request is needed; when changes are requested on a spend approval, the answer is 409 explained in words; and when the answer is 503 the card says nothing was recorded and the decision can be sent again (ADR-0014).
AC4 Given the requester of the run, when they open the approval, then they see no decision control and the reason, and a decision they send anyway is answered 403; the card shows a decision only once RunControlService/ApprovalDecided is consumed (ADR-0015).
Traces: services StudioBff, RunControlService, ArtifactService, StudioNotificationService
Traces: apis StudioBff/GetScreenModel, StudioBff/ForwardCommand, RunControlService/ListApprovals, RunControlService/GetRun, RunControlService/DecideApproval, ArtifactService/ListRunArtifacts, StudioNotificationService/ListNotifications
Traces: events RunControlService/ApprovalRequested, RunControlService/ApprovalDecided, StudioNotificationService/NotificationCreated
Traces: adrs ADR-0014, ADR-0015
Traces: requirements FUX-05, FUX-06
Relates: screens approvals-list, approval-card
Depends on feature:studio-bff, feature:component-blazor-shell, feature:run-control-service, feature:control-plane-api, feature:artifact-service, feature:knowledge-host, feature:studio-notification-service
Sources model/ux/screens.yaml, model/ux/flows.yaml, model/services/control-plane/RunControlService.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-519 Approval list and approval card ui The Workspace microfrontend renders approvals-list with the approvals that wait for the user and approval-card with the proposal version, its hash, the run and its evidence, the release and environment of a production promotion approval, and the approval family of model/ux/states.yaml. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-520 Decision bound to the proposal version implementation The decision command carries the proposal hash and the request version through StudioBff; a changed version answered 409 is explained and the current version offered, an expired request answered 410 shows Expired with a new request needed, a request for changes on a spend approval answered 409 is explained, and a 503 says nothing was recorded and offers to send again. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-521 Separation of duties on the card implementation The requester and the author see the card without the decision controls and with the reason, and a decision they send anyway is shown refused with 403. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-751 Verify studio-approval-inbox by running the declared command verification Run dotnet test -c Release --filter Category=Acceptance and npx playwright test --project=chromium with a StudioBff stub serving a pushed approval request, a decision recorded on ApprovalDecided, a changed version answered 409, an expired request answered 410, a request for changes on a spend approval answered 409, a 503 with nothing recorded and a requester decision answered 403; they pass and prove AC1 to AC4 of AIFACTORY-US-034 (RunControlService/DecideApproval, RunControlService/ApprovalDecided). ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5713 Verify the StudioBff side of the approval inbox verification Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-approval-inbox" in StudioBff against stubbed platform gateways, where a filter that matches no test fails the run; the tests prove on the StudioBff side AC1 (refresh of the approval request view on ApprovalRequested for the eligible reviewers), AC2 (composition of approval-card from GetRun and ListRunArtifacts with the proposal version and hash), AC3 (DecideApproval forwarded once with the proposal hash and the request version, its 409, 410 and 503 returned unchanged with nothing queued) and AC4 (its 403 returned unchanged, refresh on ApprovalDecided) of AIFACTORY-US-034 (StudioBff/ForwardCommand, RunControlService/DecideApproval). ConnectSoft.AI.SoftwareFactory.StudioBff

AIFACTORY-US-033: The Workspace work area of the Studio is bound to the model, and I submit a vision and follow the run as it happens

behavior · persona requester As a requester, I want the Workspace work area of the Studio (8 screens) bound to the read models, commands, state families and roles the model names for it, so that I submit a vision and follow the run step by step, seeing progress and what waits on me without reloading the page, with every control reflecting what I may do and how fresh what I see is.

This is the integration PBI of the Workspace area. The Workspace microfrontend is generated from the microfrontend library template, composed into the Studio shell through its registry as the landing area and holds the eight 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. All eight screens are delivered in I3, by AIFACTORY-US-1412 to AIFACTORY-US-1414 and AIFACTORY-US-034; two read models are not: ListReleases of AgentRegistryService on run-submit and the run timeline of DashboardService on run-detail, both delivered in I4, so each is shown as unknown in the freshness family, named, never hidden and never filled from a fake, and the run is submitted by alias. The thread of the area is the first outcome: a requester submits a vision, follows the run as it happens, a reviewer decides its approval on the exact proposal, and the requester reads the result. 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 is forwarded once with an idempotency key, the scope of the session and the approval binding its class requires, and the owning service decides. 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 Workspace microfrontend, when each of the 8 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 the first outcome, when a requester submits a vision through StudioBff/ForwardCommand and RunControlService/SubmitRun, then the accepted run is shown with its identifier and the run detail shows each step state on RunControlService/RunStateChanged without a reload, and a failed step shows its failure class and recorded outcome (ADR-0014, FUX-03).
AC3 Given an open screen and its subscription through StudioRealtimeGateway/Realtime.Subscribe, when the channel drops and returns, then the page marks the data stale while it is down and reloads StudioBff/GetScreenModel when it returns, never showing a stale state as current (FUX-04).
AC4 Given run-submit and run-detail in I3, when they open, then the release list and the run timeline are shown unknown with the source named and no invented value, and the screens render in en, ru and he right to left under docs/planes/experience/studio/localization-accessibility.md (ADR-0028).
Traces: services StudioBff, StudioRealtimeGateway, RunControlService
Traces: apis StudioBff/GetStudioSession, StudioBff/GetScreenModel, StudioBff/ForwardCommand, RunControlService/SubmitRun, StudioRealtimeGateway/Realtime.Subscribe
Traces: events RunControlService/RunStateChanged
Traces: adrs ADR-0007, ADR-0014, ADR-0015, ADR-0028
Traces: requirements FUX-03, FUX-04
Depends on AIFACTORY-US-1412, AIFACTORY-US-1413, AIFACTORY-US-1414, AIFACTORY-US-034, feature:studio-bff, feature:studio-realtime-gateway, feature:component-blazor-shell, feature:run-control-service
Sources model/ux/screens.yaml, model/ux/states.yaml, model/ux/prototype-alignment.yaml, docs/planes/experience/studio/screens/workspace.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-451 Screens of the work area Workspace: My work, Submit a run, Run detail, Approvals waiting, Approval card, Project overview, Project settings, Environment board ui The Workspace microfrontend is composed into the shell through the registry as the landing area with one navigation group and the eight routes of model/ux/screens.yaml; each screen renders from StudioBff only, and the release list and the run timeline render their sources as unknown with the source named. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-452 Commands of the work area Workspace implementation Of the twelve commands of the eight screens, SetStudioScope goes to StudioBff/SetStudioScope, the own route of StudioBff, and the other eleven (SubmitRun, CancelRun, DecideApproval, SetMembership, Delegate, RevokeDelegation, SetSourceScope, SetProjectBudget, CreateEnvironment, FreezeEnvironment, UnfreezeEnvironment) go through StudioBff/ForwardCommand with an idempotency key and the approval binding their class requires; a decision shows the exact proposal version it binds to. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-453 States, roles, locales and accessibility of the work area Workspace 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-750 Verify studio-submit-and-follow-run by running the declared command verification Run dotnet test -c Release --filter Category=Acceptance and npx playwright test --project=chromium; they pass and prove AC1 to AC4 of AIFACTORY-US-033 (StudioBff/GetScreenModel, RunControlService/SubmitRun, StudioRealtimeGateway/Realtime.Subscribe). ConnectSoft.AI.SoftwareFactory.Studio

AIFACTORY-US-1415: Workspace 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 Workspace area is usable by keyboard, in every locale and at phone width, and that a run can be submitted, approved and followed through the Studio, so that the area is accepted on a recorded check and the release list and run timeline say they are not yet delivered.

This PBI is the proof of the Workspace area and comes after its integration PBI AIFACTORY-US-033, which registers the eight screens. The accessibility and phone-width check opens each of the eight 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 including the approval decision, live updates announced politely and not animated under reduced motion, amounts with their currency code, refusals explained in words, in English, Russian and Hebrew 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 first outcome: as a workspace admin it onboards the fixture project, grants roles, delegates with an expiry and creates the acceptance environment; as a requester it submits the assessment run by alias and follows it in the run detail; as a reviewer it decides the approval on the exact proposal and sees a stale decision refused; as the requester it opens the same card without decision controls; and as an observer it reads my work and the project overview. The release list of run-submit and the run timeline of run-detail, delivered in I4, 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.

Acceptance criteria

AC1 Given each of the 8 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 and has no horizontal scroll at 390 by 844 (NFR-15, FUX-12).
AC2 Given the walk as a workspace admin, a requester, a reviewer and an observer, when it runs on the acceptance estate, then every screen renders from StudioBff/GetScreenModel, every command goes through StudioBff/ForwardCommand, the stale decision and the requester decision are refused, and the two later sources are listed by name as unknown (ADR-0007, FUX-04).
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 screen showed a value its source does not deliver in I3 (FUX-12).
Traces: services StudioBff
Traces: apis StudioBff/GetScreenModel, StudioBff/ForwardCommand
Traces: adrs ADR-0007
Traces: requirements FUX-04, FUX-12
Relates: screens my-work, run-submit, run-detail, approvals-list, approval-card, project-overview, project-settings, environment-board
Relates: nfrs NFR-15
Depends on AIFACTORY-US-1412, AIFACTORY-US-1413, AIFACTORY-US-1414, AIFACTORY-US-034, AIFACTORY-US-033, feature:studio-bff, feature:component-blazor-shell
Sources model/ux/screens.yaml, docs/planes/experience/studio/localization-accessibility.md, docs/planes/experience/studio/screens/workspace.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-5688 End-to-end walk of the Workspace area fixture A browser-driven walk in the Studio repository that signs in as a workspace admin, a requester, a reviewer and an observer, onboards the fixture project, submits and follows the assessment run, decides its approval and attempts the refused decisions, and records per screen and role the rendered state, the source markers, the offered commands and the addresses the browser called. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5689 Accessibility and phone-width check of the Workspace 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 eight screens in en, ru and he, light and dark; the results prove AC1 of AIFACTORY-US-1415 against docs/planes/experience/studio/localization-accessibility.md. ConnectSoft.AI.SoftwareFactory.Studio
AIFACTORY-TASK-5690 Verify the walk record of the Workspace area verification Run the walk of AIFACTORY-TASK-5688 on the acceptance estate; its record and network log prove AC2 and AC3 of AIFACTORY-US-1415 (StudioBff/GetScreenModel, StudioBff/ForwardCommand) and are kept with the evidence of increment I3. ConnectSoft.AI.SoftwareFactory.Studio