Methodology
How CDI publishes data
CasinoDataIndex is a structured data system. The public pages are a proof layer over that system: every visible field is sourced, dated, and validated. The notes below describe the rules that decide what appears here and what does not.
What CDI publishes
Public CDI pages expose only the datasets that are stable enough to stand on their own: market regulatory facts and operator basics. Everything else stays internal until it meets the same bar.
Source evidence
Every published field is attached to an approved official source — the regulator for regulatory facts, the operator's own properties for operator basics. The page shows the source URL and the date the value was last checked.
Validation
A record is published only if its required fields exist, foreign keys resolve, the source is active, and there is no unresolved conflict. Records that fail validation are suppressed from the public layer; the field never appears as 'N/A' or 'Unknown'.
Freshness
Each dataset has a fixed staleness window. When a value passes its window without being re-verified it is suppressed from the public page until an operator re-checks the source.
Conflicts
If two evidence-backed values disagree on a critical field, neither value is published. The conflict is queued for review and the affected page either drops the field or returns 404 if the field is contract-critical.
What CDI does not do
CDI is not a content layer. It does not interpret values, summarise sources, or rank operators. The public pages contain field/value/source/last-verified rows and nothing else.
Public datasets
These rules apply to the datasets currently exposed on CDI public pages.
- Market regulatory facts — Example market page
- Operator basics — Browse from your internal workspace or the contract API; slugs are stable per operator.