Skip to content

Workflow — Product 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 product-plan · version 1 · Draft (Draft → InReview → Published → Deprecated, BC-04)
Coordinator product-plan-coordinator · family Planning, Intent Routing & Product Vision
Owner service WorkflowEngineService (BC-38) under Run Control (BC-03)
Starts on BlueprintValidated 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

Builds the feature hierarchy, the edition scope and the roadmap-free dependency view from a validated Vision Blueprint, as artifacts for review.

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_features["Derive the feature hierarchy"]
    scope_editions["Scope by edition"]
    dependency_view["Dependency view"]
    store_artifacts["Store with lineage"]
    start --> derive_features
    derive_features --> scope_editions
    scope_editions --> dependency_view
    dependency_view --> store_artifacts
    done(("WorkflowRunCompleted"))
    store_artifacts --> 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 feature hierarchy
derive-features		 agent product-manager none read — exponential ×2 PT30M — Epics, features and stories with acceptance criteria from the goals and scope classes of the blueprint.
2 Scope by edition
scope-editions		 agent product-manager none read derive-features exponential ×2 PT30M — Assigns features to editions and marks MVP, stretch and non-goals consistently with the blueprint.
3 Dependency view
dependency-view		 agent product-manager none read scope-editions exponential ×2 PT30M — Orders features by dependency, without dates, and records the open decisions.
4 Store with lineage
store-artifacts		 agent product-manager none sandbox dependency-view exponential ×2 PT30M — Stores the plan artifacts with lineage to the blueprint version.

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 feature-hierarchy artifact-v1
out dependency-view artifact-v1

Starts on BlueprintValidated; emits ArtifactStored, 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-03 Read-only assessmentFUX: FUX-06 Source-backed artifactsADRs: ADR-0014, ADR-0024 · ADR index

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