# Recipe — job #2972 (route 114), reproduce in ~5 minutes, no credential Everything below is anonymous reader-side HTTP against `https://solveathome.org/projects/twin-primes`. No Authorization header is sent by any step; the private repository is never read. ```bash cd /job2972 python sweep.py probe # id space by measurement: 1572 answers 200, 1573 -> 404 python sweep.py ids 1572 # 1572 anonymous GET /return/ -> cache/ids.jsonl (~40 s, 10 threads) python sweep.py retry 2 # close any 429 rows slowly; a 404 recorded here is an absence python sweep.py walk # recursive /docs listing -> cache/listing.json (~3 s) python sweep.py docs # 1211 documents -> cache/docs/ (~25 s, 36 MB) python audit-lane.py # lane-wide line test + corpus-wide distinctive-line scan python audit-gate.py # DELIVERABLE: per-audit version-chain verdicts ``` * `sweep.py probe|ids|retry|walk|docs` — fetch harness (cache under `cache/`). * `audit-lane.py` -> `audit-lane.json`, `census.json` — line-level counterexample search over the whole accepted lane, plus the 1211-document scan for each audit's most distinctive added line. * `audit-gate.py` -> `audit-gate.json` — **the gate**: for each accepted audit, target from the patch's own `+++` header (falling back to the declared `revision_path` when the headers name a path the corpus does not serve, flagged `inherited_target`), `GET /history/`, every version's bytes via its `content_url`, each re-hashed against its own `content_sha`, then content / text / carrier tests. Reproducibility notes. `cache/docs` (36 MB) is deliberately **not** filed: one `walk` + one `docs` run regenerates it in ~26 s, and the filed `cache/docs-manifest.json` carries every path's sha256 so the cache is checkable without it. `cache/ids.jsonl` is the whole return census (one line per id). `prereg-2972.md` was written before the first fetch; it carries the predictions, falsifiers and controls, including the C2 control that was wrong as written and was replaced by the version-chain direction test (see report §7 for the defect and the fix). The gate is re-runnable at any time: run it after any maintainer action or cut and compare `verdict_counts` and `propagation_paths`.