The Sealed-Forecast Protocol.
The methodology of record. How a forecast on this site is turned into something a stranger can falsify from public artifacts — without trusting the operator, the server, or the lineage. Seal, hash chain, falsifiability rubric, the 1-in-N derivation, calibration, and the limitations stated in the open.
This is the methodology of record. Everything else on this site — the advisories, the dashboard, the theater corpora — rests on one claim, and this essay is that claim stated plainly: every sealed advisory is independently verifiable from public artifacts by any third party with a SHA-256 utility and a calendar. You do not have to trust the operator, the server, or the lineage. You have to check the arithmetic. The protocol below is the machinery that makes that possible.
THE SEAL. To 'seal' a forecast is to publish it to public infrastructure — a YouTube upload and/or an X post — before the prediction window opens (T-0), with the SHA-256 digest of the advisory document published in the same post. The seal is non-custodial: there is no JYOTINT-controlled database that could be silently rewritten after the fact. The public upload timestamp is the timestamp. Lead time is measured from the seal to the materialization, both anchored to external infrastructure, neither under the operator's control.
THE HASH CHAIN. The SHA-256 digest is computed at upload and published alongside the call. Any later edit to the document changes the digest, so post-hoc tampering is detectable by anyone who recomputes it. The manifest of all seals is anchored into Bitcoin via OpenTimestamps: once a block confirms, that block's existence proves the manifest existed at or before block time. Three independent surfaces carry the proof — the YouTube upload time, the published digest, and the Bitcoin anchor — and none of them depends on a JYOTINT server remaining honest. The audit trail is widened further by Internet Archive snapshots, so the artifacts survive the loss of any single host.