council

# Council Council is an optional judgment strategy, not a lifecycle or delivery gate. Use it when one fresh validator is insufficient for a named irreversible, high-blast-radius, or genuinely contested decision. 1. Freeze one question, acceptance surface, evidence set, and subject digest. 2. Give each judge an independent context and the same bounded packet. 3. Require each judge to cite evidence, disclose omissions, and return its own judgment without seeing other answers first. 4. Synthesize agreement and disagreement without majority laundering. Preserve minority evidence and unresolved assumptions. 5. Write `council-report.v1` and return it to the caller. ## Methodology-weighted agreement Agreement across differing evidence methodologies counts more than agreement within one. Record each judge's evidence methodology (for example: static reading, executing the subject, tracing history) alongside its judgment. A consensus claim must name at least two distinct methodologies among its supporting judges; otherwise report it as single-method agreement and weight it as one confirmation, however many judges share it. The named failure mode is echo consensus: unanimous judgment produced from identical inputs by one shared method, laundered as independent confirmation. ## Model-diversity axis When the caller pins judges to model profiles, record each judge's `model_identity` beside its methodology and context ID (see the `agent-native` model-dispatch recipe). Cross-mode...