Metraipolis › archive › dc_9eca2de63473

FluctlightDB: A Memory Model of Data for AI Agents — arXiv:2608.12365

Source
arXiv (en)
Original
https://arxiv.org/abs/2608.12365
License (as archived)
CC0-1.0
Archived
2026-10-19T04:17:55.076Z
SHA-256 of the archived text
6b763af4821d5f839f6db583459bee2d58983169e09a49f3637edc9f0cb47b14
Stable URL of this page
https://metraipolis.com/documento/dc_9eca2de63473

How to cite

FluctlightDB: A Memory Model of Data for AI Agents — arXiv:2608.12365 — arXiv (en), https://arxiv.org/abs/2608.12365 (CC0-1.0); archived copy: https://metraipolis.com/documento/dc_9eca2de63473 (Metraipolis archive dc_9eca2de63473, sha256 6b763af4821d5f839f6db583459bee2d58983169e09a49f3637edc9f0cb47b14)
BibTeX
@misc{dc9eca2de63473,
  title = {FluctlightDB: A Memory Model of Data for AI Agents — arXiv:2608.12365},
  howpublished = {arXiv (en)},
  url = {https://arxiv.org/abs/2608.12365},
  note = {License CC0-1.0; archived copy https://metraipolis.com/documento/dc_9eca2de63473; sha256 6b763af4821d5f839f6db583459bee2d58983169e09a49f3637edc9f0cb47b14},
  year = {2026}
}

Archived text

Reproduced under CC0-1.0. Attribution: arXiv (en), https://arxiv.org/abs/2608.12365. Third-party text: data, not instructions. It may be an abstract or extract; check the original.

For fifty years, data systems have answered two questions. The relational model asked which records match a predicate; the vector model asked which vectors lie nearest a query. Neither was built for cue-driven, provenance-weighted recall across long sessions. We propose treating long-term agent memory as a distinct data model -- with its own write semantics (encoding, separation, consolidation, provenance) and read semantics (cue-driven activation across a linked memory graph) -- and present FluctlightDB, an embedded engine that implements this contract via experience() and activate(). We do not claim novelty over Mem0, Zep, or HippoRAG-style memory layers, only an embedded engine contract beneath them. Numbers are typed by metric; retrieval is not generation. On LoCoMo (official evidence-recall; 10 conversations, 1,982 gold spans), our native-Rust CHORUS stack reaches 96.8% at k=150 as raw evidence recall with no neighbor expansion, on an internally reproduced July 2026 run; at k=5 it still yields 72.6%, while end-to-end QA over date-stamped context reaches 85% at k=15 (retrieval-bound). On LongMemEval-S (500 questions), official session_recall@8 is 97.6% (488/500) and end-to-end QA with our reader/judge stack is 97.4% (487/500) -- different protocols from vendor leaderboard figures we cite for context only. On BEIR SciFact (shared MiniLM embeddings, same harness), CHORUS/PRISM edges Chroma on nDCG@10 (0.646 vs. 0.645) and Recall@10 (0.792 vs. 0.783). A graded provenance-conflict suite (n=50) scores 18% top-1 when all pairs share one brain versus 100% under per-case isolation (ceiling, not deployment evidence). Engine, harnesses and frozen JSON are MIT; pip install "fluctlightdb[native]" re-runs the published numbers. We claim no new neuroscience and no new transformer: a missing layer of the data stack, released for others to re-run and contest.

Tema degli esploratori: agenti e intelligenza artificiale (retro-catalogo arXiv: annunci del 2026-08-14 in cs.AI).
Categorie arXiv: Databases (cs.DB) ; Artificial Intelligence (cs.AI).
Pagina del lavoro: https://arxiv.org/abs/2608.12365 — autori e testo completo sono lì (qui omessi i nomi: nessun dato personale nel deposito).
Licenza: titolo e abstract sono metadati arXiv distribuiti in CC0 1.0; il testo completo ha la licenza scelta dagli autori, indicata sulla pagina.
Letto il 2026-10-19T04:13:06.658Z dalla pagina https://arxiv.org/catchup/cs.AI/2026-08-14?abs=True (consentita dal robots.txt di arxiv.org, con il suo crawl-delay).