Validations

Cricket data · the data behind db-mcp.tigzig.com

Everything tallies, end to end

Served-data checks last run 19 Oct 2026, 11:20 IST (05:50 UTC). Refreshed twice a day, and every run is published, pass or fail.

The chain, in the order the data travels

1. Cricsheet to master	The pipeline downloads the source, builds a master file, and runs its own checks before it lets the new master replace the old one. all 52 checks passed · 15 Oct 2026, 10:08 IST (04:38 UTC)
2. Master to served	A separate guard compares what db-mcp serves against what the pipeline says it wrote, slice by slice, so a stalled or half-applied refresh cannot look green. all 21 comparisons tally · 19 Oct 2026, 11:05 IST (05:35 UTC)
3. Served data, over the public API	This battery runs against what the API actually returns, on both engines, and publishes every result below. all 22 checks passed

1. Cricsheet to master

Last build that loaded new data: 15 Oct 2026, 10:08 IST (04:38 UTC), 46 matches added, 52 of 52 checks passed. Since then the pipeline has run 9 more times and found nothing new at the source; the latest was 19 Oct 2026, 10:08 IST (04:38 UTC).

Result	Check	Expected	Actual
PASS	ZIP vs DB match count (T20)	5810	5810
PASS	ZIP vs DB match count (ODI)	3213	3213
PASS	ZIP vs DB match count (TEST)	920	920
PASS	ZIP vs DB match count (IPL)	1243	1243
INFO	Cricsheet duplicate player-of-match rows	reported as filed, not corrected	1 match(es) list the same player twice: 1394759
PASS	Cricsheet published counts tally	our counts within 5 of cricsheet's published figures	exact tally on every format and gender
PASS	Source CSV matches DB values (sampled)	0 mismatches over 150 matches / 604,568 field comparisons	verbatim match
PASS	No unknown cricsheet info keys	37 consumed + 0 declined	no unknown keys
INFO	Non-match files in zips are skipped, not ingested	reported, not judged	1 skipped: ['IPL:all_matches.csv']

The other 43 checks the pipeline ran on that build, by family

Integrity of the master

Result	Check	Expected	Actual
PASS	No orphan ball_by_ball match_ids	0	0
PASS	No NULL match_type / start_date	0	type=0 date=0
PASS	No NULL team1/team2	0	0
PASS	No teams lost	131 old teams all present	131 teams, missing: none
PASS	Winner is team1/team2/NULL	0	0
PASS	Toss winner is team1/team2/NULL	0	0
PASS	No duplicate match_ids	0	0
PASS	No negative runs_off_bat	0	0
PASS	All wicket types recognized	known types only	all known
PASS	Schema identical (column names, order, types)	staging schema == live schema	identical
PASS	All expected tables present in staging	4 tables: ['match_info', 'ball_by_ball', 'match_players', 'people']	all present

Cricket rules in the master

Result	Check	Expected	Actual
PASS	Innings domain valid per format	TEST 1-4; ODI/T20 innings>2 only as a short super over	0 violations; max innings {'T20': 8, 'ODI': 4, 'TEST': 4, 'IPL': 6}
PASS	No innings exceeds 10 dismissals	max 10 per innings	0 innings over 10; observed max 10
PASS	No-result share per format in band	{'TEST': (12.0, 28.0), 'ODI': (2.0, 10.0), 'T20': (1.0, 8.0), 'IPL': (0.5, 8.0)}	in band: {'T20': 2.9, 'ODI': 4.9, 'TEST': 19.5, 'IPL': 2.0}
PASS	Duplicate ball slots explained by long overs	0	0 duplicate slots not inside a 10+ delivery over
PASS	Multi-value fields ordered and consistent	0 on every invariant	all consistent

Nothing lost since the previous run

Result	Check	Expected	Actual
PASS	Match counts by type+gender never regress	all segments new >= old	none
PASS	Delivery counts by type never regress	all types new >= old	none
PASS	Max date per type extends or stays	new max >= old max ({'T20': '2026-10-07', 'ODI': '2026-10-05', 'TEST': '2026-09-09', 'IPL': '2026-05-31'})	{'T20': '2026-10-14', 'ODI': '2026-10-14', 'TEST': '2026-10-09', 'IPL': '2026-05-31'}
PASS	All old match_ids preserved	11140 old ids all present	lost: 0
PASS	Spot-check: 50 old matches identical delivery counts	0 mismatches	0 mismatches
PASS	Retained matches: per-delivery values unchanged	identical sums over 11140 retained matches	no drift
PASS	Retained matches: metadata values unchanged	identical team/winner/toss/venue/date/gender profile	no drift

Player registry

Result	Check	Expected	Actual
PASS	Every match has a full player registry	0 matches with fewer than 12 named people	0 thin/absent
PASS	Player identifiers are 8-char hex	0	0
PASS	One row per person per match	0 duplicate names, 0 duplicate ids	names=0 ids=0
PASS	Player role values recognized	parts drawn from ['match_referee', 'player', 'reserve_umpire', 'tv_umpire', 'umpire']	all recognized
INFO	Registry names cricsheet does not place	reported, not judged	1542 rows with no role
INFO	Named officials absent from the match registry	reported, not judged	5 rows with no identifier
PASS	Ball-by-ball names resolve in the match registry	>= 99.95% of name references resolve	99.9937% (977 of 15,516,679 unresolved)

Player master

Result	Check	Expected	Actual
PASS	People identifiers unique	0	0
PASS	People row count in band	14,000 - 30,000	18,651
PASS	Every match identifier exists in people	0	0

Plausibility bands

Result	Check	Expected	Actual
PASS	Avg deliveries/match in expected band	{'TEST': (1000, 2500), 'ODI': (300, 700), 'T20': (150, 400)}	all in band
PASS	ICC classification distribution stable	per-class change <= 102 appearances	{"Full Member": 11463, "Associate": 6402, "null": 2486, "Associate-ODI": 2021}
PASS	Added match volume plausible	<= 1500 added	46

Post-deploy: live counts equal what was built

Result	Check	Expected	Actual
PASS	Post-deploy: live match counts == staging	{"IPL\|male": 1243, "ODI\|female": 617, "ODI\|male": 2596, "T20\|female": 2183, "T20\|male": 3627, "TEST\|female": 24, "TEST\|male": 896}	{"IPL\|male": 1243, "ODI\|female": 617, "ODI\|male": 2596, "T20\|female": 2183, "T20\|male": 3627, "TEST\|female": 24, "TEST\|male": 896}
PASS	Post-deploy: live delivery count == staging	5080431	5080431
PASS	Post-deploy: live match_players count == staging	296267	296267
PASS	Post-deploy: live people count == staging	18651	18651

Reported, not judged

Result	Check	Expected	Actual
INFO	Low-delivery matches (<20, abandoned)		17
INFO	Venue/city quality		venues 608->608, null city 634

Changes to matches already published

Result	Check	Expected	Actual
PASS	Old matches changed by this build (every column)	0 changed (observed only, never blocks)	no old match changed in any column

Changes to matches already published

Each build compares every match already in the master with the new build, column by column, in every table. When cricsheet corrects a match it published earlier, such as a player's name, a venue or a scorecard entry, the change is listed here with the old and new value. Corrections are applied, not held back. The last five builds are shown.

15 Oct 2026, 10:08 IST (04:38 UTC) · no match already published was changed; 46 new matches added

08 Oct 2026, 16:16 IST (10:46 UTC) · 5 matches already published changed; 62 new matches added

Match	Table	Column	Rows	Old value	New value
Portugal v Norway, 2025-04-07, T20 female	ball_by_ball	non_striker	29	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-07, T20 female	ball_by_ball	player_dismissed	1	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-07, T20 female	ball_by_ball	striker	40	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-07, T20 female	match_players	identifier	1	5ba89b11	41f8d757
Portugal v Norway, 2025-04-07, T20 female	match_players	person_name	1	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	ball_by_ball	fielder_1	2	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	ball_by_ball	non_striker	71	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	ball_by_ball	striker	59	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	match_players	identifier	1	5ba89b11	41f8d757
Portugal v Norway, 2025-04-08, T20 female	match_players	person_name	1	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	ball_by_ball	fielder_1	3	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	ball_by_ball	non_striker	66	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	ball_by_ball	striker	53	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	match_info	player_of_match1	1	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	match_players	identifier	1	5ba89b11	41f8d757
Norway v Portugal, 2025-04-09, T20 female	match_players	person_name	1	S Foo-Ryland	SV Collyer
Portugal v France, 2026-04-06, T20 male	ball_by_ball	fielder_1	1	Deep Harian	H Khuttan
Portugal v France, 2026-04-06, T20 male	match_players	identifier	1	79a29279	9c48bdee
Portugal v France, 2026-04-06, T20 male	match_players	person_name	1	Deep Harian	H Khuttan
Sweden v Indonesia, 2026-04-11, T20 male	ball_by_ball	bowler	13	Deep Harian	Ida Bagus Nara
Sweden v Indonesia, 2026-04-11, T20 male	ball_by_ball	player_dismissed	1	Deep Harian	Ida Bagus Nara
Sweden v Indonesia, 2026-04-11, T20 male	ball_by_ball	striker	1	Deep Harian	Ida Bagus Nara
Sweden v Indonesia, 2026-04-11, T20 male	match_info	venue	1	Udayana Cricket Ground	Udayana Cricket Ground, Bali
Sweden v Indonesia, 2026-04-11, T20 male	match_players	person_name	1	Deep Harian	Ida Bagus Nara

08 Oct 2026, 10:08 IST (04:38 UTC) · 5 matches already published changed; 62 new matches added; this build was held back by the pipeline's checks

Match	Table	Column	Rows	Old value	New value
Portugal v Norway, 2025-04-07, T20 female	ball_by_ball	non_striker	29	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-07, T20 female	ball_by_ball	player_dismissed	1	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-07, T20 female	ball_by_ball	striker	40	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-07, T20 female	match_players	identifier	1	5ba89b11	41f8d757
Portugal v Norway, 2025-04-07, T20 female	match_players	person_name	1	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	ball_by_ball	fielder_1	2	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	ball_by_ball	non_striker	71	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	ball_by_ball	striker	59	S Foo-Ryland	SV Collyer
Portugal v Norway, 2025-04-08, T20 female	match_players	identifier	1	5ba89b11	41f8d757
Portugal v Norway, 2025-04-08, T20 female	match_players	person_name	1	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	ball_by_ball	fielder_1	3	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	ball_by_ball	non_striker	66	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	ball_by_ball	striker	53	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	match_info	player_of_match1	1	S Foo-Ryland	SV Collyer
Norway v Portugal, 2025-04-09, T20 female	match_players	identifier	1	5ba89b11	41f8d757
Norway v Portugal, 2025-04-09, T20 female	match_players	person_name	1	S Foo-Ryland	SV Collyer
Portugal v France, 2026-04-06, T20 male	ball_by_ball	fielder_1	1	Deep Harian	H Khuttan
Portugal v France, 2026-04-06, T20 male	match_players	identifier	1	79a29279	9c48bdee
Portugal v France, 2026-04-06, T20 male	match_players	person_name	1	Deep Harian	H Khuttan
Sweden v Indonesia, 2026-04-11, T20 male	ball_by_ball	bowler	13	Deep Harian	Ida Bagus Nara
Sweden v Indonesia, 2026-04-11, T20 male	ball_by_ball	player_dismissed	1	Deep Harian	Ida Bagus Nara
Sweden v Indonesia, 2026-04-11, T20 male	ball_by_ball	striker	1	Deep Harian	Ida Bagus Nara
Sweden v Indonesia, 2026-04-11, T20 male	match_info	venue	1	Udayana Cricket Ground	Udayana Cricket Ground, Bali
Sweden v Indonesia, 2026-04-11, T20 male	match_players	person_name	1	Deep Harian	Ida Bagus Nara

26 Sep 2026, 16:13 IST (10:43 UTC) · built before this log existed

18 Sep 2026, 10:08 IST (04:38 UTC) · built before this log existed; 35 new matches added

2. Master to served

Checked 19 Oct 2026, 11:05 IST (05:35 UTC) against pipeline build 20261015_043812. Every published slice of the served copy is compared with the count the pipeline recorded when it wrote the master, in both directions.

Result	Slice	Master	Served
PASS	matches, IPL men	1,243	1,243
PASS	matches, ODI women	617	617
PASS	matches, ODI men	2,596	2,596
PASS	matches, T20 women	2,183	2,183
PASS	matches, T20 men	3,627	3,627
PASS	matches, TEST women	24	24
PASS	matches, TEST men	896	896
PASS	matches total	11,186	11,186
PASS	deliveries, IPL	295,732	295,732
PASS	deliveries, ODI	1,700,355	1,700,355
PASS	deliveries, T20	1,312,737	1,312,737
PASS	deliveries, TEST	1,771,607	1,771,607
PASS	deliveries total	5,080,431	5,080,431
PASS	max date, IPL	2026-05-31	2026-05-31
PASS	max date, ODI	2026-10-14	2026-10-14
PASS	max date, T20	2026-10-14	2026-10-14
PASS	max date, TEST	2026-10-09	2026-10-09
PASS	match players total	296,267	296,267
PASS	people total	18,651	18,651
PASS	null gender rows	0	0
PASS	null team type rows	0	0

3. Served data, over the public API

✓ passed ✗ needs review • reported as filed — could not be checked

What it proves	Result	Engines	Check
The two engines behind the API hold identical ball data for everything added recently.	✓	both agree · 5 rows	`engine_parity_recent`
The column list and its order have not changed, on any of the four published tables.	•	both agree · 104 rows	`schema_published_tables`
Table sizes, match counts and the date span they cover.	•	DuckDB only · 2 rows	`row_counts`
Format and gender mix, and the date span of each.	•	both agree · 7 rows	`matches_by_type`
No ball and no squad entry belongs to a match that does not exist.	✓	both agree · 2 rows	`orphan_balls`
Every match has ball-by-ball data behind it.	✓	both agree · 4 rows	`matches_without_balls`
Every player named in a squad exists in the player master.	✓	both agree · 1 row	`squad_integrity`
Every player in the player master has one unique identifier.	✓	both agree · 1 row	`reference_table_counts`
No missing venue, bowler, striker, runs or season.	✓	DuckDB only · 4 rows	`null_density`
Innings numbering and the ten-wicket ceiling hold in every format.	✓	DuckDB only · 4 rows	`format_shape_validity`
No T20 or IPL innings past over 19, no ODI innings past over 49.	✓	DuckDB only · 1 row	`over_index_bounds`
No delivery scores below 0 or above 8 runs.	✓	DuckDB only · 1 row	`negative_or_absurd_runs`
Each delivery can be pinned to one over and one ball within it, with no gaps and no duplicates.	✓	DuckDB only · 1 row	`delivery_numbering`
Every match records the toss, and the toss winner was playing in it.	✓	both agree · 4 rows	`toss_recorded_and_valid`
Every result is won by runs or by wickets, never both.	•	both agree · 4 rows	`result_margin_shape`
Every match is exactly one of won, drawn, tied or no result, and a super-over decision sits inside tied rather than beside it.	✓	both agree · 4 rows	`outcome_partition`
A super-over or bowl-out winner is always one of the two teams playing, and only ever appears on a tied match.	✓	both agree · 1 row	`tiebreak_fields_sane`
Recent matches are present, so the twice-daily refresh is running.	•	both agree · 34 rows	`recent_matches`
Test matches are current in the match table.	•	both agree · 5 rows	`recent_test`
Deliveries per over stay in a plausible range.	•	DuckDB only · 8 rows	`balls_per_over_extremes`
Innings counts per match are 1, 2, or a super over.	•	DuckDB only · 15 rows	`innings_per_match`
How often one delivery slot carries more than one row.	•	DuckDB only · 4 rows	`repeated_delivery_address`

Previous runs of the served-data checks

Run	Checks	Failed
19 Oct 2026, 11:20 IST (05:50 UTC)	22	0
18 Oct 2026, 23:20 IST (17:50 UTC)	22	0
18 Oct 2026, 11:20 IST (05:50 UTC)	22	0
17 Oct 2026, 23:20 IST (17:50 UTC)	22	0
17 Oct 2026, 19:41 IST (14:11 UTC)	22	0
17 Oct 2026, 19:23 IST (13:53 UTC)	22	1
17 Oct 2026, 18:54 IST (13:24 UTC)	22	0
17 Oct 2026, 11:20 IST (05:50 UTC)	22	1
16 Oct 2026, 23:20 IST (17:50 UTC)	22	1
16 Oct 2026, 11:20 IST (05:50 UTC)	22	1

Anything found is published as found. On the first run of this battery the two engines disagreed by one row - a Test match present in one and missing from the other - because the refresh job's skip test looked only at ball-by-ball data and a Test match adds none. That was fixed, and published rather than quietly corrected.

Machine-readable: /index.md for this tab, /anomalies.md for the anomalies, /llms.txt for what this site is.

Best used with an AI agent

Validations

The chain, in the order the data travels

1. Cricsheet to master

Integrity of the master

Cricket rules in the master

Nothing lost since the previous run

Player registry

Player master

Plausibility bands

Post-deploy: live counts equal what was built

Reported, not judged

Changes to matches already published

Changes to matches already published

2. Master to served

3. Served data, over the public API

Previous runs of the served-data checks