Infra

Cross-cutting engineering concerns that don’t belong to a single component. Each page here documents something that affects multiple components — CI workflows that build all three apps, data-storage conventions shared across services, request patterns used by multiple consumers, and the C4 architecture diagrams.

Infra is deliberately narrow. If you’re documenting something specific to a single component (API, WWW, Admin, etc.), it belongs in that component’s zone — not here. Adding a new infra module requires justifying in the PR description why it can’t live elsewhere. This friction is intentional; the bucket used to drift into being a catch-all.

Modules

• Architecture (C4 diagrams) — system-level architecture.
• Analytics — GA4 marketing/product tracking: the unified property, event taxonomy, User-ID stitching, and BigQuery export.
• Data storage — DB conventions and retention.
• Cron jobs — scheduled background jobs and how they’re triggered.
• GitHub — CI workflows, PR templates, labels.

Historical change-requests previously lived here under /infra/requests/; they’ve moved to Business logic → Change requests (where the rules they describe actually live).