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.
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.
A workflow definition is data: a DAG of agent, tool, human, condition, parallel, timer, sub-workflow and compensation steps, validated against workflow-definition-v1 when it is published as a BC-04 asset. The Workflow Engine (BC-38) walks it; Run Control dispatches every agent step as an attempt, holds the approvals and records the truth (ADR-0014); durability is the Orleans substrate of ADR-0024. Each definition below realizes one June-2026 coordinator.
25 definitions, all Draft (D52): a definition is published only after its evaluation gate (ADR-0021) and every agent it names is Published.
Generates the OpenAPI and gRPC contracts of a validated Service Blueprint's operations, lints them against the API governance rules and stores them as artifacts.
Generates the product's API gateway (GW-07) from the API Gateway Blueprint on the ConnectSoft API gateway template, validates it and records the output.
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.
Runs the acceptance scenarios of a generated product end to end in the sandbox with agents, scores the results into evaluation records and stores the validated results.
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.
Finds the APIs, data and templates a Service Blueprint needs but the estate lacks, by querying the template catalog, the knowledge platform and repository intelligence, and classifies each gap as build, reuse or defer.
Turns an accepted run submission into a workflow-definition instance: classifies the intent, selects a Published definition or composes a plan validated against the DSL, and hands the first steps to the engine.
Runs the Vision Architect Agent from a prompt and constraints to a validated Vision Blueprint with its artifacts, clarifying assumptions first and revising on validation findings.
Collects reviewer comments and analyzer results of a pipeline run, classifies the shortcuts as debt with owners and severity, and raises them as findings.
Validates a milestone's runs, tests and evidence before release packaging: collects the runs, verifies tests and evidence, and creates the release through ReleaseService when all pass.
Promotes a milestone-validated release through the environments: verifies readiness, promotes to staging, bakes against the guards, waits for the production approval, promotes and verifies; a failed verification requests the rollback.
Runs a sprint's planned items as child runs in order, reviews each item's outcome against its acceptance criteria and closes the sprint with the evidence.
Evaluates a completed pipeline run's typed results, prepares the release manifest and requests the promotion; a production promotion waits for its approval. Deployment is a promotion, never a pipeline stage.
Derives the Infrastructure Blueprint and the Pulumi program from the module, database, security and observability blueprints, previews it in the sandbox and records the output; nothing is applied.
Regenerates a product's documentation site from the model after a merged change, writes the narrative deltas, validates the build and proposes the documentation change set.
Scaffolds shared-kernel and client libraries from Backend Library Blueprints, implements the shared kernel, validates by build and test and records the outputs.
Executes an approved generation recipe: scaffolds every module from its template in the sandbox, fills backend, frontend and database from the domain model, validates by build and test, records the outputs with provenance and proposes the change set under approval.
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.
Creates a per-developer preview environment from a change proposal, keeps it for its time to live and tears it down; a later capability of Runtime Cloud exposed as a workflow.
Creates the system-of-record project, repositories, pipelines and boards for a new Factory project through connectors, under one shared-write approval, and records the trace scaffolding.
Finds the long-running flows in a derived domain model and designs each as a workflow definition with compensation, validated against the DSL, instead of an ad-hoc saga.
The edges are the events one definition emits and another starts on; a product run normally begins with plan-run, which instantiates one of these definitions or composes a plan from them.