RugbyCodex Docs

RugbyCodex DocsArchitecture and workflow documentation

Built for Software engineers. User facing docs coming soon...

Start with the system overview

Browse the file map

Architecture-first

Trace the system from routing and frontend state through Supabase, workers, and media pipelines.

Start with the question you have

Question	Start here	Then follow with
What systems make up RugbyCodex?	System overview	Architecture map, Third-party services
What product surfaces are implemented versus stubbed?	Product overview	Routing and pages
How does the frontend really behave?	Frontend architecture	State and data flow, UI workflows
Where do routing and permissions live?	Routing and pages	`frontend/src/router/index.ts`, `frontend/src/router/orgRoutes.ts`
Where can frontend logic drift from backend truth?	State and data flow	Known unknowns
How does media processing leave the browser?	System overview	AWS transcoder scaling, Third-party services

Recommended reading paths

New engineer, broad orientation: System overview -> Product overview -> Architecture map
Senior frontend engineer: Frontend architecture -> Routing and pages -> State and data flow -> UI workflows
Infra / media pipeline: System overview -> Third-party services -> AWS transcoder scaling
Repo navigation: File map -> Environment and config
AI shit: AI usage

Confidence notation used in this docs set

Verified in code - directly supported by audited repository files.
Inferred from call path - not stated in one place, but strongly implied by how modules call each other.
Could not be fully verified from repository - the repo hints at the behavior, but not enough code or docs exist here to make the claim authoritative.