Files
stack/packages/mosaic/framework/runtime/codex/RUNTIME.md
Jason Woltje 319e21ddc0
Some checks failed
ci/woodpecker/push/ci Pipeline was canceled
ci/woodpecker/pr/ci Pipeline was canceled
feat(framework): P3 — extract Constitution (L0) + gut AGENTS dispatcher
Splits the 155-line thin-core AGENTS.md into:
- defaults/CONSTITUTION.md (L0): gates + integrity + escalation + block-vs-done
  + mode + two-axis precedence + hooks-are-the-gate + framework-PR firewall +
  structured-reasoning capability + tier-aware self-load. Capability-verb authored.
- defaults/AGENTS.md gutted to an ~80-line load-order dispatcher + guide table
  (kills the false "already in context, do not re-read" line).
- constitution/LAYER-MODEL.md: source-only governance spec (layers + precedence).

Non-regression wiring (fresh-install functional; upgrade-safety is P4):
- launch.ts injects CONSTITUTION.md before AGENTS.md (tolerant of un-reseeded installs)
- install.sh + file-adapter.ts seed CONSTITUTION.md (+ test fixture updated)

Runtime adapters: capability-verb the sequential-thinking binding; claude/codex/
opencode restate the REQUIRED hard-stop, pi binds to native thinking (gate=false)
— restores the force the adversarial review flagged as weakened.

Gate hardening (dual-engine review): identity denylist now covers examples/
(closes the Codex open-source gap), self-test-first, *.json in scope, ci.yml
typecheck depends on sanitization (fail-fast), L0 line-count ceiling (<=120).

Adversarial gate-preservation review: every original rule traced to L0, the
dispatcher, or a routed guide — nothing lost.

Refs #542, closes #574

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
2026-06-20 21:55:18 -05:00

2.3 KiB

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. Structured reasoning (Constitution) binds to the sequential-thinking MCP on this harness; it is REQUIRED — if unavailable, report the failure and stop planning-intensive execution.
  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.