Decision intelligence in 1.0

See the reasoning behind the verdict.

Codex Council already surfaces blockers, dissent, and verification. Decision Runtime turns that saved trail into an inspectable shadow, so you can follow what changed, compare a richer view with a simpler one, and keep the original decision untouched.

Why it matters

More signal. Less decision archaeology.

Trace the decision

Bring claims, risks, dissent, and verification into one trail; typed updates can add explicit links when they matter.

Keep dissent visible

A losing view does not disappear. It stays available beside the selected direction and the evidence that could reopen it.

Compare before committing

Decision Cells are checked against a compact frontier export from the same facts, with fidelity and size reported side by side.

Recover without drama

The shadow can be inspected, ignored, or removed while the original Council session remains usable.

How it fits

The verdict stays first. Insight sits beside it.

01

Run Council

Review, scoring, dissent, and Chairman synthesis work exactly as before.

02

Save the trail

The session keeps a compact evidence trail that stays easy to inspect later.

03

Opt into shadow

Decision Runtime projects an additional view only when you explicitly ask for it.

04

Inspect and compare

Explore the structured view without changing the saved verdict or forcing a migration.

Honest status

Experimental by choice.

Stable core

Existing sessions, artifacts, scoring, and verdicts remain the source of truth.

Opt-in shadow

The new view stays local, off by default, and outside the authoritative decision path.

Evidence before claims

1.0 makes no promise of measured token or latency savings. Replay and benchmarks come first.

Legacy-authoritative If the shadow is missing, unknown, or unhealthy, Codex Council keeps using the original session and verdict.

Explore 1.0

Start with the value. Open the internals only when you need them.

Upgrade without converting existing sessions, then explore the shadow on your terms. The Wiki keeps the full CLI, safety, and recovery contract.