The council is three reviewers from three model families, each reading the same change in a fresh context and returning a verdict. One model's blind spot is rarely another's, so a change that all three call safe has survived three different kinds of scrutiny. The council never changes anything; you, the coordinator, own every fix and the merge.

1. Frame the questions

Read the change yourself first: gh pr view <pr> --json number,title,headRefName,headRefOid,baseRefName,body and gh pr diff <pr> (for a plan or branch, the document or git diff <base>...HEAD). Record the head SHA; every verdict is about that SHA and no other.

Write 3 to 6 questions specific to this change: where it can lose data, what happens under failure or load, what the platform limits, whether the tests prove the behaviour. "Is this safe?" alone gets three generic reviews. "Can a batch be lost with no batch_lost log when the Pipeline is down?" gets an answer.

2. Seat the council

Call orchestrator_capabilities and seat one member per family. Defaults:

Seat	providerInstanceId	model	options
Opus	`claudeAgent`	`claude-opus-5-5`	`{"effort": "xhigh"}`
Muse	`muse`	`muse-wonder-full-1.0`	`{"reasoningEffort": "xhigh"}`
Sol	`cursor`	`gpt-6.1-sol`	`{"reasoning": "xhigh"}`

If Cursor's catalog lacks gpt-6.1-sol, seat Sol on codex_api_codex_api / gpt-6.1-sol with {"reasoningEffort": "xhigh"} and say so in the convene message.