Skip to content

Coordinators — Architecture, Domain Modeling & Bounded Contexts

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.

EnterpriseArchitectureCoordinator

Owns the system-level decomposition into contexts and modules, producing the Service Blueprint.

Realization workflow
Owner service WorkflowEngineService
Workflow definition architecture-decomposition
Triggers BlueprintValidated
Inputs vision blueprint
Agents Enterprise Architect Agent
Gates none (read and sandbox classes only)
Emits BlueprintValidated
Detailed page this card
## ContextMapper

The context map is derived by BlueprintService from a validated Service Blueprint.

Realization service-capability
Owner service BlueprintService
Workflow definition —
Triggers BlueprintValidated
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits ContextMapDerived
Detailed page this card
## AggregateModeler

Aggregates, entities and value objects are the derived domain model per context.

Realization service-capability
Owner service BlueprintService
Workflow definition —
Triggers BlueprintValidated
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits DomainModelDerived
Detailed page this card
## DomainEventClassifier

Published events are classified in the domain model and checked against the topic conventions through the envelope registry.

Realization service-capability
Owner service BlueprintService
Workflow definition —
Triggers DomainModelDerived
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits —
Detailed page this card
## ServiceOwnershipAssigner

Feature and service boundaries become the module plan of the recipe.

Realization service-capability
Owner service GenerationRecipeService
Workflow definition —
Triggers ContextMapDerived
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits —
Detailed page this card