Run Pipeline

Use the installed orchestrator-pipeline definition as the authoritative workflow. Keep actual role-model/tier selection in the effective Codex runtime/profile configuration and use the formal shared resolver for child-spawn effort only. Reasoning defaults to --reasoning=inherit; adaptive is the explicit selector-enforcement mode, while shadow computes without applying. --review=max remains an exact deep reviewer-only effort override, not certification or model routing.

Resolve the definition

1. Resolve the current workspace root.
2. Read ${CODEX_HOME:-$HOME/.codex}/agents/orchestrator-pipeline.toml as the authoritative workflow definition. Never manually adopt a repository .codex/agents/orchestrator-pipeline.toml; Codex project trust and effective config, not raw file presence, control workspace role routing.
3. Always query the installed global profile manager for current-workspace JSON status before adopting the workflow. A normal workspace without a profile reports global inheritance and may continue. If status cannot be verified or a configured profile's health is not ok, stop and ask the user to rerun workspace set or clear; never dispatch through an unhealthy or orphaned profile. If a configured profile's catalog_state is not current, stop before dispatch and require explicit workspace set --model-set openai or clear. If its profile_eligibility is not eligible, warn that Codex is ignoring the workspace layer and continue with global role routing. Only a healthy, eligible, current profile may route dispatched roles locally. For that eligible path, retain each role's exact saved resolved_configuration from the selected versioned model set and registered reasoning projection, including its configuration identity, version, and digest. Pass that same envelope to the formal shared resolver and trace expectations. The resolver selects effort only, so native managed normal dispatch omits a raw model; a Web session agent Job selects only the saved role model under protocols/REASONING_POLICY.md. Retired Codex model sets are not eligible for new dispatch.
4. If the global definition does not exist, stop and ask the user to run the global agents_pipeline Codex installer. Do not reconstruct the pipeline from memory.
5. Treat its developer_instructions as authoritative for decomposition, delegation, artifacts, review, retries, cleanup, and final reporting.

After the preflight succeeds, workspace profiles change effective role/model routing for dispatched agents; they do not replace this global workflow source inside the current/main agent.

Execute the workflow

1. Remove only the explicit $run-pipeline invocation token from the request. Preserve the remaining task text and pipeline flags as raw input.
2. Adopt the pipeline definition in the current/main agent. Do not spawn orchestrator-pipeline merely to enter the mode.
3. Obey the definition's hard constraints and delegation rules. If it routes scouting, implementation, testing, or review to helper roles, use those roles rather than bypassing them inline.
4. Resolve each dispatched role through protocols/REASONING_POLICY.md without changing the current/main agent. Native managed dispatch uses effective workspace/global Codex role routing, omits full-history forks and normally omits model; it verifies the local child trace before claiming adaptive enforcement. A Web session agent Job instead explicitly selects the saved role model, applies effort only in adaptive mode, observes one Job to terminal, and follows the policy's result and status limits without claiming native role identity. The sole native managed auto-recovery exception remains in protocols/CAPABILITY_RECOVERY.md and requires matching model/effort trace evidence. --review=max remains an exact reviewer-only effort gate: adaptive requests and verifies it on the native surface, shadow records it without applying it, and inherit conflicts. It remains deep ordinary review, never applies to a non-review role, and is unavailable on the Job surface until supported evidence exists. Do not rewrite role files.
5. Keep status, checkpoint, resource teardown, evidence, retry, and resume behavior exactly as required by the installed definition.
6. Return the definition's required user-facing synthesis, including changed paths, verification evidence, reviewer outcome, and explicit warnings or blockers.

Higher-priority runtime instructions and user approvals continue to apply.