Skip to content

Workflow — Test plan

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 test-plan · version 1 · Draft (Draft → InReview → Published → Deprecated, BC-04)
Coordinator test-plan-assembly-coordinator · family Testing & Quality
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

Builds the Test Blueprint from the service and module blueprints: scenarios from features and invariants, a coverage matrix and the quality constraints, validated against the DSL.

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"))
    derive_scenarios["Derive the scenarios"]
    coverage_matrix["Coverage matrix"]
    draft_test_blueprint["Draft the Test Blueprint"]
    validate{"Validate"}
    start --> derive_scenarios
    derive_scenarios --> coverage_matrix
    coverage_matrix --> draft_test_blueprint
    draft_test_blueprint --> validate
    done(("WorkflowRunCompleted"))
    validate --> 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 Derive the scenarios
derive-scenarios		 agent test-generator none read — exponential ×2 PT30M — Acceptance scenarios from features, invariants and adverse branches.
2 Coverage matrix
coverage-matrix		 agent qa-engineer none read derive-scenarios exponential ×2 PT30M — Maps scenarios to contexts, operations and NFR targets; names the gaps.
3 Draft the Test Blueprint
draft-test-blueprint		 agent qa-engineer none sandbox coverage-matrix exponential ×2 PT30M — Writes the Test Blueprint with suites, data and environments.
4 Validate
validate		 condition engine none sandbox draft-test-blueprint fixed ×2 PT2M — BlueprintService validates against blueprint-test-v1. 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 service-blueprint blueprint-service-v1
in module-blueprints blueprint-module-v1
out test-blueprint blueprint-test-v1

Starts on BlueprintValidated; 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-08 Validated artifacts with lineageXL: XL-08 Evaluate before promotionFUX: FUX-10 Evaluation evidenceADRs: ADR-0014, ADR-0024 · ADR index

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