The Central Distinction
A user is not a driver. A user is the account holder who logs in and pays, usually a parent. A driver is the person who actually races. One user can hold several drivers, and almost every rule in the platform applies to the driver rather than the account.The Entities
Alongside those sit
Audit, which records changes, and the driver files and duplicate driver collections used by the dashboard’s triage screens.
What Joins Them
Everything is keyed on Vivenu’s identifiers rather than our own, because Vivenu is the source of truth for anything to do with a sale.
Ticket State
Every ticket resolves to a state, and the Operator Dashboard is essentially a queue of everything that is notFine:
That triage screen is the product. A new person should understand this table before anything else.
The Racing Vocabulary
Class code. The racing class a driver competes in, with hard limits on age, height, weight and permitted power levels. Configured per hub region. Power level. A performance tier. It gates which classes a driver may enter and which kinds of race they may contest. It is also what the telemetry converter asks GKL for when filing a run. Eligible parts. Tags on a ticket type describing what it grants, for example a race or a practice session. Two tickets sharing an eligible part are buying the same track time, which is how conflicts are detected. A ticket is a race ticket if any of its eligible parts is a race. Eligible classes. Which class codes a ticket type admits. Championship. An event flagged as a championship, with child events. A separate configuration document maps a championship to its rounds. A championship ticket grants access to the rounds it contains, and an individual event can belong to more than one championship.Where The Data Lives
One MongoDB database per environment,GklPlatform_DEV and GklPlatform_PROD, both on the shared instance. Collections map closely onto the entities above: Users, Drivers, Events, Tickets, Checkouts, Transactions, Admins, Configurations, Audit, DriversFiles and DistinctDrivers.
There is no schema migration framework. Changes to configuration documents are applied by writing a migration script and running it by hand against the production database through Studio 3T. See Configuring a New Hub Region for a worked example.