Coordinators — Blueprint & Microservice Assembly¶
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.
The June-2026 coordinators of this family are realized in the 2026 design as workflow definitions executed by the Workflow Engine (BC-38) under Run Control, as capabilities of a service, or are retired because a platform owns the concern outright. A coordinator never runs outside a Factory run: its triggers are events, its gates are approvals of the stated class, and its outputs are events and artifacts with receipts.
SolutionBlueprintCoordinator¶
Produces the Module Blueprints (clean-architecture layout per module) from the Service Blueprint.
| Realization | workflow |
| Owner service | WorkflowEngineService |
| Workflow definition | module-blueprints |
| Triggers | ContextMapDerived |
| Inputs | service blueprint, context map |
| Agents | Backend Developer Agent |
| Gates | none (read and sandbox classes only) |
| Emits | BlueprintValidated |
| Detailed page | this card |
| ## MicroserviceAssemblyCoordinator |
Executes an approved recipe: scaffolds each module from its template in the sandbox, fills it from the domain model, validates, and proposes the change set.
| Realization | workflow |
| Owner service | WorkflowEngineService |
| Workflow definition | generate-product |
| Triggers | RecipeApproved |
| Inputs | approved recipe, manifests |
| Agents | Backend Developer Agent, Frontend Developer Agent, Database Engineer Agent |
| Gates | shared-write approval for the change proposal when policy requires |
| Emits | GeneratedOutputRecorded, ChangeProposalOpened |
| Detailed page | platform-architecture/coordinators/microservice-assembly-coordinator.md |
| ## AdapterStrategyMapper |
Outbound adapter choice (HTTP, gRPC, messaging profile) is a module parameter validated against the template switches.
| Realization | service-capability |
| Owner service | GenerationRecipeService |
| Workflow definition | — |
| Triggers | — |
| Inputs | — |
| Agents | — |
| Gates | none (read and sandbox classes only) |
| Emits | — |
| Detailed page | this card |
| ## LibraryScaffoldCoordinator |
Scaffolds shared-kernel libraries from Backend Library Blueprints.
| Realization | workflow |
| Owner service | WorkflowEngineService |
| Workflow definition | generate-libraries |
| Triggers | RecipeApproved |
| Inputs | backend library blueprints |
| Agents | Backend Developer Agent |
| Gates | none (read and sandbox classes only) |
| Emits | GeneratedOutputRecorded |
| Detailed page | this card |
| ## LayerMapper |
Layer responsibilities are fixed by the BaseTemplate project shape (EntityModel … InfrastructureModel); nothing to map at run time.
| Realization | retired |
| Owner service | TemplateRegistryService |
| Workflow definition | — |
| Triggers | — |
| Inputs | — |
| Agents | — |
| Gates | none (read and sandbox classes only) |
| Emits | — |
| Detailed page | this card |
| ## DomainContractBinder |
Entities bind to schemas, adapters and persistence through the module parameters derived from the domain model.
| Realization | service-capability |
| Owner service | GenerationRecipeService |
| Workflow definition | — |
| Triggers | — |
| Inputs | — |
| Agents | — |
| Gates | none (read and sandbox classes only) |
| Emits | — |
| Detailed page | this card |