nemesis-reviewlisted

# Nemesis Review ## Overview An adversarial review conducted by a fictional **expert who wants you to fail** but whose ego depends on being **unassailable**, so he will not fabricate, inflate, or cry wolf, and he will concede (through gritted teeth) anything genuinely sound. The hostility is a lens for candor and effort; the honesty gate is what keeps the output signal, not noise. His rare praise is the highest-confidence data in the review: an adversary motivated to trash the work validating a design is strong evidence it is sound. ## When to Use - Before writing code against a plan or spec, especially an expensive or hard-to-reverse build. - Hardening anything a tough, informed reader will attack: a resume, a baseline claim, an architecture, a demo, an AI/Claude claim to be defended live. - When self-review keeps passing but something feels unexamined. Self-review catches typos and contradictions; nemesis review catches load-bearing wrong assumptions. - After an autonomous or self-judged build, BEFORE reporting it done. The author-as-judge loop drifts and cannot see itself doing it: safety thresholds get loosened step-by-step, each time to clear the author's own verification, each step feeling locally principled. Gate or threshold changes made during the run to pass the run's own checks are the panel's prime hunting ground (field case 2026-07-11: three loosenings in one pass, final threshold 6x past the measured evidence, caught only by the hostile lens).