VERIFY THIS CAPSULE OFFLINE — no network, no trust in JYOTINT required.

Requires: Node.js (any recent version). Optional: the OpenTimestamps CLI (`ots`) to resolve the Bitcoin block.

1) Confirm the .ots commits to these exact manifest bytes AND the call hash recomputes:
     node verify-jyotint.mjs --manifest seal-manifest.json --ots seal-manifest.json.ots --id LA-019
   exit 0 = pass. exit 4 = the .ots does NOT commit to this manifest (backdate handle). exit 2 = a hash drifted.

2) Resolve the Bitcoin block the proof commits to (independent of this archive):
     ots verify seal-manifest.json.ots
   Expect the manifest anchored on/around 2026-06-06 (≈ block 952785).

3) Anteriority: open each record's sourceUrl and read the platform's own upload timestamp.
   That upload time + the Bitcoin block are what establish the call predated the event —
   neither requires trusting any file in this capsule.

Only after the above passes is the method (Vedic jyotish, named openly) even relevant.
The verdict it supports: a verifiable, falsifiable, pre-sealed anomaly worth a look,
with a disclosed ceiling — an augmenting input, never a go/no-go decision authority.