Codex Mind

From idea to validated code. Every gate visible.

Mind orchestrates Forge, Council, and the optional gated path to bundled Codex Hyper. Forge produces the bounded proposal; Council returns build, revise, or stop. When implementation is requested and the result is a blocker-free build, Mind shows the Hyper execution preflight and confirms authorization for the unchanged scope. Hyper then enters Relay, applies the approved change through one root writer, and returns PASS, FAIL, or UNKNOWN evidence.

The banner marks the start of the guided Forge-to-Council-to-Hyper path.

The pipeline

Forge proposes. Council decides. Hyper implements and verifies.

The Codex Mind pipeline IDEA FORGE COUNCIL HYPER · IMPLEMENT · VERIFY

How the guided run works

Five gated steps.

01

Start

If there is no proposal yet, Mind asks for the intended outcome and hard constraints.

02

Estimate once

One combined token estimate for Forge + Council only, shown and accepted up front. Hyper execution is not hidden inside it.

03

Forge

Five role prompts shape a bounded proposal. Forge can stop nonconverged and never exceeds three rounds.

04

Council

Council returns build, revise, or stop with blockers, dissent, confidence, and required verification.

05

Hyper execution

Mind shows the preflight and confirms existing authorization or obtains it if missing. Hyper enters Relay, applies the approved change through one root writer, runs the required checks, and closes only with no critical FAIL or UNKNOWN.

Mind orchestrates; Hyper owns implementation Mind invokes $codex-council:codex-hyper only after implementation intent, a build verdict, zero live blockers, unchanged scope, a complete handoff, and valid authorization for that scope. The preflight confirms existing authorization or obtains it if missing; material scope, risk, or sensitive actions require fresh authorization. Every Mind handoff enters Relay. Otherwise Mind stops without editing. If the bundled skill cannot be loaded, Mind returns the handoff instead of emulating it. Read how Hyper implements →

When to reach for which

Choose the workflow that matches the input.

Council alone

You already have a proposal and need structured review. Run Council →

Mind

You need Forge, Council, and the controlled implementation handoff in one guided path.

Hyper alone

You already have an authorized repository change and need implementation with explicit checks. See the method →

Use it

Hand Mind an idea.

In chat — give it an idea and say explicitly whether approved implementation should be offered:

Prompt example Use Codex Mind to forge a proposal for <your idea> and then run it through the council. Show me the combined estimate first, and end with a clear build / revise / stop call. If it is build with no blockers, scope is unchanged, and implementation is requested, hand the approved scope to $codex-council:codex-hyper and show its separate execution preflight.

Mind orchestrates the bundled skills. The CLI estimate shown for deliberation is only Forge + Council, summed:

# Estimate both stages up front (shown as one range), then accept once.
python3 scripts/codex_council.py estimate --topic "<idea>" --mode standard --type forge --token-budget compact
python3 scripts/codex_council.py estimate --topic "<idea>" --mode standard --token-budget compact
Know what the estimate covers The accepted deliberation estimate covers Forge and Council only, and the proposal—not full transcripts—moves between them. Hyper is included in the plugin but retains a separate execution preflight and authorization because implementation can edit the repository.