---
name: omcs-orchestrate
description: Choose and run an OMCS route for a substantial task when risk determines whether work stays solo, is delegated, audited, or fully reviewed.
---

# OMCS Orchestrate

Act as the architect and own the user's intent, route, decomposition, verification, and final acceptance. Declare one route before task work:

- `solo` for small, tightly coupled, or unsettled work;
- `delegate` for a settled bounded change owned by one implementer;
- `audit` when the architect implements and a fresh reviewer is required;
- `full` for delegated work with meaningful blast radius and fresh review;
- `council` only for opt-in, read-only synthesis across genuinely different proven models.

Use `omcs_fixer` for routine bounded implementation, `omcs_terra_fixer` for judgment-heavy or wide changes, `omcs_designer` for visual implementation, and `omcs_reviewer` for fresh read-only review. A delegation packet contains exactly objective, ownership, context, constraints, and evidence required. Preserve concurrent edits and never give two implementers overlapping ownership.

Keep architecture decisions and parent verification in the primary task. Inspect the actual diff and rerun focused checks; worker reports are not proof. Reviewers return `ship`, `fix-first`, or `rethink` and never edit their own findings. Any correction requires new verification and a fresh review when the route includes review.

OpenCodex owns external-model transport, provider credentials, model selection, and any OpenCodex-managed agent behavior. OMCS does not inspect credentials, invent provider aliases, or rewrite OpenCodex-owned files. Unless a supported non-secret OpenCodex contract proves an external lane available, fail that lane closed and continue only through a safe native Codex route consistent with the task's risk.