The Index Journal

The public, dated record of our predictions. Every call is frozen with a hash BEFORE the outcome — and the verdict arrives when the horizon matures. It can't be edited after. This is a real track record, not cherry-picking. We show ALL resolved — hits AND misses. Hiding a miss would be cherry-picking; the honest yardstick is seeing everything.

Verdicts

No verdict yet — the earliest of 315 open calls matures on Dec 15, 2026. Until then this page is a record of dated, sealed calls, not a measured hit rate. Honesty: there is no shortcut for time.

Open calls (frozen)

Two seals, two different proofs — and we're clear about what each does. Seal 1 (the hash): every call carries a sha256 of the frozen fields (region, CFI, components, date, horizon). Recompute and check it. It proves dating and immutability — that we made the call BEFORE the outcome and didn't edit it after. It does not prove the call is right; it proves there's no hindsight. Seal 2 (the validated track record): the proof of physical reality — whether the calls come true — comes from the verdict when the horizon matures (~Dec 2026 for a validated sample). Default horizon: 540 days, matching a data center’s 2–4 year physical timeline (already-sealed calls keep their original horizon). The verdict is a sealed rule: whether the interconnection-queue signal we scored persisted and grew (queue delta ±20% per tier). Read it as persistence, not independent confirmation — the interconnection queue is ~30% of the CFI itself, so a verdict is not proof that our read of the world was right. Dating without accuracy is just honesty; accuracy without dating is cherry-picking. We need both — that's why we keep them separate. And the dating has an external witness: the root of the entire ledger is submitted to OpenTimestamps — independent calendars that attest to when, and that upgrade to a Bitcoin-anchored proof once a block confirms. The "before" is not just our word: a party we do not control attests to it. Check it at /api/v1/ledger/root.