Persistent memory
for AI agents

gnosys_recalldone

{
  "query": "tenant isolation decision",
  "projectRoot": "/Users/sam/code/acme-api"
}

<gnosys-recall>
[Memory 1] [[deci-01KZ7Q3M8T4VXN2R6HJCW5PB9E]] (relevance: 1.00)
# Tenant isolation uses Postgres row-level security  Use Postgres row-level security for tenant isolation. Do not rely on app-level WHERE filters.

[Memory 2] [[arch-01KYV2D7RJ0C4XH9N6TQM3B8WS]] (relevance: 0.64)
# Tenant ID comes from the session token  The API sets app.tenant_id from the signed session token on every request.

[Memory 3] [[deci-01KYN8F5ZB3K7PQW2HXD4C6M1R]] (relevance: 0.30)
# Primary database is Postgres 17  We run one managed Postgres 17 instance per region.
</gnosys-recall>

gnosys_readdone

{
  "path": "deci-01KZ7Q3M8T4VXN2R6HJCW5PB9E",
  "projectRoot": "/Users/sam/code/acme-api"
}

[Source: gnosys.db]

---
id: deci-01KZ7Q3M8T4VXN2R6HJCW5PB9E
title: 'Tenant isolation uses Postgres row-level security'
category: decisions
tags: {"domain":["database","multi-tenant"],"type":["decision"]}
author: human+ai
authority: declared
confidence: 0.8
status: active
created: '2026-10-05'
---

# Tenant isolation uses Postgres row-level security

Use Postgres row-level security for tenant isolation. Do not rely on app-level WHERE filters.

gnosys_recalldone

{
  "query": "invoices table tenant database",
  "projectRoot": "/Users/sam/code/acme-api"
}

<gnosys-recall>
[Memory 1] [[deci-01KZ7Q3M8T4VXN2R6HJCW5PB9E]] (relevance: 1.00)
# Tenant isolation uses Postgres row-level security  Use Postgres row-level security for tenant isolation. Do not rely on app-level WHERE filters.

[Memory 2] [[arch-01KYV2D7RJ0C4XH9N6TQM3B8WS]] (relevance: 0.30)
# Tenant ID comes from the session token  The API sets app.tenant_id from the signed session token on every request.
</gnosys-recall>