Multi-Tenant
Architectural principle + requirement: tenant_id on every table, row-level security (RLS), and config-driven service boundaries built in from the first migration — even before a second tenant onboards — because retrofitting multi-tenancy after data/logic assume a single tenant is a rewrite, not a migration.
| Audience | Name |
|---|---|
| Engineering (code) | — |
| Design (UI label) | — |
| Borrower-facing | — |
| Do not use | — |
Sources
- Clarity Engine PRD V7 — Architectural principle 11; Requirement #19