# Local recovery drill: Northbridge training archive

This is a **local, manually copied recovery exercise**. It is not a Mesh node,
network replication test, or evidence that a real archive has survived. The
corpus is wholly synthetic and CC0-licensed; see [`LICENSE.txt`](LICENSE.txt)
and the provenance fields in [`manifest.json`](manifest.json).

## Run it

Requirements: Python 3.9 or later; no packages or network access required.

1. Download this whole `recovery-drill` directory or copy it to a separate
   location. Save `manifest.sha256` outside the bundle folder before testing.
   This models a separately retained digest only: if both files come from the
   same website, it does not independently authenticate the publisher or
   protect against a coordinated replacement of the bundle and digest.
2. Verify the received bundle:

   ```sh
   python3 verify.py
   ```

   A valid bundle reports `PASS`. The check covers the manifest digest, exact
   declared corpus file set, byte sizes, and SHA-256 digests. It does not prove
   authenticity, truth, licensing, or completeness.

   Windows PowerShell users can run `py verify.py` from the extracted
   `recovery-drill` directory. If the Python launcher is not installed, stop
   here and use the browser exercise at the public recovery page; do not paste
   commands into an unfamiliar shell.
3. Test that a byte change is detected without altering your retained copy:

   ```sh
   python3 verify.py --self-test
   ```

   In Windows PowerShell, run `py verify.py --self-test`.

   It makes a temporary disposable copy, changes one file, and expects a
   checksum mismatch.
4. For a manual restore rehearsal, place a second copy in a clean directory,
   temporarily make the source copy unavailable, and verify the second copy
   using only its files and the separately saved digest. Record what you
   did, the time, and the exact output. Do not call this replication: the copy
   was staged manually.

Expected synthetic discrepancy: `board-snapshot.txt` records a provisional
12 mm, while the transcribed ledger records 10 mm for the same day. Preserve
both records and their status; do not silently resolve the conflict.

## What's included

- `corpus/`: four original fictional files.
- `manifest.json`: provenance, license, file sizes and SHA-256 digests.
- `manifest.sha256`: SHA-256 digest of the exact manifest bytes.
- `verify.py`: standard-library verifier and disposable negative-test mode.
- `LICENSE.txt`: license notice for the original synthetic content.

The bundle is a training fixture. Its successful verification demonstrates
only that these bytes match this manifest in your local copy.
