What changes when your AI remembers every conversation?
Unified Group Memory
- SQLite + FTS5
- Vector search
- Messaging bridge
Relevant services: AI Digital Teammates · Thrivbe AI
Hypothesis
Community knowledge lives in group chats and evaporates there. If the communities you coordinate agree, a daily sync of those group conversations into one searchable, shared memory — readable by your AI systems — should turn years of chat scroll into infrastructure for matchmaking and follow-through.
What we built
A daily pipeline that syncs tracked community group chats (explicitly scoped: personal and family conversations are excluded by rule) through a unified messaging bridge into a local SQLite corpus — tens of thousands of messages across a hundred-plus groups, full-text searchable, with sender resolution against our CRM. The corpus then feeds the AI OS's single unified memory (keyword + vector), so every agent recalls from one place. Read-only by design: the pipeline never sends. Members of the tracked communities are told the sync exists, and any group or person can be excluded on request.
Learnings
- Scope is the design. The include/exclude rules — which clusters are tracked, what is permanently excluded — are more important than any technical choice, and they're written as code, not vibes.
- One memory beats many: the moment the corpus merged into the kernel's single memory store, every downstream agent got smarter for free.
- Chunking by conversation-day preserved context that per-message embedding destroyed. Granularity is a product decision.
Log
- 2026-07-07 — Merged into the OS's unified memory; sender-to-CRM resolution and search surface live.
- 2026-07-05 — First backfill of tracked community groups; daily read-only sync armed.
