cross-model-verificationlisted

# Cross-Model Verification A second model catches what the first is blind to only if it is independent. Independence has two parts: the verifier comes from a different vendor than the author, and it never sees the author's reasoning or conclusion. A verifier that sees the prior conclusion anchors to it and confirms; a blind verifier keeps its edge. ## Prefer an oracle to an opinion Before asking a model, ask whether an executable check can decide it: tests, types, a compile, a property test, a reproduction. An oracle is deterministic and not fooled by a confident argument. Reserve model verification for what no oracle covers: design soundness, subtle logic, security reasoning, "does this actually do what it claims". ## Procedure 1. **Launch a verifier with the author vendor declared** via multi-agent-delegation's `scripts/delegate-run --role verify --author-vendor VENDOR --artifact ... --claim ...`. The resolver fails if it cannot route away from every declared author vendor. A second instance of the same model shares the same blind spots, and self-preference bias is largest when a model judges its own family's output (arXiv 2410.21819). 2. **Hand over the artifact and the claim, nothing else.** The verifier gets the diff, code, or document plus a crisp statement of what it is supposed to do or guarantee. Withhold the author's chain-of-thought, self-review, and justification. Information restriction is the point. 3. **Prompt it to refute, wit