Skip to content

Increment I1: Generate a microservice

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. A vision submitted through the API or the command-line client ends as an approved change proposal that contains a generated, built and tested microservice (decision D65); the run is audited from its first command and stops at its budget cap (decision D80).

Depends on: I0 · Elaboration: stories and tasks · Azure DevOps CSV of this increment

Demonstrations

  • A person submits a vision; the chain of six workflows runs without a manual start between them.
  • A person approves the recipe and, later, the exact change set.
  • The change proposal is open in the system of record with provenance and validation results.
  • Every command, decision, approval and tool effect of the run is in the audit trail and the hash chain verifies.
  • A run with a budget below its need stops at the cap, and the usage of a finished run reconciles with its receipts.

Services delivered in this increment

Service Role Depth Scope in this increment Repository
AgentRegistryService service thin Loads the seeded Draft releases of the six chain definitions and their nine agents by alias; no publication gate and no evaluation evidence. ConnectSoft.AI.SoftwareFactory.AgentRegistryService
ControlPlaneApi platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.ControlPlaneApi
EnvironmentService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.EnvironmentService
ProjectService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.ProjectService
RunControlService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.RunControlService
CostUsageService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.CostUsageService
AgentRuntimeService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.AgentRuntimeService
WorkflowEngineService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.WorkflowEngineService
ModelGatewayHost platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.ModelGatewayHost
ModelRouterService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.ModelRouterService
ArtifactService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.ArtifactService
ContextBuilderService service thin Passes the pinned artifacts of a step through as its context package; no budget, ranking or provenance. ConnectSoft.AI.SoftwareFactory.ContextBuilderService
KnowledgeIngestionService service thin No ingestion; the calls the retrieval path requires answer empty. ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService
RepositoryIntelligenceService service thin The seven read tools run inside the sandbox of the tool executor, where the workspace of the run is mounted, and work over that workspace only (D125); no repository index, and no deployed service reads a workspace before the complete delivery. ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService
VectorMemoryService service thin The knowledge-search and graph-query tools answer with an empty, well-formed result; no index exists. ConnectSoft.AI.SoftwareFactory.VectorMemoryService
KnowledgeHost platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.KnowledgeHost
McpServerRegistryService service thin A static registry without MCP servers; every tool of the chain is native. ConnectSoft.AI.SoftwareFactory.McpServerRegistryService
ToolAdapterService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.ToolAdapterService
ToolExecutorHost platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.ToolExecutorHost
ConnectorRegistryService service thin The Azure DevOps connector for template feeds and for opening the change proposal. ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService
IntegrationService service thin One Azure DevOps connection per project with its credential reference. ConnectSoft.AI.SoftwareFactory.IntegrationService
IntegrationHost platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.IntegrationHost
PipelineExecutionService service thin The ChangeProposal aggregate and the path that opens a proposal in the system of record; no pipeline runs. ConnectSoft.AI.SoftwareFactory.PipelineExecutionService
ExecutionCapacityService service thin Sandbox and workspace leases from one worker pool; no quotas. ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService
PolicyEngineService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.PolicyEngineService
SecretBrokerService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.SecretBrokerService
AuditService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.AuditService
GovernanceHost platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.GovernanceHost
QualityScoreService service thin Accepts evaluation and outcome events and stores them; no gate and no scoring. ConnectSoft.AI.SoftwareFactory.QualityScoreService
BlueprintService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.BlueprintService
GenerationRecipeService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.GenerationRecipeService
TemplateRegistryService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.TemplateRegistryService
TemplateCatalogHost platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.TemplateCatalogHost

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-046 ExecutionCapacityService: thin delivery for the first outcome IaCProvisioningService static I2
AIFACTORY-FEAT-046 ExecutionCapacityService: thin delivery for the first outcome FactoryCommercialService static I7
AIFACTORY-FEAT-046 ExecutionCapacityService: thin delivery for the first outcome RetentionResidencyService static I4
AIFACTORY-FEAT-065 QualityScoreService: thin delivery for the first outcome FeedbackService contract-stub I4

Before development

Template and library work of this increment, done first: these features change the templates and shared libraries the Factory scaffolds from and builds on, and none delivers a Factory service. Every task under them carries the tag phase:before-development.

Feature Repositories State Tasks
AIFACTORY-FEAT-160 Base template: the symbol catalog and determinism the generation recipe needs ConnectSoft.BaseTemplate elaborated 18
AIFACTORY-FEAT-176 Audit library: the Factory audit evidence record and its sink ConnectSoft.Extensions.AuditNet elaborated 15
AIFACTORY-FEAT-177 Compliance library: the Factory data classes and redaction profiles ConnectSoft.Extensions.Compliance elaborated 14
AIFACTORY-FEAT-180 API library template: OpenAPI generation, scope and propagation before the gateway clients ConnectSoft.ApiLibraryTemplate elaborated 17
AIFACTORY-FEAT-181 Documentation template: generated sections, a stale check and a packable template for Factory repositories ConnectSoft.AzurePipelines
ConnectSoft.DocumentationTemplate
elaborated 18
AIFACTORY-FEAT-184 AI skills library template: skill packages the registry publishes and the agent host loads ConnectSoft.AISkillsLibraryTemplate elaborated 20

Features by epic

Control Plane (PF-01)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-001 AgentRegistryService: thin delivery for the first outcome
AgentRegistryService is the service of bounded context BC-04 (Asset Publication). Publishes immutable releases of agents, skills, tools, workflows, policies and model profiles with their full dependency closure, hashes and evaluation evidence; serves release resolution to Run Control and release loading to the runtime (BC-04). In this increment it is delivered thin: Loads the seeded Draft releases of the six chain definitions and their nine agents by alias; no publication gate and no evaluation evidence. Its own repository is ConnectSoft.AI.SoftwareFactory.AgentRegistryService.
development elaborated backend-developer 4 10
AIFACTORY-FEAT-002 ControlPlaneApi: gateway delivery
ControlPlaneApi is the platform API gateway of bounded context BC-01 (Project & Environment). The API gateway of the Control Plane platform (ADR-0028): routes public REST and internal gRPC calls to the 7 services it fronts, validates tokens and scopes, and owns no business state. Its own repository is ConnectSoft.AI.SoftwareFactory.ControlPlaneApi.
development elaborated backend-developer 6 16
AIFACTORY-FEAT-004 EnvironmentService: complete delivery
EnvironmentService is the service of bounded context BC-01 (Project & Environment). Owns the environments of a project (sandbox, dev, test, staging, production classes), their policy class, connections and the desired deployment references that Provisioning (BC-25) reconciles (BC-01). Its own repository is ConnectSoft.AI.SoftwareFactory.EnvironmentService.
development elaborated backend-developer 6 20
AIFACTORY-FEAT-005 ProjectService: complete delivery
ProjectService is the service of bounded context BC-01 (Project & Environment). Owns projects (workspaces) inside a tenant, their memberships and role assignments, source scope and project-level policy overrides; the scope ids every run carries (BC-01). Its own repository is ConnectSoft.AI.SoftwareFactory.ProjectService.
development elaborated backend-developer 13 43
AIFACTORY-FEAT-006 RunControlService: complete delivery
RunControlService is the service of bounded context BC-03 (Run Control). Single authority for run, step, attempt and lease state; commits every transition and its outbox record in one transaction (BC-03). Its own repository is ConnectSoft.AI.SoftwareFactory.RunControlService.
development elaborated backend-developer 20 89
AIFACTORY-FEAT-008 CostUsageService: complete delivery
CostUsageService is the service of bounded context BC-05 (Usage Accounting). Owns budgets, reservations, usage records, pricing revisions and reconciliation; reserves before dispatch, settles observed usage, keeps unknown usage uncertain and feeds meters, budgets and billing (BC-05). It is delivered complete in the first outcome by owner decision (D80), so that every run reserves before it spends and stops at its budget cap. Its own repository is ConnectSoft.AI.SoftwareFactory.CostUsageService.
development elaborated backend-developer 14 54

Agent Mesh (PF-02)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-011 AgentRuntimeService: complete delivery
AgentRuntimeService is the service of bounded context BC-06 (Execution). Executes one attempt of one step under a lease from Run Control — loads the pinned release, assembles context, runs the plan-call-observe-verify loop on the Microsoft Agent Framework adapter, checkpoints before every gated call, asks for human decisions, delegates sub-agents and reports exactly one outcome (BC-06). Its own repository is ConnectSoft.AI.SoftwareFactory.AgentRuntimeService.
development elaborated backend-developer 13 45
AIFACTORY-FEAT-012 WorkflowEngineService: complete delivery
WorkflowEngineService is the service of bounded context BC-38 (Workflow Definitions & Engine). Loads Published workflow definitions (DAGs of agent, tool, human, condition, timer, sub-workflow and compensation steps) and drives a workflow run — computing ready steps for Run Control to dispatch, evaluating conditions on recorded outputs, firing durable timers and running compensation — without ever owning run authority (BC-38). Its own repository is ConnectSoft.AI.SoftwareFactory.WorkflowEngineService.
development elaborated backend-developer 16 64

Model & Compute Platform (PF-03)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-014 ModelGatewayHost: gateway delivery
ModelGatewayHost is the platform API gateway of bounded context BC-07 (Model Access). The API gateway of the Model & Compute platform (ADR-0028): routes public REST and internal gRPC calls to the 2 services it fronts, validates tokens and scopes, and owns no business state. ModelRouterService behind it stays the only caller of model providers (GW-04). Its own repository is ConnectSoft.AI.SoftwareFactory.ModelGatewayHost.
development elaborated backend-developer 7 21
AIFACTORY-FEAT-015 ModelRouterService: complete delivery
ModelRouterService is the service of bounded context BC-07 (Model Access). The model gateway pipeline — resolves a pinned model profile into a route plan from capability evidence, privacy class, policy, region, cost and availability; invokes the provider adapter with streaming, structured outputs and tool calls; and records an invocation receipt with the actual deployment and the usage status (BC-07). Its own repository is ConnectSoft.AI.SoftwareFactory.ModelRouterService.
development elaborated backend-developer 16 53

Knowledge Platform (PF-04)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-017 ArtifactService: complete delivery
ArtifactService is the service of bounded context BC-12 (Artifacts & Lineage). The one authoritative writer of artifacts — immutable, hash-addressed content with metadata, classification, access scope, producing run and attempt, version chains and lineage to sources and inputs; previews and version history are projections (BC-12). Its own repository is ConnectSoft.AI.SoftwareFactory.ArtifactService.
development elaborated backend-developer 12 43
AIFACTORY-FEAT-018 ContextBuilderService: thin delivery for the first outcome
ContextBuilderService is the service of bounded context BC-09 (Context Assembly). The context engineering plane — plans what a task needs (mandatory instructions, task, conversation state, repository state, knowledge, graph neighbours, episodic memory, diff, tool results), retrieves and expands candidates, ranks, deduplicates, compresses and budgets tokens, and records an immutable context snapshot that says what was used and why (BC-09). In this increment it is delivered thin: Passes the pinned artifacts of a step through as its context package; no budget, ranking or provenance. Its own repository is ConnectSoft.AI.SoftwareFactory.ContextBuilderService.
development elaborated backend-developer 3 7
AIFACTORY-FEAT-019 KnowledgeIngestionService: thin delivery for the first outcome
KnowledgeIngestionService is the service of bounded context BC-10 (Sources & Ingestion). Owns knowledge sources and collections, immutable source snapshots, the ingestion pipeline (parse, normalize, metadata, chunk, publish to indexes with ACL propagation), incremental sync, staleness and deletion lineage; code, documentation, library and template sources are source types, not services (BC-10). In this increment it is delivered thin: No ingestion; the calls the retrieval path requires answer empty. Its own repository is ConnectSoft.AI.SoftwareFactory.KnowledgeIngestionService.
development elaborated backend-developer 3 7
AIFACTORY-FEAT-020 RepositoryIntelligenceService: thin delivery for the first outcome
RepositoryIntelligenceService is the service of bounded context BC-39 (Repository Intelligence). Repository indexes per revision — file tree, symbols, types, dependencies, calls, references, Git history, ownership, build and test relationships — built from repository snapshots and exposed as read tools so that large repositories are never dumped into model context (BC-39, original design §33). In this increment it is delivered thin: The seven read tools run inside the sandbox of the tool executor, where the workspace of the run is mounted, and work over that workspace only (D125); no repository index, and no deployed service reads a workspace before the complete delivery. Its own repository is ConnectSoft.AI.SoftwareFactory.RepositoryIntelligenceService.
development elaborated backend-developer 5 13
AIFACTORY-FEAT-021 VectorMemoryService: thin delivery for the first outcome
VectorMemoryService is the service of bounded context BC-11 (Retrieval & Indexes). The retrieval module (historical name kept from the June-2026 catalog) — vector, full-text, symbol, metadata, graph-projection and temporal retrieval combined under trusted scope with ACL enforced before top-k, citations with source version and index revision, embedding and index revisions pinned to profiles, and rebuildable derived indexes (BC-11, ADR-0013). In this increment it is delivered thin: The knowledge-search and graph-query tools answer with an empty, well-formed result; no index exists. Its own repository is ConnectSoft.AI.SoftwareFactory.VectorMemoryService.
development elaborated backend-developer 3 8
AIFACTORY-FEAT-022 KnowledgeHost: gateway delivery
KnowledgeHost is the platform API gateway of bounded context BC-11 (Retrieval & Indexes). The API gateway of the Knowledge platform (ADR-0028): routes public REST and internal gRPC calls to the 6 services it fronts, validates tokens and scopes, and owns no business state. Its own repository is ConnectSoft.AI.SoftwareFactory.KnowledgeHost.
development elaborated backend-developer 6 17

Tools & MCP Platform (PF-05)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-028 McpServerRegistryService: thin delivery for the first outcome
McpServerRegistryService is the service of bounded context BC-08 (Tool Execution). Registry of MCP servers the Factory consumes or exposes — transport, endpoint or connection, authentication (on by default), governance policy, discovered tools, resources and prompts bound to tool descriptors and knowledge sources, handshake health and the ModelOps-like lifecycle from registration to retirement (BC-08, ADR-0022). In this increment it is delivered thin: A static registry without MCP servers; every tool of the chain is native. Its own repository is ConnectSoft.AI.SoftwareFactory.McpServerRegistryService.
development elaborated backend-developer 3 9
AIFACTORY-FEAT-029 ToolAdapterService: complete delivery
ToolAdapterService is the service of bounded context BC-08 (Tool Execution). The one path for every tool call (GW-05): descriptor validation, permission and policy, class raised by the environment, approval binding for gated classes, brokered credentials and sandbox, execution of native, MCP or shell tools, sanitized results, receipts and audit; unconfirmed effects settle as Uncertain (BC-08). Its own repository is ConnectSoft.AI.SoftwareFactory.ToolAdapterService.
development elaborated backend-developer 14 45
AIFACTORY-FEAT-030 ToolExecutorHost: gateway delivery
ToolExecutorHost is the platform API gateway of bounded context BC-08 (Tool Execution). The API gateway of the Tools & MCP platform (ADR-0028): routes public REST and internal gRPC calls to the 2 services it fronts, validates tokens and scopes, and owns no business state. ToolAdapterService behind it stays the only executor of tools (GW-05). Its own repository is ConnectSoft.AI.SoftwareFactory.ToolExecutorHost.
development elaborated backend-developer 8 23

Integration Platform (PF-06)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-032 ConnectorRegistryService: thin delivery for the first outcome
ConnectorRegistryService is the service of bounded context BC-17 (Connectors & Webhooks). Connector descriptors (capability interfaces, retry and rate-limit profiles, webhook schemes, configuration forms) with provider certification, subscriptions to inbound events, verified inbound deliveries and outbound deliveries with receipts; first-party clients (Azure DevOps, GitHub, Deputy, Braze, Bill, Twilio, Israel019, ACS, GA, Meta) are adapters behind descriptors (BC-17). In this increment it is delivered thin: The Azure DevOps connector for template feeds and for opening the change proposal. Its own repository is ConnectSoft.AI.SoftwareFactory.ConnectorRegistryService.
development elaborated backend-developer 4 14
AIFACTORY-FEAT-033 IntegrationService: thin delivery for the first outcome
IntegrationService is the service of bounded context BC-16 (Connections). Tenant-scoped connections to external systems — provider, endpoint policy, credential references (never values), grants that say which projects, agents and tools may use a connection, rotation metadata and health — with every use brokered as a short-lived credential by the Secret Broker (BC-16). In this increment it is delivered thin: One Azure DevOps connection per project with its credential reference. Its own repository is ConnectSoft.AI.SoftwareFactory.IntegrationService.
development elaborated backend-developer 6 18
AIFACTORY-FEAT-034 IntegrationHost: gateway delivery
IntegrationHost is the platform API gateway of bounded context BC-16 (Connections). The API gateway of the Integration platform (ADR-0028): routes public REST and internal gRPC calls to the 2 services it fronts, validates tokens and scopes, and owns no business state. Its own repository is ConnectSoft.AI.SoftwareFactory.IntegrationHost.
development elaborated backend-developer 6 17

DevOps / GitOps (PF-08)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-041 PipelineExecutionService: thin delivery for the first outcome
PipelineExecutionService 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). In this increment it is delivered thin: The ChangeProposal aggregate and the path that opens a proposal in the system of record; no pipeline runs. Its own repository is ConnectSoft.AI.SoftwareFactory.PipelineExecutionService.
development elaborated backend-developer 4 9

Runtime Cloud (PF-09)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-046 ExecutionCapacityService: thin delivery for the first outcome
ExecutionCapacityService 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). In this increment it is delivered thin: Sandbox and workspace leases from one worker pool; no quotas. Its own repository is ConnectSoft.AI.SoftwareFactory.ExecutionCapacityService.
development elaborated backend-developer 6 17

Governance (PF-12)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-060 PolicyEngineService: complete delivery
PolicyEngineService is the service of bounded context BC-18 (Policy). Central policy — Published policy bundles per scope (platform, tenant, project, where a project may only tighten) that answer who may run which agent with which models against which data with which tools in which environment under which budget, and immutable recorded decisions with effects allow, deny, require-approval or prohibited and obligations (BC-18, original design §43). Its own repository is ConnectSoft.AI.SoftwareFactory.PolicyEngineService.
development elaborated backend-developer 8 30
AIFACTORY-FEAT-061 SecretBrokerService: complete delivery
SecretBrokerService is the service of bounded context BC-40 (Secret Broker). Short-lived, scoped credential issuance against secret references — agents, tools, sandboxes, the model gateway and source connectors request a capability, policy validates, the broker obtains the credential from Key Vault or a token exchange, injects it with an expiry and records the issuance; raw long-lived secrets never reach prompts, workers or sandboxes (BC-40, original design §46). Its own repository is ConnectSoft.AI.SoftwareFactory.SecretBrokerService.
development elaborated backend-developer 11 31
AIFACTORY-FEAT-064 AuditService: complete delivery
AuditService is the service of bounded context BC-19 (Audit). Append-only audit evidence with a hash chain in the immutable store for every command, decision, approval, publication, credential issuance and effect; the data classification registry with retention and redaction rules that other services obey; findings and exports for tenants and auditors (BC-19, audit-evidence-v1, D31). It is delivered complete in the first outcome by owner decision (D80), so that every run is audited from its first command. Its own repository is ConnectSoft.AI.SoftwareFactory.AuditService.
development elaborated backend-developer 12 39
AIFACTORY-FEAT-062 GovernanceHost: gateway delivery
GovernanceHost is the platform API gateway of bounded context BC-18 (Policy). The API gateway of the Governance platform (ADR-0028): routes public REST and internal gRPC calls to the 4 services it fronts, validates tokens and scopes, and owns no business state. Its own repository is ConnectSoft.AI.SoftwareFactory.GovernanceHost.
development elaborated backend-developer 6 17

Observability (PF-13)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-065 QualityScoreService: thin delivery for the first outcome
QualityScoreService is the service of bounded context BC-22 (Evaluation & Learning). Evaluation as a core capability: suites per target (models, agents, skills, tools, workflows, context and memory strategies, policies) with the quality-gate metrics, evaluation runs over datasets of historical tasks, verdicts with baseline comparison, waivers, drift monitoring and the evidence records publication reads (BC-22, D32, original design §47–49). In this increment it is delivered thin: Accepts evaluation and outcome events and stores them; no gate and no scoring. Its own repository is ConnectSoft.AI.SoftwareFactory.QualityScoreService.
development elaborated backend-developer 4 11

Template & Library (PF-15)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-082 BlueprintService: complete delivery
BlueprintService is the service of bounded context BC-02 (Blueprint). Blueprint versions as typed descriptor documents validated against their JSON Schemas and rule sets, with derived context maps and domain models, validation reports with rule ids, and submission of a validated blueprint to Asset Publication (BC-02; parser, validator, context-map and domain-model rows merged). Its own repository is ConnectSoft.AI.SoftwareFactory.BlueprintService.
development elaborated backend-developer 9 31
AIFACTORY-FEAT-083 GenerationRecipeService: complete delivery
GenerationRecipeService is the service of bounded context BC-15 (Generation Recipe). A generation recipe binds a Published blueprint version to Published template and library versions with a module plan and parameters, validated against manifests, switches and the compatibility matrix, and records the provenance of every generated output down to the commit; the scaffold commitment stays Q-22 (BC-15; template validation and pipeline generation rows merged). Its own repository is ConnectSoft.AI.SoftwareFactory.GenerationRecipeService.
development elaborated backend-developer 11 35
AIFACTORY-FEAT-084 TemplateRegistryService: complete delivery
TemplateRegistryService is the service of bounded context BC-14 (Template Catalog). One catalog module with pinned manifests: template versions read from the template repositories, library versions read from the feeds, API client catalog, dependency analysis and the compatibility matrix of templates, libraries, runtimes, editions and topologies with evidence (BC-14; eight June-2026 rows merged). Its own repository is ConnectSoft.AI.SoftwareFactory.TemplateRegistryService.
development elaborated backend-developer 9 32
AIFACTORY-FEAT-085 TemplateCatalogHost: gateway delivery
TemplateCatalogHost is the platform API gateway of bounded context BC-14 (Template Catalog). The API gateway of the Template & Library 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.TemplateCatalogHost.
development elaborated backend-developer 6 16

Engineering readiness

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-187 Commands of the command-line client against the control plane gateway
The command-line client of the first outcome gets its commands once the services they call exist: submit a vision, follow a run, approve a recipe and approve a change proposal run against the control plane gateway through the pinned typed client, with the user token of the signed-in member. The repository, the skeleton and the sign-in of the client are delivered in I0 by the feature command-line-client (owner decision D117).
development elaborated backend-developer 3 10
AIFACTORY-FEAT-178 Typed client libraries for the Factory gateways from the API library template
Every Factory service, the command-line client and the agent host call the control-plane, model and tool gateways; the Factory would otherwise hand-write those clients in each repository. The API library template (connectsoft-api-library) scaffolds a typed HTTP client library with the house conventions; once it carries the Factory's scope headers, workload-token acquisition and OpenAPI generation (FEAT-180), three client packages are generated from the gateways' OpenAPI documents, versioned with the contracts package and consumed by the CLI and the agent host switches. Component: API library template (extend).
development elaborated backend-developer 5 16

Ecosystem component extensions

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-160 Base template: the symbol catalog and determinism the generation recipe needs
The Factory generates products from the base template (D95): a Module Blueprint names the template switches of each module and the generation recipe turns them into a scaffold (workflow definitions module-blueprints and generate-product). The recipe needs a stable, versioned catalog of the symbols of the template with their allowed values and defaults, a generation whose output is the same for the same inputs (no generated ports, years or build numbers that differ between runs), a post-action that reports success by exit code, and a product tenant profile for a generated SaaS module. Component: BaseTemplate (extend).
before development elaborated backend-developer 5 18
AIFACTORY-FEAT-176 Audit library: the Factory audit evidence record and its sink
Eleven Factory services depend on the Audit.NET integration library for audit evidence, and ADR-0019 keeps that evidence seven years, redacted and immutable. The library records generic audit events; the Factory needs the record shape of audit-evidence.schema.json (scope, run, step, the kind of actor, an evidence reference), generated from the contracts package rather than typed in each service, and a sink that carries the records to the Audit service under the accepted envelope with a durable fallback. Component: Audit.NET integration (extend).
before development elaborated backend-developer 4 15
AIFACTORY-FEAT-177 Compliance library: the Factory data classes and redaction profiles
ADR-0019 fixes four classification classes, pii and classification markers on model fields, redaction in every projection and notification, and no raw prompt, response or tool-output logging. The Compliance library (classification, redaction; D31) carries the mechanism but not the Factory's data classes: prompts, completions, tool outputs, secret references, customer source code and tenant personal data. The library gains those classes and the redaction profiles the telemetry, audit and artifact projections apply, so that redaction is one implementation rather than one per service. Component: Compliance (extend).
before development elaborated backend-developer 4 14
AIFACTORY-FEAT-180 API library template: OpenAPI generation, scope and propagation before the gateway clients
The typed clients of the three Factory gateways (FEAT-178) are scaffolded from the API library template, which ships a hand-written typed HttpClient with Polly resilience, five authentication layouts, optional metrics and service discovery, WireMock tests and scaffold tests over the authentication variants. Its maintainer checklist (Docs/Template TODO.md) leaves open exactly what the Factory needs first: client generation from an OpenAPI document, header propagation, instrumentation, and JWT and API key layouts listed as open while the authentication page describes them through the OAuth2 library; the roadmap names multi-tenant configuration as a long-term goal. The Factory adds its scope headers and workload-token acquisition, and the template gains a generated-solution gate across its layouts. Component: API library template (extend).
before development elaborated backend-developer 5 17
AIFACTORY-FEAT-181 Documentation template: generated sections, a stale check and a packable template for Factory repositories
Every Factory repository publishes a documentation site, and the Documentation site module of a generated product is scaffolded from the documentation template (connectsoft-documentation). The template is a MkDocs Material site with four parameters (title, description, repository URL, build definition), log4brains ADRs, the panzoom, exclude and search plugins and an Azure documentation pipeline; the template inventory records it as empty because it has no project to pack. It knows nothing of the distinction the documentation blueprint draws between generated and hand-written sections (blueprint-documentation.schema.json), has no check that a generated page is current, and no manifest or symbol catalog. The pattern this repository's own generator follows (model, generated pages written only when changed, a check that fails on a stale page, a strict build) becomes the template's. Component: Documentation template (extend).
before development elaborated backend-developer 5 18
AIFACTORY-FEAT-184 AI skills library template: skill packages the registry publishes and the agent host loads
A skill the Factory publishes as an asset (AssetKind Skill in AgentRegistryService, SkillManifest in asset-manifests.schema.json) may be implemented as a compiled package of AIFunctions; the AI skills library template (connectsoft-aiskills-library) scaffolds such a package on the Microsoft Agent Framework with an orchestrator function and supporting functions, immutable request and result records, typed error codes, redaction through Microsoft.Extensions.Compliance and ConnectSoft.Extensions.Compliance, an embeddings pipeline on Microsoft.Extensions.VectorData, an MCP tool wrapper and a Microsoft Learn MCP client, with contract, serialization, DI and telemetry tests. Its pages are out of step with its code: the Features page is the library template''s copied (UseDI and UseTracing where the symbols are useDI and no tracing switch exists), the versioning page names Semantic Kernel and .NET 8 and 9 while the code is on the Agent Framework (ADR-0002) and net10, and a Framework choice and a targetFrameworks string coexist. For the Factory the package must carry its SkillManifest, expose its functions as governed tools under the caller''s scope, redact and measure on the Factory conventions, and build across its parameters before the package publishes. Generating skill packages from skill definitions belongs to the Factory assets epic once the chain runs. Component: AI skills library template (extend).
before development elaborated backend-developer 6 20

Factory assets: workflow definitions, agents and skills

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-107 Workflow definition: Vision to blueprint
The workflow definition vision-to-blueprint as a published asset: Runs the Vision Architect Agent from a prompt and constraints to a validated Vision Blueprint with its artifacts, clarifying assumptions first and revising on validation findings. It has 6 steps, names the agents vision-architect and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development elaborated solution-architect 5 18
AIFACTORY-FEAT-108 Workflow definition: Architecture decomposition
The workflow definition architecture-decomposition as a published asset: Decomposes a validated Vision Blueprint into bounded contexts and modules with their domain models, producing the Service Blueprint from which BlueprintService derives the context map. It has 6 steps, names the agents domain-modeler, enterprise-architect and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development elaborated solution-architect 5 14
AIFACTORY-FEAT-109 Workflow definition: Module blueprints
The workflow definition module-blueprints as a published asset: Produces one Module Blueprint per context of a derived context map: the clean-architecture layout, template switches and adapters each module will be scaffolded with. It has 6 steps, names the agents solution-architect and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development elaborated solution-architect 5 15
AIFACTORY-FEAT-110 Workflow definition: Application design
The workflow definition application-design as a published asset: Produces the application design of every module from its validated Module Blueprint: use cases and handlers, input and output ports, adapters and the telemetry span plan, stored as a typed artifact the generation recipe pins. It has 4 steps, names the agents application-architect and the tools none, and is executed by WorkflowEngineService under Run Control.
development elaborated solution-architect 4 12
AIFACTORY-FEAT-111 Workflow definition: Database blueprint
The workflow definition database-blueprint as a published asset: Builds the Database Blueprint from the Service Blueprint and the derived domain model: stores per context, tables with tenant and classification conventions, retention and migration policy; validated against the DSL. A product without persistence yields a blueprint with no stores. It has 5 steps, names the agents database-engineer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development elaborated solution-architect 4 12
AIFACTORY-FEAT-112 Workflow definition: Generate a product
The workflow definition generate-product as a published asset: Executes an approved generation recipe: reads the recipe and the design inputs it pins, scaffolds every module from its template in the sandbox, fills the backend and, when the module plan has such modules, the frontend and the database, validates by build and test, records the outputs with provenance and proposes the change set under approval. It has 12 steps, names the agents backend-developer, database-engineer, frontend-developer, microservice-generator and the tools build-and-test, get-approved-recipe, propose-change-set, and is executed by WorkflowEngineService under Run Control.
development elaborated solution-architect 9 29

Outcome verification

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-139 Demonstrate I1: Generate a microservice
The outcome of increment I1 is demonstrated end to end and the evidence is recorded: A vision submitted through the API or the command-line client ends as an approved change proposal that contains a generated, built and tested microservice (decision D65); the run is audited from its first command and stops at its budget cap (decision D80). Demonstrations: A person submits a vision; the chain of six workflows runs without a manual start between them. A person approves the recipe and, later, the exact change set. The change proposal is open in the system of record with provenance and validation results. Every command, decision, approval and tool effect of the run is in the audit trail and the hash chain verifies. A run with a budget below its need stops at the cap, and the usage of a finished run reconciles with its receipts.
development elaborated qa-engineer 4 12

Requirements this increment touches

FR-01, FR-02, FR-03, FR-04, FR-05, FR-06, FR-07, FR-08, FR-09, FR-10, FR-11, FUX-01, FUX-02, FUX-03, FUX-04, FUX-05, FUX-06, FUX-07, FUX-08, FUX-09, FUX-10, FUX-11, NFR-01, NFR-02, NFR-03, NFR-04, NFR-05, NFR-06, NFR-07, NFR-08, NFR-09, NFR-10, NFR-11, NFR-12, NFR-13, NFR-16, NFR-17, NFR-18, XL-01, XL-02, XL-03, XL-04, XL-05, XL-06, XL-07, XL-08, XL-09, XL-10, XL-12, XL-13, XL-14, XL-15, XL-16