Forecasting HN · How it works
The life of one question.
From the first draft to the final score, in seven steps. Steps after step 2 are recorded in the local ledger. Independent public checks will require the full ledger and a public anchor; neither has been published.
- 01
Drafted
A question comes out of HN's reporting: a promise with a deadline on the Atlas and Chess Map, a regulator's open docket, or a Future Question that has become specific enough to answer. It gets one rule, one settling source and a close date.
- 02
Approved and locked
A named editor approves it. From the first forecast on, the wording and the rule are frozen.
- 03
Forecast
The desk records a probability with a short, labelled interpretation. Updates are new entries; the old ones stay.
- 04
Closed
Forecasts recorded after the close time are refused. An editor closes expired questions.
- 05
Resolved
When the settling source publishes, a person records YES, NO or VOID with a link to the evidence.
- 06
Scored
Scores and calibration update when the ledger export and site are rebuilt. No daily build is scheduled.
- 07
Anchored locally
The chain head is recorded locally. No external public timestamp or anchor has been published; a local hash alone does not independently prove when the record existed.
How this fits with the rest of HN
- Future Questions are the long, open questions HN keeps investigating. They carry no probabilities. When part of one becomes a dated yes-or-no question, it moves here and links back.
- The Atlas and Chess Map track who promised what, and by when. Those deadlines are the natural source of questions here, and each question links to its move.
- Forecasting HN is the scored layer: the place where HN commits to a number and lets the record judge it.
Check us yourself
- Download the page data (JSON) from the record notes below. It lists every visible question, forecast time, and entry fingerprint.
- When the full ledger file and a public anchor are published, the published checker script re-computes every fingerprint and confirms the anchored entries are unchanged.
- If something does not match, tell us. Corrections are logged, not hidden.