melech-consultlisted

# Consult When an AI proposes an architecture, implementation plan, or idea, asking the *same* conversation thread *"are you sure?"* fails: - It suffers from **self-grading bias** (eagerly rationalizing its own proposal). - It suffers from **thread fatigue** (trapped in the same assumptions and blind spots). - It agrees too easily with whatever direction was already discussed. `melech-consult` is a **machloket l'shem shamayim**: a disagreement in service of finding what is true and useful, not winning. Take the proposal off the author's desk and into the beit midrash. Find the consequential tension inside it, then constitute **Beit Hillel** and **Beit Shammai** around the two strongest coherent readings. At standard and deep effort, give each house a fresh isolated model from a different provider when available. The houses argue the question, not the user. Neither is a disposable devil's advocate. The result is not flattened consensus. Deliver a **psak for now** while preserving the minority opinion and the conditions that should reopen the decision. --- ## When to Reach for Consult Reach for `melech-consult` **after a direction, plan, or architecture has been proposed** and you want it proofed before building: - *"Double-check this implementation plan before we start coding."* - *"Proof this architecture with another model."* - *"Are you sure about this fix? Get a second opinion."* - *"I can see two valid sides. Argue both before we choose."* - *"Convene Beit Hillel