High-Level Design (HLD)

The big-picture view: context, containers, deployment topology, and the primary request flows. Low-level contracts (RPC signatures, EF request/response shapes) live on the per-area pages and in the Backend reference.

How a change to any of this reaches production is a separate architecture with its own HLD and LLD: the Release Management System. This page describes what the platform is; that one describes how it changes. No production change ships outside it.

C4 — Level 1: System Context

C4 — Level 2: Container view

Deployment topology

Promotion is deliberate. Migrations, EFs, secrets, storage, and cron changes are applied to both Supabase projects by hand (Dev first, then Prod) — Dev/UAT does not self-sync to Prod. See Deployment & Promotion.

Primary flow — authenticated write (dashboard)

Primary flow — public page read (cached)

Design invariants (never violated)

• Data access: supabase.from() banned in src/. See Data Access Strategy.
• Tier isolation: public ⇏ user,admin; user ⇏ admin. See Tier System.
• Security: validate at boundaries (Zod), RLS on every table, EF is primary write-enforcement.
• Design system: Apple-style soft corners, zero hard-coded colors, mandatory light+dark.
• TS-first: platform-agnostic shared core (no DOM imports) so web + future native both consume it.

See also: Frontend · Backend · Database & RLS · Security.