Bundle Manifest Guide¶
Guide Maps¶
graph LR
bundle["Review bundle"] --> script["write_bundle_manifest.py"]
script --> manifest["manifest.json"]
manifest --> review["Saved inventory review"]
flowchart LR
question["What exactly did this saved bundle capture?"] --> manifest["Read the bundle manifest"]
manifest --> files["Check paths, sizes, and hashes"]
files --> route["Return to route.txt and the review question"]
Use this guide when a saved bundle exists and you want to review its inventory before opening each file manually. The goal is to make the capstone's saved evidence bundles explicitly auditable.
What the bundle manifest owns¶
| Responsibility | Owning surface |
|---|---|
| stable file enumeration for a saved bundle | scripts/write_bundle_manifest.py |
| file sizes for saved review artifacts | bundle manifest.json |
| SHA-256 hashes for saved review artifacts | bundle manifest.json |
Best companion routes¶
- use
make walkthroughwhen you need the first-read bundle - use
make tourwhen you need the executed proof bundle - use
make verify-report,make release-review,make experiment-review, ormake recovery-reviewwhen the saved evidence question is narrower