Skip to content

AIFACTORY-FEAT-160: Base template: the symbol catalog and determinism the generation recipe needs

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 Ecosystem component extensions · Increment I1 Generate a microservice · State elaborated · Route backend-developer · Phase before development · Build order 21 of 185 (Templates and libraries)

Before development

Template or library work: every task of this feature changes a template or a shared library the Factory builds on, and it lands before the Factory's own repositories of I1 are developed. The mark travels with every task (tag phase:before-development).

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).

Delivers —
Stubs —
Realizes components: cmp-base-template
adrs: ADR-0025, ADR-0028
Requirements —
Depends on AIFACTORY-FEAT-157 Base template: the Factory service profile
Sources model/components.yaml, model/blueprints.yaml, docs/planes/agent-runtime/workflow-definitions/module-blueprints.md, docs/templates-docs/base-template.md

AIFACTORY-US-275: Base template: the package carries a versioned catalog of its symbols with allowed values, defaults and the dependencies between them, generated from the template configuration at pack time

enabling · persona asset-maintainer As an asset maintainer, I want the symbols of the base template published as a catalog inside the package, so that a recipe can be validated against the pinned template version without reading a checkout of the repository.

A Module Blueprint names the template switches of its module, rule MOD-002 of model/blueprints.yaml requires that the switches used are declared by the pinned template version, and ADR-0027 decision 2 has every module entry of a recipe pin its inputs by identifier, version and hash. The only machine-readable statement of the symbols of connectsoft-base is the template configuration itself: 86 parameters, 113 computed and 11 generated symbols by the snapshot model/template-parameters/connectsoft-base.yaml, which the documentation repository derives by reading a checked-out repository. A validator that runs inside the Factory cannot read a checkout. The library template feature of this epic set the file a template package exports for this purpose, .template.config/symbol-catalog.json, produced from the template configuration at pack time. This PBI gives the base template package the same file under the same name and in the same shape, and adds what a recipe validator needs from a template with as many switches: for every parameter its name, its command line name, its data type, its default and its choices; for every computed symbol its expression and the parameters it depends on; for every generated symbol its generator and the parameter that can supply its value; and the combinations the template refuses, each with the symbols it names. The catalog names the template identity, the short name and the version of the package it travels in, so a catalog is never read against another version. It is produced by a step of the pack scripts of the template and never edited by hand. A test compares it with the template configuration and fails on a symbol that is missing, added or different. The step is part of the scripts a template that composes on the base template through the submodule already shares, so that such a template can produce its own catalog the same way; producing those catalogs and importing a catalog into the template registry of the Factory are not part of this PBI.

Acceptance criteria

AC1 Given the packed base template, when the package is inspected, then it contains .template.config/symbol-catalog.json with the template identity, the short name, the package version and every parameter with its command line name, data type, default and choices, and the catalog lists the same parameters as model/template-parameters/connectsoft-base.yaml after the next template inventory (ADR-0027 decision 2, model/blueprints.yaml).
AC2 Given the catalog, when a computed symbol, a generated symbol and a refused combination are looked up, then the computed symbol shows its expression and the parameters it depends on, the generated symbol shows its generator and the parameter that can supply its value, and the refused combination names its symbols, so that a recipe can be checked without generating (ADR-0027 decision 2, ADR-0025 decision 1).
AC3 Given a template configuration that was changed without repacking the catalog, when the pipeline of the template runs, then the comparison test fails and names the symbol that is missing, added or different; a planted change proves the refusal, and the catalog version always equals the version of the package (ADR-0028, docs/planes/agent-runtime/workflow-definitions/module-blueprints.md).
Traces: services TemplateRegistryService, GenerationRecipeService
Traces: adrs ADR-0025, ADR-0027, ADR-0028
Relates: nfrs NFR-14
Depends on feature:component-base-template-factory-profile, feature:component-library-template-factory-profile
Sources model/components.yaml, model/blueprints.yaml, model/template-parameters/connectsoft-base.yaml, docs/planes/agent-runtime/workflow-definitions/module-blueprints.md, docs/templates-docs/base-template.md, docs/architecture/adr/0027-generation-input-contract.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1241 Catalog shape of the base template with dependencies, generators and refused combinations contract The shape of .template.config/symbol-catalog.json the library template set is extended, without changing its existing fields, by the expression and dependencies of a computed symbol, the generator and supplying parameter of a generated symbol and the list of refused combinations; a schema file beside the catalog describes the shape and the catalog of the base template validates against it. ConnectSoft.BaseTemplate
AIFACTORY-TASK-591 Versioned symbol catalog published with the template implementation A step of the pack scripts reads the template configuration and writes the machine-readable catalog of its symbols, allowed values, defaults and dependencies between symbols into the package, versioned with the package; the step is usable by a template that composes on the base template through the submodule; the file is the one the template registry of the Factory will import. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1242 Comparison test of the catalog against the template configuration with a planted change fixture A test of the template pipeline compares the catalog of the packed candidate with template.json symbol by symbol and fails with the symbol named; a fixture plants an added choice in the configuration without repacking and asserts the failure. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1243 Verify the catalog of the packed template verification Pack the template and run the comparison test and the schema validation on the candidate; both pass, the planted change fails, and the parameters of the catalog equal those of model/template-parameters/connectsoft-base.yaml after the template inventory, which proves AC1 to AC3 of AIFACTORY-US-275 (ADR-0027). ConnectSoft.BaseTemplate

AIFACTORY-US-276: Base template: a generation with every input supplied is byte-identical when repeated and ends with exit code zero when scripts are not allowed

enabling · persona asset-maintainer As an asset maintainer, I want a generation that a recipe can run unattended and repeat with the same result, so that a generation run produces a change set whose content depends only on its pinned inputs and reads success from the exit code.

The recipe path of the Factory scaffolds with dotnet new in the sandbox (ADR-0025 decision 5), and a generation run produces a reviewable change set with provenance (decision 1). Two properties of the template stand in the way. First, some inputs differ between two runs with the same parameters. The generated symbol currentYear writes the year of the generation, HttpPortGenerated and HttpsPortGenerated draw ports that the replacers HttpPortReplacer and HttpsPortReplacer take whenever the parameters HttpPort and HttpsPort are absent, and buildDefinitionNumber is empty unless it is given (model/template-parameters/connectsoft-base.yaml). Two more inputs differ and are no generated symbol. The guids list of the template configuration holds b981603d-39fd-4556-a4a5-b0c2f6e09686, which the engine replaces by a new value on every generation and which is the UserSecretsId of the Application project. And the post-action that restores the NuGet packages of the generated solution writes obj folders with absolute paths. Second, the template has a script post-action that opens the page TODO.html; the Build Process page of the template describes the prompt and the option --allow-scripts No, and under that option the generation ends with exit code 104 although every file was written, so a recipe cannot tell success from failure. This PBI removes both. Every generated symbol whose value differs between runs gets a parameter that supplies it, by the coalesce pattern the two ports already follow, the year among them. The secrets identifier leaves the guids list and becomes a symbol of the same kind: a generated identifier that a parameter replaces when it is supplied. The catalog of the earlier PBI marks every symbol a caller must supply for a repeatable output, the secrets identifier included. The repeat generation of the gate and the recipe run with the restore post-action off, by --no-restore, so no restore output is part of the generated folder; the restore is a later stage of its own. A generation in which all marked symbols are supplied is byte-identical when repeated, in every file. A generation that supplies none behaves as today: it draws ports and a new secrets identifier and writes the current year. The script post-action is conditioned on a parameter the recipe sets, so an unattended generation has no script post-action and ends with exit code zero when its files are complete, while an interactive generation still offers the page. A generation that really fails, by an unknown parameter value or a refused combination, still ends with a non-zero exit code and names the reason. The checks of this PBI are validator scripts that the cases of build/template-ci.json call, because AIFACTORY-US-235 of the findings feature turns the presets of build/Test-BaseTemplateRegressions.ps1 into cases of that manifest.

Acceptance criteria

AC1 Given the same parameters with every symbol the catalog marks as required for a repeatable output supplied, that is the unattended parameter, both ports, the year, the secrets identifier and the build number, and the restore post-action off by --no-restore, when the template is generated twice into two folders, then a recursive comparison of the folders finds no difference, the launch settings, the year, the UserSecretsId of the Application project and the build number included (ADR-0025 decisions 1 and 5, model/template-parameters/connectsoft-base.yaml).
AC2 Given a generation that supplies none of those symbols, when it runs, then it draws its ports and a new secrets identifier and writes the current year as the template does today, and the catalog marks exactly the symbols whose absence makes two outputs differ, the secrets identifier among them (ADR-0027 decision 2, ADR-0028).
AC3 Given an unattended generation with scripts not allowed and the unattended parameter set, when it completes its files, then dotnet new ends with exit code zero; given an unknown parameter value or a refused combination, then it ends with a non-zero exit code and names the reason; an interactive generation still offers the page TODO.html (ADR-0025 decision 5, docs/templates-docs/base-template.md).
Traces: services GenerationRecipeService
Traces: adrs ADR-0025, ADR-0027, ADR-0028
Depends on AIFACTORY-US-275
Sources model/components.yaml, model/template-parameters/connectsoft-base.yaml, docs/templates-docs/base-template.md, docs/architecture/adr/0025-saas-descriptor-import.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-592 Deterministic generation for the same inputs implementation Two generations with the same symbols produce byte-identical output: every generated symbol whose value differs between runs (the generated ports, the current year) takes its value from a parameter by the coalesce pattern when the parameter is supplied; the entry b981603d-39fd-4556-a4a5-b0c2f6e09686 leaves the guids list and becomes a generated secrets identifier that a parameter replaces by the same pattern; the build number comes from its parameter; the catalog marks these symbols; a generation that supplies none behaves as before; the repeat generation runs with --no-restore, and the validator script of AIFACTORY-TASK-1244 generates twice and compares. ConnectSoft.BaseTemplate
AIFACTORY-TASK-593 Post-action exit code under disallowed scripts implementation The script post-action that opens TODO.html is conditioned on a parameter an unattended caller sets, so dotnet new no longer ends with exit code 104 when scripts are not allowed and a recipe reads success from the exit code; a real failure still ends non-zero with the reason. The product tenant profile this task also named is delivered by AIFACTORY-TASK-1246 to AIFACTORY-TASK-1249 of AIFACTORY-US-277. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1244 Validator scripts for the repeat generation and the exit code, called by the cases of the manifest fixture Two validator scripts that a case of build/template-ci.json calls: build/Test-RepeatGeneration.ps1 reads the marked symbols of the catalog, generates the case twice with all of them supplied and --no-restore and compares the two folders recursively; build/Test-GenerationExitCode.ps1 generates once with scripts not allowed and the unattended parameter and asserts exit code zero, and once with an unknown parameter value and asserts a non-zero exit code with the reason; neither is added to build/Test-BaseTemplateRegressions.ps1, whose presets AIFACTORY-US-235 turns into cases of the manifest. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1245 Verify the repeatable output and the exit codes verification Run the cases of the manifest with the repeat-generation and exit code validators on the packed candidate; the two folders of each case are identical, the UserSecretsId included, the unattended generation ends with exit code zero and the planted failure ends non-zero, which proves AC1 to AC3 of AIFACTORY-US-276 (ADR-0025, model/template-parameters/connectsoft-base.yaml). ConnectSoft.BaseTemplate

AIFACTORY-US-277: Base template: the product tenant profile generates the tenant resolution of a product module against the Tenants service of the product and changes nothing that UseFactoryProfile generates

enabling · persona asset-maintainer As an asset maintainer, I want a profile of the base template for a module of a generated SaaS product that resolves its tenant, so that a generated product module refuses a tenant that does not exist or is not active without code written by hand.

ADR-0015 decision 4 keeps a Factory tenant and a tenant of a generated product as distinct identities and stores, and makes any mapping between them an explicit contract of the generation recipe. The base template has the parameter UseIdentityPlatform, on by default, which gives a generated service the normalized identity context, the trusted gateway headers and tenant-required requests (model/template-parameters/connectsoft-base.yaml); it does not check that the tenant of a request exists or is active. A generated SaaS product has its own Tenants service, and the package ConnectSoft.Saas.Tenants.ServiceModel of that service offers a typed resolution client that never answers with a default tenant, which the feature component-saas-tenants delivers. This PBI adds the product tenant profile to the base template: the boolean parameter ProductTenant, off by default. With it on, the generated module takes the tenant from the validated token of the product, resolves it through the typed client, which it pins by version without copying a type, and establishes the tenant context of the SaaS libraries for the request and for message handlers. A request of an active tenant proceeds and reads only the rows of that tenant. A request whose tenant is unknown, suspended or decommissioned is refused with 403 and a problem body that names the reason. When the Tenants service cannot be reached the request is refused with 503; no default tenant is ever used and nothing is written. How long a resolution may be reused is an option of the generated module with a short default. The profile is separate from the Factory profile, as decision D114 requires: a generation with UseFactoryProfile produces the same output whether or not this PBI exists, which a comparison of the Factory preset proves, and a generation with both parameters on is refused with both symbols named, because a Factory service resolves a Factory tenant and a product module a product tenant. The product tenant profile is a declared profile of the template and gets its own gating case.

Acceptance criteria

AC1 Given a module generated with ProductTenant and a Tenants service with two active tenants, when callers of both tenants read and write, then each request runs under the tenant context of its token after one resolution through the typed client, each caller reads only its own rows, and a row of the other tenant addressed by identifier is answered 404 (ADR-0015 decisions 1 and 4 and its amendment on a resource of another tenant).
AC2 Given a token whose tenant is unknown, suspended or decommissioned, when a request arrives, then it is refused with 403 and a problem body that names the reason; given the Tenants service cannot be reached, then the request is refused with 503, no default tenant is used and nothing is written (ADR-0015 decision 1 on the inherited fail-closed rule, docs/planes/control/tenancy.md).
AC3 Given the template with this profile, when the Factory preset is generated with UseFactoryProfile and ProductTenant off, then its output equals the output of the Factory preset before this PBI; given both parameters on, then the generation is refused with both symbols named (ADR-0028 amendment on the Factory profile switch, ADR-0015 decision 4).
AC4 Given the template with ProductTenant off and UseFactoryProfile off, when the default case is generated, then its output is unchanged, and the symbol catalog and, after the next template inventory, model/template-parameters/connectsoft-base.yaml list the parameter with its default and the refused combination (ADR-0028, ADR-0027 decision 2).
Traces: adrs ADR-0015, ADR-0027, ADR-0028
Relates: nfrs NFR-01
Depends on AIFACTORY-US-275, feature:component-saas-tenants, feature:component-saas-extensions, feature:component-base-template-factory-profile
Sources model/components.yaml, model/template-parameters/connectsoft-base.yaml, docs/planes/control/tenancy.md, docs/architecture/adr/0015-factory-tenancy-under-canonical-adr-0100.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1246 Parameter ProductTenant, its computed symbols and the refused combination contract The template configuration defines the boolean parameter ProductTenant, off by default, with its description, the computed symbols that include the resolution code and the pin of the ServiceModel package of the Tenants service, and the refusal of a generation with ProductTenant and UseFactoryProfile both on that names both symbols; the catalog lists all three. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1247 Tenant resolution of a product module through the typed client implementation With ProductTenant on, the generated module resolves the tenant of the validated token through the typed resolution client of the pinned ConnectSoft.Saas.Tenants.ServiceModel package, establishes the tenant context of the SaaS libraries for requests and message handlers, refuses an unknown, suspended or decommissioned tenant with 403 and an unreachable Tenants service with 503, and reuses a resolution for the period its options set. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1248 Resolution tests against a stub Tenants service inside the generated solution and the comparison validator of the Factory preset fixture The generated solution of the product tenant case holds tests against a stub Tenants service, which runs inside those tests and is no service of the pipeline, for two active tenants, an unknown, a suspended and a decommissioned tenant and an unreachable service; a validator script build/Test-FactoryPresetUnchanged.ps1, called by the Factory preset case of build/template-ci.json, compares the generated Factory preset with its recorded output, a list of files with their hashes recorded before the profile was added, and fails on a difference with the file named. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1249 Verify the product tenant profile and the unchanged Factory preset verification Generate the product tenant case, the Factory preset and the default case, build each in Release and run their tests; the resolution tests pass, the Factory preset and the default case equal their earlier output and the generation with both profiles is refused, which proves AC1 to AC4 of AIFACTORY-US-277 (ADR-0015, ADR-0028). ConnectSoft.BaseTemplate

AIFACTORY-US-278: Base template: the catalog check, the repeat-generation check and the product tenant case pass in the shared template pipeline before the package publishes

evidence · persona asset-maintainer As an asset maintainer, I want the catalog, the repeatable generation and the product tenant profile gated on every change of the base template, so that a package whose catalog lies, whose output differs between runs or whose product module admits an unknown tenant never reaches the feed.

This PBI is the gate of the feature. The findings feature of the base template moves the template onto the shared template pipeline of ConnectSoft.AzurePipelines (template-ci/v1), and its Factory profile feature adds the Factory preset as a case of the manifest build/template-ci.json. The amendment of ADR-0028 on the Factory profile switch has the shared pipeline admit one additional gating case per declared profile beside the default case. This PBI adds the product tenant case, a generation with ProductTenant under the name of a product module. The case declares only the infrastructure it needs, because its stub Tenants service runs inside the tests of the generated solution and is no service of the pipeline. The PBI also registers in the manifest the checks the earlier PBIs deliver as validator scripts: the comparison of the symbol catalog with the template configuration, the repeat generation of the default case, the Factory preset and the product tenant case with --no-restore and a recursive comparison of each pair of outputs, the exit code check, and the comparison of the Factory preset with its recorded output. The candidate is packed once and installed; each case is generated with scripts not allowed and must end with exit code zero, then restored and built in Release; its tests run with the discovery and completion checks; the dependency audit runs. A catalog that differs from the configuration, two outputs that differ, a non-zero exit code of a complete generation or a failing resolution test fails the run with the case and the stage named, and publication is not reached. Publication requires the complete reports of every case bound to the candidate and pushes a version that is not yet on the ConnectSoft feed. This is an evidence PBI (D113): a template feature has no scenario, so the gate names what it proves through its ADRs, the requirement on release gates and its sources: the pinned inputs of ADR-0027, the generation contract of ADR-0025 and the generated-solution gate the epic requires of every template.

Acceptance criteria

AC1 Given a change of the base template, when the template pipeline runs the shared installer jobs with build/template-ci.json, then the candidate is packed once and installed, the catalog comparison passes, the default case, the Factory preset and the product tenant case are each generated twice with scripts not allowed and the restore post-action off, end with exit code zero and compare equal, and each case is restored, built in Release and tested with the discovery and completion checks (FR-11, ADR-0027 decision 2, ADR-0028 amendment on the Factory profile switch).
AC2 Given a planted catalog that differs from the configuration, a planted file that carries the time of the generation or a planted admission of an unknown tenant, when the pipeline evaluates the run, then it fails at the stage of that check with the case named and the package is not published (FR-11, ADR-0025 decision 1).
AC3 Given complete reports of every case bound to the candidate, when the publication job runs, then the package is pushed to the ConnectSoft feed with a version that was not on it, a fresh install of that version carries the catalog of that version and generates the three cases unchanged, and model/template-parameters/connectsoft-base.yaml lists the new parameters after the next template inventory (ADR-0028, model/backlog/epics.yaml states the gate as the completion of the epic).
Traces: adrs ADR-0025, ADR-0027, ADR-0028
Traces: requirements FR-11
Depends on AIFACTORY-US-275, AIFACTORY-US-276, AIFACTORY-US-277, feature:component-base-template-findings, feature:component-base-template-factory-profile
Sources model/components.yaml, model/backlog/epics.yaml, model/template-parameters/connectsoft-base.yaml, docs/architecture/catalogs/templates.md, docs/architecture/adr/0028-one-repository-and-deployable-per-service.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1250 Product tenant case and the registration of the validators in the pipeline manifest operations build/template-ci.json of the template holds the product tenant case with ProductTenant, a product module name, its test filter and only the infrastructure it needs among its required services, such as SQL Server for its store; the stub Tenants service runs inside the tests of the generated solution and is not declared; the manifest registers the catalog comparison of AIFACTORY-TASK-1242 and the validator scripts of AIFACTORY-TASK-1244 and AIFACTORY-TASK-1248 on the default case, the Factory preset and the product tenant case, and the shared installer jobs run them on every change. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1251 Planted catalog drift, planted time-dependent file and planted tenant admission for the gate fixture Pipeline fixtures plant a catalog that differs from the configuration, a generated file that carries the time of the generation and a product tenant case that admits an unknown tenant, and assert that each run fails at its stage with the case named and that publication is not reached. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1252 Publication bound to the complete reports of the three cases and both checks operations The publication job of the template pipeline requires the complete reports of the default case, the Factory preset and the product tenant case and the results of the catalog comparison and the repeat generation, each bound to the candidate; a missing or failed stage or a version that is already on the ConnectSoft feed refuses publication with the reason. ConnectSoft.BaseTemplate
AIFACTORY-TASK-1253 Verify the gate on a green run and on the three planted runs verification One pipeline run with every case and both checks green reaches publication and a fresh install of the published version carries its catalog and generates the three cases unchanged; the three planted runs fail before publication; together they prove AC1 to AC3 of AIFACTORY-US-278 (FR-11, ADR-0027, ADR-0028). ConnectSoft.BaseTemplate

AIFACTORY-US-114: Base template: the symbol catalog and determinism the generation recipe needs is delivered and proven on a generated solution

enabling · persona asset-maintainer As an asset maintainer, I want BaseTemplate to carry the symbol catalog and determinism the generation recipe needs, so that it serves every Factory service that is not a gateway or an agent host, and every generated product module (D94, D95) without later rework.

This is the integration PBI of the feature. With the symbol catalog, the unattended and repeatable generation, the product tenant profile and the gate of the earlier PBIs, the base template is a generation input the recipe path of the Factory can pin and trust. A recipe names the template by identity and version, reads from the catalog inside that package which switches exist, which values they take, which symbols depend on which and which combinations are refused, supplies every symbol the catalog marks, runs dotnet new in the sandbox with scripts not allowed, and reads success from exit code zero. The same inputs give the same bytes, so the change set of a generation run depends only on its pins. A module of a generated SaaS product is generated with ProductTenant and refuses a tenant its Tenants service does not know or does not hold active. A Factory service is generated with UseFactoryProfile exactly as before this feature. The implementation lives in the tasks of the earlier PBIs; this PBI keeps the migrated verification of the feature and the snapshot of the parameters in the documentation repository. The feature is done when the packed template passes the three cases and both checks in the shared template pipeline and the package is on the ConnectSoft feed with its catalog, before the blueprint, recipe and template registry services of this increment read it.

Acceptance criteria

AC1 Given the template repository ConnectSoft.BaseTemplate with the work of this feature, when the template is packed, installed and instantiated in its pipeline, then the generated solution of every case builds and its tests pass before the package publishes with a verified version (ADR-0028, model/components.yaml).
AC2 Given the work of AIFACTORY-TASK-591 (versioned symbol catalog published with the template) is done, then the template ships a machine-readable catalog of its symbols, allowed values, defaults and dependencies between symbols, versioned with the package, in the file the template registry of the Factory imports, and a test compares the catalog with template.json (ADR-0027 decision 2, model/blueprints.yaml).
AC3 Given the work of AIFACTORY-TASK-592 (deterministic generation for the same inputs) is done, then two generations with the same symbols and the restore post-action off produce byte-identical output, with the generated ports, the current year, the secrets identifier and the build number supplied by parameters, and a validator generates twice and diffs (ADR-0025 decision 1, model/template-parameters/connectsoft-base.yaml).
AC4 Given the work of AIFACTORY-TASK-593 (post-action exit code) and of AIFACTORY-US-277 (product tenant profile) is done, then dotnet new no longer ends with exit code 104 when scripts are not allowed, so the recipe reads success from the exit code, and the parameter ProductTenant generates the tenant resolution of a product module against the Tenants service of the product without changing what UseFactoryProfile generates (ADR-0025 decision 5, ADR-0015 decision 4).
Traces: services TemplateRegistryService, GenerationRecipeService
Traces: adrs ADR-0015, ADR-0025, ADR-0027, ADR-0028
Depends on AIFACTORY-US-275, AIFACTORY-US-276, AIFACTORY-US-277, AIFACTORY-US-278
Sources model/components.yaml, model/blueprints.yaml, docs/planes/agent-runtime/workflow-definitions/module-blueprints.md, docs/templates-docs/base-template.md

Tasks

Task Kind Expected output Repository
AIFACTORY-TASK-1254 Template inventory of the documentation repository re-run for the new parameters documentation After the package is published, python -I tools/docs_model inventory-templates is run in the documentation repository so that model/template-parameters/connectsoft-base.yaml lists ProductTenant, the unattended parameter and the parameters that supply the generated symbols and the secrets identifier, with their group and binding authored; no other file of the model is edited by hand. ConnectSoft.AI.SoftwareFactory.Documentation
AIFACTORY-TASK-674 Verify base-template-product-profile-delivered by running the declared command verification Run dotnet build -c Release and dotnet test -c Release --no-build on the authoring solution and on the default case, the Factory preset and the product tenant case generated from the published package; they pass and prove AC1 to AC4 of AIFACTORY-US-114. ConnectSoft.BaseTemplate