| 6. Historical archive and live connector breadth | About 80 registered archive importers (Google Takeout, Apple Health/Photos/Messages, Meta Facebook/Instagram/WhatsApp, Discord, Telegram, ChatGPT, Claude, Amazon, Spotify, Strava and more) plus 11 bulk /api/v1 capture lanes. | Indexes Apple Mail, Messages, Photos, Calendar, Notes and Safari on the device; does not ingest third-party archives. | Meta social graph, Messenger, Instagram, WhatsApp threads and Ray-Ban camera captures, plus files uploaded to a task. | X posts, bookmarks and DMs, plus files uploaded in chat and optional Google Drive or calendar connectors. | Ingests only chat turns and text documents pushed by a developer via API. | Syncs active calendar events and task integrations (Google/Outlook Calendar, Slack, Linear, Notion). | Siloed per app (Immich for photos, Paperless-ngx for PDFs, Home Assistant for sensors). |
|---|
| 7. Canonical entity and relationship schema | 6 core record kinds (Person, Place, Thing, Content, Event, Space) backed by ci.entities single/class-table inheritance, typed ci.relationships in PostgreSQL 18, and 768-d HNSW ci_search.embeddings. | On-device Spotlight Semantic Index and entity graph across Apple system apps. | Workspace file tree and session memory items; no user-auditable personal database. | Flat conversation history and vector chunks. | Mem0 stores vector facts and optional Neo4j triples; Zep/Graphiti stores bi-temporal graph edges; Letta stores Core/Recall/Archival blocks. | Tasks, projects, time blocks and calendar events only. | Separate schemas in each self-hosted container; no shared cross-app entity graph. |
|---|
| 8. Spatio-temporal stay-point and place resolution | PostGIS spatial indexing, GPS stay-point clustering, reverse geocoding, Home and Work suggestions after 3 weeks of routine, and next-place transition predictions (places_next). | Significant Locations and Photos Places on-device; not exposed as an open MCP or SQL query API. | Coarse location and camera context on glasses; no historical stay-point database. | IP or mobile location context for local queries; no historical stay-point graph. | No native PostGIS or stay-point clustering. | Location strings on calendar events only. | Home Assistant device tracker zones or Dawarich GPS logs in separate databases. |
|---|
| 9. Deterministic and ML entity resolution | 44-stage ci.pipeline_state enrichment ledger with automated duplicate detection and merges for people, places and things, plus manual merge or dismissal review queues. | On-device face clustering in Photos and contact card merge suggestions. | Not applicable. | Not applicable. | LLM prompt-based node deduplication during write calls. | Not applicable. | Immich face clustering for photos only. |
|---|
| 10. Governed agent memory (L0, L1, L2) and slot supersession | L0 session context + up to 24 lines of the next-24h HBPE forecast (/api/memory/context), L1 boosted keyword+vector + 1-hop graph recall (/api/memory/recall), L2 8-category writes with single-value slot supersession (lives_in, works_at, role_is, uses_primary, prefers), conflict detection (/api/memory/conflicts), path drift (/api/memory/drift) and grounded compaction (behind a setting). | No external agent memory write or recall API. | Session memory notes saved across tasks; no formal slot supersession or code-path drift API. | Cross-session conversational memory toggle; no structured slot supersession or conflict ledger. | Core focus of Mem0, Zep (bi-temporal invalidation) and Letta, without an integrated personal archive or HBPE forecast. | Not applicable. | Open WebUI flat user memory strings. |
|---|