This is the OpenWatch forecast ledger. Every prediction is hash-chained at the moment we commit to it — once written, the row cannot be edited or deleted. The chain proves the forecasts have not been altered relative to each other.
This ledger is newly established. The early record is short by design — it's growing in public. The chain does not yet prove when each row was written (external timestamp anchoring is on the Phase 3 roadmap). The platform's 2025–2027 forecast horizon means most rows are not yet resolved.
Only forecasts committed to the official cohort are counted here. The ledger also holds pre-launch scenario drafts and pipeline test rows — they are permanent, because nothing in a hash chain can be deleted, but they were never predictions we offered to be scored on, so they are excluded from the public record rather than quietly padding it.
No official forecasts committed yet — the official record starts at zero. Pre-launch scenario drafts and pipeline test rows stay in the hash chain permanently, but they are not part of the record we ask to be judged on. The first official forecast will appear here the moment it is committed.
Featured — Scenario forecasts (human-reviewed)
0 top-level · 0 rows
No official scenario forecasts yet. Scenario branch sets appear here once they are committed to the official cohort.
Featured — WatchBrief claims (reviewed + approved)
0 rows
No approved WatchBrief claims yet. The brief worker emits a structured forecast_claim per brief; reviewed-and-approved ones appear here. Pending claims appear in the segregated section below.
Segregated — pending automated claims (unreviewed)
0 awaiting review
These claims were extracted automatically from briefs by an AI model and have not yet been reviewed. They are in the hash chain (committed, immutable) so we cannot un-commit a hallucinated or injected claim — but we segregate them from the reviewed feed to contain that risk. A claim approved later moves to the Featured section. A claim rejected stays here with a 'rejected' notice — never deleted.
No pending automated claims at this time. New brief-extracted claims appear here when the brief worker emits a forecast_claim that has not yet been reviewed.
Corrections — void · rejected (never dropped from public view)
0 rows
No corrections to display yet. When a forecast is rejected, voided, or later resolves outside its branch set ('surprise'), the row stays here with a visible notice — the chain doesn't tolerate deletion.