# Define the forecast event before assigning a probability

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Define the forecast event before assigning a probability

ID: MHC-D-RESEARCH-0404 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/define-the-forecast-event-before-assigning-a-probability

A probability cannot rescue an event nobody defined.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- People are debating whether something is 'likely' without agreeing on exactly what would count as occurring.

### Avoid when

- A precise event can still be based on poor evidence; resolution clarity improves evaluability, not forecast accuracy.

### Explanation

Specify the event, observation window, resolution source and ambiguous edge cases before writing the probability. For continuous outcomes, define the threshold or interval being forecast. This makes later scoring possible and prevents forecasters from changing the meaning after seeing what happened.

### Checklist

- A third party can determine the outcome later without asking the forecaster what they originally meant.

### Example

Replace 'the rollout will probably be stable' with 'there is a 70% chance that no Sev-1 rollback-triggering incident occurs during the first seven days after full rollout.'

### Check

A third party can determine the outcome later without asking the forecaster what they originally meant.

### Limits

- A precise event can still be based on poor evidence; resolution clarity improves evaluability, not forecast accuracy.

### Evidence and sources

- supports: Strictly proper scoring rules are designed so that a forecaster minimizes expected loss by reporting their actual probability belief rather than strategically distorting it. — RS-58E31CFFFB569015. A proper score rewards honest probabilistic reporting; it does not guarantee that the underlying belief is well informed. (Definition and motivation of proper scoring rules)
- RS-58E31CFFFB569015: Proper Scoring Rules for Estimation and Forecast Evaluation — https://www.annualreviews.org/content/journals/10.1146/annurev-statistics-042424-050626

No review details supplied.
Related (use_before): https://vedokrok.com/knowledge/score-your-probability-forecasts-instead-of-remembering-the-wins
