AIFACTORY-FEAT-080: Studio work area: Software Factory¶
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 120 of 185 (Factory code)
The 11 screens of the Studio work area Software Factory 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: Software Factory |
| Requirements | — |
| Depends on | — |
| Sources | model/ux/screens.yaml, model/ux/prototype-alignment.yaml |
AIFACTORY-US-1407: Software Factory: I author, validate and submit blueprint versions, draft, validate and approve generation recipes, and read the provenance of generated outputs¶
behavior · persona asset-maintainer
As an asset maintainer, I want to take a blueprint from a Draft version to a submitted one and a recipe from a draft to an approved one, and to see which generated files came from which recipe, so that generation runs from validated, approved inputs and every generated file can be traced back to them.
An asset maintainer, a requester, a reviewer or an observer opens the screens blueprints, dsl-studio, recipes and generated-outputs. StudioBff composes them under the scope of the session and the project in scope from BlueprintService and GenerationRecipeService, reached through TemplateCatalogHost: ListBlueprints and GetBlueprintVersion with the document, the validation report and the derived context map and domain model; ListRecipes and GetRecipe with the module plan, pinned versions, switches and parameters; QueryCompatibility of TemplateRegistryService for the compatibility evidence of a recipe; and ListGeneratedOutputs with generated and preserved files by commit. A blueprint and a recipe list need the project, so the screen model always names it; a project the token does not grant is answered 403. The asset-readiness family of model/ux/states.yaml governs the display. Through ForwardCommand with an idempotency key a user stores a new Draft version with CreateBlueprintVersion, validates it with ValidateBlueprint and submits a Validated version with SubmitBlueprint, a publication-class command that carries the approval binding of its class; a recipe is drafted with DraftRecipe, validated with ValidateRecipe and approved with ApproveRecipe by a requester or an asset maintainer, and a reviewer when policy requires one. The page explains each refusal: 409 for a reused key or a version that is no longer a draft, 412 for a blueprint version a recipe may not bind, 422 per finding of the report, and 503 when a required dependency does not answer, in which case nothing changed. Until the publication gate of I4 a Submitted blueprint version may be bound by a recipe and a compatibility cell that is unknown passes with a warning; the page shows that allowance on the recipe. The dsl-studio screen also reads the topics of EnvelopeRegistryService, delivered in I4; in I3 that source is shown unknown, named, and the editor offers no topic list. StudioBff consumes BlueprintValidated, BlueprintSubmitted, RecipeValidated, RecipeApproved and GeneratedOutputRecorded and refreshes the open page without a reload.
Acceptance criteria
| AC1 | Given an asset maintainer on blueprints, recipes or generated-outputs, when StudioBff/GetScreenModel composes them for the project in scope, then they render from BlueprintService/ListBlueprints, BlueprintService/GetBlueprintVersion, GenerationRecipeService/ListRecipes, GenerationRecipeService/GetRecipe, TemplateRegistryService/QueryCompatibility and GenerationRecipeService/ListGeneratedOutputs, and a project the token does not grant is answered 403 (FUX-11). |
| AC2 | Given a Draft blueprint version, when the user validates and submits it, then StudioBff/ForwardCommand forwards BlueprintService/ValidateBlueprint and BlueprintService/SubmitBlueprint with the approval binding of the publication class, findings of a 422 are shown per rule, and the version shows Validated or Submitted only once BlueprintService/BlueprintValidated or BlueprintService/BlueprintSubmitted is consumed (FUX-02). |
| AC3 | Given a recipe, when a user drafts, validates and approves it through GenerationRecipeService/DraftRecipe, GenerationRecipeService/ValidateRecipe and GenerationRecipeService/ApproveRecipe, then a 412, 409 or 503 is explained in words with nothing changed, the allowance used before the publication gate is shown on the recipe, and GenerationRecipeService/RecipeApproved refreshes the open page (model/services/template-library/GenerationRecipeService.yaml). |
| AC4 | Given dsl-studio in I3, when it opens, then the blueprint document renders from BlueprintService/GetBlueprintVersion with validation through BlueprintService/ValidateBlueprint, and the topic source is shown unknown and named with no invented topic (FUX-04). |
| Traces: services | StudioBff, BlueprintService, GenerationRecipeService, TemplateRegistryService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, BlueprintService/ListBlueprints, BlueprintService/GetBlueprintVersion, BlueprintService/CreateBlueprintVersion, BlueprintService/ValidateBlueprint, BlueprintService/SubmitBlueprint, GenerationRecipeService/ListRecipes, GenerationRecipeService/GetRecipe, GenerationRecipeService/DraftRecipe, GenerationRecipeService/ValidateRecipe, GenerationRecipeService/ApproveRecipe, GenerationRecipeService/ListGeneratedOutputs, TemplateRegistryService/QueryCompatibility |
| Traces: events | BlueprintService/BlueprintValidated, BlueprintService/BlueprintSubmitted, GenerationRecipeService/RecipeValidated, GenerationRecipeService/RecipeApproved, GenerationRecipeService/GeneratedOutputRecorded |
| Traces: requirements | FUX-02, FUX-04, FUX-11 |
| Relates: screens | blueprints, dsl-studio, recipes, generated-outputs |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:blueprint-service, feature:generation-recipe-service, feature:template-registry-service, feature:template-catalog-host |
| Sources | model/ux/screens.yaml, model/ux/states.yaml, model/services/template-library/BlueprintService.yaml, model/services/template-library/GenerationRecipeService.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5669 Blueprint, descriptor, recipe and generated output screens in the Software Factory microfrontend |
ui | The Software Factory microfrontend renders blueprints, dsl-studio, recipes and generated-outputs with the asset-readiness and delivery families, the blueprint editor with its validation report per rule, the recipe module plan with compatibility evidence and the pre-gate allowance, the provenance of generated files by commit, and the topic source of the descriptor editor marked unknown. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5670 Screen models and command routes of the blueprint and recipe screens in StudioBff |
contract | StudioBff composes the four screens through TemplateCatalogHost, by REST through the pinned template catalog gateway client of feature typed-gateway-clients (AIFACTORY-TASK-6605), with the project in scope and the freshness of each source, marks the topic source unknown in I3, forwards the blueprint and recipe commands with an idempotency key and the approval binding SubmitBlueprint requires, and refreshes the views on BlueprintValidated, BlueprintSubmitted, RecipeValidated, RecipeApproved and GeneratedOutputRecorded. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5671 Verify the blueprint and recipe screens with every refusal |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving a blueprint from Draft to Submitted, a recipe from draft to approved, a 422 report, a 412 binding, a 409 reused key, a 503 dependency and a project not granted; the tests prove AC1 to AC4 of AIFACTORY-US-1407 (BlueprintService/SubmitBlueprint, GenerationRecipeService/ApproveRecipe). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5706 Verify the StudioBff side of the blueprint and recipe screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-factory-blueprints-recipes-and-outputs" 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 TemplateCatalogHost for the project in scope and the 403 of a project not granted returned unchanged), AC2 (ValidateBlueprint and SubmitBlueprint forwarded once with an idempotency key and the approval binding of the publication class, a 422 returned per rule, refresh on BlueprintValidated and BlueprintSubmitted), AC3 (the recipe commands forwarded, a 412, 409 or 503 returned unchanged with nothing queued, refresh on RecipeApproved) and AC4 (the topic source marked unknown in I3) of AIFACTORY-US-1407 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-1408: Software Factory: I follow change proposals and pipeline runs, reconcile a missed run, and request or roll back a promotion whose one production approval is the gate of EnvironmentPromotionService¶
behavior · persona operator
As an operator, I want to follow a change from its proposal through its pipeline run to its promotion into an environment, and to request or roll back a promotion from the Studio, so that I know which release runs where and a production promotion is approved once, at its own gate, by a person.
A requester, a reviewer, an operator, a workspace admin or an observer opens the screens proposals, pipeline-runs and promotions. StudioBff composes them under the scope of the session from PipelineExecutionService and EnvironmentPromotionService, reached through DeliveryHost: ListChangeProposals and GetChangeProposal with commits, reviews, pipeline runs and provenance; ListPipelineRuns and GetPipelineRun with stages and typed results; ListPromotions, GetPromotion with gates, approval, desired state, verification and rollback evidence, and GetCurrentRelease of each environment. The delivery and approval families of model/ux/states.yaml govern the display, and a promotion moves from Requested through GatesEvaluating to AwaitingApproval, Approved or Rejected, then Deploying, Verifying and Completed, or Failed or RolledBack. An operator reconciles a pipeline run whose delivery was missed with ReconcilePipelineRun. An operator requests a promotion of a ready release with RequestPromotion through ForwardCommand with an idempotency key; the Studio attaches no approval of its own (D133). For a production environment the one approval a person gives is the gate of EnvironmentPromotionService, bound to the release and the environment and requested from RunControlService during gate evaluation with the subject kind Promotion and the promotion id as subject (D135); StudioBff matches the ApprovalRequested it consumes to the open promotion by subjectKind and subjectId, not by a run, and the promotion page shows AwaitingApproval and says that the decision is taken on the approval card of the Workspace area. A 409, 412 or 422 of the owning service reaches the Studio unchanged (D137) and is explained in words, and a withdrawn release cannot be promoted. A promotion whose gate failed or whose approval was rejected or expired is Rejected; GetPromotion shows it with the reason, and the page says that a new RequestPromotion, which binds a new approval, is needed. A promotion of another tenant is answered 404 by GetPromotion like one that does not exist. An operator rolls back a promotion with RollbackPromotion; a promotion that cannot be rolled back is answered 409. A reviewer, a workspace admin and an observer see the commands they may not issue disabled with the reason. StudioBff consumes the proposal, pipeline and promotion events and ApprovalRequested of RunControlService and refreshes the open page without a reload. When DeliveryHost does not answer, the source is shown degraded with its last freshness and the commands are refused with 503, never queued.
Acceptance criteria
| AC1 | Given an operator on proposals, pipeline-runs or promotions, when StudioBff/GetScreenModel composes them, then they render from PipelineExecutionService/ListChangeProposals, PipelineExecutionService/GetChangeProposal, PipelineExecutionService/ListPipelineRuns, PipelineExecutionService/GetPipelineRun, EnvironmentPromotionService/ListPromotions, EnvironmentPromotionService/GetPromotion and EnvironmentPromotionService/GetCurrentRelease, and a promotion shows its state and gates (FUX-11). |
| AC2 | Given an operator who requests a production promotion, when StudioBff/ForwardCommand forwards EnvironmentPromotionService/RequestPromotion, then it carries an idempotency key and no Studio approval, the page shows AwaitingApproval once RunControlService/ApprovalRequested with the subject kind Promotion and the id of that promotion is consumed and names the approval card as the one place to decide, and a 409, 412 or 422 returned unchanged is explained in words (FUX-05, ADR-0024, D135, D137). |
| AC3 | Given a completed promotion or a missed pipeline delivery, when an operator issues EnvironmentPromotionService/RollbackPromotion or PipelineExecutionService/ReconcilePipelineRun, then the page shows the result only once EnvironmentPromotionService/RollbackCompleted or PipelineExecutionService/PipelineRunCompleted is consumed, and other roles see these commands disabled with the reason (ADR-0015). |
| AC4 | Given an open promotion, when EnvironmentPromotionService/PromotionApproved, EnvironmentPromotionService/PromotionCompleted or EnvironmentPromotionService/PromotionFailed is consumed by StudioBff, then the page shows the new state without a reload; a promotion whose gate failed or whose approval was rejected or expired shows Rejected with the reason and that a new EnvironmentPromotionService/RequestPromotion is needed (EnvironmentPromotionService/GetPromotion); a promotion of another tenant is answered 404; and when DeliveryHost does not answer the source is degraded and the commands answer 503 (model/services/factory-studio/StudioBff.yaml). |
| Traces: services | StudioBff, PipelineExecutionService, EnvironmentPromotionService, RunControlService, DeliveryHost |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, PipelineExecutionService/ListChangeProposals, PipelineExecutionService/GetChangeProposal, PipelineExecutionService/ListPipelineRuns, PipelineExecutionService/GetPipelineRun, PipelineExecutionService/ReconcilePipelineRun, EnvironmentPromotionService/ListPromotions, EnvironmentPromotionService/GetPromotion, EnvironmentPromotionService/GetCurrentRelease, EnvironmentPromotionService/RequestPromotion, EnvironmentPromotionService/RollbackPromotion |
| Traces: events | PipelineExecutionService/PipelineRunCompleted, EnvironmentPromotionService/PromotionApproved, EnvironmentPromotionService/PromotionCompleted, EnvironmentPromotionService/PromotionFailed, EnvironmentPromotionService/RollbackCompleted, RunControlService/ApprovalRequested |
| Traces: adrs | ADR-0015, ADR-0024 |
| Traces: requirements | FUX-05, FUX-11 |
| Relates: screens | proposals, pipeline-runs, promotions |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:pipeline-execution-service-complete, feature:environment-promotion-service, feature:delivery-host, feature:run-control-service |
| Sources | model/ux/screens.yaml, model/ux/states.yaml, model/services/devops-gitops/PipelineExecutionService.yaml, model/services/devops-gitops/EnvironmentPromotionService.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5672 Proposal, pipeline run and promotion screens in the Software Factory microfrontend |
ui | The Software Factory microfrontend renders proposals, pipeline-runs and promotions with the delivery, approval and freshness families, the promotion state path with its gates and evidence, the current release per environment, the request and rollback dialogs, and an AwaitingApproval state that names the approval card of the Workspace area and offers no approval control of its own. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5673 Screen models and command routes of the delivery screens in StudioBff |
contract | StudioBff composes the three screens through DeliveryHost, by REST through the pinned client package of that gateway (AIFACTORY-TASK-6601, AIFACTORY-TASK-6605), with the freshness of the source, forwards RequestPromotion with an idempotency key and no Studio approval, RollbackPromotion and ReconcilePipelineRun, refuses them with 503 while DeliveryHost does not answer, and refreshes the views on the proposal, pipeline and promotion events and on ApprovalRequested, matched to a promotion by its subject kind Promotion and subject id (D135). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5674 Verify the promotion path with its single production approval |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub driving a production promotion from Requested through AwaitingApproval to Completed, a 412 gate refusal, a promotion Rejected after its gate failed and another after its approval expired, a promotion of another tenant answered 404, a rollback, a reconciled pipeline run and a reviewer session; the tests prove AC1 to AC4 of AIFACTORY-US-1408 (EnvironmentPromotionService/RequestPromotion, RunControlService/ApprovalRequested). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5707 Verify the StudioBff side of the delivery screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-factory-proposals-pipelines-and-promotions" 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 DeliveryHost from the proposal, pipeline run and promotion reads), AC2 (RequestPromotion forwarded once with an idempotency key and no Studio approval, its 409, 412 and 422 returned unchanged, refresh on ApprovalRequested), AC3 (RollbackPromotion and ReconcilePipelineRun forwarded, refresh on RollbackCompleted and PipelineRunCompleted) and AC4 (refresh on PromotionApproved, PromotionCompleted and PromotionFailed, a Rejected promotion composed with its reason, the 404 of another tenant returned unchanged, 503 while DeliveryHost does not answer and nothing queued) of AIFACTORY-US-1408 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-1409: Software Factory: I plan and cancel provisioning runs and read the observed inventory, drift and reconciliation proposals of an environment¶
behavior · persona operator
As an operator, I want to see the desired-state specifications and provisioning runs, plan or cancel a run, and compare the observed inventory of an environment with its desired state, so that infrastructure changes are planned before they apply and drift is decided by a person instead of corrected silently.
An operator, a platform admin, a workspace admin or an observer opens the screens provisioning and inventory. StudioBff composes them under the scope of the session from IaCProvisioningService and RuntimeEnvironmentService, reached through RuntimeCloudHost: ListSpecifications with versions per environment, ListProvisioningRuns and GetProvisioningRun with the plan, the approval, the apply receipt and the logs; GetRuntimeInventory with observed workloads, versions, replicas, endpoints and bindings by reference and their staleness, ListDrift with open and resolved findings and ListReconciliationProposals with plan summaries. The delivery, approval and freshness families of model/ux/states.yaml govern the display, and inventory older than its freshness limit shows its age. An operator or a platform admin plans a run with PlanProvisioning through ForwardCommand with an idempotency key; a production apply waits for the approval its class requires, which the owning service requests with the subject kind ProvisioningRun and the provisioning run id as subject (D135), and the page shows the run waiting until the decision arrives. A planned run is cancelled with CancelProvisioning before it applies; a run already applying is answered 409. An operator triggers an observation with ObserveEnvironment and decides a reconciliation proposal with DecideReconciliation, accepting it, which plans a provisioning run, or rejecting it with a reason; production acceptance carries the approval binding of its class. A 409 or 422 is explained in words, a proposal already decided is answered 409 by DecideReconciliation, a provisioning run or an environment of another tenant is answered 404 by GetProvisioningRun, GetRuntimeInventory or ListDrift, and a role without the right sees the control disabled with the reason. StudioBff consumes ProvisioningPlanned, ProvisioningApplied, ProvisioningFailed, ObservedStateChanged, RuntimeDriftDetected, ReconciliationProposed and ReconciliationDecided and refreshes the open page without a reload. When RuntimeCloudHost does not answer, the source is shown degraded with its last freshness and the commands are refused with 503, never queued.
Acceptance criteria
| AC1 | Given an operator on provisioning or inventory, when StudioBff/GetScreenModel composes them, then they render from IaCProvisioningService/ListSpecifications, IaCProvisioningService/ListProvisioningRuns, IaCProvisioningService/GetProvisioningRun, RuntimeEnvironmentService/GetRuntimeInventory, RuntimeEnvironmentService/ListDrift and RuntimeEnvironmentService/ListReconciliationProposals, and stale inventory shows its age (FUX-04). |
| AC2 | Given an operator who plans or cancels a run, when StudioBff/ForwardCommand forwards IaCProvisioningService/PlanProvisioning or IaCProvisioningService/CancelProvisioning, then a production apply is shown waiting for its approval until IaCProvisioningService/ProvisioningApplied or IaCProvisioningService/ProvisioningFailed is consumed, and a 409 or 422 is explained in words (FUX-05). |
| AC3 | Given a drift finding, when an operator observes the environment or decides a proposal through RuntimeEnvironmentService/ObserveEnvironment or RuntimeEnvironmentService/DecideReconciliation, then a rejection carries a reason, production acceptance carries the approval binding of its class, and RuntimeEnvironmentService/RuntimeDriftDetected or RuntimeEnvironmentService/ReconciliationDecided refresh the open page (FUX-07). |
| AC4 | Given a run or environment of another tenant, an applying run, a decided proposal or an unreachable RuntimeCloudHost, when the screen or a command is requested, then the answer is 404, IaCProvisioningService/CancelProvisioning or RuntimeEnvironmentService/DecideReconciliation answers 409 explained in words, or the source is shown degraded with its last freshness and the command refused with 503 and not queued (model/services/factory-studio/StudioBff.yaml). |
| Traces: services | StudioBff, IaCProvisioningService, RuntimeEnvironmentService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, IaCProvisioningService/ListSpecifications, IaCProvisioningService/ListProvisioningRuns, IaCProvisioningService/GetProvisioningRun, IaCProvisioningService/PlanProvisioning, IaCProvisioningService/CancelProvisioning, RuntimeEnvironmentService/GetRuntimeInventory, RuntimeEnvironmentService/ListDrift, RuntimeEnvironmentService/ListReconciliationProposals, RuntimeEnvironmentService/ObserveEnvironment, RuntimeEnvironmentService/DecideReconciliation |
| Traces: events | IaCProvisioningService/ProvisioningPlanned, IaCProvisioningService/ProvisioningApplied, IaCProvisioningService/ProvisioningFailed, RuntimeEnvironmentService/ObservedStateChanged, RuntimeEnvironmentService/RuntimeDriftDetected, RuntimeEnvironmentService/ReconciliationProposed, RuntimeEnvironmentService/ReconciliationDecided |
| Traces: requirements | FUX-04, FUX-05, FUX-07 |
| Relates: screens | provisioning, inventory |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:ia-cprovisioning-service, feature:runtime-environment-service, feature:runtime-cloud-host |
| Sources | model/ux/screens.yaml, model/ux/states.yaml, model/services/runtime-cloud/IaCProvisioningService.yaml, model/services/runtime-cloud/RuntimeEnvironmentService.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5675 Provisioning and inventory screens in the Software Factory microfrontend |
ui | The Software Factory microfrontend renders provisioning and inventory with the delivery, approval and freshness families, specifications and runs with plan and apply receipts, the run waiting for its approval, observed inventory with its age, drift findings and reconciliation proposals with accept and reject-with-reason controls. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5676 Screen models and command routes of the provisioning and inventory screens in StudioBff |
contract | StudioBff composes the two screens through RuntimeCloudHost, by REST through the pinned client package of that gateway (AIFACTORY-TASK-6602, AIFACTORY-TASK-6605), with the freshness of each source, forwards PlanProvisioning with an idempotency key, CancelProvisioning, ObserveEnvironment and DecideReconciliation with the approval binding of its production class, refuses them with 503 while RuntimeCloudHost does not answer, and refreshes the views on the provisioning and runtime events. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5677 Verify provisioning and drift decisions by role |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving a planned production run waiting for approval, a 409 cancel of an applying run, a pushed drift finding, an accepted and a rejected proposal, a 409 on a proposal already decided, a provisioning run and an environment of another tenant answered 404, an unreachable RuntimeCloudHost with commands answered 503 and an observer session; the tests prove AC1 to AC4 of AIFACTORY-US-1409 (IaCProvisioningService/PlanProvisioning, RuntimeEnvironmentService/DecideReconciliation). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5708 Verify the StudioBff side of the provisioning and inventory screens |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-factory-provisioning-and-inventory" 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 RuntimeCloudHost with the freshness and age of each source), AC2 (PlanProvisioning and CancelProvisioning forwarded once with an idempotency key, refresh on ProvisioningApplied and ProvisioningFailed), AC3 (ObserveEnvironment and DecideReconciliation forwarded, production acceptance with the approval binding of its class, refresh on RuntimeDriftDetected and ReconciliationDecided) and AC4 (the 404 and 409 answers returned unchanged, 503 while RuntimeCloudHost does not answer and nothing queued) of AIFACTORY-US-1409 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-1410: Software Factory: I read the workflow graph of a run with its checkpoints, answer the decision an attempt waits for through Run Control, and ask Run Control to stop the run¶
behavior · persona operator
As an operator, I want to see the graph of a run with the state of every step, the checkpoints of an attempt and a decision an attempt waits for, and to stop the run, so that I see where a run is blocked and can stop it from its graph while Run Control stays the one place that records what the run is.
A requester, an operator or an observer opens the screen workflow-run-graph at /factory/runs/{runId}/graph. StudioBff composes it under the scope of the session through AgentRuntimeWorker, the internal gateway of the Agent Mesh platform: GetWorkflowRunGraph of WorkflowEngineService with the state of every step run, timers and compensation entries, GetAttemptTimeline of AgentRuntimeService for the attempt the user selects, and ListCheckpoints with sequence, phase and adapter version, which an operator reads before a resume decision. The run and freshness families of model/ux/states.yaml govern the display. When an attempt waits for a human input or an escalation choice, AttemptDecisionRequested marks it and the graph shows the waiting decision with its kind and options. The answer control is enabled for a user whose token holds factory.runs.operate: the page sends the answer through ForwardCommand to the public route AnswerDecision of RunControlService behind ControlPlaneApi, which passes it to the waiting attempt through Runtime.AnswerDecision of AgentRuntimeService (D137); the Studio never calls the internal Runtime.AnswerDecision itself, and a role without that scope sees the control disabled with the reason. The codes of AnswerDecision reach the page unchanged (D137) and are explained in words: 404 for a decision the open attempt did not ask for, 409 for a decision already answered, and 503, with nothing recorded, when AgentRuntimeService does not answer. An approval is never answered here, because AnswerDecision refuses an approval with 409 and approvals arrive through the approval card of the Workspace area. To stop a run the page calls CancelRun of RunControlService through ControlPlaneApi, because Run Control holds the truth of a run and asks the lease holder to interrupt (ADR-0024 decision 5); the page says that the cancellation is requested, marks each attempt interrupted when AttemptCancellationObserved is consumed, and shows the run cancelled only once RunCancelled of RunControlService is consumed. A CancelRun answered 409, as for a run that is already terminal, is explained in words with nothing changed. The page never calls Runtime.Interrupt itself. The adverse branches of the flow recover-run of model/ux/flows.yaml are shown in words: a lease still held by another holder and a checkpoint that is missing. A run of another tenant is answered 404 like one that does not exist. StudioBff consumes StepRunStateChanged, AttemptPhaseChanged, AttemptCheckpointed (D137), AttemptDecisionRequested, AttemptCancellationObserved and RunCancelled, refreshes the open page without a reload and reads the checkpoints of the selected attempt again from ListCheckpoints, so a new checkpoint appears with its sequence when it is recorded. When AgentRuntimeWorker does not answer, the source is shown degraded with its last freshness and the parts already held are marked stale.
Acceptance criteria
| AC1 | Given an operator on workflow-run-graph, when StudioBff/GetScreenModel composes it, then it renders from WorkflowEngineService/GetWorkflowRunGraph, AgentRuntimeService/GetAttemptTimeline and AgentRuntimeService/ListCheckpoints, and the adverse branches of the flow recover-run of model/ux/flows.yaml (lease held, checkpoint missing) are explained in words (FUX-07). |
| AC2 | Given an attempt marked by AgentRuntimeService/AttemptDecisionRequested, when the graph renders and a user holding factory.runs.operate answers, then the waiting decision is shown with its kind and options, the answer goes through StudioBff/ForwardCommand to RunControlService/AnswerDecision and never to the runtime directly, its 404, 409 and 503 are explained in words with nothing changed, a role without the scope sees the control disabled with the reason, and no approval is answered from this screen (ADR-0028, D137). |
| AC3 | Given a running run, when an operator stops it, then the request goes through StudioBff/ForwardCommand to RunControlService/CancelRun and never to the runtime directly, the page says the cancellation is requested, marks each attempt interrupted when AgentRuntimeService/AttemptCancellationObserved is consumed, and shows the run cancelled only once RunControlService/RunCancelled is consumed, and a 409 of RunControlService/CancelRun for a run that is already terminal is explained in words with nothing changed (ADR-0024 decision 5). |
| AC4 | Given an open graph, when WorkflowEngineService/StepRunStateChanged, AgentRuntimeService/AttemptPhaseChanged or AgentRuntimeService/AttemptCheckpointed is consumed by StudioBff, then the page updates without a reload and the checkpoints of the selected attempt are read again from AgentRuntimeService/ListCheckpoints, and a run of another tenant is answered 404 like an unknown one (FUX-04, ADR-0015). |
| Traces: services | StudioBff, WorkflowEngineService, AgentRuntimeService, RunControlService |
| Traces: apis | StudioBff/GetScreenModel, StudioBff/ForwardCommand, WorkflowEngineService/GetWorkflowRunGraph, AgentRuntimeService/GetAttemptTimeline, AgentRuntimeService/ListCheckpoints, RunControlService/CancelRun, RunControlService/AnswerDecision |
| Traces: events | WorkflowEngineService/StepRunStateChanged, AgentRuntimeService/AttemptPhaseChanged, AgentRuntimeService/AttemptCheckpointed, AgentRuntimeService/AttemptDecisionRequested, AgentRuntimeService/AttemptCancellationObserved, RunControlService/RunCancelled |
| Traces: adrs | ADR-0015, ADR-0024, ADR-0028 |
| Traces: requirements | FUX-04, FUX-07 |
| Relates: screens | workflow-run-graph |
| Depends on | feature:studio-bff, feature:component-blazor-shell, feature:workflow-engine-service, feature:agent-runtime-service, feature:agent-runtime-worker, feature:run-control-service, feature:control-plane-api |
| Sources | model/ux/screens.yaml, model/ux/flows.yaml, model/services/agent-mesh/WorkflowEngineService.yaml, model/services/agent-mesh/AgentRuntimeService.yaml, model/services/control-plane/RunControlService.yaml |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5678 Workflow run graph screen in the Software Factory microfrontend |
ui | The Software Factory microfrontend renders workflow-run-graph with the run and freshness families, the graph of step runs with timers and compensation entries, the selected attempt with its checkpoints, the waiting decision with its kind and options and an answer control enabled for a user holding factory.runs.operate and disabled with the reason for other roles, the 404, 409 and 503 of AnswerDecision explained in words, attempts marked interrupted, and a stop control that says the cancellation is requested until the run is cancelled. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5679 Screen model and command routes of the workflow run graph in StudioBff |
contract | StudioBff composes workflow-run-graph through AgentRuntimeWorker with the freshness of the source, forwards an answer to the public route AnswerDecision of RunControlService through ControlPlaneApi and never to Runtime.AnswerDecision, forwards a stop to CancelRun of RunControlService through ControlPlaneApi, never to Runtime.Interrupt, returns their codes unchanged (D137), and refreshes the view on StepRunStateChanged, AttemptPhaseChanged, AttemptCheckpointed, AttemptDecisionRequested, AttemptCancellationObserved and RunCancelled, reading the checkpoints of the selected attempt again from ListCheckpoints. |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-5680 Verify the run graph with a waiting decision and an observed stop |
verification | Run dotnet test -c Release --no-build and npx playwright test --project=chromium with a StudioBff stub serving a graph, an attempt waiting for a decision answered by an operator and refused with 409 when already answered, its answer control disabled for an observer, a held lease, a missing checkpoint, attempts marked interrupted before the run is shown cancelled on RunCancelled, a 409 cancel of a terminal run, a pushed phase change and a run of another tenant; the tests prove AC1 to AC4 of AIFACTORY-US-1410 (RunControlService/AnswerDecision, RunControlService/CancelRun, RunControlService/RunCancelled). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5709 Verify the StudioBff side of the workflow run graph |
verification | Run dotnet test -c Release --filter "Category=Acceptance&Feature=studio-factory-workflow-run-graph" 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 AgentRuntimeWorker from GetWorkflowRunGraph, GetAttemptTimeline and ListCheckpoints), AC2 (the waiting decision composed from AttemptDecisionRequested, the answer forwarded once to RunControlService/AnswerDecision through ControlPlaneApi and never to Runtime.AnswerDecision, its 404, 409 and 503 returned unchanged), AC3 (CancelRun forwarded once through ControlPlaneApi, never to the runtime, its 409 returned unchanged, refresh on AttemptCancellationObserved and RunCancelled) and AC4 (refresh on StepRunStateChanged, AttemptPhaseChanged and AttemptCheckpointed with the checkpoints read again, the 404 of another tenant returned unchanged) of AIFACTORY-US-1410 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-US-038: Every work area renders from the platform read models, and the Software Factory work area is bound to the model¶
behavior · persona observer
As an observer, I want every work area of the Studio, and the Software Factory work area in full, to show what the platforms hold, through the backend-for-frontend, so that what I read in the Studio is the state of the Factory and nothing else, and what is not yet delivered says so.
This is the integration PBI of the Software Factory area and the rule every work area follows. StudioBff composes one screen-shaped response per screen from the gateways of the platforms that own its read models, and every microfrontend of the seven work areas renders from that response only; no browser calls a platform service. A screen is offered to the roles its list in model/ux/screens.yaml names; for any other role it is absent from the navigation and GetScreenModel refuses it with 403. A screen whose platform is not delivered in the increment shows each such source as unknown in the freshness family, named, never hidden and never filled from a fake, and a read model older than its freshness limit shows its age. The Software Factory microfrontend is generated from the microfrontend library template, composed into the shell through its registry and holds eleven screens: ten are delivered in I3 by AIFACTORY-US-1407 to AIFACTORY-US-1410, and generated-products reads GeneratedProductHost of I6 and the fleet inventory of I7, so in I3 it is registered, offered to its roles, shows its sources as unknown and offers no AcknowledgeOperationsHandover. 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, never StudioBff, decides; a production promotion carries no Studio approval, because its one approval is the gate of EnvironmentPromotionService (D133). On workflow-run-graph the commands Runtime.Interrupt and Runtime.AnswerDecision that model/ux/screens.yaml lists are replaced by CancelRun of RunControlService (ADR-0024) and by the public route AnswerDecision of RunControlService (D137). 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 each of the seven work areas, when a user with a role in it opens a screen, then the screen renders from StudioBff/GetScreenModel only, composed from the read models model/ux/screens.yaml names for it, 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 a platform that is not delivered yet, such as the sources of generated-products, when one of its screens opens, then the screen shows each such source 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-04). |
| AC3 | Given an open screen and its subscription through StudioRealtimeGateway/Realtime.Subscribe, when a read model is older than its freshness limit or the channel drops, then its age is shown and the data is never presented as current, and when the channel returns the page reloads StudioBff/GetScreenModel without a browser reload (FUX-07). |
| AC4 | Given a command of a Software Factory screen, when a role issues it, then StudioBff/ForwardCommand forwards it once with an idempotency key and the approval binding its class requires through the single-entry gateway of its platform, a role without the right sees it disabled with the reason, and a production promotion carries no Studio approval (ADR-0028). |
| Traces: services | StudioBff, StudioRealtimeGateway, BlueprintService, GenerationRecipeService, PipelineExecutionService, EnvironmentPromotionService, IaCProvisioningService, RuntimeEnvironmentService, WorkflowEngineService |
| Traces: apis | StudioBff/GetStudioSession, StudioBff/GetScreenModel, StudioBff/ForwardCommand, StudioRealtimeGateway/Realtime.Subscribe |
| Traces: adrs | ADR-0007, ADR-0015, ADR-0028 |
| Traces: requirements | FUX-04, FUX-07 |
| Relates: screens | generated-products |
| Depends on | AIFACTORY-US-1407, AIFACTORY-US-1408, AIFACTORY-US-1409, AIFACTORY-US-1410, 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/software-factory.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-530 Screen models composed per screen |
contract | StudioBff composes one screen-shaped response per screen of the seven work areas from the gateways of the platforms that own its read models, with the freshness of each source, a source not delivered in the increment marked unknown and named, and 403 for a role the screen does not name. | ConnectSoft.AI.SoftwareFactory.StudioBff |
AIFACTORY-TASK-448 Screens of the work area Software Factory: Blueprints, DSL studio, Recipes, Generated outputs, Proposals, Pipeline runs, Promotions and 4 more |
ui | The Software Factory microfrontend is composed into the shell through the registry with one navigation group and the eleven routes of model/ux/screens.yaml; each screen renders from StudioBff only, and generated-products renders its sources as unknown with the source named and no command. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-449 Commands of the work area Software Factory |
implementation | The commands of the ten delivered screens are forwarded through StudioBff with an idempotency key, the scope of the session and the approval binding their class requires, RequestPromotion carries no Studio approval, the stop of workflow-run-graph goes to CancelRun of RunControlService instead of Runtime.Interrupt, the answer to a waiting attempt goes to the public route AnswerDecision of RunControlService instead of Runtime.AnswerDecision (D137), and AcknowledgeOperationsHandover of generated-products is not offered in I3. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-450 States, roles, locales and accessibility of the work area Software Factory |
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-531 Unavailable and stale states |
implementation | A screen whose platform is not delivered or whose model is stale shows that state from the state families of the model. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-532 Render check of all screens by role |
implementation | An automated pass opens every screen of the seven work areas with every role and records what rendered. | ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-749 Verify studio-work-areas-render 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-038 (StudioBff/GetScreenModel, StudioRealtimeGateway/Realtime.Subscribe). |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-US-1411: Software Factory 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 Software Factory area is usable by keyboard, in every locale and at phone width, and that a walk from blueprint to promotion works through the Studio, so that the area is accepted on a recorded check and the generated products screen says it is not yet delivered.
This PBI is the proof of the Software Factory area and comes after its integration PBI AIFACTORY-US-038, which registers the eleven screens. The accessibility and phone-width check opens each of the eleven screens of the area for every role its list in model/ux/screens.yaml names, and for one role it does not name, and asserts the rules of docs/planes/experience/studio/localization-accessibility.md: WCAG 2.2 AA by the automated checks, keyboard operation including the graph and the blueprint editor, live updates announced politely and not animated under reduced motion, 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 fixture project of the first outcome: as an asset maintainer it validates and submits a blueprint version and approves a recipe, reads the generated outputs, the change proposal and the pipeline run; as an operator it requests a promotion into the acceptance environment, follows it to Completed and rolls back a second one, plans a provisioning run, decides a drift proposal, stops a run from its graph and answers the decision a waiting attempt asks for through AnswerDecision of RunControlService (D137); as an observer it sees the same screens without commands. The screen generated-products reads GeneratedProductHost, delivered in I6, and the fleet inventory of I7; it shows its sources as unknown and is listed by name, and dsl-studio shows its topic source unknown. 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 11 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 an asset maintainer, an operator and an observer, when it runs on the acceptance estate, then every delivered screen renders from StudioBff/GetScreenModel, every command goes through StudioBff/ForwardCommand, a role a screen does not name gets 403, and generated-products is listed by name with its sources 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 | blueprints, dsl-studio, recipes, generated-outputs, proposals, pipeline-runs, promotions, provisioning, inventory, generated-products, workflow-run-graph |
| Relates: nfrs | NFR-15 |
| Depends on | AIFACTORY-US-1407, AIFACTORY-US-1408, AIFACTORY-US-1409, AIFACTORY-US-1410, AIFACTORY-US-038, feature:studio-bff, feature:component-blazor-shell |
| Sources | model/ux/screens.yaml, docs/planes/experience/studio/localization-accessibility.md, docs/planes/experience/studio/screens/software-factory.md |
Tasks
| Task | Kind | Expected output | Repository |
|---|---|---|---|
AIFACTORY-TASK-5691 End-to-end walk of the Software Factory area by role |
fixture | A browser-driven walk in the Studio repository that opens every screen of the Software Factory area with every role its list names and one it does not, walks the fixture project from blueprint to promotion, rollback, provisioning, drift and a stopped run, 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-5692 Accessibility and phone-width check of the Software Factory 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 eleven screens in en, ru and he, light and dark; the results prove AC1 of AIFACTORY-US-1411 against docs/planes/experience/studio/localization-accessibility.md. |
ConnectSoft.AI.SoftwareFactory.Studio |
AIFACTORY-TASK-5693 Verify unavailable and stale states and the walk record of the Software Factory area |
verification | Run the walk of AIFACTORY-TASK-5691 on the acceptance estate; its record shows generated-products and the topic source of dsl-studio unknown and stale data marked with its age, and with the network log proves AC2 and AC3 of AIFACTORY-US-1411 (StudioBff/GetScreenModel, StudioBff/ForwardCommand). |
ConnectSoft.AI.SoftwareFactory.Studio |