Skip to content

Coordinators — Project Initialization & Session Management

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.

ProjectInitiator

Validates and seeds a new Factory project request; the Control plane's ProjectService owns it.

Realization service-capability
Owner service ProjectService
Workflow definition —
Triggers CreateProject
Inputs project request, edition
Agents —
Gates none (read and sandbox classes only)
Emits ProjectCreated
Detailed page this card
## SessionManager

Orchestration session state, trace context and project tokens are the run's execution scope and resolved snapshot (ADR-0014); no separate session.

Realization retired
Owner service RunControlService
Workflow definition —
Triggers —
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits —
Detailed page this card
Modernization note (2026): Replaced by ExecutionScope and ResolvedExecutionSnapshot.
## UserInputValidator

Validates the run submission (prompt, metadata, blueprint hints) against run-submission-v1 at acceptance.

Realization service-capability
Owner service RunControlService
Workflow definition —
Triggers RunSubmitted
Inputs run submission
Agents —
Gates none (read and sandbox classes only)
Emits RunAccepted
Detailed page this card
## ProjectBootstrapOrchestrator

Creates the system-of-record project, repositories, pipelines and boards through connectors and records trace scaffolding; shared-write class through the propose-change-set and MCP tools.

Realization workflow
Owner service WorkflowEngineService
Workflow definition project-bootstrap
Triggers ProjectCreated
Inputs project, system of record connection
Agents DevOps Agent
Gates shared-write approval when policy requires
Emits ChangeProposalOpened
Detailed page platform-architecture/coordinators/project-bootstrap-orchestrator.md
## TraceabilityAnchorInitializer

Root trace and project ids are minted by Run Control at acceptance and carried by the envelope; no coordinator needed.

Realization retired
Owner service RunControlService
Workflow definition —
Triggers —
Inputs —
Agents —
Gates none (read and sandbox classes only)
Emits —
Detailed page this card
Modernization note (2026): traceId is diagnostic correlation in the ADR-0014 envelope.
## ArtifactRegistryInitializer

Artifact placeholders are not needed: artifacts are content-addressed when produced (BC-12).

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