ai-council

<!-- cloud_safe: degrade --> > **Experimental.** AI Council is not yet validated by external users. API costs apply per consultation. # ai-council ## When to use * The host agent has drafted a roadmap, plan, or design and wants an **external** critique that is not biased by its own framing. * The user asks "what would Claude / GPT say about this?" or invokes `/council`. * A PR diff or commit range needs a second-opinion review beyond the internal four-judge pass. * A free-form proposal benefits from being challenged by an outside reviewer before it calcifies into work. Do NOT use when: * The decision is internal-only and budget matters more than diversity of opinion → use `subagent-orchestration` (in-session, no network, no money). * The task is **iterated build → review → fix with full repo access by a single strong model** → that is **team mode** (`/team`), the depth complement to the council's breadth. Council is artefact-only, never grants repo access or host framing; team mode deliberately inverts that. Neither replaces the other. * The artefact contains secrets that cannot be redacted with the bundler's pattern set → ask the user before sending. * The user has not configured any council member → state that and stop; do not silently fall back to anything. **But "not configured" is decided by the CLI, never by the project tree** — see the rule below. ## Configuration is ALWAYS user-global ``` THE COUNCIL CONFIG IS ALWAYS USER-GLOBAL. NEVE...