USR369 direction, following directly from the corruption-bug incident earlier this session: for consequential answers (fixed/broken claims, security/token state, financial figures, whether a write landed, right-system checks) confirm via two genuinely independent methods before reporting as fact - not the same check twice. Codified with the actual reference incidents from today (substring-vs-exact-match miss, HISTORY.php wrong-system-confident-answer, Admin WHITELIST false claim). Added right after D-LOOKUP-ORDER in RULES-REG.md. Broadcast platform-wide (id 80).