Local rehearsal / Genesis 0
Recover a tiny
archive.
Practice one inspectable recovery using a small, synthetic archive. Verify its manifest, stage a second local copy, make the first copy unavailable, then recover and verify from the second. The page offers a browser path and an optional terminal path; elapsed time has not yet been measured with beginners.
Materials / authored synthetic data
Download the sample archive
Download and extract the complete bundle. The archive contains the synthetic corpus, provenance and CC0 license, SHA-256 manifests, a standard-library verifier and a disposable negative-test mode. Your copy stays on your device.
- Download the complete recovery-drill.zip (extract it; keep its directory structure)
- Read the bundle instructions
- Download the Recovery Card (printable Markdown worksheet)
- Inspect manifest.json · Download the digest as a separate file
- Inspect verify.py · CC0 license notice
- Corpus: scenario and provenance, field notes, board snapshot, observation ledger.
Optional / No terminal
Verify a folder in this browser
First download the separate digest file above and keep it outside the extracted folder. Then choose the extracted release folder and that saved file. This checks that the selected manifest and corpus agree with the saved digest. Both downloads come from the same website, so this is not an independent authenticity check. Your selected files are read locally by this page and are not uploaded. Folder selection and browser SHA-256 support vary; if either is unavailable, use the matching terminal instructions below.
Choose a folder to begin. If folder selection is unavailable in your browser, use the terminal instructions below.
The negative check alters bytes only in temporary browser memory. It does not edit your downloaded files.
01 / Download and verify
Check the extracted archive
Optional terminal route. Download the digest file above and save it outside the extracted folder. Open a terminal in the parent directory that contains recovery-drill. These commands use macOS/Linux/WSL syntax; a PowerShell version follows.
cd /path/to/the/directory-containing-recovery-drill
EXPECTED_MANIFEST_SHA256="$(cut -d ' ' -f1 /path/to/expected-manifest.sha256)"
python3 recovery-drill/verify.py --expected-manifest-sha256 "$EXPECTED_MANIFEST_SHA256" Replace both example paths with real paths. Keep using this parent directory for the next step. In Windows PowerShell, open PowerShell in the parent directory and run:
$expected = (Get-Content "C:\path\to\expected-manifest.sha256" -Raw).Trim().Split(' ')[0]
python .\recovery-drill\verify.py --expected-manifest-sha256 $expected The first output line should be:
PASS: manifest, corpus file set, byte sizes, and SHA-256 digests match This checks the exact declared corpus file set and each listed size and SHA-256 digest against the saved digest file. The digest still comes from the same publisher and is not a digital signature; it does not establish who authored the manifest.
02 / Restore while the source is unavailable
Make a local copy, then restore it
Using your file manager, copy the extracted folder as recovery-copy. Rename the original folder to recovery-unavailable, then copy the backup to a new folder called recovered-drill. In the browser verifier, select recovered-drill and the saved digest while the original is unavailable. The terminal equivalent is:
cp -R recovery-drill recovery-copy
mv recovery-drill recovery-unavailable
cp -R recovery-copy recovered-drill
python3 recovered-drill/verify.py --expected-manifest-sha256 "$EXPECTED_MANIFEST_SHA256"
mv recovery-unavailable recovery-drill In PowerShell, use:
Copy-Item .\recovery-drill .\recovery-copy -Recurse
Move-Item .\recovery-drill .\recovery-unavailable
Copy-Item .\recovery-copy .\recovered-drill -Recurse
python .\recovered-drill\verify.py --expected-manifest-sha256 $expected
Move-Item .\recovery-unavailable .\recovery-drill The restored copy should print PASS while the original folder is renamed. If verification fails, keep the folders and inspect the output before cleanup. The final command restores the original folder name.
03 / Test integrity detection
Check that detection works
Use the browser's disposable alteration check above, or run the verifier's built-in test in a terminal. Both change bytes only in a temporary copy and check that a digest mismatch is detected:
python3 recovery-drill/verify.py --self-test PASS: detects deliberate changed file04 / Interpret the result
Review what the check proves
The negative check only changes its disposable temporary copy; the extracted bundle remains unchanged. This is a check of failure detection, not evidence of network transfer, automatic failover or independent storage.
05 / Record what you learned
A successful rehearsal is a small claim
- Which file records 12 mm, and which records 10 mm? Preserve the conflict instead of choosing a winner.
- Did the restore pass against the supplied digest, and did the alteration check fail as expected?
- What would change if both copies were on the same disk and that disk failed?
The bundle preserves two synthetic records with different provisional rainfall values (12 mm on the board snapshot; 10 mm in the transcribed ledger). Keep both and their provenance visible; a hash verifies bytes, not the rainfall claim. Record the exact output in the Recovery Card. This is a manually copied, same-computer rehearsal, not an operational Mesh recovery service.