Skip to main content
reticle hunt is arithmetic, not driving. You point it at a directory of crawl reports (one JSON file per checkout, each produced by reticle_crawl) and it turns the pile into the one number the core claim needs: across N already-merged, already-green changes, how many carried a candidate false green?
No control arm is needed. Those changes shipped, so the counterfactual is already established.

Arguments

Each input file is read for label (falling back to the filename), anomalies[], and stepsRun.

What it prints

One reticle_hunt line with the summary:

Exit codes

Always 0. A read failure is logged as reticle_hunt_failed. Omitting the directory is a usage error:
That path exits 1.

Worked example

Last modified on August 14, 2026