Coordination Engine

Plan multi-domain work with coord_plan / coord_run / coord_enforce.

What you will learn

• coord_plan intent
• coord_run
• coord_enforce

Prerequisites

• Staging Engine — one Commit-Scope per commit
• Enforcement sessions
• Confidence Engine

Surface

What this feature does

Coordination Engine sequences cross-domain pipelines (staging → schema → confidence → commit). Use when a change spans multiple engines.

How to call it

Call these MCP tools through your AGS / tower-gov host — coord_plan, coord_run, coord_get, coord_validate, coord_enforce.. Prefer scan/get before validate/diff, and enforce only when the change set is ready.

1. coord_plan
2. coord_run attempt 1
3. Follow nextActions
4. coord_enforce

{
  "intent": "add auth refresh and bump minor",
  "domains": ["staging", "schema", "versioning", "confidence"]
}

What success looks like

Plan lists nextActions

coord_enforce ok when consulted

Common failure modes

Run without plan

Ignoring nextActions staging_split

Skipping coord_enforce before checkpoint

Related reference

• Architecture
• Staging scopes