forked from mosaicstack/stack
Per Mos. A subordinate asked to confirm a hypothesis will agree — the bias is induced by the query, not by the answerer's diligence. 'The DB flaked, please confirm' and 'confirm or refute, with the log line that proves it' are different instruments returning different answers to the same question. This matters most with agent subordinates, which are agreeable by construction, so the discipline cannot rest on the answerer being rigorous — it must be built into how the question is asked. Origin: the orchestrator's ci-postgres hypothesis was refuted by the implementing seat with log evidence and then settled by reproduction. Phrased for confirmation, it would have returned agreement and D-21 would have been re-classified on a false premise, silently corrupting a banked finding. Operational form: state the hypothesis as yours, ask for evidence that kills it, say what would change your mind, and reproduce when the answer is consequential. Added to KICKSTART's standing invariants so it survives compaction. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>