I built Forecast Library because a prediction is difficult to evaluate fairly when the original values, dates and assumptions are scattered or later changed. The Library gives each forecast a stable record you can inspect, download and verify independently. It is built on Open Forecast Receipt, our open standard and verification toolkit. iPulse AI is the first production client; Forecast Library is a separate product operated by Future Edge Group. Public browsing requires no account, and outside publication requests are reviewed through support. A receipt proves integrity, not that a forecast is correct. Optional blockchain anchoring provides an additional timing reference; later evaluations and corrections remain separate records. I would welcome feedback from researchers and developers: what provenance fields or verification workflows would make these records most useful to you?

Forecast Library

Portable, verifiable receipts for public forecasts

Portable, verifiable receipts for public forecasts