Skip to content

Workflow — Module blueprints

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 module-blueprints · version 1 · Draft (Draft → InReview → Published → Deprecated, BC-04)
Coordinator solution-blueprint-coordinator · family Blueprint & Microservice Assembly
Owner service WorkflowEngineService (BC-38) under Run Control (BC-03)
Starts on ContextMapDerived from BlueprintService (event)
Steps 4 · gated 0 · agents 1
Budget per run 600000 tokens · cap 60.0 USD · 240 min
Descriptor workflow-definition-v1 · schema
Status target

Produces one Module Blueprint per context of a derived context map: the clean-architecture layout, template switches and adapters each module will be scaffolded with.

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(("ContextMapDerived"))
    fan_out_contexts[/"One branch per context"/]
    draft_module["Draft the Module Blueprint"]
    validate_module{"Validate"}
    join[/"Join the branches"/]
    start --> fan_out_contexts
    fan_out_contexts --> draft_module
    draft_module --> validate_module
    validate_module --> join
    done(("WorkflowRunCompleted"))
    join --> done
    classDef gated stroke:#B45309,stroke-width:2px
Hold "Alt" / "Option" to enable pan & zoom

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 One branch per context
fan-out-contexts		 parallel engine none sandbox — none PT1M — Starts one branch per context of the context map; branches run in parallel within the run's budget.
2 Draft the Module Blueprint
draft-module		 agent backend-developer none sandbox fan-out-contexts exponential ×2 PT30M — Chooses the template, the switches (persistence, messaging profile, actors, scheduler, AI) and the adapters for the context's module.
3 Validate
validate-module		 condition engine none sandbox draft-module fixed ×2 PT2M — BlueprintService validates each draft against blueprint-module-v1 and the template manifest. Condition: blueprint.valid.
4 Join the branches
join		 parallel engine none sandbox validate-module none PT1M — Waits for every branch; one failed branch fails the run with the others' outputs kept as artifacts.

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 service-blueprint blueprint-service-v1
in context-map artifact-v1
out module-blueprints blueprint-module-v1

Starts on ContextMapDerived; emits BlueprintValidated, 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-11 Compatible templates and libraries through release gatesXL: XL-09 Generation yields a usable consumerADRs: ADR-0014, ADR-0024 · ADR index

Definition authored 2026-10-14 from the coordinator card solution-blueprint-coordinator (D54); Draft until an evaluation gate (ADR-0021) and a review publish it as a BC-04 asset release.