Journal + memory
DJINN + Supabase
Postgres behind DJINN's memory. Every message is journalled, and durable facts are promoted out of that log into a linked note vault.
How it connects
The journal is the raw record
Messages are stored with role and author and nothing rewrites history, so any summary can be checked against what was actually said.
Learning reads the journal
A nightly pass reads new rows since a watermark and files durable facts into the vault. Talking to DJINN is what grows its memory — there is no separate step to remember something.
Encrypted off-box backups
The vault is backed up nightly to object storage, encrypted.
Connector spec
- Auth
- supabase · supabase_v1
- Host
- https://supabase.com
GET customers
Emits db_row
Declared boundary: anyone in the workspace
GET orders
Emits db_row
Declared boundary: anyone in the workspace
GET products
Emits db_row
Declared boundary: anyone in the workspace
This spec parses and validates, and it has not been run against a live Supabase account. Sigil fetches and paginates today; it does not yet apply the mapping or enforce the boundary shown here. Both are declared and checked for shape, not executed.
Worth knowing before you wire it
A 404 or empty result from PostgREST usually means the query is wrong — wrong schema, stale token, wrong scope — not that the data is missing. Proposing a CREATE TABLE to fix a read failure is forbidden here, after doing exactly that once.
Documents
Supabase setup and reference.
Setup steps, scopes, and the policy boundaries that govern this connector. Sent by email — leave an address and we send them manually, same as the handbook.
- ReferenceJournal schema and learning watermark
- RunbookBackup and restore
Want Supabase wired into your own company brain?