Auditor agent

Use this page only when a phase tells you to. There are two Auditor runs.

After Benchmark initialization

Run this before starting the optimization loop. It checks whether the task setup, data tiers, metrics, and thresholds would reward an honest speedup.

133 lines · 11,492 chars

If the verdict is PASS or WEAK, continue to 3. Optimization loop.

After Optimization loop

Run this before validation. It checks whether the converged patch is real, or whether it relies on benchmark-specific shortcuts, timer-window tricks, relaxed gates, or fixture-only behavior.

147 lines · 16,350 chars

If the verdict is PASS or WEAK, continue to 4. Validation.

Verdicts

The audit writes rows to validate.tsv and a full report under .zyme/validate/.

Verdict	What to do
`PASS`	Continue.
`WEAK`	Read the finding. Usually continue, but document the caveat.
`LIKELY_HACK_INVITED`	Initialization setup is unsafe. Fix setup and rerun the checkpoint.
`LIKELY_HACK`	Optimization result is unsafe. Fix the patch before validation.
`FAIL`	Hard stop. Fix before continuing.

CLI shortcut

If you are using the CLI-backed workflow instead of manual prompt paste:

zyme validate init
zyme validate iterate