Skip to content

Increment I6: Full product generation

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 multi-module product with a user interface, a gateway and shared libraries is generated from a vision.

Depends on: I2, I5 · Elaboration: epics and features (rolling wave) · Azure DevOps CSV of this increment

Demonstrations

  • The requirements, alignment and UX workflows produce an approved UX Blueprint.
  • The frontend branch of generation runs because the recipe has a shell or microfrontend module.
  • Gateway, libraries, tests and documentation are generated for the product.

Services delivered in this increment

Service Role Depth Scope in this increment Repository
GeneratedProductHost representative complete the whole service as modelled none
GeneratedSaasFoundations representative complete the whole service as modelled none

Stub register

No stub is declared in this increment.

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-166 Identity, authorization server, SaaS, worker and health aggregator templates as generation inputs — outline —
AIFACTORY-FEAT-170 Blazor shell, SaaS shell, microfrontend and component library templates as generation inputs — outline —
AIFACTORY-FEAT-179 MassTransit messaging adapter: outbox and inbox parity for generated products — outline —
AIFACTORY-FEAT-182 Documentation site template as a generation input — outline —
AIFACTORY-FEAT-186 Marketing site template as a product module — outline —

Features by epic

Generated SaaS (PF-16)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-086 GeneratedProductHost: complete delivery
GeneratedProductHost is the per-product reference of bounded context BC-30 (Generated Product Domains). The representative shape of every product the Factory generates: domain microservices on the BaseTemplate shape per bounded context behind the product's own gateway (GW-07), a product descriptor and admin surface read by fleet operations, and a managed-operations handover record when ConnectSoft operates it (BC-30; one instance per product, never a Factory service). It is a reference of what a generated product contains and has no Factory repository.
development outline backend-developer — —
AIFACTORY-FEAT-087 GeneratedSaasFoundations: complete delivery
GeneratedSaasFoundations is the per-product reference of bounded context BC-31 (Generated Tenant & Commercial Foundations). The tenant and commercial foundations every generated SaaS product gets from the SaaS templates (Tenants, ProductsCatalog, Entitlements, Billing, Metering): product tenants mapped to opaque customer-tenant ids, editions and entitlements inside the product, subscriptions and usage meters, mirrored to the fleet when ConnectSoft operates the product (BC-31; one instance per product). It is a reference of what a generated product contains and has no Factory repository.
development outline backend-developer — —

Ecosystem component extensions

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-166 Identity, authorization server, SaaS, worker and health aggregator templates as generation inputs
A generated product with accounts, a token issuer or SaaS foundations is scaffolded from the specialized templates the way its modules are from the base template (ADR-0025, D95): the recipe needs each template's generated and preserved manifest, a versioned symbol catalog like the base template's (FEAT-160), a descriptor that validates against its schema, and the template's own generator present in the generation sandbox, because a missing external generator is a blocker and never a licence to hand-edit a descriptor-owned project (the extended-template rollout record). The Entitlements template records six mapping cases that fail on a UTC expression the object-mapping library cannot translate; that limitation sits in a shared library and is closed before the template is generated from. Components: Identity microservice, Authorization Server, the five SaaS services (extend). Scope when the wave is elaborated: a generated and preserved manifest and a versioned symbol catalog per template, imported by the template registry; the descriptor generator the SaaS templates call from build/regenerate.ps1 installed in the sandbox image, a missing generator failing the run by name; the five descriptors validated against their entity-model schemas in the descriptor import; the six excluded UTC mapping cases passing against the released object-mapping package; an identity module and an issuer module generated for a product blueprint with accounts, built and tested in the sandbox. The worker template (blueprint kinds with reconcilers and dispatchers) and the health aggregator template (the Health aggregator module of the worked examples) are generation inputs under the same rule, after their Factory profiles (FEAT-171, FEAT-173).
before development outline backend-developer — —
AIFACTORY-FEAT-170 Blazor shell, SaaS shell, microfrontend and component library templates as generation inputs
A generated product with a user interface is scaffolded from the Blazor templates the blueprint kinds name (Shell, SaaS shell, Microfrontend, Component library) through the UX handoff (ADR-0026) and the generation recipe (ADR-0025, D95). Like the specialized service templates (FEAT-166), each needs a generated and preserved manifest and a versioned symbol catalog; the UI kit adapter is chosen at the shell level by configuration, since the shell template's locked decisions refuse a uiKitAdapter symbol; the SaaS shell chrome parity record (F03) still awaits its visual review gate; and the sample and admin microfrontend templates have no generated-solution gate of their own. Scope when the wave is elaborated: manifests and symbol catalogs for the four templates imported by the template registry; the adapter choice as a generated configuration value; the visual review gate of the SaaS shell chrome passed and recorded; a generated-solution gate for the admin microfrontend templates the SaaS foundations use; screens generated from the UX blueprint's screen descriptors onto the exemplar microfrontend contract. Component: Blazor Shell + MFEs + UIKit (extend).
before development outline frontend-developer — —
AIFACTORY-FEAT-179 MassTransit messaging adapter: outbox and inbox parity for generated products
The Factory's own services run on the Orleans messaging profile (ADR-0024), but generated products may choose the MassTransit transport profile over Azure Service Bus or RabbitMQ (ADR-0003, ADR-0012), and the MassTransit adapter of the MessagingModel library is options only, with no outbox or inbox, while the Orleans adapter has both with 33 tests. Scope when the wave is elaborated: an outbox dispatcher and an inbox with the same contract tests as the Orleans adapter; the accepted envelope and scope headers on every message; profile evidence (the contract tests the components table asks for) published with the package; the generation recipe choosing the profile from the blueprint. Component: MessagingModel MassTransit adapter (extend).
before development outline backend-developer — —
AIFACTORY-FEAT-182 Documentation site template as a generation input
The Documentation site module of a generated product is scaffolded from the documentation template through the producing workflow of the documentation blueprint kind (ADR-0030) and the generation recipe (ADR-0025, ADR-0027). Scope when the wave is elaborated: the manifest and symbol catalog of FEAT-181 imported by the template registry; the blueprint's sections list driving the navigation, each section marked generated or hand-written so the workflow writes only into generated ones; audiences as navigation sections selected with the exclude plugin and locales through a static language layout, both as template parameters with defaults; a two-locale, two-audience scaffold building strictly in the sandbox; the generated API reference bound to the product gateway's OpenAPI document. Component: Documentation template (extend).
before development outline backend-developer — —
AIFACTORY-FEAT-186 Marketing site template as a product module
A generated product may include a marketing site (the Content example scaffolds one from connectsoft-marketing-site). The template is a Blazor Server site on the UI kit''s Flowbite adapter with page packs (minimal, standard, growth, full), computed page flags, a navigation catalog with legal navigation, generic placeholder copy, analytics and cookie-consent switches, an en or he default culture, an optional infra folder of Bicep files, unit, integration and E2E tests and a packaging pipeline that smoke-installs and builds the packed template before publishing; its B-F01 review gate pins the template to the live marketing site''s package line and keeps product-only surfaces out of the baseline. Scope when the wave is elaborated: the placeholder copy and metadata filled from the vision blueprint (product name, value proposition, company) and the page pack chosen from it; the FeatureManagement flags written at generation to match the pack (the template''s pages today say to set them by hand afterwards); locales and RTL from the localization blueprint rather than a two-value culture choice; analytics only through a connector the integration blueprint names, consent on; the infra folder excluded and infrastructure taken from the infrastructure blueprint and the platform template (ADR-0004, FEAT-185); the UI kit Tokens adapter (FEAT-168) beside Flowbite; telemetry on the Factory conventions (FEAT-175); the existing smoke pipeline extended across page packs and locales as the generated-solution gate. Component: Marketing site template (extend).
before development outline frontend-developer — —

Factory assets: workflow definitions, agents and skills

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-125 Workflow definition: Product plan
The workflow definition product-plan as a published asset: Builds the feature hierarchy, the edition scope and the roadmap-free dependency view from a validated Vision Blueprint, as artifacts for review. It has 4 steps, names the agents product-manager and the tools none, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-126 Workflow definition: Requirements alignment
The workflow definition requirements-alignment as a published asset: Elicits requirements, refines the backlog and records the stakeholder alignment memo that names the exact agreed versions; a Reviewer approves the memo by hash (publication class) before any final UX run can use it. It has 4 steps, names the agents business-analyst, product-owner, stakeholder-alignment and the tools none, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-127 Workflow definition: UX discovery
The workflow definition ux-discovery as a published asset: Early UX pass on a validated Vision Blueprint: synthesises research, extracts actors, builds personas and seeds journeys and hypotheses as typed artifacts that architecture and the final UX pass read; no blueprint version is produced. It has 4 steps, names the agents persona-builder, user-researcher and the tools none, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-128 Workflow definition: UX Blueprint
The workflow definition ux-blueprint as a published asset: Final UX pass on the typed, aligned input bundle: journeys and screens bound to the Service Blueprint's operations, the UX Blueprint version validated with a receipt, the coverage matrix against the agreed stories and the Claude Design handoff pack. It has 8 steps, names the agents ux-designer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-129 Workflow definition: Frontend blueprint
The workflow definition frontend-blueprint as a published asset: Builds the Frontend Blueprint from the Service and UX Blueprints: the shell, the microfrontends per work area, routes, state families, locales and the API bindings; validated against the DSL. It runs only for a product whose UX Blueprint exists. It has 5 steps, names the agents frontend-developer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-130 Workflow definition: API contracts
The workflow definition api-contracts as a published asset: Generates the OpenAPI and gRPC contracts of a validated Service Blueprint's operations, lints them against the API governance rules and stores them as artifacts. It has 4 steps, names the agents api-designer and the tools shell-sandbox, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-131 Workflow definition: Gateway generation
The workflow definition gateway-generation as a published asset: Generates the product's API gateway (GW-07) from the API Gateway Blueprint on the ConnectSoft API gateway template, validates it and records the output. It has 4 steps, names the agents api-designer, api-gateway-generator and the tools build-and-test, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-132 Workflow definition: Generate libraries
The workflow definition generate-libraries as a published asset: Scaffolds shared-kernel and client libraries from Backend Library Blueprints, implements the shared kernel, validates by build and test and records the outputs. It has 4 steps, names the agents backend-developer, library-generator and the tools build-and-test, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-133 Workflow definition: Saga design as workflow definitions
The workflow definition saga-design as a published asset: Finds the long-running flows in a derived domain model and designs each as a workflow definition with compensation, validated against the DSL, instead of an ad-hoc saga. It has 4 steps, names the agents enterprise-architect, event-driven-architect and the tools none, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-135 Workflow definition: Milestone lifecycle
The workflow definition milestone-lifecycle as a published asset: Validates a milestone's runs, tests and evidence before release packaging: collects the runs, verifies tests and evidence, and creates the release through ReleaseService when all pass. It has 4 steps, names the agents product-owner, qa-engineer, release-manager and the tools none, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-136 Workflow definition: Sprint execution
The workflow definition sprint-execution as a published asset: Runs a sprint's planned items as child runs in order, reviews each item's outcome against its acceptance criteria and closes the sprint with the evidence. It has 4 steps, names the agents product-owner, work-preparation-orchestrator and the tools none, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-150 Workflow definition: API gateway blueprint
The workflow definition api-gateway-blueprint as a published asset: Builds the API Gateway Blueprint from the Service and Security Blueprints: one route per published operation, token validation and audience, rate limits per route class and no business logic in the gateway; validated against the DSL. It has 5 steps, names the agents api-designer and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —
AIFACTORY-FEAT-151 Workflow definition: Backend library blueprint
The workflow definition backend-library-blueprint as a published asset: Builds the Backend Library Blueprint from the Service Blueprint and the derived domain model: the shared kernels more than one context needs, their layer, capability area and public surface. A product without a shared kernel yields a blueprint that declares no library. It has 5 steps, names the agents solution-architect and the tools blueprint-submit-version, blueprint-validate, and is executed by WorkflowEngineService under Run Control.
development outline solution-architect — —

Outcome verification

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-144 Demonstrate I6: Full product generation
The outcome of increment I6 is demonstrated end to end and the evidence is recorded: A multi-module product with a user interface, a gateway and shared libraries is generated from a vision. Demonstrations: The requirements, alignment and UX workflows produce an approved UX Blueprint. The frontend branch of generation runs because the recipe has a shell or microfrontend module. Gateway, libraries, tests and documentation are generated for the product.
development outline qa-engineer — —

Requirements this increment touches

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