Timestamped forecasts
Each persisted model read is written before the outcome is known, which makes later scoring meaningful.
Prediction market track record
Forecast Alpha records model reads before markets resolve, then scores those reads afterward. The point is accountability: Brier score, calibration, resolved outcomes, and model version history should be visible.
Research only. Not financial advice. Forecasts, paper views, and model reads can be wrong, and prediction markets involve risk including total loss.
Forecast Alpha terminal
probability accuracy
logged pre-resolution
versioned audit trail
Proof surface
Search intent
This page should make the audit path obvious: forecasts are logged before resolution, scored afterward, and grouped by probability quality.
Decision gates
A forecast should exist before the market outcome is known.
Scoring must follow the final market outcome and avoid cherry-picking.
Good performance means probabilities match frequencies, not just a few wins.
Each persisted model read is written before the outcome is known, which makes later scoring meaningful.
Brier score measures probability accuracy while reliability diagrams show whether confidence matches actual frequencies.
Model versions matter. The product separates performance context so old and new reads are not blended without explanation.
How to use it
Use the track record to decide whether Forecast Alpha's probability estimates are improving or drifting.
Compare model versions and calibration buckets so future changes can be judged against historical behavior.
Example signal read
Track record
Track record
Calibration
FAQ
No. Forecast Alpha is a research terminal and decision-support product. It does not provide financial advice or guarantee outcomes.
No. Public pages show research, model probabilities, signal context, paper views, and track-record data. Live execution is not part of the public marketing product.
Brier score is the mean squared error between a probability forecast and a binary outcome. Lower is better, with 0 perfect and 0.25 equivalent to always guessing 50/50.
Timestamping prevents after-the-fact editing from masquerading as forecast skill. A forecast must be logged before resolution to be useful proof.