← All agent-stack verdicts

Agent memory systems

Adopt and wrap Confidence Low Group Memory and retrieval Evidence as of 2026-09-23

Written by VerdictsServing · Reviewed by ReviewServing on 2026-09-23 (separate AI agent sessions; review record)

Bracketed tags are evidence tiers from RULEBOOK.md §1: [Verified] means checked directly, [CI-observed] read from a project’s CI pages, [Maintainer claim] asserted by the project, [External] a dated third-party source, [Inference] our judgment. A gold path:line link opens the cited line. NODUS is the four-ring verdict scale (Invest, Pilot, Explore, Monitor) used for the FrankenSuite assessments; the agent-stack verdicts use their own scale (Adopt, Adopt and wrap, Build clean-room, Watch). TRL is technology readiness level, scored 1 to 9. CI is continuous integration: automated checks that run on every push. To pin is to freeze a dependency, oracle, or assessment at an exact commit or version, so later changes cannot silently alter what was checked. The rider is the license clause withholding all rights, including benchmarking and testing, from OpenAI, Anthropic, their affiliates, and anyone acting for them; most FrankenSuite repos carry it.

Bottom line

Inference, low confidence: adopt and wrap a maintained memory layer (Mem0's open-source SDK, or Graphiti for a temporal knowledge graph) behind a thin interface of your own, rather than designing a new one. Do not rely on any published memory benchmark score: the scores are self-reported, sometimes from a managed platform or an ensemble of runs, and graded by LLM judges. Re-run LoCoMo or LongMemEval yourself with the dataset pinned by hash and the judge model pinned by name and date before you trust a number. Confidence is low because the evidence pack itself flags adoption evidence as thin.

Adopt, do not rebuild

License checked on 2026-09-23; non-permissive licenses are named in the text.

Copy these practices

Build only if

  • Every remembered item must carry verifiable origin and your candidate incumbent cannot record it. The evidence pack did not examine incumbents for per-item provenance, so check yours first; local-only operation alone is not a reason to build, since Mem0's harness ships a local Ollama provider config. All adopted projects here are Apache-2.0 or MIT, so license is not a reason either. The FrankenSuite substrate for provenance is unproven, and the companion's own starting point for such a build is small: one local SQLite store with a pinned embedding backend. [Verified] [Inference] (stack/licenses.tsv:52 mem0ai/mem0 Apache-2.0 permissive; stack/licenses.tsv:28 getzep/graphiti Apache-2.0 permissive; stack/licenses.tsv:47 letta-ai/letta-code Apache-2.0 permissive; stack/licenses.tsv:88 SuperMemoryAI/supermemory MIT permissive; ecosystem/pickup/_evidence/agent-memory.md:15 configs/{azure-openai,ollama,openai}.yaml; packets/franken_agent_detection-assessment.md:190 as a substrate for portable agent memory — unoccupied and unproven; ecosystem/pickup/pickup-agent-memory.md:34 A single local memory store (SQLite + a pinned embedding)

Where FrankenSuite touches this

What we cannot say

Revisit when

  • A party other than the vendor reproduces LoCoMo or LongMemEval numbers for Mem0, Graphiti/Zep or Letta with pinned judge and dataset.
  • A shared memory API or conformance suite appears across two or more vendors.
  • franken_agent_detection ships signed, hash-carrying provenance envelopes and a second independent consumer.

Sources

Starting a build here?

Begin from the pickup companion for Agent memory systems: it carries the charter seed, the oracle candidates and how to verify them, and the first claims to register, so a new project starts from evidence instead of from scratch.

Help fix it

Each opens a GitHub issue form with this page’s address filled in. You need a GitHub account.

Made by Joshua Nowak (ZestStream) with AI coding agents. Not affiliated with or funded by Jeffrey Emanuel; Joshua uses his public tools and is a paying subscriber to jeffreys-skills.md.

Source on GitHub MIT licensed