Increment I2: Deliver it¶
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 merged service is built by a pipeline, deployed to a preview environment and promoted under approval; the infrastructure it runs on is planned by the Factory from the design.
Depends on: I1 · Elaboration: stories and tasks · Azure DevOps CSV of this increment
Demonstrations¶
- The merged change triggers a pipeline run whose results are recorded.
- The Security, Observability and Infrastructure Blueprints of the product are produced and validated without a person writing them.
- A preview environment is provisioned, used and torn down.
- A promotion to the next environment waits for an approval bound to the exact release.
Services delivered in this increment¶
| Service | Role | Depth | Scope in this increment | Repository |
|---|---|---|---|---|
AgentRegistryService |
service | thin | ValidateRelease, SubmitRelease, PublishRelease, GetRelease, ListReleases and MoveAlias, the events AssetReleaseSubmitted and AssetReleasePublished, the worker ClosureResolver and the handler PublishOnApproval of ApprovalDecided; the publication approval names the subject asset release (D135); no evaluation verdict is required before I4. | ConnectSoft.AI.SoftwareFactory.AgentRegistryService |
ConnectorRegistryService |
service | thin | Inbound Azure DevOps deliveries recorded and announced as DeliveryReceived, and the reads of pipeline runs, pull requests, package feeds and container registries for Azure DevOps (D135). | ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService |
WebhookGatewayService |
edge-service | thin | The webhook ingress for the Azure DevOps signature scheme with replay-window and deduplication checks, emitting verified deliveries to ConnectorRegistryService (D135). | ConnectSoft.AI.SoftwareFactory.WebhookGatewayService |
DeliveryHost |
platform-gateway | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.DeliveryHost |
EnvironmentPromotionService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.EnvironmentPromotionService |
PipelineExecutionService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.PipelineExecutionService |
ReleaseService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.ReleaseService |
ExecutionCapacityService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService |
IaCProvisioningService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.IaCProvisioningService |
RuntimeCloudHost |
platform-gateway | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.RuntimeCloudHost |
RuntimeEnvironmentService |
service | complete | the whole service as modelled | ConnectSoft.AI.SoftwareFactory.RuntimeEnvironmentService |
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-047 ExecutionCapacityService: complete delivery |
FactoryCommercialService |
static | I7 |
AIFACTORY-FEAT-047 ExecutionCapacityService: complete delivery |
RetentionResidencyService |
static | 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-173 Health aggregator template: the Factory fleet profile with scoped targets and readiness events |
ConnectSoft.HealthChecksAggregatorTemplate |
elaborated | 22 |
AIFACTORY-FEAT-174 HealthChecks.Aggregator engine library: published and reusable from a base-template service |
ConnectSoft.HealthChecksAggregatorTemplate |
elaborated | 13 |
AIFACTORY-FEAT-185 Platform template: the environment stack of a Factory estate, as a real template |
ConnectSoft.PlatformTemplate |
elaborated | 20 |
Features by epic¶
Control Plane (PF-01)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-189 AgentRegistryService: the publication path of releases from I2The owner decided that the publication of releases moves before I4 (D140), so that the workflow definitions and agents of I2 and later increments become loadable as Published releases instead of growing the seed of the thin delivery. This feature delivers the publication path of AgentRegistryService in I2: validating and submitting a release candidate with its dependency closure, the closure resolver, the publication approval by a Reviewer who is not the submitter through Run Control with the subject asset release, publishing on the approval, the reads of releases and the move of an alias. The evaluation verdict, deprecation, revocation, the learning release and the remaining consumers stay with the complete delivery in I4. Repository ConnectSoft.AI.SoftwareFactory.AgentRegistryService. |
development | elaborated | backend-developer | 6 | 22 |
Integration Platform (PF-06)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-188 ConnectorRegistryService: inbound deliveries and delivery reads for the second outcomeConnectorRegistryService is the service of bounded context BC-17 (Connectors & Webhooks). In this increment it receives the inbound deliveries of Azure DevOps through the webhook ingress of WebhookGatewayService, records each verified delivery and publishes DeliveryReceived, and serves the reads of pipeline runs, pull requests, package feeds and container registries that PipelineExecutionService and ReleaseService need, so that review states, merges and pipeline runs reach the second outcome (D135). Outbound deliveries and the other providers stay with the complete delivery in I5. Its repositories are ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService and ConnectSoft.AI.SoftwareFactory.WebhookGatewayService. |
development | elaborated | backend-developer | 7 | 36 |
DevOps / GitOps (PF-08)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-042 DeliveryHost: gateway deliveryDeliveryHost is the platform API gateway of bounded context BC-23 (Source & Pipelines). The API gateway of the DevOps / GitOps platform (ADR-0028): routes public REST and internal gRPC calls to the 3 services it fronts, validates tokens and scopes, and owns no business state. Its own repository is ConnectSoft.AI.SoftwareFactory.DeliveryHost. |
development | elaborated | backend-developer | 6 | 19 |
AIFACTORY-FEAT-043 EnvironmentPromotionService: complete deliveryEnvironmentPromotionService is the service of bounded context BC-24 (Package & Release Delivery). Promotion of a ready release into an environment class (development, test, staging, production) through gates — pipeline results, deployment-domain policy, an approval of class production for production, the environment's state — with the desired-state hand-off to provisioning (BC-25), progressive strategies, verification and rollback evidence (BC-24). Its own repository is ConnectSoft.AI.SoftwareFactory.EnvironmentPromotionService. |
development | elaborated | backend-developer | 8 | 30 |
AIFACTORY-FEAT-044 PipelineExecutionService: complete deliveryPipelineExecutionService is the service of bounded context BC-23 (Source & Pipelines). Receipts for everything the Factory does in a system of record: change proposals that became branches and pull requests with their review state, pipeline runs with stages, build, test, coverage, security and package results, and the provenance that ties every commit and run back to the Factory run, agent release and change set that produced it (BC-23; BuildResultService merged). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.PipelineExecutionService. |
development | elaborated | backend-developer | 11 | 31 |
AIFACTORY-FEAT-045 ReleaseService: complete deliveryReleaseService is the service of bounded context BC-24 (Package & Release Delivery). Releases of generated products and modules — immutable version, merged commit, container image digests, packages, SBOM and provenance attestations, change-set and pipeline references — and the evidence that each package or image was published to its feed or registry (BC-24; ContainerImageService merged; package and template publishing stay in the existing CI as external canonical). Its own repository is ConnectSoft.AI.SoftwareFactory.ReleaseService. |
development | elaborated | backend-developer | 9 | 25 |
Runtime Cloud (PF-09)¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-047 ExecutionCapacityService: complete deliveryExecutionCapacityService is the service of bounded context BC-26 (Execution Capacity). Worker pools (agent runtime, sandbox, build runner, browser) with security boundary, size and autoscaling; quotas per tenant and project tied to the edition; capacity leases per attempt, sandbox, build or session, granted within quota, renewed and released, so placement is explicit and no tenant starves another (BC-26; pool manager and scaling rows merged). This feature completes the service after its thin delivery in I1: every aggregate, operation, event and worker of the model. Repository ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService. |
development | elaborated | backend-developer | 9 | 28 |
AIFACTORY-FEAT-048 IaCProvisioningService: complete deliveryIaCProvisioningService is the service of bounded context BC-25 (Provisioning & Reconciliation). The single provisioning owner: deployment specifications (desired state declared in Git, versioned), provisioning runs with plan and apply receipts from the IaC runner (Pulumi, ADR-0004), production applies gated by the promotion's approval, and GitOps reconciliation that re-plans the declared state on a schedule (BC-25; manifest, deployment and GitOps sync rows merged). Its own repository is ConnectSoft.AI.SoftwareFactory.IaCProvisioningService. |
development | elaborated | backend-developer | 7 | 29 |
AIFACTORY-FEAT-049 RuntimeCloudHost: gateway deliveryRuntimeCloudHost is the platform API gateway of bounded context BC-25 (Provisioning & Reconciliation). The API gateway of the Runtime Cloud platform (ADR-0028): routes public REST and internal gRPC calls to the 3 services it fronts, validates tokens and scopes, and owns no business state. Its own repository is ConnectSoft.AI.SoftwareFactory.RuntimeCloudHost. |
development | elaborated | backend-developer | 6 | 19 |
AIFACTORY-FEAT-050 RuntimeEnvironmentService: complete deliveryRuntimeEnvironmentService is the service of bounded context BC-25 (Provisioning & Reconciliation). The inventory of what actually runs where — workloads, versions, replicas, configuration and secret bindings by reference, endpoints — observed from the clusters and cloud APIs, compared with the declared specification to produce drift findings, and turned into reviewable reconciliation proposals, never automatic writes (BC-25; drift detection and runtime service catalog rows merged). Its own repository is ConnectSoft.AI.SoftwareFactory.RuntimeEnvironmentService. |
development | elaborated | backend-developer | 6 | 25 |
Ecosystem component extensions¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-173 Health aggregator template: the Factory fleet profile with scoped targets and readiness eventsThe health aggregator template is the component behind environment, SLO and fleet health (RuntimeEnvironmentService, SloService, FleetInventoryService and the generated product host name it). Its own control-plane backlog is complete through B-F06: merged inventory with an ops registry and Kubernetes scrape, multi-probe polling with adaptive intervals and hysteresis, aggregator-owned incidents with notify-only sinks, history and SLO tables, the Blazor graph, MCP tools, Redis leader election and the engine library. Its locked decisions make the registry single-tenant and ops-only and keep the sinks outside the Factory: the Factory needs targets that belong to an environment, a tenant and a project, reads filtered by the Factory token, health flips and the readiness bundle (readiness-bundle.schema.json, ADR-0014) as Factory events, and discovery from the Factory's own environment inventory. Component: HealthChecks aggregator (extend). |
before development | elaborated | backend-developer | 6 | 22 |
AIFACTORY-FEAT-174 HealthChecks.Aggregator engine library: published and reusable from a base-template serviceThe aggregation engine ConnectSoft.HealthChecks.Aggregator ships as a project inside the aggregator template (B-F06) with a console sample and a pack pipeline; the move to a sibling repository is deferred. The environment and SLO services of the Factory probe environments through this engine (poller, adaptive intervals, hysteresis readiness, incident state machine) rather than running one full aggregator per environment, which needs the engine on the feed with a verified version and its types carrying environment, tenant and project. Component: HealthChecks aggregator (extend), library ConnectSoft.HealthChecks.Aggregator. |
before development | elaborated | backend-developer | 4 | 13 |
AIFACTORY-FEAT-185 Platform template: the environment stack of a Factory estate, as a real templateThe platform template repository (connectsoft-platform-template) holds what a whole estate needs and no single service template carries: a Pulumi infrastructure project with an Azure stack and an AWS stack and per-stack configuration (ADR-0004), Kubernetes deployment, service and network-policy manifests, docker-compose files for a local estate and for CI, and the observability stack scripts (OpenTelemetry collector, Prometheus, Grafana) with four pages on configuring, running and debugging it. It is not a template yet: there is no .template.config, the inventory records zero switches, the README is the base template''s scaffold with its TODO markers, the Solution Structure page lists about forty projects the repository does not contain, and the hand-written platform-template page of this site describes a multi-service SaaS generator the repository does not implement. Delivering a generated service to a preview environment and promoting it (I2) needs exactly what the repository holds, bound to the Factory''s infrastructure blueprint and deployment profiles: the environment baseline, the per-service workload manifests, the observability specification and a local estate. Component: Platform template (extend). |
before development | elaborated | devops-engineer | 6 | 20 |
Factory assets: workflow definitions, agents and skills¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-113 Workflow definition: Project bootstrapThe workflow definition project-bootstrap as a published asset: Creates the system-of-record project, repositories, pipelines and boards for a new Factory project through connectors, under one shared-write approval, and records the trace scaffolding. It has 5 steps, names the agents devops-engineer and the tools propose-change-set, and is executed by WorkflowEngineService under Run Control. |
development | elaborated | solution-architect | 4 | 14 |
AIFACTORY-FEAT-114 Workflow definition: Delivery runThe workflow definition delivery-run as a published asset: Evaluates a completed pipeline run's typed results, prepares the release manifest and requests the promotion; a production promotion waits for its approval. Deployment is a promotion, never a pipeline stage. It has 5 steps, names the agents deployment-orchestrator, devops-engineer, release-manager and the tools none, and is executed by WorkflowEngineService under Run Control. |
development | elaborated | solution-architect | 4 | 13 |
AIFACTORY-FEAT-115 Workflow definition: Preview environmentThe workflow definition preview-environment as a published asset: Creates a per-developer preview environment from a change proposal, keeps it for its time to live and tears it down; a later capability of Runtime Cloud exposed as a workflow. It has 5 steps, names the agents devops-engineer, environment-manager and the tools none, and is executed by WorkflowEngineService under Run Control. |
development | elaborated | solution-architect | 4 | 14 |
AIFACTORY-FEAT-116 Workflow definition: Release promotionThe workflow definition release as a published asset: Promotes a milestone-validated release through the environments: verifies readiness, promotes to staging, bakes against the guards, waits for the production approval, promotes and verifies; a failed verification requests the rollback. It has 6 steps, names the agents deployment-orchestrator, devops-engineer, release-manager and the tools none, and is executed by WorkflowEngineService under Run Control. |
development | elaborated | solution-architect | 5 | 16 |
AIFACTORY-FEAT-147 Workflow definition: Security blueprintThe workflow definition security-blueprint as a published asset: Builds the Security Blueprint from the validated Service Blueprint: threat model, roles and scopes per operation, data classification, secrets and key handling and the controls each threat maps to; validated against the DSL. It has 5 steps, names the agents security-architect and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control. |
development | elaborated | solution-architect | 4 | 13 |
AIFACTORY-FEAT-134 Workflow definition: Infrastructure planThe workflow definition infrastructure-plan as a published asset: Derives the Infrastructure Blueprint and the Pulumi program from the module, database, security and observability blueprints, previews it in the sandbox and records the output; nothing is applied. It has 8 steps, names the agents infrastructure-architect, infrastructure-engineer and the tools blueprint-submit-version, blueprint-validate, shell-sandbox, and is executed by WorkflowEngineService under Run Control. |
development | elaborated | solution-architect | 6 | 20 |
AIFACTORY-FEAT-152 Workflow definition: Observability blueprintThe workflow definition observability-blueprint as a published asset: Builds the Observability Blueprint from the Service and Module Blueprints: spans, metrics and log events per module, health checks, service level objectives and the alerts that guard them; validated against the DSL. It has 5 steps, names the agents observability-engineer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control. |
development | elaborated | solution-architect | 4 | 13 |
Outcome verification¶
| Feature | Phase | State | Route | PBIs | Tasks |
|---|---|---|---|---|---|
AIFACTORY-FEAT-140 Demonstrate I2: Deliver itThe outcome of increment I2 is demonstrated end to end and the evidence is recorded: The merged service is built by a pipeline, deployed to a preview environment and promoted under approval; the infrastructure it runs on is planned by the Factory from the design. Demonstrations: The merged change triggers a pipeline run whose results are recorded. The Security, Observability and Infrastructure Blueprints of the product are produced and validated without a person writing them. A preview environment is provisioned, used and torn down. A promotion to the next environment waits for an approval bound to the exact release. |
development | elaborated | qa-engineer | 4 | 11 |
Requirements this increment touches¶
FR-02, FR-05, FR-06, FR-07, FR-08, FR-09, FR-10, FR-11, FUX-02, FUX-05, FUX-06, FUX-08, FUX-10, NFR-02, NFR-05, NFR-06, NFR-07, NFR-08, NFR-09, NFR-11, NFR-12, NFR-13, NFR-18, XL-01, XL-02, XL-04, XL-08, XL-09, XL-10, XL-11, XL-12, XL-14, XL-15, XL-16