- Selected
- SQLite as the local disposable index.
- Rejected
- Synchronizing the SQLite database itself through Git.
- Why not
- Binary synchronization creates merge and locking risk.
- Reopen if
- The storage model changes enough to remove those constraints.
Cursor plugin · Claude Code plugin
Talmudic AI Memory
The agent dies. The work is immortal.
Gemara remembers what was decided, why, why-not, and when to reopen — so the next agent inherits judgment, not a transcript.
“Talmudic” describes a reasoning structure (premise → dispute → ruling → reopen-if) — infrastructural only, not religious content.
One sugya
Git remembers code. Built-in memory remembers the user. Gemara remembers judgment.
Thesis
A continuity control plane — not a memory dump, not a chat summary.
More like a transaction journal for work than a notebook of memories.
- Do not preserve the conversation. Preserve the resumability of the work.
- The agent is disposable. The workstream is durable.
Assay
Slipcase — a dummy loan app. The repo says Postgres is decided. Gemara says otherwise.
The lie
ADR accepted: PostgreSQL, DATABASE_URL, STORAGE = "postgres".
The judgment
JSON for 0.1. Do not redo Postgres. Reopen only if storage actually changes.
PASS Live Chat A→B on plugin 0.2.17 met gold: Gemara id quoted, Postgres refused.
Read the assayInstall now (manual)
Cursor
https://github.com/AI4AI-Labs/talmudic-ai-memory
Enable Talmudic AI Memory, create .cursor/talmudic.json with {"enabled": true}, run /talmudic-init.
Claude Code
claude plugin marketplace add AI4AI-Labs/talmudic-ai-memory
claude plugin install talmudic-memory@talmudic-ai-memory