Coordinators overview¶
Target
This page describes intended behaviour or structure. No implementation is claimed unless a section is explicitly marked Current implementation or Evidence.
Rewritten 2026-10-09 (design plan B1)
The June-2026 page titled "50 coordinators" named 60 and five dedicated pages added three more; all 63 are registered in model/coordinators.yaml with their realization. The old page is archived under catalogs 2026-06. The five detailed pages (project bootstrap, sprint execution, milestone lifecycle, microservice assembly, release) are kept and linked from their cards.
A coordinator in the 2026 design is not a service. It is one of three things:
- a workflow definition (BC-38) executed by the Workflow Engine under Run Control — steps, agents, gates and compensation, triggered by events, producing events and artifacts with receipts;
- a capability of a platform service — the concern is a command, worker or derivation of a modelled service (for example the context map is derived by BlueprintService);
- retired — the concern is owned outright by a platform (for example the messaging bus is an installation profile of the MessagingModel port, and trace ids are minted by Run Control).
Families¶
| Family | Coordinators | Workflows | Service capabilities | Retired |
|---|---|---|---|---|
| Project Initialization & Session Management | 6 | 1 | 2 | 3 |
| Planning, Intent Routing & Product Vision | 7 | 5 | 2 | 0 |
| Architecture, Domain Modeling & Bounded Contexts | 5 | 1 | 4 | 0 |
| Blueprint & Microservice Assembly | 6 | 3 | 2 | 1 |
| Event-Driven Architecture & Messaging | 4 | 1 | 2 | 1 |
| API & Gateway Design | 4 | 2 | 2 | 0 |
| DevOps, Infrastructure & Environments | 6 | 2 | 4 | 0 |
| Testing & Quality | 4 | 2 | 2 | 0 |
| Observability, Security & Compliance | 5 | 1 | 4 | 0 |
| Documentation & Knowledge Management | 4 | 2 | 2 | 0 |
| Lifecycle Feedback & Governance | 9 | 4 | 5 | 0 |
| ChatOps, Runtime Commands, Developer Experience | 3 | 1 | 2 | 0 |
Workflow definitions behind the coordinators¶
Every coordinator realized as a workflow has its definition modelled in model/workflows/ and rendered as a page under Workflow definitions: steps, agents by id, gates, compensation and the events it starts on and emits. The family pages below link each coordinator card to its definition; the coverage page reports any workflow-realized coordinator without one (0 at the time of writing).
How a coordinator runs¶
sequenceDiagram
participant EV as Trigger event
participant RC as RunControlService
participant WE as WorkflowEngineService (BC-38)
participant AG as Agents
participant G as Gates (approvals by class)
EV-)RC: event (e.g. BlueprintValidated)
RC->>WE: run of the coordinator's workflow definition
WE->>AG: steps with context snapshots and tools
AG->>G: gated action (shared-write, production, publication, spend)
G-->>AG: approval bound to the exact version
WE-)RC: StepReady … WorkflowRunCompleted
RC-)EV: emitted events (e.g. GeneratedOutputRecorded)