ReferenceData modelTeams
Teams
Team profiles, rosters, team game logs, standings rows, traits, and team-scoped identifiers.
The team-centered resources: canonical teams, roster projections, team game logs, standings rows, and team traits. Teams are scoped to a sport and may route through a home competition.
EntityTraitunionA typed fact attached to a canonical entity (a [`Team`], or anGameOutcomeenumThe result of a game from a team's own perspective. Derived (never stored) byRosterEntryListResponseobjectRosterEntryViewobjectThe wire shape of one roster entry. Owns the serialization here (the store'sRosterSourceenumWhich edge produced a [`RosterEntry`]: an [`Appearance`](crate::entities::Appearance)StandingsCapabilityobjectOne standings table the registry advertises for a competition's sportStandingsEntryobjectOne `(edition, entrant)` standings record (Workflow-1 task A3). The storedStandingsEntryListResponseobjectStandingsKindenumWhich shape a registered standings table has.StandingsTableobjectOne standings table for an edition (spec §6) — the `/standings/{table}` envelope,StandingsTableEntriesunionThe kind-tagged rows a [`StandingsTable`] carries. `MatchRecord` rows are byte-identicalTeamobjectA team, scoped to a single [`SportId`] (not a league).TeamGameLogEntryobjectOne row of a team's game log — a game rendered from *this* team's side: whoTeamGameLogListResponseobjectTeamIdscalarMinted entity id (`team_<base32>`).TeamListResponseobjectTeamRefobjectThe home/away team side of a [`MatchupCard`] — just enough to label theTeamTraitQueryscalarTeam trait filter in `kind:value` form, e.g. `represents_country:ARG`.