Reference Documentation
System-level documentation describing how BattleScore is structured,
how its layers interact, and where key behaviours live.
Architecture
Onboarding
Cross-Component
Purpose of this section
The SQL, API, App, TO and Admin sections document individual parts of the solution. This Reference section sits above those areas and explains the platform as a coherent system.
It is intended to answer questions such as:
- What are the main components of BattleScore?
- How does data move between database, API, and user interface?
- How do gameplay and scoring actually work end-to-end?
- Which parts of the solution are affected when a specific feature changes?
Reference pages
| Page | Focus |
|---|---|
| System Overview | Full-stack architecture and domain layout |
| Solution Components | Detailed breakdown of each layer and responsibility |
| Component Interactions | How SQL, API, App, TO and Admin work together |
| Data Flow | How reference, transactional and runtime data move through the platform |
| Gameplay & Scoring Flow | End-to-end play model and scoring mechanics |
| Tournament & TO Flow | How tournaments, entrants, armies and standings fit together |
| Change Impact Guide | Where to change things and what else is affected |
Related documentation
- SQL – database schema and table-level documentation
- API – endpoint-level server documentation
- User Interface – user-facing frontend pages and scripts
- TO – tournament organiser frontend workflows
- Admin – internal maintenance and configuration layer