PROOF-5 contract
Five gates, no invented trust score
Each gate contains two observable checks. A gate is complete only when both checks have public proof. A provider statement without a readable supporting record remains partial, however convincing the marketing sounds.
- P · Publication provenance
- The exact forecast can be traced to a genuinely pre-match public record.
- R · Record completeness
- The advertised denominator can be rebuilt from a complete eligible ledger.
- O · Outcome and metric definition
- The probability target, settlement rule and headline calculation are fixed.
- O · Out-of-sample protocol
- Model evaluation uses only information available before each prediction.
- F · Fair comparison
- Probability quality, uncertainty and a frozen baseline are reported together.
- Claim only
- A useful lead for further checking, but not evidence until the supporting artifact is inspectable
- JSON report
- Deterministic record of the user's selections, protocol version and explicit non-claims
Result meanings
Audit-ready does not mean independently verified
- Contradiction found
- The reported percentage does not match the supplied correct and settled counts.
- Not auditable yet
- At least one PROOF-5 gate is missing or supported only by a provider claim.
- Audit-ready
- All ten checks have user-declared public proof; the underlying artifacts still need independent verification.
No result is a provider rating, certification or promise that a model is accurate, profitable or trustworthy.
Efficient audit order
Verify one prediction before trusting an aggregate
Start with the smallest falsifiable unit: one exact forecast and its publication trail. Then test whether the advertised performance page can be rebuilt from every eligible record.
- 01
Open one record
Find the complete probability vector for the declared market, original publication time, kick-off and model identity.
- 02
Trace the archive
Confirm that misses remain browseable and edits create revisions instead of replacing the original.
- 03
Rebuild the sample
Match the headline denominator to its dates, leagues, markets, versions and exclusions.
- 04
Recalculate quality
Use proper probability scores, calibration, uncertainty and a frozen baseline on the same rows.
Evidence boundary
A checklist records observations; it does not authenticate them
This page never opens the entered URL. “Public proof” means the user says they found an inspectable artifact; it does not mean Football Proof AIverified the publisher, archive, hash, pipeline or data source.
- A matching hash proves byte identity, not historical publication.Use an independent archive, witness or signed publication trail when timing matters.
- A complete ledger proves transparency, not skill.Recalculate scores and compare the same rows with a relevant frozen baseline.
- A strong backtest does not guarantee deployment performance.Monitor drift, model changes and future out-of-sample results.
- No evidence audit proves betting value.Odds, transaction costs, limits and harmful gambling risk are outside this protocol.
Authoritative foundations
Why timing, probability scores and version identity matter
The protocol combines established timestamp, canonicalization, hashing, proper-scoring and time-ordered validation building blocks. These sources do not endorse this checklist or certify any result.
- RFC 3339.Date and time on the Internet: timestamps.
- RFC 8785.JSON Canonicalization Scheme.
- Brier (1950).Verification of forecasts expressed in probability.
- TimeSeriesSplit.Time-ordered cross-validation reference.