Architecture & Data¶
Use this section when you need to understand how Stat'sTheGame is put together, where authority lives, how cricket events are represented, how data moves through ingestion and publication, or how security boundaries are enforced.
Recommended reading order¶
- Architecture overview — component boundaries and responsibilities.
- System architecture and roadmap — current architecture, decisions and later-tier direction.
- Database architecture guide — marker/developer route through persistence, migrations and trade-offs.
- Event model and ERD — cricket identities, revisions and relationships.
- Batch ingestion pipeline — staged file processing, worker and publication architecture.
- Security overview — authentication, authorisation, data and API protection boundaries.
Architecture map¶
| Question | Authoritative starting point | Go deeper |
|---|---|---|
| What are the major components? | Architecture overview | System architecture |
| How is cricket represented? | Sport domain definition | Event model |
| Why does the schema look this way? | Database architecture guide | Cricsheet data source |
| What tables and relationships exist? | ERD | Database overview |
| How are writes and transactions controlled? | Database access | Batch persistence |
| How do large uploads become published data? | Batch ingestion pipeline | Batch API |
| How are identity and permissions enforced? | Security overview | Authentication, roles |
| What happens when an account is deleted? | Privacy and retention | Password recovery ownership |
| Why was the auth provider selected? | Provider comparison | Decisions index |
Source data and derived data¶
The Cricsheet data source records the corpus used to validate cricket-specific assumptions. The event model records the resulting identity and persistence choices. Calculation behaviour is documented separately under Fixture statistic calculations and Participant aggregate calculations.
Keeping those concerns separate avoids turning a schema page into an API manual or a statistics page into a database reference.
Decisions and deployment¶
Architecture Decision Records and other project-level decisions are indexed in Decisions. Hosted topology, capacity, recovery and deployment commands belong under Deployment & Operations, not on this architecture hub.
AI Declaration¶
The architecture/data documentation hub and reading path were planned and drafted with the assistance of ChatGPT-Web[GPT-5.6 Sol].