Inspect the questions issued before outcomes, the evidence waiting for review,
and how reviewed forecasts compare with simple baselines. Event probability
and confidence in evidence are separate. Legacy history remains visible and ungraded.
Descriptive accountability metric — not a forecast
This page measures analyst-reviewed evidence coverage and calibration,
not future events. A high grade-rate means more forecasts were checked against
intel evidence; it is not a claim about what will happen. Calibration figures on a
small graded set are diagnostic only. PIE withholds a calibration rating until there are
at least 30 graded forecasts including an evidence-backed refutation.
Legacy automated verdicts remain in the audit history but do not count toward accuracy or calibration.
Engineering review queue
Bounded software candidates that passed protected evaluation but still require a human patch review. This read-only queue cannot approve, merge, deploy, promote, or change serving behavior.
Descriptive scores on the same questions. The earliest issued version is used; a later revision cannot replace an unreviewed original.
Loading prospective evaluation…
—Outcome records
—Grade rate
—Mass unverified
—Brier (graded)
The accountability funnel
How many resolved predictions survive to a real verdict
(confirmed/refuted).
Resolved calls — the actual verdicts
Every graded prediction: what PIE called, the
event probability it assigned, and the open-source evidence that confirmed or
refuted it. Newest first.
Why predictions go ungraded
Ungraded records need a valid analyst review or dated evidence.
Missing evidence does not establish whether a forecast was correct.
Grading coverage by impact tier
Graded (green) vs ungraded (red), split by the stakes of the call.
Reported probability distribution
Histogram of predicted probability across all resolved forecasts.
Reliability diagram
Each point is a probability bucket: x = predicted, y = observed
frequency. Points should sit on the dashed line. Bubble size = sample count.
Calibration by domain and impact
Calibration broken out by domain and impact tier: how often
each slice’s statements resolve true (confirmed share), how the stated
probabilities are (Brier, lower = better), and whether the
engine over- or under-states its confidence in that slice.
Methodology: groups computed in-browser from the same prediction_outcomes
payload; per-domain Brier prefers the resolver’s published
calibration_scores where available. Slices with fewer than 30 graded
calls are flagged low sample and make no confidence claim.
Grading rate by domain
Historical volume and reviewed coverage by domain.
Domain
Total
Graded
Rate
Retained ungraded outcome history
Original automated and unregistered labels remain inspectable. They do not count toward prospective calibration.
Loading historical records…
Loading prediction outcomes…
Source: prediction_outcomes via /api/data, generated by
prediction resolver.
Article matching suggests evidence for review. Only dated analyst reviews bound to the
exact forecast contribute to the graded rate; automated matches never decide a verdict.