Increment I3: Studio¶
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).
Outcome. The same chain is submitted, watched and decided in Factory Studio.
Depends on: I1 · Elaboration: stories and tasks · Azure DevOps CSV of this increment
Demonstrations¶
- A requester submits a run and follows it live in the Studio.
- A reviewer decides approvals from the approval inbox.
- Every work area renders from the platform read models through the backend-for-frontend.
Services delivered in this increment¶
| Service | Role | Depth | Scope in this increment | Repository |
|---|---|---|---|---|
AgentRuntimeWorker |
platform-gateway | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.AgentRuntimeWorker |
ObservabilityHost |
platform-gateway | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.ObservabilityHost |
StudioBff |
bff | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.StudioBff |
StudioNotificationService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.StudioNotificationService |
StudioRealtimeGateway |
edge-service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.StudioRealtimeGateway |
Stub register¶
A stub stands in for a service that this increment needs but does not build; the increment that completes it is named.
| Feature | Stubbed service | Mode | Completed in |
|---|---|---|---|
AIFACTORY-FEAT-072 StudioBff: complete delivery |
FleetOperationsHost |
static | I7 |
AIFACTORY-FEAT-072 StudioBff: complete delivery |
DataEventFoundations |
static | I4 |
AIFACTORY-FEAT-074 StudioRealtimeGateway: complete delivery |
DashboardService |
contract-stub | I4 |
Before development¶
Template and library work of this increment, done first: these features change the templates and shared libraries the Factory scaffolds from and builds on, and none delivers a Factory service. Every task under them carries the tag phase:before-development.
| Feature | Repositories | State | Tasks |
|---|---|---|---|
AIFACTORY-FEAT-167 Blazor shell template: gateway adapters, filter diagnostics and pinned packages before the Studio |
ConnectSoft.AzurePipelinesConnectSoft.Blazor.MicrofrontendLibraryTemplateConnectSoft.Blazor.Shell.ServicesConnectSoft.Blazor.Shell.Services.AbstractionsConnectSoft.Blazor.ShellTemplate |
elaborated | 23 |
AIFACTORY-FEAT-168 Blazor microfrontend library template: AppShell chrome, a neutral exemplar and a generated-solution gate |
ConnectSoft.Blazor.MicrofrontendLibraryTemplate |
elaborated | 15 |
AIFACTORY-FEAT-169 UI kit: the token work and the Factory compositions the alignment gate ranks first |
ConnectSoft.Blazor.MicrofrontendLibraryTemplateConnectSoft.Blazor.ShellTemplateConnectSoft.Blazor.UIKit |
elaborated | 19 |
Features by epic¶
Agent Mesh (PF-02)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-013 AgentRuntimeWorker: gateway deliveryAgentRuntimeWorker is the platform API gateway of bounded context BC-06 (Execution). The internal gateway of the Agent Mesh platform (ADR-0028): fronts AgentRuntimeService and WorkflowEngineService, which deploy alone as silo kinds of one Orleans cluster (ADR-0024); routes internal gRPC and owns no run state. Its own repository is ConnectSoft.AI.SoftwareFactory.AgentRuntimeWorker. |
development | elaborated | backend-developer | 5 | 14 |
Observability (PF-13)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-066 ObservabilityHost: gateway deliveryObservabilityHost is the platform API gateway of bounded context BC-21 (Operations). The API gateway of the Observability platform (ADR-0028): routes public REST and internal gRPC calls to the 5 services it fronts, validates tokens and scopes, and owns no business state. Its own repository is ConnectSoft.AI.SoftwareFactory.ObservabilityHost. |
development | elaborated | backend-developer | 6 | 17 |
Factory Studio (PF-14)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-072 StudioBff: complete deliveryStudioBff is the backend-for-frontend of bounded context BC-29 (Experience Composition). The backend-for-frontend of the Factory Studio (GW-02): composes read models from every platform into screen-shaped responses under the caller's execution scope, forwards commands to the owning platform with idempotency keys and approval bindings, keeps session projections, saved views and preferences, and fronts StudioNotificationService; it owns no factory truth (BC-29). Its own repository is ConnectSoft.AI.SoftwareFactory.StudioBff. |
development | elaborated | backend-developer | 6 | 27 |
AIFACTORY-FEAT-073 StudioNotificationService: complete deliveryStudioNotificationService is the service of bounded context BC-29 (Experience Composition). Per-user notifications in the Studio — approvals waiting, alerts, releases ready, promotions and rollouts, incidents, proposals, exports — derived from platform events under each user's scope and role, with read state, grouping, digests and per-user channel preferences (in-app always; email and chat through connectors); the in-app channel is the one every other platform can rely on (BC-29). Its own repository is ConnectSoft.AI.SoftwareFactory.StudioNotificationService. |
development | elaborated | backend-developer | 5 | 22 |
AIFACTORY-FEAT-074 StudioRealtimeGateway: complete deliveryStudioRealtimeGateway is the edge service of bounded context BC-29 (Experience Composition). The SignalR hub that pushes projection updates, notifications and run events to Studio sessions — subscriptions per session bounded by its scope, backed by the platforms' gRPC streams (operations projections, run events) and StudioNotificationService; an edge service that deploys alone (ADR-0028, BC-29). Its own repository is ConnectSoft.AI.SoftwareFactory.StudioRealtimeGateway. |
development | elaborated | backend-developer | 5 | 21 |
AIFACTORY-FEAT-075 Studio work area: AssetsThe 11 screens of the Studio work area Assets 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. |
development | elaborated | frontend-developer | 4 | 15 |
AIFACTORY-FEAT-076 Studio work area: Governance & administrationThe 14 screens of the Studio work area Governance & administration on the Blazor shell and microfrontends, bound to the read models and commands the model names for them, with their state families, roles, locales and accessibility contracts. Screens come from model/ux/screens.yaml and the prototype alignment. |
development | elaborated | frontend-developer | 6 | 23 |
AIFACTORY-FEAT-077 Studio work area: IntelligenceThe 6 screens of the Studio work area Intelligence 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. |
development | elaborated | frontend-developer | 3 | 11 |
AIFACTORY-FEAT-078 Studio work area: Operations & usageThe 13 screens of the Studio work area Operations & usage 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. |
development | elaborated | frontend-developer | 5 | 19 |
AIFACTORY-FEAT-079 Studio work area: Quality & releasesThe 6 screens of the Studio work area Quality & releases 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. |
development | elaborated | frontend-developer | 3 | 11 |
AIFACTORY-FEAT-080 Studio work area: Software FactoryThe 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. |
development | elaborated | frontend-developer | 6 | 26 |
AIFACTORY-FEAT-081 Studio work area: WorkspaceThe 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. |
development | elaborated | frontend-developer | 6 | 26 |
Ecosystem component extensions¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-167 Blazor shell template: gateway adapters, filter diagnostics and pinned packages before the StudioFactory Studio is a Blazor shell composed of microfrontends behind StudioBff (ADR-0007). The shell template's own runtime backlog (docs/Control Plane) records what the Studio would otherwise inherit: the named ApiGateway client has host adapters for products and entitlements only, while the tenant list, feature flags, notifications and activity still fall back to in-memory or deny-all; a hidden navigation entry cannot be explained (OP-025: a filter result of false does not say whether a flag, an entitlement, a missing tenant or a gateway failure caused it); and the UIKit and Shell.Services pins drift between the shell, the microfrontend library and the sample templates (the integration checklist). Component: Blazor Shell + MFEs + UIKit (extend). |
before development | elaborated | frontend-developer | 6 | 23 |
AIFACTORY-FEAT-168 Blazor microfrontend library template: AppShell chrome, a neutral exemplar and a generated-solution gateThe Studio microfrontends are scaffolded from the microfrontend library template. Its own F11 record logs the gaps left open: the sample chrome is a custom navigation instead of the UIKit AppShell and still uses raw Tailwind colours instead of the cs-* semantic tokens, the sample microfrontends are Identity teaching stubs, the build has no MAX_PATH redirect, and the epic-level acceptance of the template (install, generate every parameter combination, build, run) is still unchecked. Component: Blazor Shell + MFEs + UIKit (extend). |
before development | elaborated | frontend-developer | 5 | 15 |
AIFACTORY-FEAT-169 UI kit: the token work and the Factory compositions the alignment gate ranks firstThe UI kit's own alignment gate (F01) against the design prototypes lists what the Studio screens need and the kit does not have: density that does not reach the cs-* spacing and type tokens, no named elevation scale, no motion tokens; the P0 primitives JsonViewer, DiffViewer and LogStream; and the P0 Factory compositions FactoryRunCard, AgentExecutionGraph, QualityGatePanel, TraceViewerPanel, ArtifactExplorer, ArtifactDiffPanel, ArtifactLineageGraph and HumanReviewQueue. The state-family, run-timeline and approval components are FEAT-101; this feature closes the rest of the P0 list and the adapter conformance of every new component across the Tokens, Flowbite and DaisyUI adapters. Component: Blazor Shell + MFEs + UIKit (extend). |
before development | elaborated | frontend-developer | 5 | 19 |
AIFACTORY-FEAT-101 Blazor shell, microfrontends and UI kit for the StudioThe Blazor shell template, the microfrontend library template and the UI kit are extended with what the Studio needs: the work-area navigation, the state families, the run timeline and approval components, and the realtime connection. Component: Blazor Shell + MFEs + UIKit (extend). |
development | elaborated | backend-developer | 5 | 26 |
Outcome verification¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-141 Demonstrate I3: StudioThe outcome of increment I3 is demonstrated end to end and the evidence is recorded: The same chain is submitted, watched and decided in Factory Studio. Demonstrations: A requester submits a run and follows it live in the Studio. A reviewer decides approvals from the approval inbox. Every work area renders from the platform read models through the backend-for-frontend. |
development | elaborated | qa-engineer | 4 | 10 |
Requirements this increment touches¶
FR-01, FR-03, FR-05, FR-10, FUX-01, FUX-02, FUX-03, FUX-04, FUX-06, FUX-07, FUX-08, FUX-09, FUX-10, FUX-11, FUX-12, NFR-01, NFR-02, NFR-03, NFR-05, NFR-06, NFR-08, NFR-10, NFR-11, NFR-13, NFR-17, XL-01, XL-05, XL-06, XL-08, XL-12, XL-16