Skip to content

AIFACTORY-FEAT-088: Repository and pipeline conventions for one repository per service

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 Engineering readiness · Increment I0 Readiness · State elaborated · Route solution-architect · Build order 44 of 185 (Factory code)

Thirty repositories are created for the first outcome and sixty-five for the whole system. This feature fixes how a repository is named, created, scaffolded, built and released, so that every later feature can say 'create the repository' and mean the same steps (ADR-0028), and it creates and scaffolds every first-outcome repository in I0 from its template at the pinned version with a green template pipeline, so that the I1 features start from a repository that exists (D140).

Delivers —
Stubs —
Realizes adrs: ADR-0028
Requirements —
Depends on AIFACTORY-FEAT-156 Agent host template: generated-solution gate and a publishable package
AIFACTORY-FEAT-159 API gateway template: the platform gateway profile
AIFACTORY-FEAT-090 Contracts package from the published schemas
Sources docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md

AIFACTORY-US-360: Repository conventions: one checklist names a Factory repository, scaffolds it from the template of its kind with the Factory switch of that template and sets its branch policy

enabling · persona operator As an operator, I want one checklist that tells me the name, the template, the scaffold command and the branch policy of a Factory repository, so that every feature that says create the repository means the same steps.

ADR-0028 decision 1 builds every modelled Factory service in the repository ConnectSoft.AI.SoftwareFactory.<ServiceId> and ships it as its own deployable: sixty-five repositories for the whole system, about thirty for the first outcome. This PBI delivers the one checklist page of this site that an operator follows for each of them. The checklist decides nothing the model already states; it reads it. For a modelled service or gateway the name is the repository field of its service file under model/services and the template is the template field of the same file. The contracts package, the gateway client packages and the command-line client have no service file: their names are the entries ConnectSoft.AI.SoftwareFactory.Contracts, ConnectSoft.AI.SoftwareFactory.Clients and ConnectSoft.AI.SoftwareFactory.Cli under library_repositories and other_repositories of model/backlog/backlog.yaml, and their template is the one the row of their kind on the checklist names. The page holds one row per kind with its command, and the Factory switch differs by template. A service is scaffolded with dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.<ServiceId> --UseFactoryProfile true; the microservice template is not used for a Factory service (ADR-0028 amendment on the base template). A platform gateway is scaffolded with dotnet new connectsoft-apigateway -n <name> --UseFactoryProfile true --GatewayRole Platform, and StudioBff with --GatewayRole BackendForFrontend; the two gateway roles are two declared profiles of that template (decision D115). The agent template has no UseFactoryProfile: decision D114 puts that boolean, off by default and named the same, in the base, worker, gateway and library templates only, and the agent template takes its Factory shape from the choice agent-host-kind (decision D113, AIFACTORY-US-138), so AgentRuntimeService is scaffolded with dotnet new connectsoft-ai-agent -n ConnectSoft.AI.SoftwareFactory.AgentRuntimeService --agent-host-kind attempt-runtime and WorkflowEngineService with --agent-host-kind workflow-engine. A worker is scaffolded from connectsoft-worker, the contracts package from connectsoft-library and the gateway client packages from connectsoft-api-library, each with --UseFactoryProfile true. The command-line client is a console application for which the model names no template: its repository is created without a scaffold command and follows the name, pipeline and feed rules of the checklist. Every other parameter takes the Factory binding that model/template-parameters records for the template. The template package is restored from the ConnectSoft feed and its version is written into the repository together with the scaffold command, in the generation manifest where the template writes one. The first commit is the unchanged output of the scaffold, which builds and passes its template tests. The checklist then sets the branch policy of the default branch with its required reviewers and hands over to the pipeline convention of AIFACTORY-US-361. No repository is created before the owner approves its creation, and nothing in this documentation repository creates one. The Factory switch and the Factory shape of each template are delivered by the template features of the epic component-extensions; this PBI depends on them and adds no template parameter of its own. A kind whose template does not yet carry its Factory switch, a service whose service file names a SaaS template among them, is listed on the page as blocked with the feature that delivers the switch, and is given no command.

Acceptance criteria

AC1 Given a modelled service and the checklist page, when an operator prepares its repository, then the name is ConnectSoft.AI.SoftwareFactory.<ServiceId> and equals the repository field of the service file, and the template is the one the template field of that file names: connectsoft-base for a service, connectsoft-apigateway for a platform gateway, connectsoft-ai-agent for the two agent services; for the contracts package, the gateway client packages and the command-line client, which have no service file, the name is their entry under library_repositories or other_repositories of model/backlog/backlog.yaml and the template is the one the row of the kind names; the page names no template the model does not name (ADR-0028 decision 1 and its amendment on the base template; model/services/control-plane/RunControlService.yaml is the first example).
AC2 Given the scaffold command of the kind on the checklist, dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.<ServiceId> --UseFactoryProfile true for a service, dotnet new connectsoft-apigateway -n <name> --UseFactoryProfile true --GatewayRole Platform for a platform gateway and dotnet new connectsoft-ai-agent -n <name> --agent-host-kind attempt-runtime or --agent-host-kind workflow-engine for the two agent services, with the template package restored from the ConnectSoft feed, when its output is committed unchanged, then the solution builds in Release and its template tests pass without an edit, the other parameter values are the Factory bindings of the snapshot of the template under model/template-parameters, such as model/template-parameters/connectsoft-base.yaml, and the command with the template package version is recorded in the repository (ADR-0028 amendment on the Factory profile switch).
AC3 Given the checklist, when a repository is about to be created, then the page requires the recorded approval of the owner for that creation before the first step, sets the branch policy of the default branch with its required reviewers after the first commit, and states that nothing in this documentation repository creates a repository (ADR-0028 decision 1; docs/architecture/adr/0028-one-repository-and-deployable-per-service.md).
AC4 Given a kind whose template does not yet carry its Factory switch (UseFactoryProfile, or agent-host-kind for the agent template), when the checklist page lists the scaffold command per kind, then that kind is listed as blocked with the feature of the epic component-extensions that delivers the switch and is given no command, so that no repository is scaffolded from a template without its Factory shape (ADR-0028 amendment on the Factory profile switch; model/templates.yaml).
Traces: adrs ADR-0028
Depends on feature:component-base-template-factory-profile, feature:component-api-gateway-template, feature:component-agent-template, feature:component-library-template-factory-profile, feature:component-worker-template-factory-profile
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md, model/templates.yaml, model/template-parameters/connectsoft-base.yaml, model/services/control-plane/RunControlService.yaml, model/backlog/backlog.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-139 Repository creation checklist and naming documentation A checklist page of this site with the steps in their order: the recorded approval of the owner before any repository is created, the name read from the repository field of the service file or, for the contracts package, the gateway client packages and the command-line client, from library_repositories and other_repositories of model/backlog/backlog.yaml, the template of the kind, the scaffold command of the kind with its Factory switch (UseFactoryProfile for the base, worker, gateway and library templates, with --GatewayRole for a gateway, and agent-host-kind without UseFactoryProfile for the agent template), the unchanged first commit that builds and passes its template tests, the branch policy of the default branch with its required reviewers, the pipeline from the shared templates and the ConnectSoft feed as the only package source. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1510 Scaffold command per repository kind on the checklist page documentation The checklist page holds one row per repository kind with the template id the model names, the scaffold command, the parameter snapshot under model/template-parameters that holds its Factory bindings and the feature of the epic component-extensions that delivers the Factory switch of that template: service, dotnet new connectsoft-base -n <name> --UseFactoryProfile true; platform gateway, dotnet new connectsoft-apigateway -n <name> --UseFactoryProfile true --GatewayRole Platform, with --GatewayRole BackendForFrontend for StudioBff; AgentRuntimeService, dotnet new connectsoft-ai-agent -n <name> --agent-host-kind attempt-runtime, and WorkflowEngineService, dotnet new connectsoft-ai-agent -n <name> --agent-host-kind workflow-engine, both without UseFactoryProfile; worker, dotnet new connectsoft-worker -n <name> --UseFactoryProfile true; contracts package, dotnet new connectsoft-library -n <name> --UseFactoryProfile true; gateway client package, dotnet new connectsoft-api-library -n <name> --UseFactoryProfile true with the generation switch of that template; the command-line client has a row without a template and without a command; a kind whose template does not yet carry its Factory switch is marked blocked and has no command. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1511 Verify the checklist page against the model verification Run python -I tools/docs_model check for the model and the freshness of the generated output and mkdocs build --strict for the site with the checklist page; every service file under model/services names a repository and a template, and a read of the page against model/templates.yaml and model/backlog/backlog.yaml finds the name rule, the template and the command of each kind with its Factory switch, the approval step and the branch policy step, which proves AC1 to AC4 of AIFACTORY-US-360 (ADR-0028). ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-361: Repository conventions: the pipeline of a scaffolded repository builds, tests, packs and publishes from the shared pipeline templates to the ConnectSoft feed, with no script of its own

enabling · persona operator As an operator, I want the pipeline of every Factory repository to come from the shared pipeline templates and to use one feed, so that sixty-five pipelines are maintained in one place and no repository carries a build script of its own.

ADR-0028 accepts more pipelines as the price of one repository per service and states that the work a host did once is now done per service by the scaffold. This PBI fixes what the pipeline of a Factory repository is. The pipeline file that the template generates calls the shared step templates of ConnectSoft.AzurePipelines for a service: the build and lint steps, the test steps, the publish steps and the container image steps. A Factory repository therefore produces four results from shared steps: the build, the tests with complete reports, the package where the repository publishes one, and the container image of a deployable. It holds no build, test, pack or push script of its own. A gap that the first Factory repository finds in a shared service step is closed in that shared step, with its default unchanged for the consumers that exist today, and never by a script in the repository. The feed is settled by decision D114 and the amendment of ADR-0028 on the Factory profile switch: the Factory feed is the Azure Artifacts feed the ConnectSoft libraries already publish to, named the ConnectSoft feed here. A Factory repository restores from it and publishes to it, and no second feed is created. The shared pipeline of the templates themselves is not this PBI: the gate hook and the opt-in version guard of the shared template installer steps are AIFACTORY-TASK-1426 under AIFACTORY-US-232 of feature component-base-template-findings, and the admission of one additional gating case per declared profile is delivered under AIFACTORY-US-230 of feature component-base-template-factory-profile. This PBI depends on both features and repeats none of their tasks. Before the first repository is created, the versions of the templates and libraries that the first-outcome repositories use are recorded and each is restored from the feed by a clean project; a version that is not on the feed is recorded as missing and blocks the repositories that need it. The first repository, ConnectSoft.AI.SoftwareFactory.RunControlService, is then created by the checklist of AIFACTORY-US-360 and its pipeline proves the convention.

Acceptance criteria

AC1 Given a repository scaffolded by the checklist of AIFACTORY-US-360, when its pipeline runs, then the build, the tests with complete reports, the package and the container image come from the shared step templates of ConnectSoft.AzurePipelines, and the pipeline file holds no build, test, pack or push script of its own (ADR-0028 consequences; docs/architecture/adr/0028-one-repository-and-deployable-per-service.md).
AC2 Given the pipeline of a Factory repository, when it restores and when it publishes, then the ConnectSoft feed, the Azure Artifacts feed the ConnectSoft libraries already publish to, is its only package source and its only publication target, and no second feed exists for the Factory (ADR-0028 amendment on the Factory profile switch).
AC3 Given the recorded list of the template and library versions the first-outcome repositories use, when a clean project with the ConnectSoft feed as its only source restores each of them, then every listed version restores, and a version that is not on the feed is recorded as missing with the repositories it blocks (ADR-0028; model/templates.yaml and model/libraries.yaml name the templates and libraries).
AC4 Given the shared template pipeline tasks that the epic component-extensions already holds, when the work of this PBI in ConnectSoft.AzurePipelines is reviewed, then it changes the shared service steps only and adds no second gate hook, version guard or profile gating case beside AIFACTORY-TASK-1426 and the additional case of the base template gate (ADR-0028 amendment on the Factory profile switch; model/backlog/pbis/component-extensions/component-base-template-findings.yaml).
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, feature:component-base-template-findings, feature:component-base-template-factory-profile
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/architecture/capability-dependencies.md, model/templates.yaml, model/libraries.yaml, model/backlog/pbis/component-extensions/component-base-template-findings.yaml, model/backlog/pbis/component-extensions/component-base-template-factory-profile.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-140 Pipeline templates for a Factory service repository operations A service repository gets build, test, package and container publication from the shared service steps of ConnectSoft.AzurePipelines (the build and lint steps, the test steps, the publish steps and the container image steps) with no per-repository script; a gap the first Factory repository finds is closed in the shared step with its default unchanged for the consumers of today; the shared template pipeline template-ci/v1 and the installer steps with the gate hook and the version guard of AIFACTORY-TASK-1426 are not changed by this task. ConnectSoft.AzurePipelines
AIFACTORY-TASK-141 Verify template and package versions on the feed documentation A recorded list, on the checklist page, of the template and library versions the first-outcome repositories use, each restored from the ConnectSoft feed by a clean project with that feed as its only source; a version that does not restore is recorded as missing with the repositories it blocks. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-190 Prove the checklist on the first repository verification The repository ConnectSoft.AI.SoftwareFactory.RunControlService is created by the checklist after the approval of the owner; this is the one creation of the repository, and feature run-control-service of increment I1 takes the repository as it stands; its first commit is the unchanged output of the scaffold command with UseFactoryProfile, and one run of its pipeline is green: build, tests with complete reports, package and container image from the shared steps, with the ConnectSoft feed as the only source in the restore log, which proves AC1 and AC2 of AIFACTORY-US-361 and AC2 of AIFACTORY-US-360 (ADR-0028). ConnectSoft.AI.SoftwareFactory.RunControlService

AIFACTORY-US-362: Repository conventions: a conformance check reports every name, template, pipeline and feed deviation of a repository and passes on the first repository

evidence · persona operator As an operator, I want a check that tells me where a repository deviates from the checklist, so that the sameness of the Factory repositories is proven by a run and not by a reading.

A checklist that sixty-five repositories follow drifts unless something checks it. This PBI is the proof of the feature: a conformance check, a script of this documentation repository, that takes the working tree of one repository and the model of this site and reports where the repository deviates from the conventions of AIFACTORY-US-360 and AIFACTORY-US-361. It knows four classes of deviation. A name deviation: the repository name is neither the repository field of a service file under model/services nor an entry of library_repositories or other_repositories of model/backlog/backlog.yaml. A template deviation: the scaffold record of the repository names another template than the one its kind requires, or shows a scaffold without the Factory switch of its kind. For a service or gateway the required template is the template field of its service file; for an entry of the two lists it is the template the checklist row of the kind names, connectsoft-library for the contracts package and connectsoft-api-library for the client packages; the command-line client has no template rule. The Factory switch is UseFactoryProfile for the base, worker, gateway and library templates, with the gateway role for a gateway, and agent-host-kind with the value attempt-runtime or workflow-engine for the agent template. A pipeline deviation: the pipeline file holds a build, test, pack or push step that is not a shared step template of ConnectSoft.AzurePipelines, or omits a result its kind requires. A feed deviation: the package source configuration or the pipeline names a source or a target other than the ConnectSoft feed. The check reports every deviation of a run with the file and the rule, exits with a failure when it found one, reads only, and creates and changes nothing in the checked repository or in any tracker. A fixture of six planted trees proves it: four trees, one per class, prove that each class is reported, and two trees that follow the checklist, a service repository and a library repository named in library_repositories, prove the silent pass. The check is then run on the first repository that the checklist created. Its result is the evidence that later features rely on when they say that a repository was created by the checklist.

Acceptance criteria

AC1 Given a repository tree whose name is neither the repository field of a service file nor an entry of library_repositories or other_repositories of model/backlog/backlog.yaml, and a tree whose scaffold record names a template other than the one its kind requires or shows a scaffold without the Factory switch of its kind, when the conformance check runs, then each deviation is reported with the rule and the file and the run ends with a failure; for an entry of the two lists the template is the one the checklist row of the kind names (connectsoft-library for the contracts package, connectsoft-api-library for the client packages) and the console client has no template rule (ADR-0028 decision 1 and its amendment on the Factory profile switch; model/services/control-plane/RunControlService.yaml).
AC2 Given a repository tree whose pipeline file holds a build, test, pack or push step of its own, and a tree whose package source configuration names a source other than the ConnectSoft feed, when the conformance check runs, then the pipeline deviation and the feed deviation are each reported with the step or the source named (ADR-0028 consequences and its amendment on the Factory profile switch).
AC3 Given the first repository created by the checklist, and a planted library repository tree named in library_repositories of model/backlog/backlog.yaml and scaffolded from connectsoft-library, when the conformance check runs on each working tree, then it reports no deviation and ends with success, it has written nothing to the checked repository, and the recorded result names the revision that was checked (ADR-0028; docs/architecture/adr/0028-one-repository-and-deployable-per-service.md).
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/architecture/capability-dependencies.md, model/templates.yaml, model/backlog/backlog.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-189 Checklist and conformance check implementation A script of this repository, linked from the checklist page, that takes the path of a repository working tree, reads the service files under model/services and the lists library_repositories and other_repositories of model/backlog/backlog.yaml, and reports the name, template, pipeline and feed deviations of that repository, each with the rule and the file: the name is the repository field of a service file or an entry of one of the two lists; for those entries the template is the one the checklist row of the kind names (connectsoft-library for the contracts package, connectsoft-api-library for the client packages) and the console client has no template rule; the template rule reports a scaffold without the Factory switch of its kind; it exits with a failure when a deviation exists, reads only and writes nothing to the checked repository. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1512 Planted repository trees for the four classes of deviation and the two passes fixture A fixture of six small repository trees beside the script: a wrong name, a wrong template or a scaffold without the Factory switch of its kind, a pipeline file with a step of its own, a package source other than the ConnectSoft feed, one service tree that follows the checklist and one library repository tree named in library_repositories and scaffolded from connectsoft-library; a test of the script asserts the reported rule for each of the four and the silent pass of the fifth and the sixth. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1513 Verify the conformance check on the fixture and on the first repository verification The test of the script over the six planted trees passes, and one run of the check on the working tree of ConnectSoft.AI.SoftwareFactory.RunControlService reports no deviation with the checked revision recorded on the checklist page, which proves AC1 to AC3 of AIFACTORY-US-362 (ADR-0028). ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-002: A new service repository is ready in one pass

enabling · persona operator As an operator, I want to create a Factory service repository by following one checklist, so that every one of the sixty-five repositories is built, tested and released the same way.

This is the integration PBI of the feature. An operator creates a Factory repository in one pass: the checklist of AIFACTORY-US-360 gives the name, the template of the kind and the scaffold command of the kind with its Factory switch; the pipeline convention of AIFACTORY-US-361 gives build, tests, package and container image from the shared pipeline templates and the ConnectSoft feed as the only feed; the conformance check of AIFACTORY-US-362 reports any deviation. The work lives in those three PBIs and this one proves them together on two repositories of different kinds. The first, ConnectSoft.AI.SoftwareFactory.RunControlService, is a service scaffolded from the base template. The second, ConnectSoft.AI.SoftwareFactory.ControlPlaneApi, is a platform gateway scaffolded from the API gateway template, which the feature trusted-scope-chain then works in. Both are created only after the owner approved their creation, each is created once, here, and the feature of increment I1 that delivers its content takes the repository as it stands, both first commits are the unchanged scaffold output, both pipelines are green and the conformance check reports no deviation for either. The feature is done when a later feature can say that a repository is created by the checklist and mean these steps, for a service and for a gateway alike. Decision D140 then creates every other first-outcome repository in this feature, in increment I0, by the same steps: AIFACTORY-US-1596 to AIFACTORY-US-1601 hold the thirty creation tasks that the I1 features carried before, grouped by plane and with their identifiers kept, so that the I0 demonstration of AIFACTORY-US-1336, every first-outcome repository exists, builds and runs its template tests in its pipeline, can pass in I0, and the I1 features start from the repository created and scaffolded here. The shared template pipeline tasks stay with the features component-base-template-findings and component-base-template-factory-profile of the epic component-extensions, which this feature depends on. The services that the repositories hold are delivered by their own features from increment I1 on.

Acceptance criteria

AC1 Given the checklist, when an operator creates a repository for a modelled service, then its name is ConnectSoft.AI.SoftwareFactory.<ServiceId> and the scaffold of its template with the Factory switch of its kind builds unchanged (ADR-0028 decision 1 and its amendment on the Factory profile switch).
AC2 Given the scaffolded repository, when its pipeline runs, then build, tests, package and container image succeed from the shared pipeline templates and the ConnectSoft feed is the only package source (ADR-0028; docs/architecture/adr/0028-one-repository-and-deployable-per-service.md).
AC3 Given a repository that deviates from the checklist in its name, its template, its pipeline or its feed, when the conformance check runs, then the deviation is reported, and given the two repositories created by the checklist, a service and a platform gateway, then the check reports none (ADR-0028 decisions 1 and 2).
AC4 Given the thirty first-outcome repositories that AIFACTORY-US-1596 to AIFACTORY-US-1601 create in I0 beside RunControlService, ControlPlaneApi and AgentRuntimeService, when the conformance check runs over each and its pipeline runs on the default branch, then every one is green and reports no deviation, and the list of their run identifiers is the one the readiness proof of AIFACTORY-US-1336 records (ADR-0028 decision 1, D140).
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361, AIFACTORY-US-362, AIFACTORY-US-1596, AIFACTORY-US-1597, AIFACTORY-US-1598, AIFACTORY-US-1599, AIFACTORY-US-1600, AIFACTORY-US-1601
Sources docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1514 Prove the checklist on a repository of a second kind verification The repository ConnectSoft.AI.SoftwareFactory.ControlPlaneApi is created by the same checklist after the approval of the owner, with dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.ControlPlaneApi --UseFactoryProfile true --GatewayRole Platform; this is the one creation of the repository, and feature control-plane-api of increment I1 takes the repository as it stands; its first commit is the unchanged scaffold output, its pipeline is green from the shared steps and the conformance check reports no deviation, which proves AC1 to AC3 of AIFACTORY-US-002 for a platform gateway (ADR-0028 decision 2). ConnectSoft.AI.SoftwareFactory.ControlPlaneApi
AIFACTORY-TASK-717 Verify repository-in-one-pass by running the declared command verification Run python -I tools/docs_model validate; it passes with the checklist page, the recorded versions, the recorded conformance results of the two repositories and the green runs and conformance results of the thirty repositories of AIFACTORY-US-1596 to AIFACTORY-US-1601 in place, and proves AC1 to AC4 of AIFACTORY-US-002. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1596: Repository conventions: the first-outcome repositories of the control plane and the workflow engine are created and scaffolded in I0 by the checklist, each with a green template pipeline

enabling · persona operator As an operator, I want the repositories of AgentRegistryService, EnvironmentService, ProjectService, CostUsageService and WorkflowEngineService created and scaffolded before increment I1 starts, so that the readiness demonstration of I0 finds every first-outcome repository built and tested in its own pipeline, and the I1 features start from a scaffold that is known to build.

Decision D140 moves the creation of every first-outcome repository into increment I0, so that the first demonstration of I0, which AIFACTORY-US-1336 proves (each first-outcome repository exists, builds and runs its template tests in its pipeline), can pass in I0. This PBI holds the five repositories of the control plane and the agent mesh beside RunControlService, ControlPlaneApi and AgentRuntimeService, which were already created in I0. The tasks keep the identifiers they had in their I1 features: AIFACTORY-TASK-001 creates ConnectSoft.AI.SoftwareFactory.AgentRegistryService, AIFACTORY-TASK-010 ConnectSoft.AI.SoftwareFactory.EnvironmentService, AIFACTORY-TASK-016 ConnectSoft.AI.SoftwareFactory.ProjectService and AIFACTORY-TASK-238 ConnectSoft.AI.SoftwareFactory.CostUsageService, each with dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the base template package at the version the gate of AIFACTORY-US-230 published; AIFACTORY-TASK-037 creates ConnectSoft.AI.SoftwareFactory.WorkflowEngineService with dotnet new connectsoft-ai-agent -n <name> --agent-host-kind workflow-engine from the pinned agent template package, without UseFactoryProfile. Every repository is created by the steps of the checklist of AIFACTORY-US-360, only after the recorded approval of the owner for its creation, which stays an open row of the register of AIFACTORY-US-379 until the owner gives it. Its first commit is the unchanged scaffold output with the messaging service name of its service file, the repository records the template version and the scaffold command, the branch policy is set, and the pipeline of AIFACTORY-US-361 builds it, runs the template tests and publishes the container image from the shared steps with the ConnectSoft feed as the only source. No Factory code is written here: the I1 features agent-registry-service-thin, environment-service, project-service, cost-usage-service-complete and workflow-engine-service take each repository as it stands and start from its scaffold. A repository whose scaffold does not build, whose template tests fail or that the conformance check of AIFACTORY-US-362 reports as deviating is recorded by name and blocks the readiness proof; it is never waived.

Acceptance criteria

AC1 Given the recorded approval of the owner for each creation and the checklist of AIFACTORY-US-360, when AIFACTORY-TASK-001, AIFACTORY-TASK-010, AIFACTORY-TASK-016 and AIFACTORY-TASK-238 run, then the repositories ConnectSoft.AI.SoftwareFactory.AgentRegistryService, ConnectSoft.AI.SoftwareFactory.EnvironmentService, ConnectSoft.AI.SoftwareFactory.ProjectService and ConnectSoft.AI.SoftwareFactory.CostUsageService exist, each first commit is the unchanged output of dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the template package the gate of AIFACTORY-US-230 published, and each records that version and the messaging service name of its service file under model/services/control-plane (ADR-0028 decision 1, D140).
AC2 Given the pinned agent template package, when AIFACTORY-TASK-037 runs, then ConnectSoft.AI.SoftwareFactory.WorkflowEngineService exists, its first commit is the unchanged output of dotnet new connectsoft-ai-agent -n ConnectSoft.AI.SoftwareFactory.WorkflowEngineService --agent-host-kind workflow-engine with no UseFactoryProfile, and it records the template version, the messaging service name workflow-engine and the silo kind of the workflow engine (ADR-0028 amendment on the Factory profile switch, model/services/agent-mesh/WorkflowEngineService.yaml).
AC3 Given each of the five repositories, when its pipeline runs on the default branch, then it restores from the ConnectSoft feed alone, builds in Release, passes the template tests with complete reports and publishes the container image from the shared steps of AIFACTORY-US-361, and the conformance check of AIFACTORY-US-362 reports no deviation, so that the five rows of the repository list of AIFACTORY-US-1336 carry a green run (ADR-0028, D140).
Traces: services AgentRegistryService, EnvironmentService, ProjectService, CostUsageService, WorkflowEngineService
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361, AIFACTORY-US-362, feature:component-base-template-factory-profile, feature:component-base-template-findings, feature:component-agent-template-release, feature:contracts-package
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/services/control-plane/AgentRegistryService.yaml, model/services/control-plane/EnvironmentService.yaml, model/services/control-plane/ProjectService.yaml, model/services/control-plane/CostUsageService.yaml, model/services/agent-mesh/WorkflowEngineService.yaml, handoffs/2026-10-09-independent-review/decision-log.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-001 Create the repository ConnectSoft.AI.SoftwareFactory.AgentRegistryService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists, the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.AgentRegistryService --UseFactoryProfile true from the pinned template package is committed with the messaging service name agent-registry, the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
AIFACTORY-TASK-010 Create the repository ConnectSoft.AI.SoftwareFactory.EnvironmentService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists, the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.EnvironmentService --UseFactoryProfile true from the pinned template package is committed with the messaging service name environment, the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.EnvironmentService
AIFACTORY-TASK-016 Create the repository ConnectSoft.AI.SoftwareFactory.ProjectService and scaffold it from the base template with the Factory profile implementation The repository exists; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.ProjectService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.ProjectService
AIFACTORY-TASK-238 Create the repository ConnectSoft.AI.SoftwareFactory.CostUsageService and scaffold it from the base template with the Factory profile implementation The repository exists; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.CostUsageService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.CostUsageService
AIFACTORY-TASK-037 Create the repository ConnectSoft.AI.SoftwareFactory.WorkflowEngineService and scaffold it from the pinned agent host template as the workflow-engine host kind implementation The repository exists as the checklist of feature repository-and-pipeline-conventions creates it, the output of dotnet new connectsoft-ai-agent -n ConnectSoft.AI.SoftwareFactory.WorkflowEngineService --agent-host-kind workflow-engine from the pinned template package is committed with the messaging service name workflow-engine and the silo kind of the workflow engine, the repository records the template version, the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
AIFACTORY-TASK-6471 Verify the five control plane and agent mesh repositories and their green pipeline runs verification The repository list of AIFACTORY-US-1336 holds ConnectSoft.AI.SoftwareFactory.AgentRegistryService, ConnectSoft.AI.SoftwareFactory.EnvironmentService, ConnectSoft.AI.SoftwareFactory.ProjectService, ConnectSoft.AI.SoftwareFactory.CostUsageService and ConnectSoft.AI.SoftwareFactory.WorkflowEngineService, each with the recorded approval of its creation, its template and template version, the identifier of one green pipeline run on its default branch that restored from the ConnectSoft feed alone, built in Release and passed the template tests, and a conformance check with no deviation; the comparison of these rows with AIFACTORY-TASK-001, AIFACTORY-TASK-010, AIFACTORY-TASK-016, AIFACTORY-TASK-238 and AIFACTORY-TASK-037 proves AC1 to AC3 of AIFACTORY-US-1596, and python -I tools/docs_model check passes with the list in place. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1597: Repository conventions: the first-outcome repositories of the governance plane are created and scaffolded in I0 by the checklist, each with a green template pipeline

enabling · persona operator As an operator, I want the repositories of PolicyEngineService, SecretBrokerService, AuditService and GovernanceHost created and scaffolded before increment I1 starts, so that the readiness demonstration of I0 finds the governance repositories built and tested in their own pipelines, and the I1 governance features start from a scaffold that is known to build.

Decision D140 moves the creation of every first-outcome repository into increment I0, so that the first demonstration of I0, which AIFACTORY-US-1336 proves, can pass in I0. This PBI holds the four repositories of the governance plane. The tasks keep the identifiers they had in their I1 features: AIFACTORY-TASK-101 creates ConnectSoft.AI.SoftwareFactory.PolicyEngineService, AIFACTORY-TASK-108 ConnectSoft.AI.SoftwareFactory.SecretBrokerService and AIFACTORY-TASK-231 ConnectSoft.AI.SoftwareFactory.AuditService, each with dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned base template package; AIFACTORY-TASK-454 creates the platform gateway ConnectSoft.AI.SoftwareFactory.GovernanceHost with dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.GovernanceHost --UseFactoryProfile true --GatewayRole Platform, whose template tests include the architecture test of the Platform role. Every repository is created by the steps of the checklist of AIFACTORY-US-360 only after the recorded approval of the owner for its creation, which stays an open row of the register of AIFACTORY-US-379 until the owner gives it. Its first commit is the unchanged scaffold output with the messaging service name of its service file where the service has one, the repository records the template version and the scaffold command, the branch policy is set, and the pipeline of AIFACTORY-US-361 builds it, runs the template tests and publishes the container image from the shared steps with the ConnectSoft feed as the only source. No Factory code is written here: the I1 features policy-engine-service, secret-broker-service, audit-service-complete and governance-host take each repository as it stands. A repository whose scaffold does not build, whose template tests fail or that the conformance check of AIFACTORY-US-362 reports as deviating is recorded by name and blocks the readiness proof; it is never waived.

Acceptance criteria

AC1 Given the recorded approval of the owner for each creation and the checklist of AIFACTORY-US-360, when AIFACTORY-TASK-101, AIFACTORY-TASK-108 and AIFACTORY-TASK-231 run, then ConnectSoft.AI.SoftwareFactory.PolicyEngineService, ConnectSoft.AI.SoftwareFactory.SecretBrokerService and ConnectSoft.AI.SoftwareFactory.AuditService exist, each first commit is the unchanged output of dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned template package, and each records the template version and the messaging service name of its service file under model/services/governance (ADR-0028 decision 1, D140).
AC2 Given the pinned API gateway template package, when AIFACTORY-TASK-454 runs, then ConnectSoft.AI.SoftwareFactory.GovernanceHost exists, its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.GovernanceHost --UseFactoryProfile true --GatewayRole Platform, it records the template version, and the template tests pass with the architecture test of the Platform role (ADR-0028 decision 2, model/services/governance/GovernanceHost.yaml).
AC3 Given each of the four repositories, when its pipeline runs on the default branch, then it restores from the ConnectSoft feed alone, builds in Release, passes the template tests with complete reports and publishes the container image from the shared steps of AIFACTORY-US-361, and the conformance check of AIFACTORY-US-362 reports no deviation, so that the four rows of the repository list of AIFACTORY-US-1336 carry a green run (ADR-0028, D140).
Traces: services PolicyEngineService, SecretBrokerService, AuditService, GovernanceHost
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361, AIFACTORY-US-362, feature:component-base-template-factory-profile, feature:component-base-template-findings, feature:component-api-gateway-template, feature:contracts-package
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/services/governance/PolicyEngineService.yaml, model/services/governance/SecretBrokerService.yaml, model/services/governance/AuditService.yaml, model/services/governance/GovernanceHost.yaml, handoffs/2026-10-09-independent-review/decision-log.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-101 Create the repository ConnectSoft.AI.SoftwareFactory.PolicyEngineService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists by the repository checklist of feature repository-and-pipeline-conventions, the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.PolicyEngineService --UseFactoryProfile true from the pinned template package is committed unchanged with the messaging service name policy-engine, the repository records the template version, the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.PolicyEngineService
AIFACTORY-TASK-108 Create the repository ConnectSoft.AI.SoftwareFactory.SecretBrokerService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.SecretBrokerService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name secret-broker; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.SecretBrokerService
AIFACTORY-TASK-231 Create the repository ConnectSoft.AI.SoftwareFactory.AuditService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.AuditService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name audit; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.AuditService
AIFACTORY-TASK-454 Create the repository ConnectSoft.AI.SoftwareFactory.GovernanceHost and scaffold it from the API gateway template with the Factory profile and the Platform gateway role implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.GovernanceHost --UseFactoryProfile true --GatewayRole Platform from the pinned template package, whose version the repository records; the solution builds and the template tests, the architecture test of the Platform role included, pass in the repository pipeline, which publishes the container image; a deviation is corrected in the repository before the fronts file of AIFACTORY-TASK-455 is written. ConnectSoft.AI.SoftwareFactory.GovernanceHost
AIFACTORY-TASK-6472 Verify the four governance repositories and their green pipeline runs verification The repository list of AIFACTORY-US-1336 holds ConnectSoft.AI.SoftwareFactory.PolicyEngineService, ConnectSoft.AI.SoftwareFactory.SecretBrokerService, ConnectSoft.AI.SoftwareFactory.AuditService and ConnectSoft.AI.SoftwareFactory.GovernanceHost, each with the recorded approval of its creation, its template and template version, the identifier of one green pipeline run on its default branch that restored from the ConnectSoft feed alone, built in Release and passed the template tests (the architecture test of the Platform role for GovernanceHost), and a conformance check with no deviation; the comparison of these rows with AIFACTORY-TASK-101, AIFACTORY-TASK-108, AIFACTORY-TASK-231 and AIFACTORY-TASK-454 proves AC1 to AC3 of AIFACTORY-US-1597, and python -I tools/docs_model check passes with the list in place. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1598: Repository conventions: the first-outcome repositories of integration, delivery and runtime capacity are created and scaffolded in I0 by the checklist, each with a green template pipeline

enabling · persona operator As an operator, I want the repositories of ConnectorRegistryService, IntegrationService, IntegrationHost, PipelineExecutionService and ExecutionCapacityService created and scaffolded before increment I1 starts, so that the readiness demonstration of I0 finds these repositories built and tested in their own pipelines, and their I1 features start from a scaffold that is known to build.

Decision D140 moves the creation of every first-outcome repository into increment I0, so that the first demonstration of I0, which AIFACTORY-US-1336 proves, can pass in I0. This PBI holds the five repositories of the integration plane, of the delivery plane and of the runtime capacity that the first outcome needs. The tasks keep the identifiers they had in their I1 features: AIFACTORY-TASK-086 creates ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService, AIFACTORY-TASK-089 ConnectSoft.AI.SoftwareFactory.IntegrationService, AIFACTORY-TASK-092 ConnectSoft.AI.SoftwareFactory.PipelineExecutionService and AIFACTORY-TASK-095 ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService, each with dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned base template package; AIFACTORY-TASK-463 creates the platform gateway ConnectSoft.AI.SoftwareFactory.IntegrationHost with dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.IntegrationHost --UseFactoryProfile true --GatewayRole Platform, whose template tests include the architecture test of the Platform role. Every repository is created by the steps of the checklist of AIFACTORY-US-360 only after the recorded approval of the owner for its creation, which stays an open row of the register of AIFACTORY-US-379 until the owner gives it. Its first commit is the unchanged scaffold output with the messaging service name of its service file where the service has one, the repository records the template version and the scaffold command, the branch policy is set, and the pipeline of AIFACTORY-US-361 builds it, runs the template tests and publishes the container image from the shared steps with the ConnectSoft feed as the only source. No Factory code is written here: the I1 features connector-registry-service-thin, integration-service-thin, integration-host, pipeline-execution-service-thin and execution-capacity-service-thin take each repository as it stands. A repository whose scaffold does not build, whose template tests fail or that the conformance check of AIFACTORY-US-362 reports as deviating is recorded by name and blocks the readiness proof; it is never waived.

Acceptance criteria

AC1 Given the recorded approval of the owner for each creation and the checklist of AIFACTORY-US-360, when AIFACTORY-TASK-086, AIFACTORY-TASK-089, AIFACTORY-TASK-092 and AIFACTORY-TASK-095 run, then ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService, ConnectSoft.AI.SoftwareFactory.IntegrationService, ConnectSoft.AI.SoftwareFactory.PipelineExecutionService and ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService exist, each first commit is the unchanged output of dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned template package, and each records the template version and the messaging service name of its service file (ADR-0028 decision 1, model/services/integration/ConnectorRegistryService.yaml, D140).
AC2 Given the pinned API gateway template package, when AIFACTORY-TASK-463 runs, then ConnectSoft.AI.SoftwareFactory.IntegrationHost exists, its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.IntegrationHost --UseFactoryProfile true --GatewayRole Platform, it records the template version, and the template tests pass with the architecture test of the Platform role (ADR-0028 decision 2, model/services/integration/IntegrationHost.yaml).
AC3 Given each of the five repositories, when its pipeline runs on the default branch, then it restores from the ConnectSoft feed alone, builds in Release, passes the template tests with complete reports and publishes the container image from the shared steps of AIFACTORY-US-361, and the conformance check of AIFACTORY-US-362 reports no deviation, so that the five rows of the repository list of AIFACTORY-US-1336 carry a green run (ADR-0028, D140).
Traces: services ConnectorRegistryService, IntegrationService, IntegrationHost, PipelineExecutionService, ExecutionCapacityService
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361, AIFACTORY-US-362, feature:component-base-template-factory-profile, feature:component-base-template-findings, feature:component-api-gateway-template
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/services/integration/ConnectorRegistryService.yaml, model/services/integration/IntegrationService.yaml, model/services/integration/IntegrationHost.yaml, model/services/devops-gitops/PipelineExecutionService.yaml, model/services/runtime-cloud/ExecutionCapacityService.yaml, handoffs/2026-10-09-independent-review/decision-log.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-086 Create the repository ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService --UseFactoryProfile true from the pinned template package, whose version the repository records, with the messaging service name connector-registry; the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService
AIFACTORY-TASK-089 Create the repository ConnectSoft.AI.SoftwareFactory.IntegrationService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.IntegrationService --UseFactoryProfile true from the pinned template package, whose version the repository records, with the messaging service name integration; the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.IntegrationService
AIFACTORY-TASK-463 Create the repository ConnectSoft.AI.SoftwareFactory.IntegrationHost and scaffold it from the API gateway template with the Factory profile and the Platform gateway role implementation The repository exists by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.IntegrationHost --UseFactoryProfile true --GatewayRole Platform from the pinned template package, whose version the repository records; the solution builds and the template tests, the architecture test of the Platform role included, pass in the repository pipeline, which publishes the container image; a deviation is corrected in the repository before the fronts file of AIFACTORY-TASK-464 is written. ConnectSoft.AI.SoftwareFactory.IntegrationHost
AIFACTORY-TASK-092 Create the repository ConnectSoft.AI.SoftwareFactory.PipelineExecutionService and scaffold it from the ConnectSoft.BaseTemplate template implementation The repository exists by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.PipelineExecutionService --UseFactoryProfile true from the pinned template package, whose version the repository records, with the messaging service name pipeline-execution; the solution builds and the template tests pass in the repository pipeline. ConnectSoft.AI.SoftwareFactory.PipelineExecutionService
AIFACTORY-TASK-095 Create the repository ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService --UseFactoryProfile true from the pinned template package, whose version the repository records, with the messaging service name execution-capacity; the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService
AIFACTORY-TASK-6473 Verify the five integration, delivery and runtime repositories and their green pipeline runs verification The repository list of AIFACTORY-US-1336 holds ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService, ConnectSoft.AI.SoftwareFactory.IntegrationService, ConnectSoft.AI.SoftwareFactory.IntegrationHost, ConnectSoft.AI.SoftwareFactory.PipelineExecutionService and ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService, each with the recorded approval of its creation, its template and template version, the identifier of one green pipeline run on its default branch that restored from the ConnectSoft feed alone, built in Release and passed the template tests (the architecture test of the Platform role for IntegrationHost), and a conformance check with no deviation; the comparison of these rows with AIFACTORY-TASK-086, AIFACTORY-TASK-089, AIFACTORY-TASK-463, AIFACTORY-TASK-092 and AIFACTORY-TASK-095 proves AC1 to AC3 of AIFACTORY-US-1598, and python -I tools/docs_model check passes with the list in place. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1599: Repository conventions: the first-outcome repositories of the knowledge plane are created and scaffolded in I0 by the checklist, each with a green template pipeline

enabling · persona operator As an operator, I want the repositories of ArtifactService, ContextBuilderService, KnowledgeIngestionService, RepositoryIntelligenceService, VectorMemoryService and KnowledgeHost created and scaffolded before increment I1 starts, so that the readiness demonstration of I0 finds the knowledge repositories built and tested in their own pipelines, and the I1 knowledge features start from a scaffold that is known to build.

Decision D140 moves the creation of every first-outcome repository into increment I0, so that the first demonstration of I0, which AIFACTORY-US-1336 proves, can pass in I0. This PBI holds the six repositories of the knowledge plane. The tasks keep the identifiers they had in their I1 features: AIFACTORY-TASK-054 creates ConnectSoft.AI.SoftwareFactory.ArtifactService, AIFACTORY-TASK-061 ConnectSoft.AI.SoftwareFactory.ContextBuilderService, AIFACTORY-TASK-064 ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService, AIFACTORY-TASK-067 ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService and AIFACTORY-TASK-070 ConnectSoft.AI.SoftwareFactory.VectorMemoryService, each with dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned base template package; AIFACTORY-TASK-466 creates the platform gateway ConnectSoft.AI.SoftwareFactory.KnowledgeHost with dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.KnowledgeHost --UseFactoryProfile true --GatewayRole Platform, whose template tests include the architecture test of the Platform role. Every repository is created by the steps of the checklist of AIFACTORY-US-360 only after the recorded approval of the owner for its creation, which stays an open row of the register of AIFACTORY-US-379 until the owner gives it. Its first commit is the unchanged scaffold output with the messaging service name of its service file where the service has one, the repository records the template version and the scaffold command, the branch policy is set, and the pipeline of AIFACTORY-US-361 builds it, runs the template tests and publishes the container image from the shared steps with the ConnectSoft feed as the only source. No Factory code is written here: the I1 features artifact-service, context-builder-service-thin, knowledge-ingestion-service-thin, repository-intelligence-service-thin, vector-memory-service-thin and knowledge-host take each repository as it stands. A repository whose scaffold does not build, whose template tests fail or that the conformance check of AIFACTORY-US-362 reports as deviating is recorded by name and blocks the readiness proof; it is never waived.

Acceptance criteria

AC1 Given the recorded approval of the owner for each creation and the checklist of AIFACTORY-US-360, when AIFACTORY-TASK-054, AIFACTORY-TASK-061, AIFACTORY-TASK-064, AIFACTORY-TASK-067 and AIFACTORY-TASK-070 run, then ConnectSoft.AI.SoftwareFactory.ArtifactService, ConnectSoft.AI.SoftwareFactory.ContextBuilderService, ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService, ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService and ConnectSoft.AI.SoftwareFactory.VectorMemoryService exist, each first commit is the unchanged output of dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned template package, and each records the template version and the messaging service name of its service file under model/services/knowledge (ADR-0028 decision 1, D140).
AC2 Given the pinned API gateway template package, when AIFACTORY-TASK-466 runs, then ConnectSoft.AI.SoftwareFactory.KnowledgeHost exists, its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.KnowledgeHost --UseFactoryProfile true --GatewayRole Platform, it records the template version, and the template tests pass with the architecture test of the Platform role (ADR-0028 decision 2, model/services/knowledge/KnowledgeHost.yaml).
AC3 Given each of the six repositories, when its pipeline runs on the default branch, then it restores from the ConnectSoft feed alone, builds in Release, passes the template tests with complete reports and publishes the container image from the shared steps of AIFACTORY-US-361, and the conformance check of AIFACTORY-US-362 reports no deviation, so that the six rows of the repository list of AIFACTORY-US-1336 carry a green run (ADR-0028, D140).
Traces: services ArtifactService, ContextBuilderService, KnowledgeIngestionService, RepositoryIntelligenceService, VectorMemoryService, KnowledgeHost
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361, AIFACTORY-US-362, feature:component-base-template-factory-profile, feature:component-base-template-findings, feature:component-api-gateway-template, feature:contracts-package
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/services/knowledge/ArtifactService.yaml, model/services/knowledge/ContextBuilderService.yaml, model/services/knowledge/KnowledgeIngestionService.yaml, model/services/knowledge/RepositoryIntelligenceService.yaml, model/services/knowledge/VectorMemoryService.yaml, model/services/knowledge/KnowledgeHost.yaml, handoffs/2026-10-09-independent-review/decision-log.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-054 Create the repository ConnectSoft.AI.SoftwareFactory.ArtifactService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.ArtifactService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name artifact; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.ArtifactService
AIFACTORY-TASK-061 Create the repository ConnectSoft.AI.SoftwareFactory.ContextBuilderService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.ContextBuilderService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name context-builder; the repository records that template version; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.ContextBuilderService
AIFACTORY-TASK-064 Create the repository ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name knowledge-ingestion; the repository records that template version; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService
AIFACTORY-TASK-067 Create the repository ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService --UseFactoryProfile true from the pinned template package, whose version the repository records, with the messaging service name repository-intelligence; the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService
AIFACTORY-TASK-070 Create the repository ConnectSoft.AI.SoftwareFactory.VectorMemoryService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.VectorMemoryService --UseFactoryProfile true from the pinned template package, whose version the repository records, with the messaging service name vector-memory; the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.VectorMemoryService
AIFACTORY-TASK-466 Create the repository ConnectSoft.AI.SoftwareFactory.KnowledgeHost and scaffold it from the API gateway template with the Factory profile and the Platform gateway role implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.KnowledgeHost --UseFactoryProfile true --GatewayRole Platform from the pinned template package, whose version the repository records; the solution builds and the template tests, the architecture test of the Platform role included, pass in the repository pipeline, which publishes the container image; a deviation is corrected in the repository before the fronts file of AIFACTORY-TASK-467 is written. ConnectSoft.AI.SoftwareFactory.KnowledgeHost
AIFACTORY-TASK-6474 Verify the six knowledge repositories and their green pipeline runs verification The repository list of AIFACTORY-US-1336 holds ConnectSoft.AI.SoftwareFactory.ArtifactService, ConnectSoft.AI.SoftwareFactory.ContextBuilderService, ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService, ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService, ConnectSoft.AI.SoftwareFactory.VectorMemoryService and ConnectSoft.AI.SoftwareFactory.KnowledgeHost, each with the recorded approval of its creation, its template and template version, the identifier of one green pipeline run on its default branch that restored from the ConnectSoft feed alone, built in Release and passed the template tests (the architecture test of the Platform role for KnowledgeHost), and a conformance check with no deviation; the comparison of these rows with AIFACTORY-TASK-054, AIFACTORY-TASK-061, AIFACTORY-TASK-064, AIFACTORY-TASK-067, AIFACTORY-TASK-070 and AIFACTORY-TASK-466 proves AC1 to AC3 of AIFACTORY-US-1599, and python -I tools/docs_model check passes with the list in place. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1600: Repository conventions: the first-outcome repositories of model compute, tools and quality scoring are created and scaffolded in I0 by the checklist, each with a green template pipeline

enabling · persona operator As an operator, I want the repositories of ModelRouterService, ModelGatewayHost, McpServerRegistryService, ToolAdapterService, ToolExecutorHost and QualityScoreService created and scaffolded before increment I1 starts, so that the readiness demonstration of I0 finds these repositories built and tested in their own pipelines, and their I1 features start from a scaffold that is known to build.

Decision D140 moves the creation of every first-outcome repository into increment I0, so that the first demonstration of I0, which AIFACTORY-US-1336 proves, can pass in I0. This PBI holds the six repositories of the model compute plane, of the tools plane and of the quality scoring that the first outcome needs. The tasks keep the identifiers they had in their I1 features: AIFACTORY-TASK-047 creates ConnectSoft.AI.SoftwareFactory.ModelRouterService, AIFACTORY-TASK-073 ConnectSoft.AI.SoftwareFactory.McpServerRegistryService, AIFACTORY-TASK-076 ConnectSoft.AI.SoftwareFactory.ToolAdapterService and AIFACTORY-TASK-115 ConnectSoft.AI.SoftwareFactory.QualityScoreService, each with dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned base template package; AIFACTORY-TASK-044 creates the platform gateway ConnectSoft.AI.SoftwareFactory.ModelGatewayHost and AIFACTORY-TASK-083 the platform gateway ConnectSoft.AI.SoftwareFactory.ToolExecutorHost, each with dotnet new connectsoft-apigateway -n <name> --UseFactoryProfile true --GatewayRole Platform, whose template tests include the architecture test of the Platform role. Every repository is created by the steps of the checklist of AIFACTORY-US-360 only after the recorded approval of the owner for its creation, which stays an open row of the register of AIFACTORY-US-379 until the owner gives it. Its first commit is the unchanged scaffold output with the messaging service name of its service file where the service has one, the repository records the template version and the scaffold command, the branch policy is set, and the pipeline of AIFACTORY-US-361 builds it, runs the template tests and publishes the container image from the shared steps with the ConnectSoft feed as the only source. No Factory code is written here: the I1 features model-router-service, model-gateway-host, mcp-server-registry-service-thin, tool-adapter-service, tool-executor-host and quality-score-service-thin take each repository as it stands. A repository whose scaffold does not build, whose template tests fail or that the conformance check of AIFACTORY-US-362 reports as deviating is recorded by name and blocks the readiness proof; it is never waived.

Acceptance criteria

AC1 Given the recorded approval of the owner for each creation and the checklist of AIFACTORY-US-360, when AIFACTORY-TASK-047, AIFACTORY-TASK-073, AIFACTORY-TASK-076 and AIFACTORY-TASK-115 run, then ConnectSoft.AI.SoftwareFactory.ModelRouterService, ConnectSoft.AI.SoftwareFactory.McpServerRegistryService, ConnectSoft.AI.SoftwareFactory.ToolAdapterService and ConnectSoft.AI.SoftwareFactory.QualityScoreService exist, each first commit is the unchanged output of dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the pinned template package, and each records the template version and the messaging service name of its service file (ADR-0028 decision 1, model/services/model-compute/ModelRouterService.yaml, D140).
AC2 Given the pinned API gateway template package, when AIFACTORY-TASK-044 and AIFACTORY-TASK-083 run, then ConnectSoft.AI.SoftwareFactory.ModelGatewayHost and ConnectSoft.AI.SoftwareFactory.ToolExecutorHost exist, each first commit is the unchanged output of dotnet new connectsoft-apigateway -n <name> --UseFactoryProfile true --GatewayRole Platform, each records the template version, and the template tests pass with the architecture test of the Platform role (ADR-0028 decision 2, model/services/model-compute/ModelGatewayHost.yaml, model/services/tools-mcp/ToolExecutorHost.yaml).
AC3 Given each of the six repositories, when its pipeline runs on the default branch, then it restores from the ConnectSoft feed alone, builds in Release, passes the template tests with complete reports and publishes the container image from the shared steps of AIFACTORY-US-361, and the conformance check of AIFACTORY-US-362 reports no deviation, so that the six rows of the repository list of AIFACTORY-US-1336 carry a green run (ADR-0028, D140).
Traces: services ModelRouterService, ModelGatewayHost, McpServerRegistryService, ToolAdapterService, ToolExecutorHost, QualityScoreService
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361, AIFACTORY-US-362, feature:component-base-template-factory-profile, feature:component-base-template-findings, feature:component-api-gateway-template, feature:contracts-package
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/services/model-compute/ModelRouterService.yaml, model/services/model-compute/ModelGatewayHost.yaml, model/services/tools-mcp/McpServerRegistryService.yaml, model/services/tools-mcp/ToolAdapterService.yaml, model/services/tools-mcp/ToolExecutorHost.yaml, model/services/observability/QualityScoreService.yaml, handoffs/2026-10-09-independent-review/decision-log.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-047 Create the repository ConnectSoft.AI.SoftwareFactory.ModelRouterService and scaffold it from the base template with the Factory profile implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.ModelRouterService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name model-router; the repository records that template version and pins the contracts package and the AI library packages; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.ModelRouterService
AIFACTORY-TASK-044 Create the repository ConnectSoft.AI.SoftwareFactory.ModelGatewayHost and scaffold it from the API gateway template with the Factory profile and the Platform gateway role implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.ModelGatewayHost --UseFactoryProfile true --GatewayRole Platform from the pinned template package, whose version the repository records; the solution builds and the template tests, the architecture test of the Platform role included, pass in the repository pipeline, which publishes the container image; a deviation is corrected in the repository before the fronts file of AIFACTORY-TASK-045 is written. ConnectSoft.AI.SoftwareFactory.ModelGatewayHost
AIFACTORY-TASK-073 Create the repository ConnectSoft.AI.SoftwareFactory.McpServerRegistryService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists by the repository checklist of feature repository-and-pipeline-conventions, the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.McpServerRegistryService --UseFactoryProfile true from the pinned template package is committed with the messaging service name mcp-server-registry, the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.McpServerRegistryService
AIFACTORY-TASK-076 Create the repository ConnectSoft.AI.SoftwareFactory.ToolAdapterService and scaffold it from the ConnectSoft.BaseTemplate template with the Factory profile implementation The repository exists by the repository checklist of feature repository-and-pipeline-conventions, the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.ToolAdapterService --UseFactoryProfile true from the pinned template package is committed with the messaging service name tool-adapter, the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.ToolAdapterService
AIFACTORY-TASK-083 Create the repository ConnectSoft.AI.SoftwareFactory.ToolExecutorHost and scaffold it from the ConnectSoft.ApiGatewayTemplate template with the Factory profile and the Platform role implementation The repository exists by the repository checklist of feature repository-and-pipeline-conventions, the output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.ToolExecutorHost --UseFactoryProfile true --GatewayRole Platform from the pinned template package is committed, the solution builds and the template tests, the architecture test of the Platform role included, pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.ToolExecutorHost
AIFACTORY-TASK-115 Create the repository ConnectSoft.AI.SoftwareFactory.QualityScoreService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.QualityScoreService --UseFactoryProfile true from the pinned template package, whose version the repository records; the solution builds and the template tests pass in the repository pipeline, which publishes the container image. ConnectSoft.AI.SoftwareFactory.QualityScoreService
AIFACTORY-TASK-6475 Verify the six model compute, tools and quality repositories and their green pipeline runs verification The repository list of AIFACTORY-US-1336 holds ConnectSoft.AI.SoftwareFactory.ModelRouterService, ConnectSoft.AI.SoftwareFactory.ModelGatewayHost, ConnectSoft.AI.SoftwareFactory.McpServerRegistryService, ConnectSoft.AI.SoftwareFactory.ToolAdapterService, ConnectSoft.AI.SoftwareFactory.ToolExecutorHost and ConnectSoft.AI.SoftwareFactory.QualityScoreService, each with the recorded approval of its creation, its template and template version, the identifier of one green pipeline run on its default branch that restored from the ConnectSoft feed alone, built in Release and passed the template tests (the architecture test of the Platform role for the two gateways), and a conformance check with no deviation; the comparison of these rows with AIFACTORY-TASK-044, AIFACTORY-TASK-047, AIFACTORY-TASK-073, AIFACTORY-TASK-076, AIFACTORY-TASK-083 and AIFACTORY-TASK-115 proves AC1 to AC3 of AIFACTORY-US-1600, and python -I tools/docs_model check passes with the list in place. ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-1601: Repository conventions: the first-outcome repositories of the template library are created and scaffolded in I0 by the checklist, each with a green template pipeline

enabling · persona operator As an operator, I want the repositories of BlueprintService, GenerationRecipeService, TemplateRegistryService and TemplateCatalogHost created and scaffolded before increment I1 starts, so that the readiness demonstration of I0 finds the template library repositories built and tested in their own pipelines, and their I1 features start from a scaffold that is known to build.

Decision D140 moves the creation of every first-outcome repository into increment I0, so that the first demonstration of I0, which AIFACTORY-US-1336 proves, can pass in I0. This PBI holds the four repositories of the template library plane. The tasks keep the identifiers they had in their I1 features: AIFACTORY-TASK-118 creates ConnectSoft.AI.SoftwareFactory.BlueprintService, AIFACTORY-TASK-125 ConnectSoft.AI.SoftwareFactory.GenerationRecipeService and AIFACTORY-TASK-132 ConnectSoft.AI.SoftwareFactory.TemplateRegistryService, each with dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the base template package at the version the gate of AIFACTORY-US-230 published; AIFACTORY-TASK-509 creates the platform gateway ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost with dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost --UseFactoryProfile true --GatewayRole Platform, whose template tests include the architecture test of the Platform role. Every repository is created by the steps of the checklist of AIFACTORY-US-360 only after the recorded approval of the owner for its creation, which stays an open row of the register of AIFACTORY-US-379 until the owner gives it. Its first commit is the unchanged scaffold output with the messaging service name of its service file where the service has one, the repository records the template version and the scaffold command, the branch policy is set, and the pipeline of AIFACTORY-US-361 builds it, runs the template tests and publishes the container image from the shared steps with the ConnectSoft feed as the only source. No Factory code is written here: the I1 features blueprint-service, generation-recipe-service, template-registry-service and template-catalog-host take each repository as it stands. A repository whose scaffold does not build, whose template tests fail or that the conformance check of AIFACTORY-US-362 reports as deviating is recorded by name and blocks the readiness proof; it is never waived.

Acceptance criteria

AC1 Given the recorded approval of the owner for each creation and the checklist of AIFACTORY-US-360, when AIFACTORY-TASK-118, AIFACTORY-TASK-125 and AIFACTORY-TASK-132 run, then ConnectSoft.AI.SoftwareFactory.BlueprintService, ConnectSoft.AI.SoftwareFactory.GenerationRecipeService and ConnectSoft.AI.SoftwareFactory.TemplateRegistryService exist, each first commit is the unchanged output of dotnet new connectsoft-base -n <name> --UseFactoryProfile true from the template package the gate of AIFACTORY-US-230 published, and each records that version and the messaging service name of its service file under model/services/template-library (ADR-0028 decision 1, D140).
AC2 Given the pinned API gateway template package, when AIFACTORY-TASK-509 runs, then ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost exists, its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost --UseFactoryProfile true --GatewayRole Platform, it records the template version, and the template tests pass with the architecture test of the Platform role (ADR-0028 decision 2, model/services/template-library/TemplateCatalogHost.yaml).
AC3 Given each of the four repositories, when its pipeline runs on the default branch, then it restores from the ConnectSoft feed alone, builds in Release, passes the template tests with complete reports and publishes the container image from the shared steps of AIFACTORY-US-361, and the conformance check of AIFACTORY-US-362 reports no deviation, so that the four rows of the repository list of AIFACTORY-US-1336 carry a green run (ADR-0028, D140).
Traces: services BlueprintService, GenerationRecipeService, TemplateRegistryService, TemplateCatalogHost
Traces: adrs ADR-0028
Depends on AIFACTORY-US-360, AIFACTORY-US-361, AIFACTORY-US-362, feature:component-base-template-factory-profile, feature:component-base-template-findings, feature:component-api-gateway-template, feature:contracts-package
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/services/template-library/BlueprintService.yaml, model/services/template-library/GenerationRecipeService.yaml, model/services/template-library/TemplateRegistryService.yaml, model/services/template-library/TemplateCatalogHost.yaml, handoffs/2026-10-09-independent-review/decision-log.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-118 Create the repository ConnectSoft.AI.SoftwareFactory.BlueprintService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.BlueprintService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name blueprint; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.BlueprintService
AIFACTORY-TASK-125 Create the repository ConnectSoft.AI.SoftwareFactory.GenerationRecipeService and scaffold it from the base template with the Factory profile implementation The repository exists, created by the steps of the repository checklist; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.GenerationRecipeService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name generation-recipe; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.GenerationRecipeService
AIFACTORY-TASK-132 Create the repository ConnectSoft.AI.SoftwareFactory.TemplateRegistryService and scaffold it from the base template with the Factory profile implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist; the output of dotnet new connectsoft-base -n ConnectSoft.AI.SoftwareFactory.TemplateRegistryService --UseFactoryProfile true, generated from the template package at the version the gate of AIFACTORY-US-230 published, is committed unchanged with the messaging service name template-registry; the repository records that template version and pins the contracts package; the solution builds and the generated tests pass in the repository pipeline, which publishes a container image. ConnectSoft.AI.SoftwareFactory.TemplateRegistryService
AIFACTORY-TASK-509 Create the repository ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost and scaffold it from the API gateway template with the Factory profile and the Platform gateway role implementation The repository exists after the recorded approval of the owner, created by the steps of the repository checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-apigateway -n ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost --UseFactoryProfile true --GatewayRole Platform from the pinned template package, whose version the repository records; the solution builds and the template tests, the architecture test of the Platform role included, pass in the repository pipeline, which publishes the container image; a deviation is corrected in the repository before the fronts file of AIFACTORY-TASK-510 is written. ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost
AIFACTORY-TASK-6476 Verify the four template library repositories and their green pipeline runs verification The repository list of AIFACTORY-US-1336 holds ConnectSoft.AI.SoftwareFactory.BlueprintService, ConnectSoft.AI.SoftwareFactory.GenerationRecipeService, ConnectSoft.AI.SoftwareFactory.TemplateRegistryService and ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost, each with the recorded approval of its creation, its template and template version, the identifier of one green pipeline run on its default branch that restored from the ConnectSoft feed alone, built in Release and passed the template tests (the architecture test of the Platform role for TemplateCatalogHost), and a conformance check with no deviation; the comparison of these rows with AIFACTORY-TASK-118, AIFACTORY-TASK-125, AIFACTORY-TASK-132 and AIFACTORY-TASK-509 proves AC1 to AC3 of AIFACTORY-US-1601, and python -I tools/docs_model check passes with the list in place. ConnectSoft.AI.SoftwareFactory.Documentation