Skip to content

Increment I7: Operate and commercialise

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. Generated products are inventoried, upgraded and off-boarded, and Factory usage is billed by edition.

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

Demonstrations

  • The fleet inventory lists every generated product with its template and library versions.
  • A template upgrade rolls out in waves with a rollback.
  • Usage is metered and billed according to the edition of the tenant.

Services delivered in this increment

Service Role Depth Scope in this increment Repository
FactoryCommercialService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.FactoryCommercialService
FleetIncidentService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.FleetIncidentService
FleetInventoryService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.FleetInventoryService
FleetOperationsHost platform-gateway complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.FleetOperationsHost
FleetRolloutService service complete the whole service as modelled ConnectSoft.AI.SoftwareFactory.FleetRolloutService

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-104 Products catalog integration for Factory editions — outline —
AIFACTORY-FEAT-105 Entitlements integration for Factory features — outline —
AIFACTORY-FEAT-106 Billing integration for Factory usage — outline —
AIFACTORY-FEAT-165 SaaS Products Catalog, Entitlements and Billing templates before the Factory editions — outline —

Features by epic

Control Plane (PF-01)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-009 FactoryCommercialService: complete delivery
FactoryCommercialService is the service of bounded context BC-34 (Factory Commercial). Factory editions, plans, subscriptions, invoices and meters for the Factory's own tenants, implemented by extending the SaaS ProductsCatalog, Entitlements, Billing and Metering templates (BC-34, ADR-0020). Its own repository is ConnectSoft.AI.SoftwareFactory.FactoryCommercialService.
development outline backend-developer — —

Product Fleet Operations (PF-10)

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-051 FleetIncidentService: complete delivery
FleetIncidentService is the service of bounded context BC-37 (Fleet Incidents & Off-boarding). Incidents on operated products with severity, timeline, linked alerts, runs and rollouts, on-call records per edition, customer notifications through connectors and post-incident reviews; and off-boarding of a customer tenant or a whole product with data handover through export and deletion orders (BC-37, D33). Its own repository is ConnectSoft.AI.SoftwareFactory.FleetIncidentService.
development outline backend-developer — —
AIFACTORY-FEAT-052 FleetInventoryService: complete delivery
FleetInventoryService is the service of bounded context BC-35 (Fleet Inventory & SLOs). The inventory of every generated product ConnectSoft operates — product, its instances per customer tenant and environment, the release each instance runs, the template and library versions it was generated from, its managed-service edition, objectives and health — derived from delivery, runtime cloud and observability events and the product's own health endpoints (BC-35, D33). Its own repository is ConnectSoft.AI.SoftwareFactory.FleetInventoryService.
development outline backend-developer — —
AIFACTORY-FEAT-053 FleetOperationsHost: gateway delivery
FleetOperationsHost is the platform API gateway of bounded context BC-35 (Fleet Inventory & SLOs). The API gateway of the Product Fleet Operations 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.FleetOperationsHost.
development outline backend-developer — —
AIFACTORY-FEAT-054 FleetRolloutService: complete delivery
FleetRolloutService is the service of bounded context BC-36 (Fleet Upgrades & Rollouts). Rollouts of a product release, a template or library upgrade, or a re-scaffold across the instances of an operated product in waves — each wave a set of promotions with the same gates, a bake time against the product's objectives, automatic halt and rollback on breach, and a production-class approval for production waves (BC-36). Its own repository is ConnectSoft.AI.SoftwareFactory.FleetRolloutService.
development outline backend-developer — —

Ecosystem component extensions

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-104 Products catalog integration for Factory editions
The editions and plans of the Factory are defined in the SaaS Products Catalog and read by the Factory commercial service. Component: SaaS Products Catalog service (extend).
before development outline backend-developer — —
AIFACTORY-FEAT-105 Entitlements integration for Factory features
Feature access and quotas of a tenant come from the SaaS Entitlements service and are enforced by policy and capacity. Component: SaaS Entitlements service (extend).
before development outline backend-developer — —
AIFACTORY-FEAT-106 Billing integration for Factory usage
Invoices for Factory usage are produced by the SaaS Billing service from metered usage and the tenant's plan. Component: SaaS Billing service (extend).
before development outline backend-developer — —
AIFACTORY-FEAT-165 SaaS Products Catalog, Entitlements and Billing templates before the Factory editions
FactoryCommercialService extends the SaaS Billing template and reads editions and entitlements from the Products Catalog and Entitlements templates (ADR-0020, FEAT-104 to FEAT-106); the marketplace LicenseService extends Billing as well. The templates' own gap backlogs record what blocks that use: Billing creates subscriptions Active instead of Draft, consumes non-canonical inbound topics, has no suspend-on-quota event and no decided invoice read model while the Factory models invoices; the Products Catalog has no ListEditions query; the Entitlements template pins a Products Catalog messaging package behind its documented version. FEAT-104, FEAT-105 and FEAT-106 depend on this feature; the rest of the gap backlogs stays with the templates. Components: SaaS Products Catalog, Entitlements and Billing services (extend). Scope when the wave is elaborated: subscriptions created Draft until activated and the invoice read-model decision recorded, with a projection for the Factory's ListInvoices if chosen (saas-BIL-F01, F03); canonical inbound topics, the MeterKey quota payload, a suspend-on-quota event and a rating-window event to Metering, all under the accepted envelope (saas-BIL-F02, F06, F07); ListEditions and get-by-id queries on the Products Catalog (saas-CAT-F06); the Entitlements template on the documented catalog package with the pin policy of saas-INTEG-F07 (saas-ENT-F08); architecture tests that fail on a layering violation or a write past the grain in all three.
before development outline backend-developer — —

Outcome verification

Feature Phase State Route PBIs Tasks
AIFACTORY-FEAT-145 Demonstrate I7: Operate and commercialise
The outcome of increment I7 is demonstrated end to end and the evidence is recorded: Generated products are inventoried, upgraded and off-boarded, and Factory usage is billed by edition. Demonstrations: The fleet inventory lists every generated product with its template and library versions. A template upgrade rolls out in waves with a rollback. Usage is metered and billed according to the edition of the tenant.
development outline qa-engineer — —

Requirements this increment touches

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