councillisted

# Council — Structured Multi-Voice Decision Making ## Iron Law NO MAJOR DECISION WITHOUT AT LEAST TWO OPPOSING VIEWPOINTS. ## When to Trigger - Architecture choices (monolith vs microservice, SQL vs NoSQL) - Technology selection (framework, library, language) - Design decisions with no clear right answer - Trade-offs between competing requirements (speed vs quality, security vs usability) - User explicitly requests deliberation ## Process ### 1. Identify the Decision State the decision in one clear question. Example: "Should we use WebSockets or SSE for real-time updates?" ### 2. Summon 4 Voices (Parallel) Launch 4 independent subagents using the Agent tool, each with ONLY the question and relevant context (NOT the full conversation history — this prevents anchoring bias): | Voice | Role | Focus | |-------|------|-------| | **Architect** | Long-term correctness | Maintainability, extensibility, architectural alignment | | **Skeptic** | Challenge assumptions | Simpler alternatives, hidden costs, "what if we don't?" | | **Pragmatist** | Ship it now | Timeline, user impact, operational complexity, team skills | | **Critic** | Find the cracks | Edge cases, failure modes, migration risks, rollback difficulty | **Anti-Anchoring Rule**: Each voice receives only: - The decision question - Relevant codebase context (file paths, current architecture) - Their role and focus area They do NOT receive: the full conversation, other voices' opinions, or the user's leaning. ### 3. Sy