Skip to content

Coordinators — Lifecycle Feedback & Governance

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.

The June-2026 coordinators of this family are realized in the 2026 design as workflow definitions executed by the Workflow Engine (BC-38) under Run Control, as capabilities of a service, or are retired because a platform owns the concern outright. A coordinator never runs outside a Factory run: its triggers are events, its gates are approvals of the stated class, and its outputs are events and artifacts with receipts.

ReleasePackagingCoordinator

Releases are assembled from succeeded pipeline runs with components and evidence (BC-24).

Realization service-capability
Owner service ReleaseService
Workflow definition —
Triggers PipelineRunCompleted
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits ReleaseReady
Detailed page this card
## RolloutStrategyCoordinator

Canary, blue-green and wave rollouts are promotions and fleet rollouts (BC-24, BC-36).

Realization service-capability
Owner service FleetRolloutService
Workflow definition —
Triggers ReleaseReady
Inputs —
Agents —
Gates production approval
Emits RolloutPlanned
Detailed page this card
## FeedbackLoopTrigger

Observability and user feedback become learning proposals reviewed by maintainers (BC-22).

Realization service-capability
Owner service FeedbackService
Workflow definition —
Triggers FeedbackRecorded, DriftDetected
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits LearningProposalRaised
Detailed page this card
## TechnicalDebtTracker

Tags shortcuts found by reviewers and analyzers as findings with owners.

Realization workflow
Owner service WorkflowEngineService
Workflow definition debt-review
Triggers PipelineRunCompleted
Inputs analysis results, review comments
Agents Code Reviewer Agent
Gates none (read and sandbox classes only)
Emits FindingRaised
Detailed page this card
## TraceabilityGraphCoordinator

The DAG of agents, commits, blueprints and events is artifact lineage plus provenance (BC-12, BC-15).

Realization service-capability
Owner service ArtifactService
Workflow definition —
Triggers —
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits —
Detailed page this card
## HumanApprovalEscalator

Approval points are decided by approval policy per action class (D21, ADR-0015).

Realization service-capability
Owner service ApprovalPolicyService
Workflow definition —
Triggers —
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits —
Detailed page this card
## SprintExecutionCoordinator

Runs a sprint's planned items as runs in sequence with reviews and evidence.

Realization workflow
Owner service WorkflowEngineService
Workflow definition sprint-execution
Triggers RunAccepted
Inputs sprint plan
Agents Project Manager Agent
Gates none (read and sandbox classes only)
Emits RunCompleted
Detailed page platform-architecture/coordinators/sprint-execution-coordinator.md
## MilestoneLifecycleCoordinator

Validates a milestone's runs, tests and evidence before release packaging.

Realization workflow
Owner service WorkflowEngineService
Workflow definition milestone-lifecycle
Triggers RunCompleted
Inputs milestone plan
Agents Project Manager Agent, QA Agent
Gates none (read and sandbox classes only)
Emits ReleaseCreated
Detailed page platform-architecture/coordinators/milestone-lifecycle-coordinator.md
## ReleaseCoordinator

Promotes a milestone-validated release through environments with the promotion gates.

Realization workflow
Owner service WorkflowEngineService
Workflow definition release
Triggers ReleaseReady
Inputs release
Agents DevOps Agent
Gates production approval
Emits PromotionRequested
Detailed page platform-architecture/coordinators/release-coordinator.md