Model Coverage
Warehouse load and a typed API surface are two different completeness axes. A sport can have rows in Redshift and still ship no Pydantic model — and a registry key can exist with no rows at all. This is model coverage, not load.
Pydantic models
of 27 catalog registry keys carry a typed model.
Modelled
9
typed + shippable
Schema, no model
12
rows exist, unmodelled
Absent
14
no rows today
CLAUDE.md historically said '9 of 22'; live registry is 27 keys. This is model coverage, not warehouse load.
Modelled9
Registry keys with a Pydantic model — the typed, shippable surface.
Has schema, no model12
Warehouse rows exist, model missing — the highest-ROI modelling backlog.
race
match
judged
other observed
Absent from warehouse14
Registry keys with no schema rows today — modelling these invents empty surface.
Model the 12 sports that already have schemas (bkfc, f1, pbr, rawmotion…) bkfc, f1, pbr, rawmotion… before inventing empty ones.
Pulled with AWS_PROFILE=asd against Redshift Serverless (us-west-1 / default-workgroup / dev).