Court Geometry
Schema Reference — Star
Complete schema docs for star tier (274 schemas)
Generated schema contract
Use star reference as the exact warehouse contract
This is the scorebook for the public model. Use it to verify final columns, constraints, and foreign keys, then switch to curated schema pages when you need table selection, grain guidance, or join patterns.
verify the exact public schema that analysts, tests, and exports depend on
the table name and constraint block tell you how to query without inventing columns
regenerate from schema metadata instead of hand-editing
Pick the public table family before reading columns
Dimensions, facts, bridges, derived tables, and analytics views all surface different grains and workloads.
Use constraints to keep joins honest
Foreign keys and nullability often answer the real question faster than the descriptions alone.
Switch to curated pages for judgment calls
This page proves what exists; curated schema pages help you choose the right surface for the analysis.
Coverage boundary
This contract page covers only outputs with generated schema entries
The star reference is the exact contract layer for outputs that currently have generated schema metadata. Some lineage-tracked outputs still sit outside this reference layer, so absence here is a coverage limit, not proof that an output does not exist.
An output counts as covered only when docs-autogen can pair a lineage-tracked output with a generated schema reference entry.
The remaining 0 outputs may still appear in lineage or curated docs, but they do not yet have this schema-backed contract layer.
Source of truth: docs/lib/generated/schema-coverage.json. Refresh it with uv run nbadb docs-autogen --docs-root docs/content/docs.
Next possession
Turn exact star contracts into working analysis
The generated star reference is the scorebook. These curated pages help you decide which public tables to start with, how they join, and where analyst-friendly shortcuts already exist.
Dimensions
Understand the identity and calendar tables that anchor most warehouse joins.
Facts & Bridges
Choose the smallest useful fact family before you write a single query.
Analytics Views
Check whether a pre-joined analyst surface already answers the question faster.
Schema Reference — Star
This tier contains 274 schemas.
Progressive scan
Open only the generated family and contract you need
The full board is still here, but it now stays grouped until you open a family or filter to the exact table you need.
Companion cuts
Turn exact public contracts into practical table choices
Once the star contract is confirmed, use curated pages to decide which table family or analyst shortcut fits the question.
Use dimensions for stable entity context
Start here when the query needs player, team, season, date, or venue anchors.
Pick the right fact or bridge grain
Use the fact scouting report to avoid starting from a wider or noisier table than necessary.
Check whether an analytics view already solves it
Look for a pre-joined outlet before rebuilding a common analyst surface by hand.
