Eighteen-line router for Codex sessions working with prose commands and .prose.md contracts of kind responsibility, function, gateway, pattern, or test. Instructs the agent to embody the OpenProse VM in-session for prose run and never shell out to a prose binary unless the host provides one. Points to skills/open-prose/SKILL.md as the authoritative router and forbids searching for alternate docs copies. Prescribes prose upgrade --dry-run for legacy migration instead of the old migrate command, prose init and prose compose for progressive programs, and prose write for focused single-contract authoring. Asks runs that expose an OpenProse improvement to use prose run std/evals/prose-contributor with user approval before pushing, and to read CONTRIBUTING.md for the contribution bar. Codex agents at session start before running or authoring any contract.
OpenProse for Codex
If you're running in Codex and see a prose command, a *.prose.md contract (kind: responsibility, kind: function, kind: gateway, kind: test, or kind: pattern), or a mention of OpenProse, ProseScript, Forme, or Contract Markdown, OpenProse is the language you're being asked to run.
Treat prose run ... as an instruction inside the current agent session. Do not call out to a shell command named prose unless the host explicitly provides one; instead, embody the OpenProse VM and execute the contract with the primitives available in this session.
Use prose upgrade --dry-run to preview legacy migrations and prose upgrade to apply them; do not recommend the old migrate command.
Open skills/open-prose/SKILL.md and treat it as the authoritative router. Every command, every file routing decision, and every capability assumption lives there or behind a pointer inside it. Do not search the workspace for alternate copies of the OpenProse documentation — the canonical files are the ones bundled under skills/open-prose/.
Use prose init and prose compose for progressive program architecture; use
prose write for focused authoring when one Contract is already understood.
If your run exposes a concrete improvement to OpenProse itself, consider
prose run std/evals/prose-contributor -- subjects: <run-ids>. It turns run
evidence into one focused draft PR. It still needs explicit user approval before
using the user's GitHub identity to push a branch or open the PR. Read
CONTRIBUTING.md before selecting the patch; it is the public contribution bar.