# Model and Asset Bundle Verifier Complete offline manifest creation and verification for a directory of model or asset files. Python 3.10+ standard library; Tkinter for the native UI. No model runtime, additional purchase, pip packages or network calls. It never loads code or models. `python app.py` opens the JSON editor. CLI: `python checker.py examples/input.json new-manifest.json`. Then create verify input: `{"mode":"verify","root":"examples/assets","manifest":"new-manifest.json"}` and run `python checker.py verify.json new-result.json`. Optional expectedSha256 pins the manifest's exact byte hash from your trusted release record. Save all manifests/reports outside the bundle. Existing outputs are refused. Paths are absolute or relative to the working/product folder. Create requires explicit source/license metadata. The generated asset-bundle/1 manifest inventories relative paths, byte lengths and SHA-256. Verify reports every missing, unexpected or changed file and the manifest digest. Check matches, not just process success: a saved mismatch report is a successful inspection. Bounds: 1000 files, 1000 directories, 8GiB/file, 32GiB total, 2MiB manifest, 64KiB configuration. Hashes stream in 1MiB chunks. Links, junctions, multiple hard links, special files, case-colliding paths and duplicate JSON keys are refused. File state is compared before/after each hash and inventory is checked again. Empty directories are not part of the contract. A concurrently changed bundle must be quiesced and reverified; this does not lock the directory against later writes. Unsigned manifests do not establish trusted origin; independently pin the digest. Metadata is not rights verification. Byte equality does not establish model quality, runtime compatibility or safe deserialization. This general recursive asset format is distinct from the older flat model-bundle-manifest-v1 runtime-pinning format. Tests: `python -m unittest discover -s tests -v`. Native visual acceptance pending.