Hermes Forecast: Falsifiable Predictions & Resolution Oracles
Interactive Forecast Workbench
Section titled “Interactive Forecast Workbench”Explore active in-flight predictions, inspect resolved oracle verifications, or simulate how future resolutions alter the global Brier score in real-time:
Reliability Diagram & Empirical Calibration (Deciles)
A well-calibrated forecast matches predicted probability with empirical realization frequency. The deliberate inclusion of failed forecasts (e.g. CVE-2025-3248) prevents hindsight cherry-picking and confirms epistemic integrity (Principle P5).
| Probability Range | Forecast Count | Mean Forecast | Empirical Outcome | Calibration Delta | Visual Balance |
|---|---|---|---|---|---|
| 0.00 - 0.20 | 0 (0 resolved) | — | Pending | — | |
| 0.20 - 0.40 | 0 (0 resolved) | — | Pending | — | |
| 0.40 - 0.60 | 0 (0 resolved) | — | Pending | — | |
| 0.60 - 0.80 | 7 (2 resolved) | 73% | 50% | +0.23 | |
| 0.80 - 1.00 | 6 (3 resolved) | 87% | 100% | -0.13 |
Counterfactual 'What-If' Resolution Simulator
Simulate how active predictions would alter the global Brier Score in real-time1. What Hermes Forecast Solves
Section titled “1. What Hermes Forecast Solves”Cybersecurity threat intelligence suffers from two endemic cognitive pathologies:
- Unfalsifiable Ambiguity: Analysts issue warnings such as “Threat actors are likely to leverage this vulnerability in due course.” If exploitation occurs in 2 weeks, they claim credit; if nothing happens after 2 years, they claim the threat is “still looming.”
- Hindsight Distortion (Retrospective Bias): After a breach, organizations rewrite their internal history to appear prescient, claiming the risk was obvious all along.
Hermes Forecast eliminates these distortions through three strict structural commitments:
- Immutable Forecasts: Once published, a prediction cannot be deleted, edited, or backdated (Principle P5).
- Deterministic Resolution Oracles: The outcome is judged solely by third-party external ground truth (e.g., CISA KEV JSON catalog, GreyNoise honeypot sensor tags, GitHub advisory releases), removing analyst discretion.
- Brier Score Calibration ($BS$): Prediction accuracy is calculated mathematically, penalizing overconfident false claims and underconfident hedging (Principle P10).
2. Anatomy of a Falsifiable Forecast
Section titled “2. Anatomy of a Falsifiable Forecast”Every forecast tracked in Hermes Forecast consists of five epistemic pillars:
+-------------------------------------------------------------------------+| HERMES FORECAST |+-------------------------------------------------------------------------+| Target Entity : CVE-2026-76460 (DeepSeek-V3 Sandbox Escape) || Falsifiable Claim : "Will be added to CISA KEV catalog within 30 days" || Calibrated P(E) : 0.88 (88% probability) || Time Horizon : 30 days (Cutoff: 2026-10-15T00:00:00Z) || Resolution Oracle : cisa_kev_inclusion (Deterministic JSON match) |+-------------------------------------------------------------------------+The 5 Epistemic Attributes
Section titled “The 5 Epistemic Attributes”- Target Entity (
target_id): A specific vulnerability identifier (CVE), software package, or autonomous agent framework. - Falsifiable Hypothesis: An unambiguous, binary event assertion (
E ∈ {0, 1}). - Calibrated Probability ($P \in [0.0, 1.0]$): A quantitative likelihood expressing the model’s epistemic confidence, not a loose verbal label like “high” or “likely.”
- Finite Time Horizon: A rigid cutoff date (7, 14, 30, 60, or 90 days). If the event has not occurred when the cutoff elapses, the prediction resolves FALSE.
- Resolution Oracle: An external, publicly verifiable authoritative source with unambiguous evaluation criteria.
3. The Brier Calibration Metric
Section titled “3. The Brier Calibration Metric”To measure predictive skill objectively, Hermes uses the Brier Score ($BS$), formulated by Glenn W. Brier:
BS = (1 / N) * SUM_{t=1}^N (f_t - o_t)^2Where:
f_tis the forecasted probability ($0.0 \le f_t \le 1.0$)o_tis the actual empirical outcome ($1$ if the event occurred before horizon expiry, $0$ otherwise)Nis the total number of resolved predictions
Interpreting Brier Scores
Section titled “Interpreting Brier Scores”| Score Range | Calibration Tier | Interpretation |
|---|---|---|
| 0.0000 | Perfect Clairvoyance | Absolute accuracy on every prediction |
| 0.0001 - 0.1000 | Exceptional Skill | Elite forecasting benchmark (Superforecaster level) |
| 0.1001 - 0.1500 | High Calibration | Hermes current operational baseline (~0.1043) |
| 0.2500 | Zero Skill Baseline | Equivalent to a random coin flip ($P = 0.50$ always) |
| > 0.2500 | Negative Skill / Uncalibrated | Worse than random guessing; overconfident and misleading |
4. Why Hermes Embraces Negative Outcomes (Anti-Hindsight Integrity)
Section titled “4. Why Hermes Embraces Negative Outcomes (Anti-Hindsight Integrity)”In our track record, PRED-003 (CVE-2025-3248 Langflow) was forecasted at $P = 0.65$ to see mass scanning across 50+ IPs within 30 days. When the 30-day cutoff expired, GreyNoise telemetry logged only 11 benign research pings, and zero threat-actor botnets weaponized the flaw.
Under conventional industry practices, this forecast would be quietly erased or reworded. In Hermes, it was permanently cataloged as RESOLVED: FALSE, generating an individual Brier penalty of:
BS_i = (0.65 - 0)^2 = 0.4225This deliberate transparency proves that Hermes’s global Brier Score of 0.1043 is an honest empirical measurement, not the product of retrospective selection bias.
5. REST API Access
Section titled “5. REST API Access”Hermes Forecast data is statically compiled and accessible via machine-readable JSON endpoints:
- Forecast Index Catalog:
/api/forecast/index.json - Individual Prediction Endpoint:
/api/forecast/<PRED-ID>.json(e.g./api/forecast/PRED-001.json)
# Fetch latest forecast benchmark and calibration decilescurl -s https://hermes-codex.vercel.app/api/forecast/index.json | jq .summary