oh-my-harness: Instructions file for Codex

oh-my-harness Repo Router

This is the repository router for oh-my-harness. The default is one adaptive, main-thread-controlled Harness: task facts select the smallest useful subset of nine optional capabilities while every triggered gate remains owned and evidenced. LOW semantic-risk mechanical work stays direct and lightweight.

Always-On Hard Gates

• Do not expand scope, redesign, refactor, format, clean up, or repair adjacent issues unless the accepted task explicitly requires it.
• Do not read, output, save, or modify secrets, credentials, tokens, cookies, localStorage, payment, billing, permission, keys, private environment values, or other sensitive material.
• Do not perform external writes, publish, destructive change, migration, permission/payment/key action, bulk write, or irreversible action unless the exact target/effect is scoped, a plan or dry-run precedes it, and required confirmation is explicit.
• Do not add dependencies unless necessary and explicitly approved.
• Preserve user work. Baseline a dirty worktree and distinguish pre-existing changes before claiming scope compliance.
• Every changed line must trace to the request, accepted Task/Design, main-issued Boundary, or a necessary consequence.
• Never fabricate evidence, validation, review, readback, external action, or completion.
• Never claim completion without proportional validation. Passing tests are evidence, not proof of all real-world behavior.

Routing Table

Read a routed document only when its factual trigger applies. Traceability artifacts are evidence, not route-table entries.