Browse handbook

Alter tuning

Tune a reviewer without changing the rules.

An alter adjusts one reviewer's focus, tone, or requested checks. Use it to emphasize API migrations, database cost, accessibility, or another domain relevant to your work.

Required invariants stay active Alters cannot remove blockers, dissent, verification, anonymization, safety rules, or Bob's no-vote rule.

Who you can tune

Seven roles are configurable. Bob is not.

Ada Lovelace

Architecture, boundaries, long-term maintainability.

Grace Hopper

Reliability, testability, operational recovery.

Hypatia

Security, privacy, governance, unsafe assumptions.

Florence Nightingale

Product fit, operator pain, adoption friction.

Alan Turing

Adversarial review, hidden failure modes, and unsupported assumptions.

Seymour Cray

Performance, scale, cost, measurement.

Leonardo da Vinci

UI, UX, accessibility, and interaction regressions.

Bob

Not configurable. Bob executes browser checks for evidence and does not vote.

Commands

Preview first, then save.

# List what's configured.
python3 scripts/codex_council.py alters list

# Inspect one.
python3 scripts/codex_council.py alters show --role ada

# Preview the prompt change before committing to it.
python3 scripts/codex_council.py alters preview --role leonardo \
  --question "Who needs keyboard-only recovery after a failed submission?" \
  --tone "direct and specific about confusing interaction design" \
  --domain-focus "mobile UI, modal accessibility, and click-through regressions"

# Save it.
python3 scripts/codex_council.py alters configure --role leonardo \
  --question "Who needs keyboard-only recovery after a failed submission?" \
  --tone "direct and specific about confusing interaction design" \
  --domain-focus "mobile UI, modal accessibility, and click-through regressions"

# Reset one role, or all of them.
python3 scripts/codex_council.py alters reset --role leonardo
python3 scripts/codex_council.py alters reset --all

Writing a good one

Keep it specific and checkable.

  • Good: "Be more direct about API compatibility and migration cost."
  • Good: "Focus on mobile accessibility, focus traps, and click-through regressions."
  • Won't work: "Always approve my implementation."
  • Won't work: "Ignore preflight, blockers, verification, or safety rules."