--- name: council description: Use independent strong models to propose and challenge solutions, synthesize a better decision, recheck the synthesis and resolve disputed assumptions with evidence. --- # Strong-model council Use for consequential uncertainty, a persistent difficult dead end or a material architecture decision where diverse frontier reasoning can change the answer. Do not convene it for every routine slice. Select several strong suitable available models, preferably with meaningfully different reasoning tendencies/providers when actually available. Record the real models. Multiple sessions of one model may be useful, but are not a multi-model council. If only one model is available, label the limitation rather than inventing participants. Council size/round count is chosen by value and evidence, not ritual. 1. Independent proposals: same raw problem, goals, constraints and verified facts; no preferred Lead plan to rubber-stamp. Each provides a recommended approach, critical assumptions, weaknesses and a discriminating check. 2. Cross-challenge: inspect alternative proposals, seek counterexamples, missing constraints and a genuinely stronger alternative. Hide author labels when useful. 3. Synthesis: a strong decision-maker selects or combines the best reasoning. Do not force incompatible architectures into a compromise. Retain important disagreement and track assumptions introduced by the synthesis itself. 4. Recheck the synthesized decision: fresh independent scrutiny addresses the actual combined result, not merely the component proposals already reviewed. 5. Test contested claims: run a small prototype, benchmark, reproduction or other discriminating experiment when feasible. Revisit the choice if evidence refutes it. Lead owns the selected solution. Majority agreement is not truth and unanimity is not required. One valid counterexample can outweigh multiple endorsements. Overseer ends unproductive debate or asks for an experiment; a stated unresolved assumption is better than manufactured consensus. Routine engineering decisions return to execution, not to a human ballot. Output a concise decision, reasons, material dissent, validation evidence, remaining uncertainty and the decomposition implications. Save detailed proposal receipts outside the Lead's active context using the existing evidence mechanism.