# Codex Harness

Use `templates/harnesses/codex/binding.json.template` when creating or converting a Codex-bound loop.

The Codex adapter maps portable sessions, delegates, and completions only from first-party tools actually present in the current runtime. Capability discovery is by callable tool contract, never child-system generation, experimental label, or product version. Capabilities without a complete launch, ownership, completion, and cancellation contract remain unavailable.

Before child mutation or review, require the environment and ownership checks in `launch-safety.md`. A failed launch blocks the mission and returns evidence; it never triggers an unverified compatibility fallback.

Completion criterion: the binding validates, the active runtime identifies as Codex, and every strategy required by the execution profile and orchestration brief is supported by currently callable certified capabilities. If only direct execution is certified, an adaptive loop may run directly; an `orchestrator-callback` loop blocks until separate sessions and structured completion are certified.