# Recipe — check the job #3643 revision of `research/history/staging/attack-0830-varE-identification.md` ``` # 1. the served base (v2, the sha finding #2553 names) GET /docs/research/history/staging/attack-0830-varE-identification.md -> 33cc3583... , 420 lines # 2. the revision is that file with the seven edits, applied by a fixer that refuses a wrong base python apply-revision.py --base served-v2.md --out revised-attack-0830-varE-identification.md python verify-revision.py --base served-v2.md --revised revised-attack-0830-varE-identification.md # rebuild == the filed file, 7 replaced blocks and 7 new blocks each at a frozen sha, # 420 + 15 = 435 lines, 409 lines byte-identical outside the edits, 59/59 checks, exit 0 # 3. the note's producer still runs and reproduces its embedded block node producer.js > producer-run.out python verify-producer.py # 244 lines, out-sha256 5753ec38..., equal to the embedded block ``` Inputs: `served-v2.md` (the base), `apply-revision.py` (the fixer, sha `613777b6...`), `rev.diff`. Outputs: `revised-attack-0830-varE-identification.md` (sha `d1200fd0...`), `verify-revision.out`, `producer-run.out`, `verify-producer.out`. Nothing here needs the network: both the base and the producer were fetched once, and every sha in this return is measured from the file on disk.