Skip to content

AIFACTORY-FEAT-092: Local development environment for a Factory 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 devops-engineer · Build order 47 of 185 (Factory code)

A developer or a coding agent can run any first-outcome service locally with its store, messaging and identity, from documented steps, without touching a shared database.

Delivers —
Stubs —
Realizes —
Requirements —
Depends on —
Sources docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md

AIFACTORY-US-372: Local environment: a developer or a coding agent starts one Factory service locally with its own store, the Orleans messaging profile, a local authorization server and model access by secret reference

enabling · persona operator As an operator, I want written steps by which one Factory service starts on a developer machine with everything it needs, so that a developer or a coding agent can run and test a service without touching a shared database.

One repository per service (ADR-0028) means that a developer or a coding agent works on one service at a time and has to start it alone. This PBI delivers the page of this site with the steps for that, written so that a coding agent can follow them without asking. The steps cover four things a service needs and state for each where its value comes from. The store: ADR-0028 decision 5 gives every service one relational store that it alone binds, and model/stores.yaml names it, so the steps create one local database per service and never point a service at a shared database. The name of every local database is on a list that the owner agreed before any database is created; a step that creates, resets or removes a database names that database and no other. The messaging transport: the Orleans messaging profile of the messaging port, with the outbox and the inbox in the store of the service and its own messaging service name, as ADR-0028 decision 7 and ADR-0012 require, so a local run needs no broker. The identity: the Factory instance of the Identity Platform runs locally and issues the tokens. The page says where it comes from: the Factory owns the two repositories of that instance, ConnectSoft.AI.SoftwareFactory.Identity, scaffolded from the Identity template, and ConnectSoft.AI.SoftwareFactory.AuthorizationServer, scaffolded from the authorization server template (ADR-0028 amendment on the Factory instance of the Identity Platform, decision D117), and AIFACTORY-US-527 creates them. The steps start both from a checkout of those repositories, each with a local database of its own from the agreed list, and no folder outside a repository stands in for them. The seeded clients work only in the Development environment (AIFACTORY-US-245). The steps register the local clients, the public client of the command-line client among them, and a tenant, a project and a member for local work, and they use no secret that works outside the Development environment. The model access: ModelRouterService is the only service that calls a model provider (ADR-0028 decision 3) and reads its key through a secret reference that the developer resolves from a local secret store; no key value is written to a file of the repository or of this site. Every other service reaches a model through the model gateway, holds no key and starts without one. The steps name the ports that the service file declares, the health and readiness addresses of the scaffold and the one command that starts the service. They are written against a repository scaffolded with the Factory profile, which the feature component-base-template-factory-profile delivers, and are proven first on ConnectSoft.AI.SoftwareFactory.RunControlService. The page creates nothing by itself: it is followed by a person or an agent, and the databases it names exist only after the owner agreed their names.

Acceptance criteria

AC1 Given a repository scaffolded with the Factory profile and the steps page, when a developer or a coding agent follows the steps on a machine that has only the listed prerequisites, then the service starts on the ports its service file declares and reports ready, a call with a token of the local authorization server is answered and a call without a token is answered 401 (ADR-0015 decision 2; model/services/control-plane/RunControlService.yaml declares the ports of the first service).
AC2 Given the steps, when the service starts, then it binds only the relational store it owns, a local database whose name is on the list the owner agreed before any database was created, no connection string of the page names a shared database, and every step that creates, resets or removes a database names that database (ADR-0028 decision 5; model/stores.yaml names the store of each service).
AC3 Given the steps, when the service publishes and consumes an event locally, then it uses the Orleans messaging profile with its outbox and inbox in its own store and its own messaging service name, and no broker is started (ADR-0012 decisions 2 and 4, ADR-0028 decision 7).
AC4 Given ModelRouterService, the only service that calls a model provider (ADR-0028 decision 3), when the page describes its local start, then its key is read through a secret reference resolved from the local secret store of the developer, a start without the reference fails with the name of the missing reference, and no key value appears on the page or in a file of the repository; every other service calls the model gateway and starts without a key, which the recorded run shows for the first repository, and the failing start of ModelRouterService is recorded when the feature of increment I1 that delivers that service runs these steps (ADR-0028 decision 7 places secrets with the owning service; docs/architecture/data-governance.md).
Traces: adrs ADR-0012, ADR-0015, ADR-0028
Depends on AIFACTORY-US-527, feature:component-base-template-factory-profile, feature:component-auth-server-template-factory-tokens, feature:repository-and-pipeline-conventions
Sources docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/architecture/adr/0012-messaging-port-and-transport-profiles.md, model/stores.yaml, model/services/control-plane/RunControlService.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-148 Documented local setup: store, messaging transport, identity and model access documentation A page of this site with written, repeatable steps to start one Factory service locally: the prerequisites, one local database per service with the names agreed with the owner before any database is created, the Orleans messaging profile without a broker, the Factory instance of the Identity Platform, started from a checkout of ConnectSoft.AI.SoftwareFactory.Identity and ConnectSoft.AI.SoftwareFactory.AuthorizationServer (AIFACTORY-US-527), each with a local database of its own, with clients that work only in Development (AIFACTORY-US-245) and with its tenant, project and member, the model key of ModelRouterService through a secret reference only and no key for any other service, the ports of the service file, the health and readiness addresses and the start command. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1538 Verify the local setup 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 page; a read of the page against the model finds that every first-outcome service has a row whose store is the one model/stores.yaml names for it and whose ports equal its service file, and finds no connection string to a shared database and no key value, which proves AC2 and the page half of AC4 of AIFACTORY-US-372 (ADR-0028). ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1569 Verify the local start, the event without a broker and the start without a model key by the recorded run verification The recorded run of AIFACTORY-TASK-1540 on ConnectSoft.AI.SoftwareFactory.RunControlService shows the service ready on the ports of its service file, a call with a token of the local authorization server answered and a call without a token answered 401, one event published and consumed through the Orleans messaging profile with no broker process running, and a start with no model key configured; it proves AC1, AC3 and the run-time half of AC4 of AIFACTORY-US-372 for a service that calls no model provider (ADR-0012, ADR-0015). ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-373: Local environment: one acceptance environment runs the first-outcome services together behind their gateways for the fixture runs of the workflow definitions

enabling · persona operator As an operator, I want one environment in which the first-outcome services run together, so that a fixture run of a workflow definition crosses real services before the first outcome is demonstrated.

A service that starts alone proves little about a chain of six workflows. This PBI defines the one environment in which the first-outcome services run together: the acceptance environment. It is the environment that the amendment of ADR-0021 names: until the evaluation gate exists, a Draft workflow or agent release may run only in the acceptance environment and in the projects a platform-scope policy rule names as internal, so the environment and its fixture project have to exist and have a name before the first fixture run. The page of this site that defines it holds an inventory and the procedures. The inventory lists every service and gateway of the first outcome, the ones a feature of increment I1 delivers, with its repository, its database, its ports, its messaging service name and its health address, and names for each row the task of increment I0 that created and scaffolded its repository and the feature of increment I1 that delivers the service (D140). Each service has a database of its own, on the list of names the owner agreed before any database is created, because a service binds only the store it owns (ADR-0028 decision 5). The two agent silo kinds join one Orleans cluster (ADR-0028 decision 4), the gateways front the services of their platform, and the Factory instance of the Identity Platform issues the tokens: the identity service and the authorization server run from their own repositories, ConnectSoft.AI.SoftwareFactory.Identity and ConnectSoft.AI.SoftwareFactory.AuthorizationServer (ADR-0028 amendment on the Factory instance of the Identity Platform), and each has a row of the inventory with its repository, its database, its ports and its health address. The procedures are the order in which the estate is brought up, the way a fixture run is started with a token of the fixture tenant and project, and a reset that names every database it resets and touches none outside the list. Every first-outcome repository exists in increment I0 (D140): RunControlService and ControlPlaneApi are created by AIFACTORY-TASK-190 and AIFACTORY-TASK-1514 of feature repository-and-pipeline-conventions, AgentRuntimeService by AIFACTORY-TASK-146 of feature durable-execution-spike, every other first-outcome service and gateway by the tasks of AIFACTORY-US-1596 to AIFACTORY-US-1601 of feature repository-and-pipeline-conventions, each scaffolded from its template at the pinned version with a green template pipeline, and the two repositories of the Identity Platform instance by AIFACTORY-US-527; this PBI creates no repository. A bring-up in increment I0 therefore starts the scaffold of every first-outcome service and gateway behind the scaffold of ControlPlaneApi, and from increment I1 each service runs what its feature delivers. A row changes its delivery mark, and nothing else, when its feature delivers the service. The environment is defined by written steps here. The environment stack that the platform template generates arrives with a later increment and is not a dependency of this PBI.

Acceptance criteria

AC1 Given the acceptance environment page, when its inventory is compared with the features of increment I1 in model/backlog/features, then every service and gateway of the first outcome has one row with its repository, its own database from the agreed list, its ports, its messaging service name and its health address, each row names the task of increment I0 that created and scaffolded its repository and the feature of increment I1 that delivers the service (D140), and the identity service and the authorization server of the Factory instance of the Identity Platform have a row each with their own repository and database (ADR-0028 decisions 1 and 5 and its amendment on the Factory instance of the Identity Platform).
AC2 Given the environment brought up by the written order, when a call with a token of the fixture tenant and project passes the control plane gateway to a service, then every first-outcome service and gateway reports ready, which in increment I0 is the scaffold of each, created and scaffolded in increment I0 (D140), behind the scaffold of ControlPlaneApi, and the service reads the tenant and project of the token from its scope (ADR-0015 decision 2, ADR-0028 decision 2).
AC3 Given the waiver for Draft releases, when the page is read, then it names this environment as the acceptance environment and names the fixture tenant and project that the platform-scope policy rule lists as internal, so that the rule of the amendment of ADR-0021 has an environment and a project to name.
AC4 Given the reset procedure of the page, when it is read against the agreed list, then it names every database it resets, resets none outside the list, and states that no database is created, reset or removed before the owner agreed its name (ADR-0028 decision 5; model/stores.yaml).
Traces: adrs ADR-0015, ADR-0021, ADR-0028
Depends on AIFACTORY-US-372, feature:repository-and-pipeline-conventions, feature:trusted-scope-chain
Sources docs/architecture/capability-dependencies.md, docs/architecture/adr/0021-quality-gates.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/backlog/increments.yaml, model/stores.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-149 Acceptance environment for cross-service fixture runs documentation A page of this site that defines the one environment where the first-outcome services run together for the fixture runs of the workflow definitions: the inventory of the first-outcome services and gateways with repository, database, ports, messaging service name and health address, each row naming the task of increment I0 that created and scaffolded its repository and the feature of increment I1 that delivers the service (D140), a row each for the identity service and the authorization server of the Factory instance of the Identity Platform with their repositories ConnectSoft.AI.SoftwareFactory.Identity and ConnectSoft.AI.SoftwareFactory.AuthorizationServer, the bring-up order of every first-outcome service and gateway, the fixture tenant and project, the way a fixture run is started and the reset procedure that names every database it resets. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1539 Verify the inventory of the acceptance environment against the backlog and the stores 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 page; a comparison of the inventory with the deliveries of increment I1 in model/backlog/features and with model/stores.yaml finds one row per first-outcome service and gateway, the task of increment I0 that created its repository and the feature that delivers the service, and one store per service, which proves AC1, AC3 and AC4 of AIFACTORY-US-373 (ADR-0028, ADR-0021). ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-374: Local environment: a recorded run on a clean machine starts a service from the steps alone, and a recorded call crosses the acceptance environment with its scope

evidence · persona operator As an operator, I want recorded runs that show the steps work for someone who did not write them, so that the local estate is accepted on facts before services are built on it.

Steps that only their author has followed are not proven. This PBI is the proof of the feature and consists of two recorded runs. In the first, a person or a coding agent who did not write the local setup page follows it on a machine that has only the listed prerequisites, for the first repository, ConnectSoft.AI.SoftwareFactory.RunControlService. The record holds every step that was run and its result, the time the service took to report ready, the databases the service opened, the answer to a call with a token and to a call without one, one event published and consumed with no broker process running and the start with no model key configured. A step that had to be changed, guessed or repeated is recorded as a finding and leads to a correction of the page before the run is repeated. The record shows that every database the service opened is on the list the owner agreed and that no shared database was touched. In the second run, the acceptance environment is brought up by its written order with the services whose repository exists at the time of the run, which in this increment is the scaffold of RunControlService behind the scaffold of ControlPlaneApi, and one call with a token of the fixture tenant and project passes the control plane gateway to the service. The record holds the readiness of every started service, the rows of the inventory that are marked not yet created, the trace identifier of the call and the tenant and project the service read. Both records are kept on this site beside the pages they prove. They name no person and carry no date; they name the revision of the page and of each repository that was used. A failed run is recorded as failed with the step that failed, and the feature is not accepted on it.

Acceptance criteria

AC1 Given a machine with only the listed prerequisites and a person or coding agent who did not write the page, when the steps are followed for the first repository, then the service reports ready, a call with a token is answered and a call without one is answered 401, and the record names every step with its result and the revision of the page (ADR-0015 decision 2; model/services/control-plane/RunControlService.yaml).
AC2 Given the record of that run, when the databases the service opened are compared with the agreed list, then each is on the list and no shared database was opened, and a step that had to be changed or guessed is recorded as a finding with the correction of the page (ADR-0028 decision 5; model/stores.yaml).
AC3 Given the acceptance environment brought up by its written order, when one call with a token of the fixture tenant and project passes the control plane gateway to a service, then the record holds the readiness of every service whose repository exists at the time of the run, which in increment I0 is the scaffold of RunControlService behind the scaffold of ControlPlaneApi, the rows that are marked not yet created, the trace identifier of the call and the tenant and project the service read, which equal those of the token (ADR-0015 decision 2, ADR-0028 decision 2).
Traces: adrs ADR-0015, ADR-0028
Depends on AIFACTORY-US-372, AIFACTORY-US-373
Sources docs/architecture/capability-dependencies.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, model/stores.yaml, model/backlog/increments.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1540 Recorded run of the local steps on a clean machine verification A record on this site of one run of the local setup page for ConnectSoft.AI.SoftwareFactory.RunControlService by someone who did not write the page: every step with its result, the time to ready, the databases opened, the answers to a call with and without a token, one event published and consumed with no broker process running, the start with no model key configured, each finding with the correction of the page, and the revisions used, which proves AC1 and AC2 of AIFACTORY-US-374 (ADR-0028). ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-1541 Recorded scoped call across the acceptance environment verification A record on this site of one bring-up of the acceptance environment by its written order and of one call through the control plane gateway with a token of the fixture tenant and project: the readiness of every service whose repository exists at the time of the run, the rows marked not yet created, the trace identifier and the tenant and project the service read, which proves AC3 of AIFACTORY-US-374 (ADR-0015). ConnectSoft.AI.SoftwareFactory.Documentation

AIFACTORY-US-527: Local environment: the Factory instance of the Identity Platform has its two repositories, scaffolded from the Identity and authorization server templates with the registration data of the Factory

enabling · persona operator As an operator, I want the identity service and the authorization server of the Factory to live in repositories of their own, so that the local and the acceptance environment start the sole token issuer from a repository with a pipeline and not from a folder nobody owns.

ADR-0028 builds every deployable of the Factory in a repository of its own, scaffolded from a published template. Its amendment on the Factory instance of the Identity Platform (decision D117) applies that to identity: the Factory owns ConnectSoft.AI.SoftwareFactory.Identity, scaffolded from the Identity template, and ConnectSoft.AI.SoftwareFactory.AuthorizationServer, scaffolded from the authorization server template, each with its pipeline and its deployable. Before that decision the local environment generated an authorization server into a folder that was no repository. This PBI replaces that folder by the two repositories, and the local setup page and the acceptance environment page of this feature start the instance from them. Each repository is created once, by the steps of the checklist of feature repository-and-pipeline-conventions: after the recorded approval of the owner for that creation, under the name the amendment gives, with the template package restored from the ConnectSoft feed at the version the gate of its template feature published, component-identity-template-factory-roles for the Identity template and component-auth-server-template-factory-tokens for the authorization server template. The first commit of each is the unchanged output of its scaffold command, dotnet new connectsoft-identity -n ConnectSoft.AI.SoftwareFactory.Identity and dotnet new connectsoft-authorization-server -n ConnectSoft.AI.SoftwareFactory.AuthorizationServer. What makes the two a Factory instance is data and no code, and it is the second commit. The identity repository gets the role registration file with the seven Factory roles (AIFACTORY-US-240). The authorization server repository gets the scope registration file that maps each Factory scope of the service files to the resource of the gateway that fronts its service (AIFACTORY-US-244), the workload registration file with one client for each Factory service and agent host whose repository exists (AIFACTORY-US-245), and the public client registration file with the command-line client and its two sign-in flows (AIFACTORY-US-526). The feature that creates a later service repository adds its workload entry. No generated file is edited; a gap found while scaffolding is reported to the template feature and not patched. Each repository builds and tests in its generated pipeline from the shared pipeline templates and restores from the ConnectSoft feed only. The seeded development secrets work only in the Development environment, and the deployment checklist of the template names the credentials an operator replaces elsewhere. The identity service is the system of record of memberships, role assignments and delegations, and the authorization server reads them when it issues a token, so the two start together and the authorization server is configured with the address of the identity service of the same instance. Each of the two has a relational store of its own. Its local database is on the list of names the owner agreed before any database is created, and nothing in this PBI creates, resets or removes a database outside that list.

Acceptance criteria

AC1 Given the recorded approval of the owner and the two template packages at the versions their gates published, when the repositories are created by the steps of the checklist, then ConnectSoft.AI.SoftwareFactory.Identity holds the unchanged output of dotnet new connectsoft-identity and ConnectSoft.AI.SoftwareFactory.AuthorizationServer the unchanged output of dotnet new connectsoft-authorization-server, both names are entries of model/backlog/backlog.yaml, each solution builds and its tests pass in its generated pipeline, and the ConnectSoft feed is the only package source (ADR-0028 decision 1 and its amendment on the Factory instance of the Identity Platform).
AC2 Given the registration data of the second commit, when the two services are seeded in the Development environment, then the identity service holds the seven Factory roles, and the authorization server holds the Factory scopes mapped to the resource of the gateway that model/gateways.yaml names for their service, one workload client per registered service and the public client of the command-line client with the authorization code flow with PKCE and the device code flow; and no generated file differs from a fresh generation of the pinned template package (ADR-0015 decisions 5 and 6 and its amendment on the client sign-in).
AC3 Given the instance started from the two repositories, when a member of the fixture project signs in, then the authorization server reads the role assignments from the identity service of the same instance and issues a user token with the tenant claim, the role claim of the project and the one audience of the control plane gateway, and the local setup page and the acceptance environment page of this feature start this instance and no server generated into a folder that is no repository (ADR-0015 decision 6; docs/architecture/adr/0028-one-repository-and-deployable-per-service.md).
AC4 Given the stores of the two repositories, when the instance is started locally, then each binds a local database of its own whose name is on the list the owner agreed before any database was created, and no step of this PBI creates, resets or removes a database the list does not name (ADR-0028 decision 5).
Traces: adrs ADR-0015, ADR-0028
Depends on feature:component-identity-template-factory-roles, feature:component-auth-server-template-factory-tokens, feature:repository-and-pipeline-conventions
Sources docs/architecture/adr/0028-one-repository-and-deployable-per-service.md, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md, model/backlog/backlog.yaml, model/gateways.yaml, model/templates.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-2119 Scaffold the identity repository of the Factory from the Identity template implementation The repository ConnectSoft.AI.SoftwareFactory.Identity is created once, after the recorded approval of the owner and by the steps of the checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-identity -n ConnectSoft.AI.SoftwareFactory.Identity with the template package restored from the ConnectSoft feed at the version the gate of feature component-identity-template-factory-roles published; the solution builds, its tests pass and one run of its generated pipeline is green. ConnectSoft.AI.SoftwareFactory.Identity
AIFACTORY-TASK-2120 Scaffold the authorization server repository of the Factory from the authorization server template implementation The repository ConnectSoft.AI.SoftwareFactory.AuthorizationServer is created once, after the recorded approval of the owner and by the steps of the checklist of feature repository-and-pipeline-conventions; its first commit is the unchanged output of dotnet new connectsoft-authorization-server -n ConnectSoft.AI.SoftwareFactory.AuthorizationServer with the template package restored from the ConnectSoft feed at the version the gate of feature component-auth-server-template-factory-tokens published; the solution builds, its tests pass and one run of its generated pipeline is green. ConnectSoft.AI.SoftwareFactory.AuthorizationServer
AIFACTORY-TASK-2121 Role registration file of the Factory in the identity repository contract The identity repository holds the role registration file with the seven Factory roles, their allowed scope kinds and the roles each covers, as ADR-0015 decision 5 names them, in the schema that AIFACTORY-US-240 delivers; the seed reads it in the Development environment, and no generated file is edited. ConnectSoft.AI.SoftwareFactory.Identity
AIFACTORY-TASK-2122 Scope, workload and public client registration files of the Factory in the authorization server repository contract The authorization server repository holds the scope registration file with every Factory scope of the service files under model/services mapped to the resource of the gateway that model/gateways.yaml names for its service, the workload registration file with one client for each Factory service and agent host whose repository exists and only its svc. scopes, and the public client registration file with the command-line client, its two flows, its loopback redirect address and the scopes of the control plane gateway; the server is configured with the address of the identity service of the same instance, and no generated file is edited. ConnectSoft.AI.SoftwareFactory.AuthorizationServer
AIFACTORY-TASK-2123 Verify the Factory instance of the Identity Platform by a seeded start and one issued token verification Run dotnet build -c Release and dotnet test -c Release --no-build on both solutions and start the two services together in the Development environment, each on a throwaway database of the pipeline container; the comparison of the generated files with a fresh generation, the seeded roles, scopes and clients, and the token of a member of the fixture project with its tenant claim, its role claim and the one audience of the control plane gateway pass and prove AC1 to AC4 of AIFACTORY-US-527 (ADR-0015, ADR-0028); no named or shared database is touched. ConnectSoft.AI.SoftwareFactory.AuthorizationServer

AIFACTORY-US-134: Local development environment for a Factory service is delivered

enabling · persona operator As an operator, I want a local development environment and an acceptance environment for the Factory services, so that a developer or a coding agent can run any first-outcome service with its store, messaging and identity from documented steps.

This is the integration PBI of the feature. A developer or a coding agent can run any first-outcome service locally with its store, its messaging and its identity, from documented steps, without touching a shared database, and the first-outcome services can run together in one acceptance environment. AIFACTORY-US-372 delivers the local setup page: one local database per service with names the owner agreed before any database is created, the Orleans messaging profile without a broker, the Factory instance of the Identity Platform started from its own two repositories and model keys through secret references only. AIFACTORY-US-527 creates those two repositories, ConnectSoft.AI.SoftwareFactory.Identity and ConnectSoft.AI.SoftwareFactory.AuthorizationServer, from the Identity template and the authorization server template with the registration data of the Factory (ADR-0028 amendment of decision D117). AIFACTORY-US-373 delivers the page of the acceptance environment with its inventory, its bring-up order, its fixture tenant and project and a reset that names every database it resets. AIFACTORY-US-374 proves both by recorded runs of someone who did not write the pages. This PBI closes the feature: the two pages and the two records are linked from the index of the handoff records and from the navigation of the site, which are written by hand, and the site builds with them; the page of increment I0 is generated from the model and is not edited. The feature is done when the local estate that the epic names in its completion exists as pages that were followed successfully. No page here creates a database, a repository or an environment by itself; the steps are run by a person or an agent after the owner agreed the names, and the two repositories of AIFACTORY-US-527 are created only after the recorded approval of the owner. The environment stack generated by the platform template replaces the written bring-up in a later increment and is no part of this feature.

Acceptance criteria

AC1 Given the tasks of AIFACTORY-FEAT-092 are done, then the local setup page, the acceptance environment page and the two recorded runs exist in ConnectSoft.AI.SoftwareFactory.Documentation and are linked from the index of the handoff records, handoffs/2026-10-09-independent-review/INDEX.md, and from the navigation of the site; no generated page is edited for a link (ADR-0028 decision 5; the pages name one store per service as model/stores.yaml does).
AC2 Given the repository with those outputs, when python -I tools/docs_model validate runs, then it reports no error and no warning, and the pages name one store per service as model/stores.yaml does (ADR-0028 decision 5).
AC3 Given the two recorded runs, when they are read, then the local run opened only databases of the agreed list and the call across the acceptance environment carried the tenant and project of its token to the service (ADR-0015 decision 2, ADR-0028 decision 5).
Traces: adrs ADR-0015, ADR-0028
Depends on AIFACTORY-US-372, AIFACTORY-US-373, AIFACTORY-US-374, AIFACTORY-US-527
Sources docs/architecture/capability-dependencies.md, docs/ai-software-factory/current-state.md, handoffs/2026-10-09-independent-review/INDEX.md, model/stores.yaml

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1542 Link the environment pages and the recorded runs from the handoff records documentation The local setup page, the acceptance environment page and the two recorded runs are linked from the index of the handoff records, a page written by hand, and the navigation of the site lists the two pages; no page that tools/docs_model generates is edited, so python -I tools/docs_model check reports no changed output, which proves AC1 of AIFACTORY-US-134. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-715 Verify local-development-environment against its acceptance criteria verification The outputs of the tasks of AIFACTORY-FEAT-092 exist and python -I tools/docs_model validate reports no error, which proves AC1 to AC3 of AIFACTORY-US-134. ConnectSoft.AI.SoftwareFactory.Documentation