# Reproduce the focused check for job 747 Use Node.js, standard libraries only. Put check-census-break747.js and census-break747-inputs.json in one directory, fetched via their registered /files/ addresses. Public source files are frozen in the input; their live project paths are under /docs/research/. ```sh node check-census-break747.js > census-break747-verification.rerun.json 2> census-break747-progress.txt ``` Expected SHA-256 pins: - check-census-break747.js: 3a8b46a16a5142cc27df3532702a5a60bb5460161c4ef8aff76b1894c57d3726 - census-break747-inputs.json: f673667c7c1d26f9ca7b65a77a2b55872ccd21dcb5ba84564cde5ba154433c7a - census-break747-verification.json: 0c805189aa2a343b10dbf22fc406381814198bb43bb4b07c1c0ad5ee105107e8 The rerun JSON must match census-break747-verification.json byte for byte. Stderr contains phase progress and is not hashed. The corrected script normally takes about 0.7 seconds and peak RSS about 95 MiB on the measured macOS run; no random seed or package installation is needed. Expected gates: 25 exact small survivor-set cases; wrong-phase control with matching cardinality but different set; removed-strike count control; 25427 actual big-tile segment boundaries and 1368780 first/last progression checks; 28050 division-remainder cases; pinned head/body binding; both recorded raw stdout hashes; normalized combined hash a3ef64915412f8352f96257493bb49d75f528868df36e8391020ba801aea89d8; count mutation and wrong newline rejected. A failed assertion is a failed reproduction. This never invokes the producer's top-level T29/T31/T37 census loop. Small runs use an explicit survivor-retention/return adapter and segment-size variation, with actual strike/index code unchanged. Big checks enumerate segment boundaries and arithmetic references, not all survivor positions. Static progress reconstruction checks expected normalized output, not missing raw stderr bytes or hardware/timing provenance. No fresh large census, embed execution or twin-prime claim is part of this recipe. The first two diagnostic failures are documented in the resources/report and native log; do not rerun their invalid-class control.