bounded-orchestration-contract
Bounded Orchestration Contract
Use this skill only when separate planning, review, or independent execution slices materially improve a non-trivial task. Small or tightly coupled work stays with the root.
This is an opt-in coordination discipline, not a scheduler, model router, provider bridge, permission grant, or persistent configuration layer.
Authority
The root owns intent, canonical plan state, delegation decisions, integration, safety, verification, and the final answer. Planner and Reviewer are read-only. Executors receive only their bounded slice. Explicit no subagents or equivalent instructions disable delegation.
Plan protocol
Version every canonical plan. Use exactly these first-line states:
PLAN_DRAFT: first complete candidate plan.PLAN_REVISE: the current version has material findings.PLAN_APPROVED: the exact reviewed version may release executor work.
The Reviewer returns PLAN_APPROVED or PLAN_REVISE. Stop immediately on approval. Never exceed five total review rounds. If round five still returns PLAN_REVISE, halt before executor release and report unresolved findings.