Workflow — Architecture decomposition¶
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.
| Workflow id | architecture-decomposition · version 1 · Draft (Draft → InReview → Published → Deprecated, BC-04) |
| Coordinator | enterprise-architecture-coordinator · family Architecture, Domain Modeling & Bounded Contexts |
| Owner service | WorkflowEngineService (BC-38) under Run Control (BC-03) |
| Starts on | BlueprintValidated from BlueprintService (event) |
| Steps | 4 · gated 0 · agents 2 |
| Budget per run | 600000 tokens · cap 60.0 USD · 240 min |
| Descriptor | workflow-definition-v1 · schema |
| Status | target |
Decomposes a validated Vision Blueprint into bounded contexts and modules with their domain models, producing the Service Blueprint from which BlueprintService derives the context map.
Authored design, Draft (D54, D57)
These definitions were authored on 2026-10-14 from the coordinator cards as design assumptions. None is published, evaluated or has run; agents are named by id as design bindings, not as tested integrations.
Definition¶
flowchart TD
start(("BlueprintValidated"))
identify_contexts["Identify bounded contexts"]
model_domains["Model the domains"]
draft_service_blueprint["Draft the Service Blueprint"]
validate{"Validate the Service Blueprint"}
start --> identify_contexts
identify_contexts --> model_domains
model_domains --> draft_service_blueprint
draft_service_blueprint --> validate
done(("WorkflowRunCompleted"))
validate --> done
classDef gated stroke:#B45309,stroke-width:2px
Shapes: rectangle = agent attempt · double rectangle = tool call · stadium = human decision · diamond = condition evaluated by the engine · parallelogram = fan-out or join · circle = timer · cylinder = sub-workflow · flag = compensation. A thick amber border marks a gated step.
Steps¶
| # | Step | Kind | Runs | Gate | Class | Depends on | Retry | Timeout | Compensation | What it does |
|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Identify bounded contextsidentify-contexts |
agent | enterprise-architect |
none | read | — | exponential ×2 | PT30M | — | Names the contexts, their responsibilities and relationships from the blueprint's capabilities. |
| 2 | Model the domainsmodel-domains |
agent | domain-modeler |
none | read | identify-contexts | exponential ×2 | PT30M | — | Aggregates, entities, value objects, invariants and published events per context, in the ubiquitous language. |
| 3 | Draft the Service Blueprintdraft-service-blueprint |
agent | enterprise-architect |
none | sandbox | model-domains | exponential ×2 | PT30M | — | Assembles contexts, modules, operations and events into the Service Blueprint. |
| 4 | Validate the Service Blueprintvalidate |
condition | engine | none | sandbox | draft-service-blueprint | fixed ×2 | PT2M | — | BlueprintService validates against blueprint-service-v1; on success it derives the context map and the domain model. Condition: blueprint.valid. |
Gates and approvals¶
No approval is required: every step runs in the read or sandbox class; the agents' own tool calls still carry their classes (D21). Compensation steps run in reverse order of the succeeded steps on failure after the last checkpoint; a step without a compensation leaves its sandbox output in place and the run ends Failed with the evidence (ADR-0014, recovery not replay).
Inputs, outputs and events¶
| Direction | Name | Descriptor |
|---|---|---|
| in | vision-blueprint | blueprint-vision-v1 |
| out | service-blueprint | blueprint-service-v1 |
Starts on BlueprintValidated; emits BlueprintValidated, ContextMapDerived, DomainModelDerived, plus the engine's WorkflowRunStarted, StepReady, StepRunStateChanged and WorkflowRunCompleted / WorkflowRunFailed and Run Control's run and attempt events (ADR-0014).
Decisions and traceability¶
FR: FR-08 Validated artifacts with lineage · FR-11 Compatible templates and libraries through release gatesXL: XL-09 Generation yields a usable consumerFUX: FUX-11 Software Factory journeyADRs: ADR-0014, ADR-0024 · ADR index
Definition authored 2026-10-14 from the coordinator card enterprise-architecture-coordinator (D54); Draft until an evaluation gate (ADR-0021) and a review publish it as a BC-04 asset release.