Codex Hyper · Evidence-backed implementation

Turn authorized scope into validated code.

Hyper is bundled with Codex Council. It selects Solo for contained, low-risk work or Relay when uncertainty, contracts, or blast radius justify bounded read-only explorers. One root agent owns every edit. Hyper records each required check as PASS, FAIL, or UNKNOWN and closes only when no critical gate remains unresolved. Relay adds a fresh read-only verifier.

Adaptive routing

Solo for bounded direct work. Relay for every Mind handoff or wider uncertainty.

Solo — one tight loop

For a direct, localized, reversible Hyper task with a clear path and deterministic check.

The root agent inspects, writes, tests, and reviews in one bounded loop.

Relay — evidence before and after

For every approved Mind handoff, plus uncertain, cross-module, or contract-sensitive direct work.

Read-only explorers narrow the path. The root writes. A fresh verifier challenges the result.

File count does not choose the route Every Mind handoff enters Relay. For direct runs, uncertainty and blast radius decide: public contracts, persistent data, auth, concurrency, build, deployment, or external state route to Relay. Hyper never uses parallel writers.

The method

Contract. Observe. Orient. Act. Falsify. Close.

Contract-first development, an Observe–Orient–Act loop, single-writer ownership, and an explicit attempt to disprove completion.

00

Contract

Define outcome, done, scope, constraints, risk, rollback, checks, and route before the first edit.

01

Observe

Read repository rules, code, tests, and worktree. Establish the smallest safe baseline.

02

Orient

Check claims against source and bind each acceptance criterion to a verification method.

03

Act

Apply small, reversible patches. Run focused checks after every meaningful increment.

04

Falsify

Challenge the contract, diff, and check results. Relay uses a fresh verifier; Solo reports its reduced independent coverage.

05

Close

Reconcile every done-when item with evidence. Any unmet required gate blocks completion.

Relay topology

One writer. A fresh verifier challenges the result.

Explore without touching

Each explorer gets one bounded read-only question and returns file-and-line evidence. No edits.

One writer integrates

The root checks the findings, protects existing user changes, and owns every patch.

Verify cold

A fresh verifier hunts regressions, missing criteria, unsafe scope, and reproducible counterexamples.

Claims need evidence Agents do not vote on correctness. When findings conflict, Hyper returns to the files or runs the smallest discriminating check.

Completion record

What a completed run reports.

Hyper marks a change complete only when every required gate passes. The final record includes:

  • Route and rationale — why Solo or Relay was the smallest justified topology.
  • Outcome and changed surfaces — what changed and what stayed out of scope.
  • Done-when evidence — each acceptance criterion mapped to a concrete result.
  • Checks and status — every required check and its result.
  • Falsification result — root review in Solo or a fresh verifier in Relay, with counterexamples and remaining uncertainty.
  • Rollback and residual risk — how to reverse the change and what remains unverified.
Prompt example Use $codex-council:codex-hyper to implement <change> with the smallest justified agent topology and evidence-backed verification.
Direct invocation or Mind handoff Invoke Hyper directly for a repository change authorized for that exact scope. Mind completes its execution preflight first and may hand over only an approved, unchanged scope after a blocker-free build verdict and valid implementation authorization. Every Mind handoff enters Relay; for direct runs Hyper chooses Solo or Relay. Hyper owns edits, checks, and falsification. A Council verdict never counts as permission to write.