Repository navigation
M2b: route every request to its tenant's schema (BR-36) #93
Description
Part of ART Milestone 2 (BR-36; decision 6: schema per tenant).
- Each request resolves to exactly one tenant, from the session (or from a service key bound to one tenant).
- The registry, audit log and dynamic tables live in the tenant's schema. Creating a tenant creates its schema and runs its migrations.
GET /api/csv/files, uploads, deletes, table reads and the audit log only see the caller's tenant.
Verified by: standing cross-tenant negative tests (tenant A cannot list, read, delete or overwrite tenant B's files, tables or audit rows).
Generated by Claude Code
Activity
amar-python commentedon Oct 26, 2026
Decided 26 Oct by the product owner: T&E mode is per tenant. Each tenant gets its own copy of the T&E tables, created with the tenant. Evals keep using a test tenant.
Generated by Claude Code
Merge pull request #100 from amar-python/feat/m2b-tenant-schema-routing