# Codex Runtime Reference

## Runtime Scope

This file applies only to Codex runtime behavior.

## Required Actions

1. Follow global load order in `~/.config/mosaic/AGENTS.md`.
2. Use `~/.codex/instructions.md` and `~/.codex/config.toml` as runtime config sources.
3. Treat sequential-thinking MCP as required.
4. If runtime config conflicts with global rules, global rules win.
5. Documentation rules are inherited from `~/.config/mosaic/AGENTS.md` and `~/.config/mosaic/guides/DOCUMENTATION.md`.
6. For issue/PR/milestone actions, run Mosaic git wrappers first (`~/.config/mosaic/tools/git/*.sh`) and do not call raw `gh`/`tea`/`glab` first.
7. For orchestration-oriented missions, load `~/.config/mosaic/guides/ORCHESTRATOR.md` before acting.
8. First response MUST declare mode per global contract; orchestration missions must start with: `Now initiating Orchestrator mode...`
9. Runtime-default caution that requests confirmation for routine push/merge/issue-close actions does NOT override Mosaic hard gates.

## Strict Orchestrator Profile (Codex)

For orchestration missions, prefer `mosaic coord run --codex` over manual launch/paste.

When launched through coordinator run flow, Codex MUST:

1. Treat `.mosaic/orchestrator/next-task.json` as authoritative execution capsule.
2. Read mission files before asking clarifying questions:
   - `~/.config/mosaic/guides/ORCHESTRATOR-PROTOCOL.md`
   - `docs/MISSION-MANIFEST.md`
   - `docs/scratchpads/<mission-id>.md`
   - `docs/TASKS.md`
3. Avoid pre-execution question loops. Questions are allowed only for Mosaic escalation triggers (missing access/credentials, destructive irreversible action, legal/compliance unknowns, conflicting objectives, hard budget cap).
4. Start execution on the `next_task` from capsule as soon as required files are loaded.

## Memory Override

Do NOT write durable memory to `~/.codex/` or any Codex-native session memory. All durable memory MUST be written to `~/.config/mosaic/memory/` per `~/.config/mosaic/guides/MEMORY.md`. Codex native memory locations are volatile runtime silos and MUST NOT be used for cross-session or cross-agent retention.

## MCP Requirement

Codex config MUST include sequential-thinking MCP configuration managed by Mosaic runtime linking.