models-consensus
Models Consensus
Turn one decision into independent model opinions, let them meet, and return a recommendation the user can act on. The council deliberates; implementation is a separate request.
Plan
- Choose the mode:
pollby default,debatefor a contested direction,personasfor five lenses from one model. - Choose the seats: the models the user names, then the
seatspreferences in.rar-skills/config.local.yamlwhen it exists, thenpython3 shared/scripts/model_routing.py council <technical|analysis|routine|security>for the question's shape. Poll and debate default to three seats on distinct models; seat every model the user names, with no upper limit. - Show the neutral question, mode, each role with its model, effort, and host route, and the expected and maximum calls. Ask: "Approve this council plan, or specify changes." Dispatch after a clear yes.
Seat fidelity: a seat speaks only through its approved model. A failed seat stays an observable failure in the report; a model change needs a new approval. Stop when fewer than two opening seats remain.
Seats
Each seat is one context that lives for the whole run. Its later turns (gap repair, the next debate round, a format retry) go to that same context, so it remembers what it argued. Every other role (organizer, moderator, judge, reviewer, synthesizer, chairman) gets its own fresh context, even on a model already seated. Contexts start without this conversation; they see the brief and what the protocol hands them. Peers appear only as anonymized digests labeled A, B, C.
Route each seat by host: