Coordinators — ChatOps, Runtime Commands, Developer Experience¶
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.
ChatOpsCommandCoordinator¶
Chat commands arrive through chat connectors and are forwarded as Studio commands with the same gates.
| Realization | service-capability |
| Owner service | ConnectorRegistryService |
| Workflow definition | — |
| Triggers | DeliveryReceived |
| Inputs | — |
| Agents | — |
| Gates | none (read and sandbox classes only) |
| Emits | — |
| Detailed page | this card |
| ## DeveloperSandboxCoordinator |
Per-developer preview environments from a change proposal (later capability of BC-25).
| Realization | workflow |
| Owner service | WorkflowEngineService |
| Workflow definition | preview-environment |
| Triggers | ChangeProposalOpened |
| Inputs | change proposal |
| Agents | DevOps Agent |
| Gates | none (read and sandbox classes only) |
| Emits | PromotionRequested |
| Detailed page | this card |
| ## BotCommandRouter |
Developer queries route to agent skills or answers through the Studio's command surface.
| Realization | service-capability |
| Owner service | StudioBff |
| Workflow definition | — |
| Triggers | — |
| Inputs | — |
| Agents | — |
| Gates | none (read and sandbox classes only) |
| Emits | — |
| Detailed page | this card |