# validation.tigzig.com

Published validation results for the cricket data served by the db-mcp API, refreshed
twice a day, every run published pass or fail.

WHAT IT IS
  Every layer of the chain that puts cricket data behind https://db-mcp.tigzig.com,
  checked and published:
    1. Cricsheet to master - the pipeline's own checks, including what cricsheet publishes
       against what the master holds.
    2. Master to served - a guard that compares the served copies with the master, slice
       by slice.
    3. Served data over the public API - referential integrity, null density, freshness
       and cricket-rule validity, run against the database engines behind the API. Most
       checks run on both engines and are compared row for row.
  Plus every anomaly the checks count, row by row, with the explanation where there is one.

CURRENT STATE
  Everything tallies, end to end. Served-data checks last run 11 Sep 2026, 23:20 IST (17:50 UTC).

USE THIS WHEN
  You want to know whether the cricket data behind the API is trustworthy before relying
  on it, or you want to see whether a number you think is wrong is a known issue.

MACHINE-READABLE
  https://validation.tigzig.com/index.md       tab 1, the pipeline checks, as markdown
  https://validation.tigzig.com/anomalies.md   tab 2, the anomalies row by row, as markdown

EVERYTHING ELSE ON THIS SITE
  https://www.tigzig.com/llms.txt