Bundle Manifest Guide¶
Guide Maps¶
graph LR
bundle["Saved bundle directory"] --> script["write_bundle_manifest.py"]
script --> inventory["bundle-manifest.json"]
inventory --> review["Stable bundle review"]
flowchart LR
question["Did the saved bundle include what I expected?"] --> manifest["Read the bundle manifest"]
manifest --> files["Check paths, byte counts, and hashes"]
files --> compare["Compare the inventory with the review route"]
Use this guide when the capstone's saved bundles are helpful but you need a precise inventory of what was written. The goal is to make bundle review reproducible without opening every file manually.
What the bundle manifest owns¶
| Responsibility | Owning surface |
|---|---|
| enumerating saved bundle files in stable path order | scripts/write_bundle_manifest.py |
| recording file sizes for review bundles | bundle-manifest.json |
| recording SHA-256 hashes for saved artifacts | bundle-manifest.json |
Best proof surfaces¶
tests/test_bundle_manifest.pyfor executable proof that the inventory stays stablemake inspect,make tour, andmake verify-reportwhen you want real saved bundlesBUNDLE_GUIDE.mdwhen you need to choose the right saved bundle first
Best companion guides¶
- read BUNDLE_GUIDE.md when the question is which saved route to build
- read INSPECTION_GUIDE.md when the next question is the content of the inspect bundle
- read PROOF_GUIDE.md when the next question is the strongest saved proof route