tenant-isolation

Design tenant isolation for a multi-tenant agentic product so one customer can never read, retrieve, remember, or be billed for another's data. Covers the three isolation models (pooled + row-level, bridge, silo), the agent-specific leakage paths most teams miss (cross-tenant retrieval, memory, cache, trace, and model-supplied tenant_id), where tenant_id binds into the Agent Contract / permissions / memory / tools / evals, and the mandatory cross-tenant leakage eval. Use whenever the user mentions multi-tenant, multi-tenancy, tenant isolation, B2B SaaS agent, per-customer data, row-level security / RLS, data residency, "can tenant A see tenant B's data," noisy neighbor, or namespacing memory/knowledge per customer.