# Try to break the evaluator before trusting it

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Try to break the evaluator before trusting it

ID: MHC-D-RESEARCH-1163 · Version: 0.1.0 · Kind: protocol
Source: https://vedokrok.com/knowledge/try-to-break-the-evaluator-before-trusting-it

If the agent can game the judge, a higher score can mean a worse system.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An automated evaluator will decide whether agent behavior passes, fails or improves.

### Avoid when

- Passing adversarial checks does not prove the evaluator is complete. New shortcuts can appear as the agent changes.

### Explanation

Design counterexamples that should clearly fail and see whether the evaluator catches them. Test shortcuts, superficial completion signals and plausible-but-wrong outputs. Repair the evaluator before optimizing the agent against its score.

### Steps

1. Create a clear true-pass case and a clear true-fail case.
2. Add a shortcut that looks successful but violates the task.
3. Add a plausible output with the wrong underlying state.
4. Inspect false passes before using the evaluator for model or prompt selection.

### Example

A desktop agent's evaluator checks that a file exists. Add a case where the file exists with the wrong contents; if it passes, the evaluator is too shallow.

### Check

The evaluator rejects the intentionally broken cases that matter to the task before its score is used as an optimization target.

### Limits

- Passing adversarial checks does not prove the evaluator is complete. New shortcuts can appear as the agent changes.

### Evidence and sources

- supports: A task evaluator should itself be challenged with cases designed to expose false passes before its score is used as a trusted optimization target. — RS-273F6FA5C48C6C0B. Adversarial evaluator tests improve confidence only for the tested failure modes; evaluator drift and unanticipated shortcuts still require monitoring. (9:04-10:50, tool changes the result and try to break the evaluator before trusting its score)
- RS-273F6FA5C48C6C0B: Computer-Use 2.0: Agents Just Got Multi-Cursor — https://ai.engineer/talks/ZSQb5fzRFPw-computer-use-2-0-agents-just-got

No review details supplied.
