council-reviewlisted

# Council of Experts — Multi-Model Validation > **⚠️ Status (2026-07-15, ADR-0008 FIX).** Command paths corrected `~/bin/` → `bin/` > (`bin/validate-plan` and `bin/review` are real and on PATH; `~/bin/` is empty). > **Not yet provisioned here, and deliberately not rewritten:** `~/.claude/council.yaml` > (absent — the binaries do not read it), a `claude-fable-5` wrapper (absent — Claude is the > host), and the **Codex** reviewer (`codex` absent). The real roster + config mechanism is a > **conclave/council design decision** (ADR-0008, handoff item 1), not a prune edit — until then, > treat the roster and `council.yaml` references below as *illustrative*, and rely on > `bin/validate-plan`'s own honest exit codes (voted / unavailable / broken → exit 2, no verdict). > > **Where that decision now lives (2026-07-17):** `docs/contracts/three-project-cohesion.md` — the > canonical map of the Conclave·Tessera·pr-arbiter system. The roster/config question is Open > decision **D1** (routing home: do these `bin/` wrappers collapse into conclave gateway calls?). > **Tension to carry into that decision — this skill is NOT shielded by anti-conflation guard (a).** > Guard (a) protects pr-arbiter's *union-recall code review* from conclave's "route, don't judge" > null. But council-review's **plan-VALIDATION** path (a panel judging one plan → approve/revise) is > **select-best, not union-recall** — the exact regime where conclave's null is a *genuine caution*, > not a false blocker. So: a mul