Individual Reports
mem0langmemhonchoengrammempalaceswafrallm-wiki-memoryrainboxlettasupermemoryverelhindsightgraphitimastra-observational-memorymemosbasic-memoryagentmemorytencentdb-agent-memorycogneeclaude-mema-memholographichermes-agentopenvikingredis-agent-memory-serverbyteroveropenclawhipporagvoyagergenerative-agentsmagic-contextpimetaclawnanobotcowagentgenericagentopen-coworkgini-agentmoltismercury-agentllamaindexatomic-agentmateclawwaku-agentmemoraloongflowcore-memorymemantomemory-engineai-memoryctxoptmemmemvidmemoryosmemuopenworkerqwen-codeopencodenooa-memoryneo4j-agent-memoryelastic-atlasmirixmemobasememarymemoriremepowermemminecontextacontextsecond-metigrimosrnemoclawdaimonmemmachinebuzzlogseqopenhumanadk-pythonaukora-kernelautogengoodai-ltmeveroseccskalesnekosillytavernrisuaisoul-of-waifuz-waifvirtualwifehelmagnosimplemempydantic-ai-harnesscamelagent-frameworkcrewaigobiiagent-memory-supabaselivingfeedcosmonapsenpcpyjugglermagicoregitlordagent-afkcortexmnemopitokenmizerzerostacklethecsmgraphifylorekitclioagentswarmsempryodextoproject-golemopenyakmementomembasepalazzoauramemex-zero-ragagentrecall-xmemledgerterse-memoryagentic-context-enginedeer-flowean-agentosm-flowuniversal-memory-enginenova-aimemsemcambiumperseus-vaultprovemargosovereignmemoryops-aideepcodeprime-agentmnemosyneomikirocrewmnemoryengram-alphasesaopensresmythos-sreqwen-mm-pluginsremem-mcpwindie-sandboxplur1busomniintelligenceomniclaudehillockmemory-compileragent-memory-doctrineodsneurakeepopen-knowledge-formatomnimemtempomemdovsgopenmake-llmelaiargosreporecallthoughtdagopenmasqno-humankwipucraftholomemhumanspro-workflowteamai-clievox-genesismemcontinuumsage-memorypluropenzync-coresibyl-memoryauto-companyripwireripwire-rsengram-formatkhojanything-llmjoplinusememossilverbulletsiyuantriliumvistavelantrim-exocortex-crystalforgetfulhalofyorigintrail-dkgai-agent-bookdsh-mnemewidemem-aikaerualtk-evolveopen-braindistill-kurawagglekektordbclaude-mem-liteegcprojectmemstratagateagent-memory-mcpvelesdbdsh-mnemonyantrikdb-hermes-plugininite-braingoodmemorymemorixdense-memloreaimazemakermemtomemtracedecaytitenllm-memory-apidemarkuspeople-contextstate-memory-mcpthe-librarianakbjazagentrtinno-agentoh-my-hermesbitterbot-desktopyantrikdb-enginenodedbopenconchooxmaximem-synap-sdksykesivtreliot-memory-osneuralmindinspeximuspi-memorypi-jarvismandalorekannaka-memorychumplongterm-memory-mcpagent-memory-guarda-memorymemexyacmemolevhanda-dbtemporalstoremushroomdbflairtheurianyantrik-oshuiran-cerebrolight-membifrostmnemorachitta-fieldmnemonicnougenshardseddaosirisholo-invariantcodememtessellumneothhungry-hippacortanacortex-hypermnesiaengram-cognitiveclaudinio-brainre-callokf-agent-memoryloreweavetemveramindreaderverimemanatidmemhtmlbwmemhuqanontomemyantrik-mindmnesioulpiagaiusaidememocogzleteomemorywhalerememorafava-trailsleankghyphaai-maestrocontextstream-mcpmnesticcognee-rskipi-systembeevibeknowlkiwi-membeever-atlaspensyvekglitemeridianmemory-vaultopen-graph-memoryfunesdeusgastownbeadsmemorizeryantrikdb-mcppmbspectormempalace-coderesonant-mindresonantengram-nickcirvemulosqlite-memory-mcpautomemmexm3-memoryruvectorogadcontext-engineeringgraftmind-mempapercliprrsiememagent-memory-distillationfarmembodied-lgrliving-mind-cortexopen-bridgevortx-ememshellbrainmemeshmamamnemosyne-nabzxautoharnessmegamemorykagura-memory-cloudprismer-cloudmemseekexomemrust-self-learning-memorymemhopcortexeswordcelloctop-memoryrecallnestmemoosezenbrainobelyth-cortexcortex-hubmindmemoslindahaviv-second-brainrexleimo-aiosdynamics-memorydsh-layered-memorycyrene-agentneo-agent-brainoctobrainkimetsulint-aiautobot-ainano-braindreamgraphflowlyglobal-agent-memoryrecollectrightmemorytidemindwindvanectx-openroampal-coreopencode-session-recallaoci-codemcp-context-servertree-ring-memoryengram-mcpdsh-continual-harnesscounterpartsclaude-engram-mlapeterorgtreesmritimainlinemintaagent-memory-enginealphaonedev-ai-memoryselvedgegmeow-ontologylocal-memory-mcparcheusmarvisattune-aisession-recallmgi-mindmnemocortexdbsynapse-layerfernmefluctlightdbosk-systempluribusihmt-memoryparticlesharness-evolutionarchiver-ragbrowsenticcloud-alter-egotigerless-agent-memorymusclememoryremembrabrain-mcpobsidian-wikihive-minddsh-auto-memorygambletan-cortexflatbreadhermes-fleet-memoryaigent-oscrystallinebinderontofeliaelephantasm-corescreenpipehyperconsciousnesskenhy-memorymakaharness2cindymindciris-agentlibrarian-agentsdsh-superagentopenmemtextfoldmaster-agent-systemopenai-codexunderstand-anythingllm-harness-memorymem-masteroultimateassistantmonomemsol0monactive-memory-indexvanilla-rag-memoryrefindbot-boardsqlite-graph-memorykibisisimmunememgraph-ai-toolkitobsidian-second-brainzettelforgegraphiclehermes-memory-installerkybfridayzizkadbmnemosyne-28naem-delluna-local-agentmnemos-mcpbillion-contextopenyantranoosphere-lite-mcpclm-memseverianpok-agentwaifu-companionagoramanaged-agents-dreamingmanaged-agents-knowledge-wikiopenagents-controlqualitylayerzeroshotwillderbolt-pchierakhoctxvaultdecision-keeperreqlartexllm-memory-mordituxheurchaincairnbackboard-desktoppentagilcm-xvaultiteopencomputerclickhouse-loomspookling-memoryagentic-graphragevomemnavhomebodylucidmaximem-synap-core
Repos Inspected
- mem0ai/mem0 at
c7ee362a…— read only at the second pin; eighteen dependency surfaces inside the cooldown, nothing installed or run. The memory package now fetches a remotely switchable notice config and classifies search queries as temporal, gated on telemetry that defaults on - langchain-ai/langmem
at
9d033b47…— read at the second pin and audited there on 2026-09-30, which is upstream HEAD, with the store read in langchain-ai/langgraph atcheckpoint==4.2.0andcheckpointpostgres==3.1.2; no auto-run surface and two build-time execution points, read rather than executed; nothing installed, built or run.scope_enforcedholds; no committed test asserts it. - plastic-labs/honcho at
210b56cf…— read only; four dependency files were inside the seven-day cooldown, so nothing was installed - Gentleman-Programming/engram
at
140bbedd…— read only; three dependency surfaces were inside the seven-day cooldown, so nothing was installed or run - MemPalace/mempalace at
8c4865f7… - Prateek816/7layermem
at
d3500bfd… - cognicore-dev/cognicore-env
at
6fc657d0… - RBKunnela/ALMA-memory
at
91a352f2… - deepractice/promptx at
93c1e535… - fuyuxiang/echo-agent
at
f612b74f… - kitfunso/hippo-memory
at
f774b2db… - kunal12203/swafra
at
669e7bdb… - ctxr-dev/llm-wiki-memory
at
4e7f98f3…— read only; one auto-run surface (AGENTS.md, addressed to a reading agent and recorded as data), fifty floating ranges behind a lockfile and one manifest inside the seven-day cooldown, so nothing was installed and no stage was run. The unread quality marker was established by sweeping every non-test reference to the metadata field, not by executing a recall - neoneye/RainBox at
aaa084ea…— read only; no auto-run surface, three build-time execution points (twoconftest.pyfiles and apostinstallin the Python sandbox'spackage.json) and one floating range behind a lockfile, so nothing was installed and no suite was run - letta-ai/letta at
5bcdd177… - supermemoryai/supermemory
at
2415a5c7…— read only at the second pin; a dependency surface inside the cooldown, so nothing was installed or run. The web console was reduced to a redirect shell, andscope_enforcedwas re-tested against the exact-match container-tag predicate that moved intopackages/tools/src/claude-memory.ts - amitpatole/verel
at
aaf163ef…— read only; no auto-run surface, one build-time execution surface (tests/conftest.py), one unpinned surface and nothing inside the seven-day cooldown. Nothing was installed and nothing was run. The pin was checked for reachability fromHEADbefore reading, because an earlier pin for this repository turned out to be unreachable from any branch. The project ships a self-grader against this atlas's seven capabilities, so every mark is stated against a file read here rather than against that probe - vectorize-io/hindsight
at
16d4025f…— read only at the second pin; 51 dependency surfaces inside the cooldown, so nothing was installed or run.negative_evaladded on the tests that came with a fix for chunk ids colliding across banks - BatterWorks/Hatchdoor
at
c2b9861a…— read only; the screen found no auto-run surface and no build-time execution, one unpinned manifest (frontend/package.json, 39 floating ranges behind a lockfile) and both lockfiles unchanged for 14 days, so nothing was installed, nocargoornpmcommand was run and no container was started.AGENTS.mdis addressed to a reading agent and was recorded as data. The thirty-six committed eval runs were recomputed from their own per-query tables rather than quoted; the README's badges and Docker Hub image still name the pre-renameBattermanZ/Hatchdoor. AGPL-3.0 - getzep/graphiti at
c035afb7… - mastra-ai/mastra
at
2f05e3e8… - MemTensor/MemOS at
de806942… - basicmachines-co/basic-memory
at
3bf2d523… - rohitg00/agentmemory
at
e04ba888… - TencentCloud/tencentdb-agent-memory
at
8f2dc830… - topoteretes/cognee at
c0d18c80… - thedotmack/claude-mem
at
40be934a… - agiresearch/A-mem
at
ceffb860… - NousResearch/hermes-agent
at
8df0a037…— one commit carrying two reports: Hermes's own built-in memory, and theholographicHRR plugin shipped in the same tree. Read only; one auto-run surface, twenty-one build-time execution surfaces, five unpinned surfaces and twenty files inside the seven-day cooldown. Nothing was installed and no suite was run - volcengine/OpenViking
at
192b813e…— read only at the second pin; a dependency surface inside the cooldown, so nothing was installed or run.scope_enforcedre-located from the write-target isolation handler to the account predicate on the vector backend - redis/agent-memory-server
at
8683648f… - campfirein/byterover-cli
at
1052ac1a… - openclaw/openclaw
at
2e7e5ef6… - Trustedwear-Tech/citra-decision-system
at
6f200f29…— read only; eight build-time execution surfaces and eight dependency surfaces inside the seven-day cooldown, so nothing was installed and nothing was run - Arc-Computer/ATLAS at
c226386f…— examined, no report; see the boundary note below - OSU-NLP-Group/HippoRAG
at
1438aba3… - MineDojo/Voyager
at
55e45a88… - joonspk-research/generative_agents
at
fe05a71d… - cortexkit/magic-context
at
8805036a… - earendil-works/pi
at
f9bcd351… - aiming-lab/MetaClaw at
922caf3a… - HKUDS/nanobot at
1c3c6826…— read only at the second pin; nothing installed or run. Archiving restructured into aMemoryArchiverwith a raw-checkpoint fallback; no mark moved - zhayujie/CowAgent
at
3bf04290…— read only at the second pin; two dependency surfaces inside the cooldown, nothing installed or run. Scope re-tested across four retrieval arms including a new vector backend - lsdefine/GenericAgent
at
1b6442fe…— read only at the second pin; nothing installed or run. The memory policy gained one exclusion — project-specific facts belong in the project, not in L3 — and the L1/L2 files turn out to be untracked runtime artifacts - OpenCoworkAI/open-cowork
at
a1d0e4ab… - Open-Curiosity/gini-agent
at
6c5d85ed… - moltis-org/moltis
at
1f6d28ea…— audited at the third pin, where no memory path had moved; nothing installed, built or run. Session logs are written raw by a hook while the sanitizing exporter has no caller, and the agent-scope predicate sits on the memory tools and not on the per-turn prefetch - cosmicstack-labs/mercury-agent
at
781daac2…— read only at the second pin; two dependency surfaces inside the cooldown, so nothing was installed or run. The stack row was traced and promoted from seeded to reviewed, and ashareableflag gating an outward cloud fetch was read at its defaults - run-llama/llama_index
at
0f43c00b… - AtomicBot-ai/atomic-agent
at
f31ec05d… - mateaix/mateclaw
at
5c67af85… - ShenSeanChen/waku-agent
at
761c4201…— read only;pyproject.tomlchanged the day of the reading and two build-time execution points (Makefile,evals/conftest.py), so nothing was installed or run.waku/memory/did not move; the reading was the new gate-accuracy eval underevals/judge/, which closes a criticism the report had published in six places, and a producer re-test ofhuman_reviewfrom the dashboard fact rows toSqliteFactStore - agentic-box/memora at
4b91fa74…— read only; five auto-run surfaces (.claude-plugin/marketplace.json, which was not present at the previous pin and was read first, and the plugin underclaude-plugin/with hooks and an MCP server), one build-time exec at pytest collection, two unpinned manifests and no dependency surface inside the cooldown; nothing was installed or executed - baidu-baige/LoongFlow
at
945c78bc… - JohnnyFiv3r/Core-Memory
at
b3857ff5… - moorcheh-ai/memanto at
ce38df50…— read only; one auto-run surface (.gitattributes), six build-time execution points, nothing installed or run - timescale/memory-engine
at
2ef90da9… - acdesigntech/memory-project
at
83b2ac97… - akitaonrails/ai-memory
at
995e35d5…— read only, at the head ofmain, a commit dated 17 October 2026; read before at74d2d31e…. MIT. Screened before reading from a full clone: six auto-run surfaces (.claude-plugin/,hooks/and the plugin underplugins/claude-code/, with hooks on nine events and an MCP server), two build-time execution points (build.rsincrates/ai-memory-webandcompanions/ai-memory-desktop), 22 dependency files inside the seven-day cooldown, and a committedCargo.lock. Nothing was installed, built or run - ActiveMemory/ctx
at
955749b4… - VictorTaelin/OptMem at
1fb164cf…— no licence file - memvid/memvid at
e6bd9f7b… - BAI-LAB/MemoryOS
at
587ed775… - NevaMind-AI/memU
at
08e1ed4c… - andrewyng/openworker
at
5bc10d92…— read only; no auto-run surface, three build-time execution surfaces, two unpinned surfaces and one dependency file inside the seven-day cooldown. Nothing was installed and nothing was run. MIT - QwenLM/qwen-code
at
537311b8… - anomalyco/opencode at
e03db9bc… - NVIDIA-NeMo/labs-OO-Agents
at
362f8bd2… - neo4j-labs/agent-memory
at
f801acc6… - noamschwartz/atlas-memory-demo
at
d84f9235… - NVIDIA/NemoClaw at
be46805b… - HarnessMD/munder-difflin
at
71dbbc18…Re-pinned and re-screened on 2026-10-04: the condenser gained a framed reply parser and its first test file, which stops at the parser, and releases from v0.5.2 on are binaries-only. The 2026-09-19 reading followed three that published a false absence claim: each said the repository contains no tests, and 107 test files sat in a top-leveltest/directory at the last of those pins. - imran31415/kube-coder
at
8a4e1ed2… - munch2u-a11y/Cognitive-Spatial-Memory
at
39df03a1… - esengine/DeepSeek-Reasonix
at
025bd17b…— read only, at the tip ofstudio, the default branch; the screen found one auto-run surface (committed.githooks/pre-push), one build-time execution path (Makefile), five unpinned manifests behind lockfiles and eleven dependency files inside the seven-day cooldown, so nothing was installed, built or run.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were read as data. MIT - Morephine/feltstate at
3a9f7f52… - yaminbkk/NexusMem
at
e1842964…— read only; one auto-run surface (server.json), two manifests inside the seven-day cooldown, nothing installed or run - Daily-Nerd/daimon
at
1afddb69…— read only; three auto-run surfaces, three build-time execution paths, one unpinned surface and two files inside the seven-day cooldown. Nothing was built and nothing was run. Apache-2.0 - Mirix-AI/MIRIX at
8cb06a62… - memodb-io/memobase at
358c16bb… - kingjulio8238/Memary
at
b2331a2c… - MemoriLabs/Memori
at
10d65015… - agentscope-ai/ReMe at
bebad367… - oceanbase/powercontext
at
9d1b4844… - volcengine/MineContext
at
171c7a9e… - memodb-io/Acontext at
259d73bf… - mindverse/Second-Me at
d0e40251… - Sompote/TigrimOSR
at
e6056e80… - MemMachine/MemMachine
at
da7de4cb… - block/buzz at
7c789dee…— read only at the second pin; five dependency surfaces inside the cooldown, nothing installed or run. Scope recorded against the relay's engram read gate, which keeps an id-lookup exemption the newer result-gated kinds close - logseq/logseq at
8e15eeec…— read only from a shallow clone with a blobless clone for history; a pnpm lockfile and twenty-six manifests inside the seven-day cooldown, one build-time exec, nothing installed or run - tinyhumansai/openhuman
at
97eb9252… - google/adk-python
at
322e3bf0… - aumara-xyz/aukora-kernel
at
b441edc4… - microsoft/autogen
at
027ecf0a… - GoodAI/goodai-ltm
at
22ca10c2… - GoodAI/goodai-ltm-benchmark
at
188e7618…— the companion benchmark, described on the benchmarks page - EverMind-AI/EverOS at
5076683a… - affaan-m/ECC at
8321021c… - skalesapp/skales
at
ce47854a…— BSL 1.1, source-available; a v7.1.0 snapshot that upstream removed from every commit on 18 September 2026, read from the atlas archive; screened at this pin on 2026-09-17: no auto-run surface, one build-time execution surface (apostinstallrunning a nestednpm install), two unpinned surfaces; nothing installed, built or run - Project-N-E-K-O/N.E.K.O
at
bcdd5c2f… - netease-youdao/LobsterAI
at
2921c1e5…— not a report; cited in the OpenClaw analysis - SillyTavern/SillyTavern
at
06bde939… - kwaroran/RisuAI at
669b12ce… - jofizcd/Soul-of-Waifu
at
747048b3… - SugarcaneDefender/z-waif
at
aaf905c1… - yakami129/VirtualWife
at
c8afd6d3… - GOODMAN-PRO/helm
at
f453eaa9… - agno-agi/agno at
85b6d1d1… - aiming-lab/SimpleMem
at
db80b6a7… - pydantic/pydantic-ai
at
a205b282… - camel-ai/camel at
8c791b7b… - microsoft/agent-framework
at
c030fa35… - crewAIInc/crewAI
at
7b796623… - gobii-ai/gobii-platform
at
c9929bf8… - reescalder/agent-memory-supabase
at
b711e6d7… - showjihyun/livingfeed
at
732d8bed… - Cosmonapse/cosmonapse-core
at
47462600… - npc-worldwide/npcpy at
26fc78b5… - juggler-ai/juggler at
4908d8d0… - jihadkhawaja/magicore
at
ae8ba6bb…— formerly jihadkhawaja/mem0sharp; read only - yashneil75/gitlord at
8bfe0aa3…— read only; one commit past the first pin, a version bump with no source change; no auto-run surface, no build-time execution point, one unpinned manifest with no lockfile; nothing installed, built or run - griffinwork40/agent-afk
at
e0a607b1… - CortexPrism/cortex at
0c446572… - can1357/oh-my-pi
at
c5a8e0e0… - Shweta-Mishra-ai/tokenmizer
at
6b26679c… - gi-dellav/zerostack at
16fadb3b… - deeplethe/lethe at
b6053b7b… - NovasPlace/CSM at
9c7cfb22…— read only, audited at an unchanged pin on 2026-09-28 from a full clone; three auto-run surfaces (.mcp.json,hooks/,hooks/hooks.json), eleven floating ranges behind a lockfile, and anAGENTS.mdread as data; the optionalCSM_LIVING_MIND_URLserver was read atf8bdb805…to match its route; nothing installed, built or run - Graphify-Labs/graphify
at
b9cd9570… - mthines/lorekit at
4a4641ff… - SyntheticAutonomicMind/CLIO
at
444398c5…— re-screened on 2026-09-28 from a full clone: one build-time exec path (Makefile) and anAGENTS.mdread as data, no auto-run surface; nothing installed, built or run. - AgentSwarms-fyi/agentswarms
at
cf179dd9…Re-pinned and re-screened on 2026-09-19 after the first reading published a false absence claim: its section 10 said no test file existed anywhere in the repository, and 395 did at that pin. - proxysoul/Empryo
at
64ea2ec8…— renamed fromproxysoul/soulforge - truffle-ai/dexto
at
ac56fbfc…— read only at the second pin; a dependency surface inside the cooldown, so nothing was installed or run. The memory packages did not change;human_reviewre-tested and recorded as delete-only, since pinning is an agent tool - Arvincreator/project-golem
at
210658a1… - openyak/openyak at
bd88bff8… - xD4O/memento at
f8e1dc14… - 12ziyad/universal-memory-engine
at
b17c5486… - unibaseio/membase1.0-sdk
at
9e03b75a… - calibrae/palazzo
at
07a788ac… - youngbryan97/aura
at
19cf16e8…— read only at the fourth pin; each earlier pin is an ancestor; two manifests inside the seven-day cooldown, so nothing was installed and the audit-chain suite was read, having run at the first pin only - JPeetz/MeMex-Zero-RAG
at
f955d993…— read only; the previous pin was fetched by sha after a history rewrite and the two trees compared; one auto-run surface (.mcp.json), one build-time execution point, nothing installed or run - Goldentrii/AgentRecall-X
at
5d3389d2… - riktar/memledger
at
27f67e43… - terse-lang/terse
at
637140a3…— the report coversapps/terse-memory/ - kayba-ai/agentic-context-engine
at
31f4e118… - bytedance/deer-flow at
34bbeb18…— read only at the second pin; nothing installed or run. Both marks re-tested; scope rests on the host always resolving a user, since the default backend's shared index filters conditionally - eanai-ro/ean-agentos
at
0c5e0ecf… - FlowElement-xinliuyuansu/m_flow
at
0d585cda…— audited at this pin on 2026-09-30, which is upstream HEAD; no auto-run surface, five build-time execution points and five unpinned surfaces, read rather than executed; nothing installed, built or run. The published benchmark totals were recomputed fromFlowElement-xinliuyuansu/mflow-benchmarksata04accf3… - Whooptie/NOVA_AI
at
1211abfc…— read only; no auto-run surface, three build-time execution points, ten unpinned requirements, nothing installed or run - WindSeries83/memsem at
8332a236…— read only; the repository moved fromWindSeries69/memsem; no auto-run surface, one build-time execution point, nothing installed or run - velantrian/velantrim-exocortex-crystal
at
692e05e3…— read only; no auto-run surface, one build-time execution point, two unpinned surfaces, nothing inside the cooldown, nothing installed or run - KimGLee/Cambium at
6ed60b8c… - os-tack/ostk-recall at
4c75f920… - Perseus-Computing-LLC/perseus-vault
at
9c829207… - BernhardJackiewicz/provem
at
c1625436… - derekhu0002/Argo
at
607a1c1d… - Renkasha/Sovereign at
86018d65… - patibandlavenkatamanideep/memoryops-ai
at
b357e90b…— read only at v2.5; two dependency surfaces inside the cooldown and fourconftest.pyfiles that execute on pytest collection, so the eval sets, the Mem0 comparison harness and the committed perf runs were read rather than executed - HKUDS/DeepCode at
4bb4fd9c…— read only at the second pin; three dependency surfaces inside the cooldown, so nothing was installed or run. The scope predicate cited by the first reading turned out to live in a repository method with no caller, and the mark now rests on the Python filter that the live listing path applies - PrimeIntellect-ai/prime-agent
at
3bf96596…— read only, from a depth-1 clone; no auto-run surface, one build-time execution surface (the Makefile), nine unpinned surfaces and 23 files inside the seven-day cooldown, a count the shallow clone inflates by dating every file to the tip.AGENTS.mdwas read as data. Nothing was installed and nothing was run. The TypeScript product was replaced by a Rust workspace in39bc99a9…on 30 September 2026. The repository is the artifact behind two papers — arXiv:2608.23552 for the harness and arXiv:2605.09998 for the memory design — whose figures are not reproducible from anything in the tree. MIT, with a note that the Rust code ports a TypeScript product originally copyright 2025 Mario Zechner under MIT - mnemosyne-oss/mnemosyne
at
3bb08dd7… - BasedHardware/omi
at
b38c5457… - kirodotdev/KiroCrew at
a170442f… - fpytloun/mnemory
at
c67b9167… - techtheist/engram
at
ed4fe24d… - munch2u-a11y/Helix-AGI
at
7ecefca0… - munch2u-a11y/AIMAOS at
0d8c58c2… - Cedrick-Coto/Aeris at
68a2bd6d… - MakerViking/mimir
at
ff5b3688…— read only; no auto-run surface, no build-time execution, no manifest inside the cooldown, nothing installed or run - fpytloun/cognis at
f475b8ae… - fpytloun/intaris
at
ba0fb257… - mindmuxai/brain.md at
8064f333… - scrypster/muninndb at
34b505f4…— read only at the second pin; nothing installed or run. Five marks re-tested and given evidence records; contradiction debt now surfaces at session start - CodeAbra/iai-personal-memory-engine
at
c400059a…— read only; the screen found five auto-run surfaces (.claude-plugin/marketplace.json, a Claude Code plugin manifest, and the plugin underplugin/with hooks and an MCP server), four build-time execution paths (setup.py, the Tauribuild.rs, twoconftest.py) and two unpinned manifests, with every lockfile at least thirteen days old, so nothing was installed, built or run. The LongMemEval figures were read from the README and the harness; the seven committed contradiction-benchmark runs were read from their own Markdown and JSON. MIT - Zenghuang-Fu/SESA-Self-Evolving-Search-Agents
at
74de5d77… - Tracer-Cloud/opensre
at
730ebc1a…— read only at the second pin; nothing installed or run. 745 commits on, the memory subsystem moved by 99 lines, all three marks re-tested at the producer, and the rejected-value gap is unchanged - yoloshii/clawmem
at
ba09cb83… - agi-is-going-to-arrive/memory-palace
at
56c9bed3… - vornicx/Midas at
ee9953c1… - carsteneu/yesmem
at
d9e02873… - CortexReach/memory-lancedb-pro
at
93899f88…— MIT declared inpackage.json, no LICENSE file in the tree - wenlan-app/wenlan
at
80528ef3…— the product is named Wenlan - kage-core/kage at
e7cc0876…— GPL-3.0 - esaradev/icarus-memory-infra
at
6e348708… - omega-memory/omega-memory
at
4a3cfc69… - RyjoxTechnologies/Octopoda-OS
at
583ddf19…— MIT for the SDK only; the native engine is proprietary and not in the tree - samvallad33/vestige at
26a54f15…— AGPL-3.0; the benchmark page's numbers were measured on the v3 engine and earlier - varun29ankuS/shodh-memory
at
e44fdce6…— re-pinned three commits on and read from the GitHub API rather than a clone; nothing was installed or run - Mibayy/token-savior at
73e9c7f5…— the tsbench harness is not published; the README says so at this commit - H-XX-D/recall-memory-substrate
at
b448f24e… - RedPlanetHQ/core
at
4a5b18d8…— AGPL-3.0 with a Commons Clause, source-available - yantrikos/yantrikdb-server
at
36dca9ac…— Apache-2.0 - haagndaazer/vibe-cognition
at
e8684fdc… - garrytan/gbrain at
d13aa742…— read only; a.claude-plugin/directory that runs on load and apostinstall, two manifests inside the seven-day cooldown, nothing installed or run - qualixar/superlocalmemory
at
5bfa47c9…— AGPL-3.0 - orneryd/NornicDB
at
e917408d…— MIT perLICENSE.md; no plainLICENSEfile - EmpiricaAI/empirica at
763859dc… - quixiai/hexis at
7423622a… - sweetsophia/noosphere
at
6406d867…— release 1.13.3; read only, twelve manifests inside the cooldown - prefrontal-systems/cortexgraph
at
81a2daa3…— AGPL-3.0 inLICENSE, MIT inCITATION.cff - virtual-context/virtual-context
at
f8319282…— AGPL-3.0 with a commercial-licence contact - SuanmoSuanyangTechnology/MemoryBear
at
e5087b10…— read only at the second pin; no auto-run surface and nothing inside the cooldown, and nothing was installed or run. The scheduled forgetting cycle is commented out at the Celery beat entry while the crontab built from its config is still constructed and unreferenced - jumbocontext/cli
at
30e7947a…— AGPL-3.0 - Modern-Prometheus-AI/Neuroca
at
b4d4198e…— read mid-refactor; the memory integration suites are skipped at module level - winstonkoh87/Athena-Public
at
26b98486…— read only, from a full clone. Ten files scanned, two auto-run surfaces (the committed Claude Code hooks and a devcontainerpostCreateCommand), one build-time execution point, one unpinned surface and one file inside the seven-day cooldown, withCLAUDE.mdandAGENTS.mdread as data. Nothing was installed, built or run - mem9-ai/mem9 at
5af03a68…— read only at the second pin; nothing installed or run.scope_enforcedwithdrawn at unchanged code: the tenant boundary is a database per tenant, and inside it the identity columns are optional filters read from the request body - hamr0/aurora at
750a39da… - AIOSAI/AIPass at
f9c4d6e4…— read only; memory is one of nineteen subsystems in a monorepo; three auto-run surfaces under.claude/, thirty build-time execution points, one manifest inside the seven-day cooldown, nothing installed or run - vbcherepanov/total-agent-memory
at
42c70076…— renamed tototal-agent-memory; the old URL still redirects - OmniNode-ai/omnimemory
at
92b9c1a2…— expire commands reach a compare-and-set with one outcome event each; retrieval serves only unseeded in-memory test doubles; omnimarket (d62a297b…) and omnibase_infra (26706331…) read at their heads for the copied lifecycle and the missing table; screened 2026-11-12, nothing installed or run - christopherkarani/Wax
at
9f79b1a6…— Swift; read on macOS notes only, never built - buildingjoshbetter/TrueMemory
at
063e5b88…— AGPL-3.0; telemetry is opt-out and defaults on. Re-pinned after six commits, all Dependabot bumps touching no source file; both marks re-tested at the producer and unchanged - 9thLevelSoftware/Daem0n-MCP
at
00809c67… - Alby2007/PLTM-Claude-repost-
at
5146bfbf…— MIT declared inpyproject.toml; noLICENSEfile in the tree - zhangfengcdt/memoir at
b8b14fce…— read only at the second pin; nothing installed or run. Three marks re-tested and given evidence records - 24kchengYe/MemoMind at
d45a7a08…— vendors and patches Hindsight; its own Python is 1,411 lines - gitmem-dev/gitmem
at
430d7431… - Harshitk-cp/engram at
4a3d2048…— the third distinct repository named Engram in this atlas - CompleteIdeas/agent-working-memory
at
eb56cb35… - rahilp/second-brain-cloudflare
at
7bd02dab… - JubaKitiashvili/context-mem
at
2a55af0a…— six benchmark harnesses with dated result JSONs committed - nhevers/moltbrain
at
1cb9a703…— AGPL-3.0; the companion Virtuals plugin is a separate repository and was not read - hermes-labs-ai/fidelis
at
1b567a69…— mid-rename fromcogito-ergo; the store path and the benchmark writeup still use the old name - TeleAI-UAGI/telemem at
4f11e89e…— the tech report PDF and arXiv entry were not read; the repository's own files were - alibaizhanov/mengram
at
e90a8caa…— the repository's own spec describes the regression gate as unbuilt; it is implemented and wired in - tickernelz/opencode-mem
at
0c8ed7d5…— read only; no auto-run surface, one build-time execution surface, two unpinned surfaces and two files inside the seven-day cooldown.AGENTS.mdis addressed to a reading agent and was treated as data. Nothing was installed and no test was run.SECURITY_AUDIT.mdis scoped to a commit older than this pin. MIT - CaviraOSS/LongMemory
at
4da4986d…— formerly OpenMemory; read only, nothing installed or run. A rewrite at the same slug: every previously cited file is gone, the report was rewritten,negative_evalwithdrawn for want of any test, andbitemporal,trust_stateandaudit_logadded on the new engine - aayoawoyemi/ori-mnemos
at
db5d3224…—bench/results/is gitignored, so no benchmark run is committed - sachitrafa/yourmemory
at
0bda3e03… - fozikio/cortex-engine
at
a0925da1… - breferrari/obsidian-mind
at
af615d10…— read only at the second pin and audited there on 2026-09-30, which is upstream HEAD; three in-repo auto-run surfaces (plugin manifest, five settings hooks, one MCP server), read rather than executed. The first reading missed a 1,425-case test suite and with it three marks, all of which predate that pin; the audit kept the three marks and corrected the prose and records beside them - djolex999/vir at
e4f180bc… - growth-kinetics/diffmem
at
48ecbb61…— read only; no auto-run surface, no build-time execution and three unpinned dependency surfaces; nothing was installed, built or run, and no command was executed against the router or its HTTP route. MIT declared by a README badge and apyproject.tomlclassifier; no licence file in the tree. Audited on 2026-09-30 at the same pin, which is upstream HEAD - zilliztech/memsearch
at
fc0ef776… - arhuman/mnemos at
8d8d65c6…— read only, past the v0.3.0 tag, from a full clone; no auto-run surface, one build-time execution path in theMakefile,go.modinside the seven-day cooldown andgo.sumpresent. Nothing was installed, built or run; the collection argument, the deny list and the journal flag were read from the MCP tool inputs,internal/search/bm25.goandinternal/memory/service.goagainst the committed tests - dataojitori/nocturne_memory
at
ffb5c709…— read only at the second pin; nothing installed or run. The web backend now runsnpm installat startup when the frontend is unbuilt, which the repository screen cannot see - gupsammy/claudest
at
9088bf8d…— theclaude-memoryplugin of the eight in the marketplace - jordanmccann/agentmemory
at
3aa3b838…— the dataset file the run log names is not committed and was not obtained - vstorm-co/memv at
21891376…— read at the second pin and audited there on 2026-09-30, which is upstream HEAD; two auto-run surfaces in.claude/and two build-time execution points, read rather than executed; nothing installed, built or run. The audit addednegative_evalon committed isolation and expiry cases that predate both pins - maydali28/memcp at
81c7177d… - eshaan-nair/arcrift at
5424ea14…— the browser extension's permissions and network behaviour were not examined - divagr18/memlayer
at
5e95f440… - alash3al/stash at
d34ed430… - rahulmranga/knowledge-worker
at
bbb46379… - rlabs-inc/memory-ts at
8fcadf6d… - GoogleCloudPlatform/open-knowledge-format
at
ad30107c… - richarvey/OmniMem
at
ae72d64b…— after the 7.0.8 release, a Rust workspace on SQLite - wikieden/tempomem
at
92181fbb…— read only; nothing installed - BJHYZJ/DovSG at
b355987a…— read only; the six submodules were left uninitialised and the two committed shared objects were not inspected - openmake/openmake_llm
at
1a4089d7…— read only; nine manifests inside the seven-day cooldown, nothing installed or run - DITlieD/ELAI-archive
at
26bf2bc7…— read only; four build-time execution paths and six unpinned surfaces, nothing inside the cooldown, nothing installed - bobaba76/Argos at
755f652a…— read only;requirements.txtinside the seven-day cooldown, nothing installed or run. The repository has since been deleted or made private — it returns 404 with no redirect — and the pinned commit survives only in the atlas's fork,agent-memory-atlas-archive/bobaba76--Argos - jags111/reporecall at
0c0a9ff6…— read only; a committed.mcp.jsonauto-start and aprepublishOnlybuild, nothing installed; a copy of a project whose manifest repository no longer resolves - chenxiachan/thoughtdag
at
d450c982…— read only; three dependency files inside the seven-day cooldown, nothing installed - benmaster82/Kwipu
at
01dd7d40…— read only; one unpinned manifest - drobins25/craft at
7006381d…— read only, from a depth-one clone; four auto-run surfaces read, one manifest inside the seven-day cooldown - polmanas1998-star/holomem
at
b09cb1b0…— read only; one unpinned requirement, two manifests inside the seven-day cooldown - munch2u-a11y/HUMANs at
a1c86c29…— read only; one manifest with no lockfile, one file inside the seven-day cooldown,AGENTS.mdtreated as data - rohitg00/pro-workflow
at
7f7209d7…— read only; three auto-run surfaces read, one unpinned manifest behind a 96-day-old lockfile, MIT asserted with no licence file - Tencent/teamai-cli at
c6367b96…— read only;package.jsoninside the seven-day cooldown,AGENTS.mdandCLAUDE.mdtreated as data - aquifer-labs/artesian
at
14e4f2d9…— read only; no auto-run surface, no build-time execution path, one unpinned dependency surface in the Python bindings,AGENTS.mdandCLAUDE.mdtreated as data - jarmstrong158/context-keeper
at
d08355a4…— read only; seven hook scripts and an MCP start command as auto-run surfaces, one build-time execution path intests/conftest.py,CLAUDE.mdtreated as data - smaramwbc/statewave at
8d4d1e26…— read only; no auto-run surface, three build-time execution paths in pytest conftest files, one manifest inside the seven-day cooldown,AGENTS.mdtreated as data - caura-ai/caura at
c4406e4c…— read only; three auto-run surfaces in the project's own harness configuration, twelve manifests inside the seven-day cooldown, four build-time execution paths, ten unpinned dependency surfaces - shisa-ai/shisad at
e4e33e59…— read only; one auto-run surface, four build-time execution paths, one unpinned dependency surface,AGENTS.mdandCLAUDE.mdtreated as data - doobidoo/mcp-memory-service
at
742f50b1…— read only; seven auto-run surfaces, among them plugin hooks inclaude-hooks/.claude-plugin/hooks.json, seven build-time execution paths, eight unpinned dependency surfaces, an uninstalledpre-commithook payload - zjunlp/LightMem at
8449d574…— read only; no auto-run surface, one build-time execution path, four unpinned dependency surfaces including arequirements.txtwith twenty-six unversioned entries - vshulcz/deja-vu at
910d490f…— read only; six auto-run surfaces, among them hooks declared inline inclaude-plugin/.claude-plugin/plugin.jsonand aPostToolUseFailurehook inclaude-plugin/hooks/hooks.json, ten npm manifests inside the seven-day cooldown, one build-time execution path, six unpinned dependency surfaces - grapeot/context-infrastructure
at
421df58b…— read only; no auto-run surface, no build-time execution path, one unpinned dependency surface,AGENTS.mdtreated as data; no licence file in the repository - Intelligent-Internet/CommonGround
at
10b50ddb…— read only, without submodules; one auto-run surface, one build-time execution path,uv.lockunchanged for 113 days,AGENTS.mdtreated as data. The CG-Cardbox payload store is a submodule and was not present - tenequm/pond at
3507b50a…— read only; one auto-run surface, two manifests inside the seven-day cooldown, two build-time execution paths, four unpinned dependency surfaces - JanYork/llm-wiki-cli
at
11e869f5…— read only; no auto-run surface, three manifests inside the seven-day cooldown, one build-time execution path, one unpinned dependency surface, and nothing was built or run - Haustorium12/continuity-v2
at
4e98d464…— read only; one auto-run surface in the four hook scripts, no manifest, no build-time execution path and no unpinned dependency surface, and nothing was installed or run - siimvene/memspec
at
7c0a47f3…— read only; one auto-run surface in the three Claude Code hooks, one build-time execution path, one unpinned dependency surface, three manifests dated inside the cooldown by the shallow clone's tip date, and nothing was installed, built or run - AlexisOlson/somnigraph
at
6dc4d349…— read only; no auto-run surface, no manifest inside the cooldown, no build-time execution path and no unpinned dependency surface, with a lockfile 161 days old and aCLAUDE.mdtreated as data; nothing was installed or run. Apache-2.0 under a Commons Clause, which is not an open-source licence - slowave-ai/slowave at
23c95142…— read only; one auto-run surface, five build-time execution points, one unpinned dependency surface and one dependency file inside the seven-day cooldown, withuv.lockpresent. Nothing was installed, built or run and no benchmark was reproduced. AGPL-3.0-or-later, with a commercial licence offered separately - ultracontext/ultracontext
at
736b4711…— read only, onmain; three side branches were left unread, one build-time execution path in the JS SDK'spostinstall, eight unpinned dependency surfaces and a root lockfile 100 days old; nothing was installed, built or run - openmasq/openmasq
at
2e401b6f…— read only; a.githooks/directory not installed, ten dependency files inside the seven-day cooldown, nothing installed - no-human-ai/no_human
at
5f99b7af…— read only; twoconftest.pyfiles that execute on collection, six dependency files inside the seven-day cooldown, nothing installed or run - El-AI-Intelligence/engram-format
at
f1e92dad…— read only; both manifests inside the seven-day cooldown, nothing compiled or run - khoj-ai/khoj at
ae229ca8…— read only; a devcontainer and a VS Code settings file that execute on open, five unpinned surfaces, nothing installed or run - Mintplex-Labs/anything-llm
at
90108f98…— read only from a shallow clone; a devcontainer, a.gitmodulesand two VS Code files that run on open, thirteen manifests inside the seven-day cooldown, nothing installed or run - laurent22/joplin
at
981a03c5…— read only from a shallow clone; an.envrcand a VS Code settings file that run on open, over a hundred manifests inside the seven-day cooldown, nothing installed or run - usememos/memos at
14d3c689…— read only from a shallow clone; ago.sumand four manifests inside the seven-day cooldown, nothing installed or run - silverbulletmd/silverbullet
at
b7548912…— read only from a shallow clone; a VS Code settings file that runs on open, ten manifests inside the seven-day cooldown, threebuild.rsfiles and two Makefiles, nothing installed or run - siyuan-note/siyuan at
9f775e8a…— read only from a shallow clone; a pnpm lockfile with thirty-one floating ranges, nothing inside the seven-day cooldown, nothing installed or run - TriliumNext/Trilium at
d78999ff…— read only from a shallow clone; an.envrc, an.mcp.jsonand a VS Code settings file that run on open, twenty-seven manifests inside the seven-day cooldown, four build-time execution points, nothing installed or run - joshhhhhan/VISTA
at
900aa338…— read only; apyproject.tomlinside the seven-day cooldown with no lockfile beside it, nothing installed or run - marsmanleo/marsnme at
25b7d6c1…— the hosted service was not used - The-825/breadcrumbs at
f07fbd51…— the fleet architecture its docs describe is not in the tree; screened again 2026-11-12, two agent-addressed files read as data, no auto-run or unpinned surface - HamedMP/matrix-os
at
f155f1a1…— read only; two auto-run surfaces, two build-time execution surfaces, twenty-seven unpinned surfaces and fourteen files inside the seven-day freshness cooldown, ten of them changed the day it was read. Nothing was installed and nothing was run;AGENTS.mdandCLAUDE.mdwere read as data. AGPL-3.0 - veracium-ai/Veracium
at
c31bd9f0…— read only, from a full clone; four files scanned, one auto-run surface (server.json, a registry manifest), one build-time execution point (tests/conftest.py), one unpinned dependency surface and one dependency file inside the seven-day cooldown, bothpyproject.toml. Nothing was installed, built or run and no benchmark was reproduced. MIT - VectifyAI/OpenKB
at
ff54396e…— read only; one auto-run surface, one build-time execution surface, one unpinned surface, and both lockfiles unchanged for more than a month.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were treated as data. Nothing was installed and nothing was run. Apache-2.0 - munch2u-a11y/Habitus-AI
at
f93b770e…— read only; no auto-run surface, no build-time execution surface, one unpinned surface, and apyproject.tomlmodified the same day. Nothing was installed and nothing was run. Apache-2.0 - infiniflow/ragflow at
302ada2c…— read only; one auto-run surface (.github/copilot-instructions.md, a stale template still carrying(fill)placeholders and naming arequirements.txtabsent from the tree), thirty-six build-time execution surfaces, eight unpinned surfaces and nine files inside the seven-day cooldown,go.modandgo.sumamong them on the day of reading. Nothing was installed, no container was started and nouv,make,goor npm command was run.AGENTS.mdandCLAUDE.md, which is a symlink to it, are addressed to a reading agent and were recorded as data. Read for the Memory subsystem; the retrieval-augmented-generation half is a document index and out of scope. Apache-2.0 - openvurp/openvurp
at
fc68e643…— read only; the screen found no auto-run surface and no build-time execution, and two unpinned manifests both changed inside the seven-day cooldown (pyproject.tomlon the day of the pinned commit,channels/wa-bridge/package.jsonthe day before, neither with a lockfile), so nothing was installed and nopip,npmorpytestcommand was run. Test functions were counted withgrep; the CI workflow's own comment says 443 and the tree holds 594. MIT - railstracks/animus at
931cd7ca…— read only; the screen found no auto-run surface and no build-time execution, one unpinned manifest (admin-ui/package.json, 12 floating ranges behind a lockfile) and both lockfiles unchanged for 113 days, so nothing was installed, nocmake,make,npmor Lua command was run, and no binary from the checkout was executed, including the committedtest_hkdfat the tree root.AGENTS.mdandAGENTS.orm.mdare both addressed to a reading agent and were recorded as data; one of their claims names a directory,include/animus_kernel/store/, that is not in the tree. Apache-2.0 - AreevAI/areev at
34f0163c…— read only, from a full clone; one committed git hook that runs only ifcore.hooksPathpoints at it, two build-time execution points, three unpinned dependency surfaces and no dependency file inside the seven-day cooldown.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run and no benchmark was reproduced. Dual MIT or Apache-2.0 - Taki7980/Ai-workflow
at
ae3d3851…— the screen scanned one file, there being no manifest, lockfile or hook in the tree; the execution surface is fourteen PowerShell scripts it does not parse, read by hand and not run.AGENTS.mdwas read as data. No licence file - ScPlaceholder/MOTH-agent-memory-template
at
d4b404c3…— the screen returnedNOTHING SCANNED, so the execution surface was read by hand: standard library only, writes confined totempfiledirectories inside--selftest, one local-Ollama call. On that basis the tools were run and their output is quoted in the report. Apache-2.0 - Lumen-Labs/brainapi2
at
b434f92a…— read only; no auto-run surface, three build-time execution surfaces, three unpinned surfaces, and four dependency manifests inside the seven-day freshness cooldown. Nothing was installed and nothing was run;AGENTS.mdandCLAUDE.mdwere read as data. BUSL-1.1, Additional Use Grant: None, Change Date 2030-08-13 - sebastianbrzustowicz/Agentic-GraphRAG-Blueprint
at
e33f5f69…— read only; no auto-run surface, two build-time execution surfaces, four unpinned surfaces, and every dependency manifest inside the seven-day freshness cooldown. Nothing was installed and nothing was run. MIT - FareedKhan-dev/all-agentic-architectures
at
cf9d620a…— thememory/package and the twelve architectures that import it; the other twenty-six were skimmed. Read only; two auto-run surfaces (a devcontainerpostCreateCommand, a committed.vscode/settings.json), one build-time execution surface, one unpinned surface and no lockfile. Nothing was installed and nothing was run. MIT - KhanCold/merchantbench
at
f44ce969…— read only; no auto-run surface, no build-time execution surface, four unpinned requirement files and no lockfile. Nothing was installed and nothing was run. Apache-2.0 - memseekai/membukkit at
ecd2cfe9…— read only; no auto-run surface, no build-time execution surface, one unpinned surface, and both lockfiles unchanged for fourteen days. Nothing was installed and nothing was run. Apache-2.0 - OpenHands/software-agent-sdk
at
97dbce5c…— read only; no auto-run surface, fourteen build-time execution surfaces, four unpinned surfaces and six files inside the seven-day cooldown.AGENTS.mdis addressed to a reading agent and was treated as data. Nothing was installed and nothing was run. MIT - NIMI-research/Tycho at
f68912a7…— read only; no auto-run surface, one execution surface (aMakefilewhose default target is worth checking before a baremake) and one unpinned surface. Nothing was installed and nothing was run. Apache-2.0 - ryanbbrown/Retrodict
at
71672e8e…— read only; no auto-run surface, no unpinned surface, and one execution surface intests/conftest.py, which runs on pytest collection before any test does.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were treated as data. Nothing was installed and nothing was run. - Mininglamp-AI/polyphony-arc-3
at
9bb384c2…— read only; no auto-run surface, no execution surface, one unpinned surface. Nothing was installed and nothing was run. MIT, with the vendored ARC-AGI SDK, engine and game files MIT from the ARC Prize Foundation. Screened from a fresh clone at each reading with the same result; the vendored SDK and engine were searched for memory terms, and the published scorecard was recomputed from its per-environment table - github/gh-aw at
9259aea1…— the memory subsystem only; the compiler's other surfaces were not traced - mksglu/context-mode at
f889a053…— Elastic License 2.0; the sandbox executor was not exercised - ollama/ollama at
38fdb5dd…— theagent/package was read at the previous pin and is removed at this one; the inference engine was not read - oraios/serena at
18fa47bf…— the memory subsystem; the language-server tooling was skimmed, not traced - lucasrosati/claude-code-memory-setup
at
a89c275e…— the importer, its cron wrapper and the SessionEnd hook; Obsidian and Graphify are separate and Graphify has its own report - vllm-project/semantic-router
at
b4be720c…— the memory package and its end-to-end suite; the classification and routing halves were not traced - ruvnet/ruflo at
2602b642…— read only at the second pin; ten dependency surfaces inside the cooldown, nothing installed or run.negative_evaladded on a supersession test present at the first pin, on a store now documented as the live hierarchical-memory path - alexgreensh/token-optimizer
at
689cba8a…— PolyForm Noncommercial 1.0.0; the OpenClaw TypeScript half, not the 40,314-line Python core - dahshanlabs/klypix-mcp
at
1f133014…— read only; the dependency surface was inside the seven-day cooldown, so nothing was installed and the committed benchmarks were inspected rather than reproduced - cbalgeman/agent-mesh
at
a8187089…— read only; no third-party dependencies to install, and the two shipped examples were read rather than run - SmythOS/sre at
5c382a1e…— read only; theMemoryManagersubsystem, the fourMemory*components, the security decorator and the SDK chat store, not the LLM-provider or component libraries - QwenLM/Qwen-MM-Plugins
at
07736672…— thevideo-memoryandomni-memorycapabilities; the other thirteen are tool bundles. Read only at the third pin, withpyproject.tomlinside the cooldown; nothing installed, built or run. A node-type exclusion case earnsnegative_eval, andomni-memorystamps its superseded triples on a copy the written store never holds - tinhien11/remem-mcp at
7590cece…— read only at the third pin, 70 commits and four versions on; a manifest was inside the cooldown, so nothing was installed. All four marks re-tested at the producer; the v11 raw fallback dropstrust_statefrom its exclusions and is held off rejected rows by the soft-delete instead - buiilding/Windie-Sandbox
at
bd0dcd8f…— read only; the three declared submodules were left uninitialised and nothing undervendor/was inspected, and the dependency surface changed the same day so nothing was built - potpie-ai/potpie
at
7726221d…— read only; six manifests were inside the seven-day cooldown and aMakefileand fiveconftest.pyexecute on collection, so nothing was installed and the conformance and approval assertions were read rather than run - repowise-dev/repowise
at
04e1dc67…— read only; a.claude-plugin/directory and an MCPserver.jsondeclare start commands, the plugin underplugins/claude-code/registers hooks and an MCP server, five dependency surfaces were inside the seven-day cooldown, and a pytest tree of this size carries manyconftest.pyfiles that execute on collection, so nothing was installed and the published benchmark numbers were read rather than reproduced - zzet/gortex at
2b5480bf…— read only at the second pin; nothing installed or run. Marks hold; the trust record now names the speculative tier that is excluded by default - truefoundry/trueforge
at
4fad485a…— read only at the second pin; eight dependency surfaces inside the cooldown, nothing installed or run. The tenant now comes from the request context, real only under the TrueFoundry authenticator; turn reads still take a session id alone - NORTHTEKDevs/lossless-context-mcp
at
1ef5bf9e…— read only; two auto-run surfaces (thehooks/directory, which is the product, and an MCPserver.json), one build-timepackage.jsonlifecycle script and one unpinned range with a lockfile beside it; the benchmark numbers were read rather than reproduced, and the corpus behind them is the author's own transcript history and is not published - RAZZULLIX/KAISEN
at
b709ecc7…— read only; no auto-run surface, one dependency manifest inside the seven-day cooldown, one unpinned range, and atests/conftest.pythat executes on collection; nothing was installed and no test was run - vercel-labs/fx at
e45d7809…— read only; no auto-run surface, one dependency manifest inside the seven-day cooldown, two unpinned ranges in test packages, and anAGENTS.mdaddressed to a reading agent, recorded as data; the corrupt-file path in the memory tool was established by readingloadMemoriesand its caller rather than by executing them - Cyb3rb1ade/openclaw-plur1bus-memory
at
cf4bc88e…— read only, at tag v7.16.10; no auto-run surface, no manifest inside the seven-day cooldown, nothing installed or run - OmniNode-ai/omniintelligence
at
25ee01e7…— read only, on thedevdefault branch; its framework packages resolve from PyPI, andomnibase_corev0.47.24 andomnibase_infrav0.38.59, the tagsuv.locknames, were read for the evidence-tier ordering, the repository runtime and the view refresh;omnibase_spiandomnimarketwere not read beyond an organisation-wide code search - OmniNode-ai/omniclaude
at
ad7861d7…— read only, on thedevdefault branch; theomnibase-*framework dependencies resolve from PyPI and the sibling OmniNode packages from pinned public git revisions. Both dependency manifests were inside the seven-day cooldown at this pin, so nothing was installed. Audited on 2026-09-20 at the earlier pin: one sentence said two cohort-identity parameters are never passed anywhere in the repository, and the tests pass both at five call sites — the production call site passes neither, which is what the finding rests on. - roandejager/Hillock at
92eebfb9…— read only; its benchmark needs the TALON extraction stack and its first launch fetches 822 MB of GloVe vectors, so nothing was run, and the gate scores were checked by reimplementing the subword encoder and the late-interaction arithmetic in separate code - KTVSUN/memory-compiler
at
e79ee179…— read only, at the third commit of a repository created the same day;screen_repo.pyreported NOTHING SCANNED, so the eleven-file tree was enumerated and read by hand - MythologIQ-Labs-LLC/agent-memory
at
c80f0685…— read only; one auto-run surface (.github/copilot-instructions.md), three manifests inside the seven-day cooldown, nothing installed or run - Osmantic/ODS at
21f4b3a6…— read only; reviewed forods/memory-shepherd/, the only agent-memory mechanism in a tree that is otherwise a deployment system for a local AI stack - jbsalles/Selmem at
8da0e8d1…— read only; no auto-run surface, no build-time execution point and no manifest inside the cooldown; nothing installed, built or run - Tencent/WeKnora at
b82fd6c0…— read only; four dependency surfaces inside the cooldown and six build-time execution points, so nothing was installed or run; reviewed forinternal/**/memory*, the long-term memory subsystem added at v0.8.0, with the surrounding RAG and wiki framework as context - dominiclachance/neurakeep
at
57f1afa2…— read only; both manifests were inside the cooldown, so nothing was installed and the native SQLite module was never built. The local core is Apache-2.0; the product's hosted tier is commercial and was not inspected - alexisfox7/PRO-LONG at
d87233c9…— read only; the sync routine in section 9 of its report was re-derived over scratch files rather than run from the tree, and the 25 committed runs were compared byte for byte against their own sandbox copies. Paper v3 was read against the pinned CLI for which of its ablations have a flag. The screen at this pin reported no auto-run surface, nothing inside the cooldown and two floating npm ranges behind a lockfile. - jerber/arc-code at
6b33c1f7…— read only;tests/conftest.pyexecutes on collection and two dependency surfaces changed the day of the reading, so nothing was installed and no test was run - OmniNode-ai/knowledge_base
at
d7ff5a73…— read only; nothing was installed and the counts come from reading the frontmatter of every artifact in the tree - faisalhussain-devs/MindCache
at
45b904a7…— read only; the manifest had changed four days earlier and carries no lockfile, so nothing was installed and no test was run - szara7678/OpenAkashic
at
6c916d9a…— read only; two MCP manifests declare start commands and two dependency surfaces are unpinned, so nothing was installed and nothing was run - TrianglLabs/otis
at
b8b8aaba…— read only;package.jsonandbun.lockchanged inside the seven-day cooldown and apostinstallis declared, so nothing was installed and no test was run - Q00/ouroboros at
79a423e8…— read only; two harness hooks fire on prompt submit and after every edit, and both dependency surfaces changed inside the cooldown, so nothing was installed and no test was run. The hooks were read first and reach neither the network nor anything outside the project and~/.ouroboros/data - camgitt/memoir at
8de61433…— read only; one auto-run surface (server.json), two manifests inside the seven-day cooldown, nothing installed or run - deepseek-ai/deepseek-harness
at
0d1f5000…— read only; the repository became public hours before the reading, so every one of its 244 dependency surfaces is inside the cooldown and 97 manifests are unpinned. Bothpostinstallscripts were read first and neither reaches the network; nothing was installed and nothing was executed - nutshellai-tech/mobius
at
0f74ca84…— read only; seven dependency surfaces changed inside the cooldown, so nothing was installed and no test was run. Source-available under a bespoke non-commercial licence rather than an OSI-approved one - itechmeat/open-second-brain
at
54bb28d9…— read only; two committed git hooks are activated by the packagepreparescript and were read first (fmt, lint, typecheck only, no network), and two dependency surfaces sit inside the cooldown, so nothing was installed and no test was run - getzep/zep at
495bf728…— read only; nothing was installed, built or run. The committed LoCoMo experiments were read from git rather than rerun, and Graphitiv0.3.21and thezep-cloud3.28.0 SDK were read at their tags for the engine and contract claims - zhongwanjun/MemoryBank-SiliconFriend
at
cf61c419…— read only; the screen returned NOTHING SCANNED, so the execution surface was read by hand. The forgetting curve's behaviour was established by evaluating the expression, not by running the repository - noahshinn/reflexion at
218cf0ef…— read only;.gitmodulespulls further trees on a recursive clone andhuman-eval/setup.pyexecutes at install time, so neither was done. The AlfWorld success trajectories were computed from the committed JSON - langchain-ai/langgraph
at
230927fb…— read only; 8 dependency surfaces sit inside the cooldown. The backend divergences reported were read from the SQL and from the absence of a pragma, not observed in a running store - langchain-ai/langchain
at
41d35728…— read only; 42 dependency surfaces sit inside the cooldown, and the monorepo is the rare fully lockfiled tree here, with zero unpinned surfaces - NirDiamant/Agent_Memory_Techniques
at
dacb760a…— read only; nineteen unpinned requirements and atests/conftest.pythat runs on pytest collection, so nothing was installed and no notebook was executed. The code was read by extracting the notebook cells as source - xai-org/grok-build at
37949780…— read only; 102 dependency surfaces sit inside the cooldown and sevenbuild.rsfiles execute at build time, so nothing was installed and the tree was never compiled. The deletion gap reported was established by reading the clear path against the index location, not by running a store - crlome/runar-forge at
68224879…— read only; the cleanest screen of anything read this round, with no auto-run surface, no build-time execution and no unpinned manifest, but four dependency surfaces inside the cooldown, so nothing was installed or built. The graduation cap reported was established by reading the caller against the list query's ORDER BY - martian56/redcell
at
cb557584…— read only; five unpinned manifests and eight dependency surfaces inside the cooldown, so nothing was installed or run. The scope call — findings in, the LangGraph checkpointer out — was made by tracing what the assistant reads back against what the checkpointer stores - kovartravis/neuron at
14872690…— read only; one auto-run surface (the.claude/settings.jsonhooks the system installs), two build-time execution points, nothing installed or run - cytostack/openwolf at
521fbc47…— read only, at release 2.1.0; no auto-run surface, one build-timeprepublishOnly, and bothpackage.jsonandpnpm-lock.yamlchanged the same day, inside the seven-day cooldown, so nothing was installed and nothing was run. The reflection cron's whole-file replacement ofcerebrum.mdwas established by readingrunAiTaskagainst the shipped cron manifest, not by executing it - juanceresa/sift-kg at
d786991c…— read only; no auto-run surface, atests/conftest.pythat executes on pytest collection and no lockfile besidepyproject.toml, so nothing was installed and no stage of the pipeline was run. The claim that a rebuild discards the review decisions was established by readingbuild's inputs against whereapply-mergeswrites - outworked/outworked at
89ed7b99…— read only, at v0.4.3; no auto-run surface, one build-time lifecycle script and one unpinned range behind a lockfile, so nothing was installed and the desktop app was never launched. The caller-supplied scope was established by reading the three tool definitions againsthandleMcpRequestand itsagentIdinjection, not by running two agents against one store - Corbell-AI/Corbell at
75c7b20a…— read only; no auto-run surface, atests/conftest.pythat executes on pytest collection, and an unpinnedpyproject.tomlwith no lockfile beside it, so nothing was installed and no command was run. The confirmation-gate finding was established by reading theauto_scandefault against the only assignment toCandidateDoc.confirmed - legoambarish/portable-handoff
at
ec5f203b…— read only, at version 0.1.0; screened on a fresh full clone on 2026-10-18 at the same pin: one build-time execution point (tests/conftest.py) andpyproject.tomlwith no lockfile, so nothing was installed and no capsule was produced. The provenance cap and the fields it skips, the preflight read-back, the finalize merge, the secret scan's skip-list and status, the budget's drop order and the load-time checks and briefing were read frommodels.py,preflight.py,finalize.py,sanitize.py,budgeting.py,storage.py,cli.pyandload.pyagainst the committed tests - memorax-ai/memorax-code
at
1525c20f…— read only; no auto-run surface, three build-time execution points, nine dependency manifests inside the seven-day cooldown, andAGENTS.mdandCLAUDE.mdaddressed to a reading agent, recorded as data. Nothing was installed, no client was deployed and no request was made to the hosted service, so every claim is about the client half: the store behind/v1/memories/*was not exercised. The second reading read the scope key itself —baseUserId@repositoryName, with the collision-resistant key kept local — and found the task-status projection deleted - Lolaplex/agents-memory
at
f9149259…— read only, at version 1.2.0 on a 131-commit history, from a full clone; no auto-run surface, no build-time execution, nothing inside the seven-day cooldown, one unpinned manifest, andAGENTS.mdandCLAUDE.mdaddressed to a reading agent, recorded as data. Nothing was installed and no test was run; the hash-anchored id, the scope argument and the rule guard were read fromstore.py,index.pyandrules.pyagainst the ABI they implement - ArihantDeva/heimdall
at
8c7fb780…— read only, re-screened at the re-pin; no auto-run surface, no build-time execution, three files inside the seven-day cooldown and two unpinned dependency surfaces (three floating ranges inpackage.jsonagainst a present lockfile, sixteen>=requirements invendor/graphify/requirements.txt). Nothing was installed, no Graft daemon was started, no reconciler was run and no search was issued, so the verdict ordering, the journal schema and the convergence loop were read frombin/kb_search_verify.pyandbin/lib/; Graft's vendored C source was read only for its licence and vendoring note - thefullnacho/hestia at
5ccaa7b4…— read only; no auto-run surface, one build-time execution point, three unpinned surfaces, nothing inside the cooldown. Nothing was installed, no local model was pulled and no service was started; the memory records are gitignored runtime data and were absent from the checkout, so every claim is about the code that writes them - nanocoai/nanoclaw
at
f5967d3c…— read only; two auto-run surfaces, one build-time execution point, two unpinned surfaces, and bothpackage.jsonandpnpm-lock.yamlchanged the same day. Nothing was installed, no container was built and no command from the tree was run - RuneLind/muninn at
34c9e0b5…— read only; one auto-run surface, no build-time execution, one unpinned surface under a lockfile, one dependency file inside the seven-day cooldown. Nothing was installed, no Postgres was started and no test was run - LinzeColin/AgentDatabase
at
e9acee95…— read only; one auto-run surface and a long tail of build-time execution points inside vendored skill reference material. Nothing was installed and no script was run. No licence file is present in the tree - AdultSwimmer/AuraOS at
81dffa9b…— read only; no auto-run surface, two build-time execution points in documentation Makefiles, three unpinned requirement files, nothing inside the seven-day cooldown. Nothing was installed, no model was pulled and no server was started; the two committed.pycfiles were disassembled with the standard library'sdisand not executed. No licence file is present in the tree; the README's License section says MIT - patham9/mettaclaw
at
7b30527b…— read only; the screen returned NOTHING SCANNED, because the repository carries no package manifest of any kind, so the dependency surface was read by hand rather than parsed. PeTTa was not cloned, nothing was installed and no agent was run - singnet/Omega at
78c6691a…— read only; build-time execution declared in sixconftest.pyfiles underAutotests/. Nothing was installed, no container was built and no test was run - NORTHTEKDevs/genome at
ea76cf92…— read only; two auto-run surfaces (mcp.jsonandserver.json, both MCP publication manifests declaring a start command), two build-time execution points (prepublishOnlyin the TypeScript SDK andtests/conftest.pyon pytest collection), two unpinned surfaces, and three files changed three days before the pin, inside the seven-day cooldown. Nothing was installed, no test or benchmark was run, andpython -m genome.verify— the repository's own air-gap receipt — was not invoked - nehloo-interactive/graphnosis-app
at
b79be25d…— read only; one auto-run surface, two build-time execution points, eight unpinned surfaces including a non-registry dependency pinned asgithub:nehloo-interactive/graphnosis-secure-sync#v0.4.1, and aCLAUDE.mdaddressed to a reading agent. Nothing was installed, nothing was built and no test was run. The graph store, its encryption and the op-log codec live in that pinned dependency and were not read; the report covers the sidecar around it and says where its claims stop - vmDeshpande/Arcon
at
f04a5e49…— read only; no auto-run surface, no build-time execution, ten unpinned surfaces and nine files inside the seven-day cooldown. Nothing was installed and no test was run. The README's licence badge points at aLICENSEfile the tree does not contain, so what a reader may do with it is not established by this repository - vmDeshpande/ai-agent-automation
at
86b6072d…— read only, at release v0.12.0; screened again on a full clone on 2026-09-26 at the same pin: one build-time execution point (the rootpreparescript running husky), three unpinned surfaces with lockfiles unchanged for 13 days, two inert husky hook payloads and anAGENTS.mdtreated as data. Nothing was installed and no test was run. The recall service, the store, the embedding adapter, theAgentschema and the one memory test file were read against each other - hellangleZ/Agent-MemoryForge
at
770b4eef…— read only; screened twice at this pin, on 2026-09-13 and on a full clone on 2026-09-26: twoconftest.pyfiles that execute on pytest collection, apyproject.tomlwith no lockfile, fifteen floating ranges inportal-uibehind a lockfile, and nothing inside the seven-day cooldown. Nothing was installed and no suite was run - aakarim/OpenLore
at
d1038017…— re-read at the v0.7.2 release;dashboard/package.jsonand its lockfile inside the 7-day cooldown and aMakefileexecution surface. Nothing was installed, built or run. The shellhistoryquery filters by plain prefix and skips the nested-docset carve-out the filesystem read path enforces - rekal-dev/rekal-cli at
4550e602…— read only; screened on 2026-09-13 and again on a full clone on 2026-09-26 at the same pin: two auto-run surfaces (a.claude-plugin/marketplace manifest and a configured LFS smudge filter over the packed embedding model),go.sumunchanged since 16 July 2026, and an uninstalledscripts/pre-pushhook. Nothing was installed and no suite was run - xerj-org/xerj at
2c31f968…— read only; screened again on a full clone on 2026-09-26: 9 dependency manifests inside the 7-day cooldown, twobuild.rsfiles cargo executes at build time, and two uninstalled git hooks. Nothing was installed, built or run. The boundary between namespaces is a reserved index per namespace behind an index-name authorizer, with no scope key on the document - linggen/linggen-memory
at
9e1c0326…— read only; five auto-run surfaces, among them plugin hooks inplugins/linggen/hooks/hooks.jsonand two dependency manifests changed inside the seven-day cooldown. Nothing was installed and no test was run - JordyZomer/lemmalog at
b8e24dbd…— read only; screened on 2026-09-13 and again on a full clone on 2026-09-26, clean both times: no auto-run surface, no build-time execution point, and aCargo.locklast changed on 2 September 2026.scripts/install.shruns only when invoked.cargo testwas not run, so the claims about tests are claims about their committed source - GuyMannDude/mnemo-cortex
at
fec22efd…— read only; four dependency manifests underintegrations/changed the day of the pin, inside the cooldown, and a build-time execution point. Nothing was installed and the suite was not run - MaxFreedomPollard/Compartment
at
05c2816a…— read only; three auto-run surfaces (a.claude-plugin/marketplace manifest,mcp.jsonandserver.json), atests/conftest.pythat executes on collection, and apyproject.tomlchanged inside the seven-day cooldown. Nothing was installed, no harness was wired and the suite was not run - Dicklesworthstone/cass_memory_system
at
61561508…— read only; an npmpostinstallrunning a patch script, and three dependency files changed two days before the pin, inside the cooldown. Nothing was installed and the suite was not run - nambok/mentedb at
4ba993dc…— read only; screened on 2026-09-13 and again on a full clone on 2026-09-26 at the same pin: two cargobuild.rsbuild-time execution points, floating benchmark requirements and an agent-instructions file. Nothing was installed andcargo testwas not run, so the claims about tests are claims about their committed source - iamtouchskyer/memex at
453c0e33…— read only; screened on 2026-09-13 and again on a full clone on 2026-09-26: six auto-run surfaces — a.claude-plugin/marketplace manifest,.cursorrules,hooks/andhooks/hooks.jsonregistering SessionStart and Stop,server.jsonandsmithery.yaml— two build-time execution points, an npmpreparethat copiesscripts/pre-commitinto.git/hooksand aprepublishOnlybuild, plus a committeddist/, and nothing inside the seven-day cooldown on the second screen. Nothing was installed, no hook was registered and no test was run - framerslab/agentos at
1e992183…— read only, re-pinned one commit on; an npmpreparelifecycle that builds on install and aprepublishOnlychain, nothing inside the cooldown;pnpm-lock.yamllast changed on 20 July 2026. Nothing was installed and no test was run - grpcer/ownmem at
14f4edec…— read only; one auto-run surface and two dependency files changed within the seven-day cooldown, so nothing was installed and neither the self-tests nor the public benchmark was run - Coding-Dev-Tools/engraphis
at
ca790261…— read only; two auto-run surfaces (a.claude-plugin/marketplace manifest and committed.githooks/pre-commit), five build-time execution points, and seven dependency files changed the day of the pin, inside the cooldown. Nothing was installed, no hook was registered and no eval was run. Open-core: the README places hosted sync, analytics and team services outside this repository, and only the local engine was read - kiycoh/silica-core at
3fd11a00…— read only; four auto-run surfaces (a.claude-plugin/marketplace and plugin manifest, ahooks/hooks.jsonregistering SessionStart, PreCompact and Stop, and anmcp.json), three build-time execution points, and bothpyproject.tomlanduv.lockchanged the day of the pin. Nothing was installed, no hook was registered, no eval was run and no vault was opened. One flagged finding is a false positive worth recording:silica/router/states/setup.pymatched the install-time-execution heuristic on its filename and is an FSM state - NORTHTEKDevs/rck
at
440f6259…— read only; no auto-run surface, one build-time execution point (aMakefilein the paper directory), one unpinned surface, nothing inside the cooldown. Nothing was installed, no test was run and no benchmark was executed; the substrate comparison reported here is the project's own measurement, read from its paper and the JSON studies indata/ - aiming-lab/AutoResearchClaw
at
be4ba475…— read only; no auto-run surface, one build-time execution point (tests/conftest.pyon pytest collection), one unpinned surface, nothing inside the cooldown. Nothing was installed and no test was run - Sidharth-Singh10/weave
at
ff8a6afa…— read only; no auto-run surface, no build-time execution, one unpinned surface and three files inside the seven-day cooldown. Nothing was installed, no container was started and no test was run, so the findings come from the tree and its nine migrations. There is noLICENSEfile in the repository - RakuenSoftware/aimee
at
204d4e55…— read only; one auto-run surface (.claude/hooks/), one build-time execution point (src/Makefile), three unpinned manifests, none inside the seven-day cooldown, nothing installed or built; the commit is tagv1.0.2and the tip ofmain, andtesting, whichorigin/HEADdesignates as the default branch, deleted the memory module on 7 November 2026 in01b6cd29… - Starksood/fireweed-mcp
at
b37747b0…— read only; one auto-run surface, one unpinned surface and one dependency file inside the seven-day cooldown, no build-time execution. Nothing was installed and no test was run, so the findings come from the tree. FSL-1.1-ALv2, source-available, converting to Apache 2.0 on 1 January 2028. The README cites recall figures and erasure canaries held in a repository not published at this pin; those are recorded as pointers and not as citations - zeenie-ai/OpenCompany
at
2d238ee6…— read only; no auto-run surface, eight build-time execution surfaces, four unpinned surfaces and two files inside the seven-day cooldown. Nothing was installed and no suite was run, so the findings come from the tree.CLAUDE.mdat the root is addressed to a reading agent and was treated as data. MIT - Open-Finance-Lab/AgenticTrading
at
8df40dbe…— read only; one auto-run surface, five build-time execution surfaces, seven unpinned surfaces and two dependency files changed inside the seven-day cooldown.CLAUDE.mdat the root is addressed to a reading agent and was treated as data. Nothing was installed and nothing was run. OpenMDW-1.0, a model-and-data licence rather than a software one - SenteLabsAI/OpenExecutive
at
c54d0e71…— read only; three auto-run surfaces, two build-time execution surfaces, one unpinned surface, and lockfiles unchanged for 56 and 75 days.CLAUDE.mdat the root is addressed to a reading agent and was treated as data. Nothing was installed and nothing was run. Twelve commits between 11 June and 3 July 2026, with nothing since. Apache-2.0 - buiilding/WindieOS at
da2deadc…— read only; one auto-run surface, one build-time execution point, eight unpinned manifests, lockfiles unchanged for 47–130 days so no cooldown exposure. Nothing installed or run. A distinct repository from the same author's Rust Windie Sandbox, sharing no git history; the embedding-space rebuild and delete gaps were read fromlocal_store.pyagainst the architecture doc and the delete-cleanup tests - Krilliac/Sonder-runtime
at
ad7e59d4…— read only from a full clone; no auto-run surface, no dependency surface inside the cooldown, two build-time execution points (conftest.py,tests/conftest.py), two unpinned requirement files (requirements-dev.txt,requirements-train.txt); Apache-2.0 with no rider. Nothing installed or run; the quarantine base-rate and attribution guards, the outcome-provenance enforcement, thelesson_tombstonesregistry, fact validity intervals, the playbook approval gate, the opt-in authoritative fact journal and the unscopedmemory_searchtool were read fromretriever.py,reflection.py,lesson_pruner.py,server.py,sonder_runtime/adapters/memory_store.py, the playbook modules andsonder_runtime/adapters/persistence/sqlite/against the committed tests. - Anchorstate-Lab/GMR at
7bee2a08…— read only, at release v0.6.6; dependency surfaces inside the seven-day cooldown and the ordinary Cargo build surfaces,Cargo.lockpresent, so nothing was installed or run. The content-addressed transition, theAttempt/ReasonClass/FailureCodetaxonomy, the append-only journal and the drift-surfacing semantics were read fromgmr-coreandgmr-runtimeand cross-checked against the committedgrounding.rsandoperations.rstests - parcadei/Continuous-Claude-v3
at
d07ff4b0…— read only; two.claude/auto-run surfaces (hooks/,settings.json), five floating npm ranges behind a committed lockfile, one floatingopc/pyproject.toml, so nothing was installed or run.opc/was established as the authoritative memory tree (the.claude/scripts/core/*.pycopy has nodb/layer); the daemon extraction, the broken default SQLite backend, the per-session dedup against global recall, the inert confidence and the unstamped embedding column were read fromopc/scripts/core/anddb/againstdocker/init-schema.sqland the compiled hooks - fellowgeek/mcp-memory
at
a50a8770…— read only; one build-time exec (the setup wizard) and one unpinned surface (fastmcp<=3,pyyaml>=6.0), nothing inside the cooldown, so nothing was installed or run. The upsert-and-mirror OKF store, the FTS5 read path, the namespace predicate on retrieve and delete and its optional form on search, thelog.mdchange log, and the write-only handling of OKF'sstatus/verified/stale_afterwere read from the five source files againsttest_memory.py - CloudLLM-ai/mentisdb
at
4c9b9504…— read only; no auto-run surface, one build-time exec, one unpinned surface, so nothing was installed or run. The SHA-256 hash chain and its refuse-to-load verification, the append-only supersession with default exclusion, the relation-hosted validity time, and the Ed25519-verified skill registry were read fromsrc/lib.rs,src/server.rsandsrc/skills.rsagainst the committedinvalidation_search_tests.rs; the two hash-excluded fields and the unverified thought signatures were confirmed against the whitepaper - team-monet/monet
at
9fa38c2d…— read only; FRESH manifests behind a committedpnpm-lock.yaml, so nothing was installed or run. The concept–observation store, the lexical stage/rule binding, the declare/ratify/resolve human loop, the circle scoping and the append-only event logs were read fromengine.ts,gates.ts,mcp-server.tsandresolution.tsagainst the Vitest suite; the "moments" and "corrections" claims were sized against the code - MemTensor/memmy-agent
at
65c1825d…— read only; FRESH manifests across the workspaces, so nothing was installed or run. TheMemory/package was confirmed as the authoritative local SQLite engine (distinct from the MemOS Python package and from the opt-in hosted OpenMem backend); the layered store, the evolution and negative-experience pipelines, the injected per-agent CLI skill and the unscoped main recall were read fromMemory/src/storage/,service/andcli/against the committed tests - GoogleCloudPlatform/generative-ai
(always-on-memory-agent) at
97597c46…— read only; a sample subdir (standalone originShubhamsaboo/always-on-memory-agent, MIT), build-time execution points and unpinned surfaces typical of a Python sample, so nothing was installed or run. The embedding-free SQLite store, the load-and-read query (read_all_memoriesatLIMIT 50, no search), the 30-minute consolidation daemon and the hard-delete correction were read fromagent.pyagainst the README - klairtech/one-agent-many-hats
at
a90396cf…— read only, at 36 commits over three days, under PolyForm Noncommercial 1.0.0; both manifests were inside the cooldown and the two declared dependencies are build-time, so nothing was installed or built. The five memory layers, the write-time lesson refusal, the canary slice and the feedback verdicts were read fromsrc/memory/againsttest/memory.test.ts; the committed working paper was read in its published form at sandeepkavety.com, because the PDF in the tree does not extract to legible text with the tools on this machine - bytechefhq/bytechef at
dc28f0b7…— read only; the knowledge base, the nine chat-memory components, the guardrail advisors and the tenant and environment contexts, not the workflow engine, the connector catalogue or the React client. A Gradle monolith needing Postgres, pgvector and a broker to test, so nothing was built or run and the Testcontainers suites were read rather than executed - codician-team/growmos
at
510deb2d…— read only, at 23 commits on a repository created the same day; three auto-run surfaces all invoking the project's own binary, one manifest changed that day and no lockfile, so nothing was installed and the twenty committed tests were read rather than run - kevin-hs-sohn/hipocampus
at
df88ca19…— read only; the screener reported zero auto-run surfaces becausehooks/hooks.jsonand.claude-plugin/are not on its fixed path list, so the three hooks it registers were found and read by hand. Nothing was installed or run, and the MemAware benchmark the README reports lives in a separate repository that was not read - KnowledgeXLab/MemHarness
at
31329e8e…— read only;agent_system/memory/and the Milvus store, not the vendoredverltrainer or the five environment packages. The stack needs conda, vLLM, flash-attn and a served embedding model, so nothing was installed and the published ALFWorld and WebShop figures were read rather than reproduced — no run artifacts are committed for them - scottrbk/forgetful at
35764a88…— read only; no auto-run surface, threeconftest.pycollection-time surfaces,pyproject.tomlanduv.lockinside the seven-day cooldown, three agent-instruction files read as data; nothing installed or run. - EMI-Group/genesis
at
1ab2e249…— read only; no auto-run surface, one build-time execution point in the Tauri crate, two Rust manifests inside the seven-day cooldown. The commit read on 2026-09-17 wasab8f6f6d, which the project's rebuilt merges left offmainthe same day; this pin is the commit onmaincarrying the identical root tree, so the reading and the pin describe the same bytes - krakozavr/MemContinuum
at
d5d29fbc…— read only; one auto-run surface (eighteen hook scripts a plugin manifest can register), two unpinned dependency surfaces,pyproject.tomlinside the seven-day cooldown, nothing installed or run - l33tdawg/sage at
43dcd61e…— read only; two auto-run surfaces, five build-time execution points, five unpinned surfaces, six manifests inside the cooldown, nothing installed or run - plur-ai/plur at
e26901c1…— read only; three auto-run surfaces (two plugin manifests and a hooks directory), one build-time execution point, twelve unpinned surfaces, nothing installed or run - openzync/openzync-core
at
17cea04b…— read only; no auto-run surface, nine build-time execution points, two unpinned surfaces and two dependency files inside the seven-day cooldown; nothing installed, built or run - Sibyl-Labs/Sibyl-Memory
at
761bfc64…— read only; no auto-run surface, three build-time execution points, four manifests inside the seven-day cooldown, nothing installed or run - MaxMiksa/Auto-Company
at
e1dfce15…— read only; one auto-run surface (.claude/settings.json, which setsbypassPermissionsand allows Bash, Edit and Write), one build-time execution point, three unpinned dependency surfaces and one manifest inside the seven-day cooldown, so nothing was installed or run; still no licence file in the tree against an MIT badge in the README - redhat-et/ripwire
at
e54b688e…— read only; two auto-run surfaces and four unpinned dependency surfaces, none inside the seven-day cooldown.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run and no benchmark was reproduced. Apache-2.0 - casonadams/ripwire-rs
at
5eba0755…— read only, from a full clone, at the head ofmain. No auto-run surface, two build-time execution points (Makefile,build.rs),Cargo.tomlandCargo.lockinside the seven-day cooldown, no unpinned surface;AGENTS.mdread as data. Nothing was installed, built or run. Apache-2.0, with aNOTICEnaming it an independent Rust port of redhat-et/ripwire - swang1024/SAGE at
01466cd1…— read only, at the head ofmain; no auto-run surface, three build-time execution points, one unpinned requirements file, and apoetry.lockunchanged for 88 days so the tree is outside the seven-day cooldown. Nothing was installed and no suite was run; the published accuracy figures were recomputed offline from the committed per-question judge output rather than by re-running the benchmark - 0xranx/OpenContext at
0649e713…— read only, at the head ofmain; no auto-run surface, four build-time execution points, three unpinned manifests each with a lockfile beside it, three lockfiles between 222 and 253 days old, anAGENTS.mdaddressed to a reading agent read as data, and an inertscripts/pre-commitpayload read rather than run. Nothing was installed and no suite was run - bakka22/khabeer at
cd752621…— read only; no auto-run surface, three build-time execution paths all inside the bundled skill library (aconftest.py, asetup.pyand a LaTeXMakefile), the Termux half of the tree left unread, nothing built or installed - Nikeshchaudhary52494/memora
at
4c3d1aa9…— read only; no auto-run surface and no build-time execution path, four dependency manifests inside the seven-day cooldown and two unpinned surfaces; nothing installed or run, and the evaluation ranking was reproduced offline rather than by running the suite - Ste2027/ContextMeld at
77d0acbd…— read only; no auto-run surface, one build-time execution path insrc-tauri/build.rs, four manifests inside the seven-day cooldown and one unpinned surface; nothing installed, built or run - Tanglies/AgentOS
at
08a3af64…— read only, re-pinned 46 commits on; two editor-configuration findings in.vscode/, neither set to run on folder open, oneconftest.pythat executes at pytest collection, and three dependency surfaces changed the same day, all inside the seven-day cooldown. A.gitattributesnew since the previous pin was read before checkout — line-ending and binary markers, nofilter=. The folder was not opened in an editor and nothing was installed or run. - drephantom/memory-garden
at
d7fdb1c7…— read only; no auto-run surface, oneconftest.py, two manifests inside the seven-day cooldown and no unpinned surface; nothing installed or run - codexofc/kept at
8177f233…— read only; no auto-run surface and no build-time execution path, two manifests inside the seven-day cooldown and no unpinned surface; nothing built or run - causewayai/hivemind at
666bfa10…— read only; the previous pin was fetched from the archive fork after a history rewrite and the two trees compared; no auto-run surface, one build-time execution point (aMakefile), nothing inside the seven-day cooldown and no unpinned surface; nothing installed, built or run, and the embedding distances were computed by reimplementing the hash offline - stevefunng/Nuum at
51c9ec34…— read only; no auto-run or build-time surface, eight manifests and the pnpm lockfile inside the seven-day cooldown, floating ranges under one workspace lockfile,AGENTS.mdread as data; nothing built or run - 410979729/scope-recall-hermes
at
365e5784…— read only from a full clone; no auto-run surface, threeconftest.pyfiles that run at pytest collection,pyproject.tomlanduv.lockinside the seven-day cooldown, and anAGENTS.mdread as data; nothing installed, built or run - codecoradev/uteke
at
d69a1cc5…— read only, from a full clone at the head ofdevelopon 10 November 2026; one auto-run surface,server.json, listing a hosted remote MCP endpoint rather than a local start command;Cargo.lock,Cargo.tomland three crate manifests inside the seven-day cooldown; three unpinned surfaces in benchmark and docs tooling;AGENT.mdandAGENTS.mdread as data. Nothing was built or run, the 1,653 test functions were not run, and the LongMemEval headline was recomputed from the committed raw output. Apache-2.0 with no rider. - zzjzzb/ai-memory
at
92082815…— read only; no auto-run surface, three build-time execution paths (twopreparescripts that run cargo at install, a napibuild.rs), five manifests inside the seven-day cooldown and no lockfile committed; nothing built or run, and the tokenizer and hash-embedding figures were computed by reimplementing them offline - Maple-Aikon/janus-graph
at
5a66516f…— read only; no auto-run surface, onetests/conftest.py,pyproject.tomlanduv.lockinside the seven-day cooldown and no unpinned surface; nothing built or run, and the graph schema, group-to-graph mapping and edge invalidation were read in graphiti-core at tagv0.29.3, the versionuv.lockpins - ramakay/claude-self-reflect
at
ca5655a8…— read only; three auto-run surfaces (a Claude Code plugin manifest whose postInstall installs hooks, a committed pre-commit hook, an empty MCP manifest), one build-time path (an npm postinstall that downloads a checksum-verified release binary and does not activate without an opt-in), eleven floating ranges in the docs-site manifest against a present lockfile, three lockfiles unchanged for 23 days; nothing installed, built or run, and the committed eval-kit artifacts were inspected rather than regenerated - deeplethe/utopia
at
e26d97aa…— read only; no auto-run surface and no build-time execution path, one floating version and seven manifests genuinely inside the cooldown on a full clone,web/package.jsonheld reproducible by its pnpm lockfile; nothing installed, built or run, and the linked BIRD Mini-Dev submission opened and read - activeloopai/hivemind
at
ce30de7c…— read only; four auto-run surfaces (a plugin marketplace manifest pointing at a pinned subdirectory of the same repository, and that subdirectory's manifest,hooks/directory andhooks/hooks.json), two build-time execution paths (a postinstall running a tree-sitter native-build heal, a prepare running husky and the build), one unpinned manifest with 26 floating ranges against a present lockfile, none inside the cooldown from a full clone, a pre-commit payload not installed in a bare checkout; nothing installed, built or run - rush-db/rushdb at
67214ab6…— read only; one auto-run surface that turns out to hold no hooks, two build-timepreparescripts, six unpinned manifests with the root lockfile untouched for eleven days,CLAUDE.mdread as data; nothing installed, built or run, the conformance fixture's event id recomputed in Python from the committed JSON - Signet-AI/signetai at
131a90d9…— read only; one auto-run surface in a committed.githooks/that the rootpreparescript would activate, five build-time execution paths, 38 manifests and lockfiles inside the cooldown after a release-day version bump, 31 unpinned surfaces in connector, web and benchmark tooling,AGENTS.mdandCLAUDE.mdread as data; nothing installed, built or run, and the LongMemEval headline checked against the committed run ledger, whose per-run rows were recomputed as data - angelnicolasc/graymatter
at
d03c408e…— read only; three auto-run surfaces, all MCP manifests declaring the project's own server with no network fetch and no out-of-tree read, six dependency surfaces inside the cooldown and one unpinned manifest in the docs site; nothing built, installed or run, every benchmark figure read from a committed artifact or the test that pins it - BennettSchwartz/membrane
at
b3f1f091…— read only; screened twice at this pin, on 2026-09-12 and on a full clone on 2026-09-26: no auto-run surface, two build-time execution paths (the Makefile default target and a TypeScriptprepublishOnlychain), no dependency surface inside the seven-day cooldown on the full clone (the thirteen found on 2026-09-12 were depth-1 clone artifacts), nine unpinned surfaces across the SDKs, the harness and a scanning workspace; nothing installed, built or run, and the compounding decay trajectory recomputed from the committed constants in a scratch script - Lyellr88/marm-memory
at
f3d626cb…— read only; no auto-run surface, three build-time execution points (a pnpm-enforcingpreinstalland twoconftest.py), five unpinned dependency surfaces in the Python requirements and the console manifests, oneAGENTS.mdread as data, the console lockfile outside the cooldown at eight days; nothing installed, built or run, and the concept-graph predicate shadowing reproduced by re-implementing the trigger table and its matching loop in a scratch script - lobu-ai/lobu at
462df8b7…— read only; five auto-run surfaces read before anything else and all benign project-local guards, thirty-four manifests inside the cooldown and thirty-four unpinned surfaces, two build-time execution paths,AGENTS.mdandCLAUDE.mdtreated as data; nothing installed, built or run, one submodule left uninitialised, and the live table set recomputed from the 280 migrations in Python rather than read off the baseline dump - ChristopherKahler/base
at
566c7531…— read only; no auto-run surface, one build-time execution path (build.rs, which runsgit rev-parseto stamp the version), nothing inside the seven-day cooldown, two unpinned surfaces (a dashboard manifest above a present lockfile, and 29 unpinned Python requirements for the AST pass),Cargo.lockpresent; nothing installed, built or run, and the licence read as the Functional Source License 1.1 with an Apache-2.0 future licence rather than theNOASSERTIONthe API reports - dcostenco/prism-coder
at
5e509052…— read only; five auto-run surfaces read before anything else (a Claude Code plugin manifest, a.claude/settings.jsonhook pointing at a script absent from the tree, an empty.gitmodules, and MCP and Smithery manifests naming the published npm package), three build-time execution paths, four dependency surfaces inside the seven-day cooldown, 33 floating ranges above a present lockfile, one uninstalled git-hook payload,GEMINI.mdread as data; nothing installed, built or run - Facets-cloud/flow
at
99efdaef…— read only; no auto-run surface, one build-time execution path (theMakefiledefault target), nothing inside the seven-day cooldown (go.modandgo.sumlast changed 23 June 2026), no unpinned dependency surface, andAGENTS.mdread as data; nothing installed, built or run - mnemon-dev/mnemon
at
b0661c0b…— read only; no auto-run surface, one build-time execution path (theMakefiledefault target), five dependency surfaces inside the seven-day cooldown, one floating npm range above a present lockfile, andAGENTS.mdandCLAUDE.mdread as data; nothing installed, built or run, and one check made outside the checkout — the MAGMA abstract, against the README's citation of it - memoket/memoket-kite
at
8745feda…— read only; screened twice at this pin, on 2026-09-12 and on a full clone on 2026-09-26: no auto-run surface, one build-time execution path (tests/conftest.pyat collection), no dependency surface inside the cooldown and one unpinned manifest that declares no runtime dependencies at all; nothing installed, built or run, and two checks made against GitHub rather than the tree at each reading — the release listing, and a GET against the release-asset URL the reproduction downloader constructs - semantica-agi/semantica
at
de2e200e…— read only; no auto-run surface, fourconftest.pyfiles executing at pytest collection, three dependency surfaces changed the day of the pin and two unpinned surfaces (apyproject.tomlwith no lockfile, an Explorer manifest with forty floating ranges above a present lockfile); nothing installed, built or run, and the filtered-deletion behaviour reproduced by transcribing the predicate and its caller into a scratch script outside the tree - EverMind-AI/SkillCorpus
at
c82ca38d…— read only; no auto-run surface, one build-time execution path (aMakefilewhose default target was checked), sixteen dependency surfaces inside the seven-day cooldown because the pin is the day after the tree was last touched, and twelve unpinned surfaces across the requirements files and the plugin manifests; nothing installed, built or run, so no test in this repository was executed, and the published benchmark table was checked against the tree rather than recomputed because no result artifact is committed. Audited on 2026-09-20 at the same pin: two sentences said no feedback signal exists anywhere in the tree, and the consumer plugin emits one for its host — what is absent is anything that persists it. - neo4j-labs/create-context-graph
at
707b168d…— read only, and audited on 2026-09-26 at the same pin, the head ofmain; no auto-run surface, two build-time execution paths (aMakefileand aconftest.pyat collection), one unpinned manifest in the docs site with a lockfile beside it and both lockfiles outside the cooldown,CLAUDE.mdread as data; the dependency neo4j-labs/agent-memory read at itspython-v0.5.0tag,8bd50eff…, for whatadd_entitywrites; nothing installed, built or run, the entity-type distribution and the tool-body domain check recomputed from the committed domain YAMLs in Python - halofyai/halofy at
3763e64f…— read only; no auto-running configuration, no build-time execution path, no manifests inside the cooldown, two unpinned surfaces andAGENTS.mdtreated as data; nothing installed or run, and the test counts taken from the files rather than a run - OriginTrail/dkg at
d499fb2d…— read only; two auto-running editor surfaces (.cursor/mcp.jsonand Cursor rules) read as data, two build-time execution points, no manifests inside the cooldown and 58 unpinned surfaces; nothing installed, built or run, and the chain, economics and synchronization packages outside the reading - bojieli/ai-agent-book
at
cf7f7a8e…— read only and scoped to the Chapter 3 user-memory projects; 27 build-time execution points, 98 unpinned surfaces and two manifests inside the cooldown across the repository; nothing installed or run, and every result read from committed evidence files - modusensus/dsh-mneme
at
5bd2dab7…— read only; one build-time execution point, one unpinned surface and three manifests inside the cooldown; nothing installed or run - remete618/widemem-ai
at
fdf736fc…— read only; one build-time execution point and one unpinned manifest; nothing installed or run; the LoCoMo figure taken from the README since its result files are not committed, and no committed runner scores the adversarial category - LamantinAI/kaeru
at
566b6c6e…— read only; one auto-run surface (an uninitialised benchmarks submodule), three manifests inside the cooldown, one unpinned surface,AGENTS.mdandCLAUDE.mdtreated as data; nothing installed, built or run - AgentToolkit/altk-evolve
at
b81d64ee…— read only; one auto-run surface (a Claude Code marketplace definition), three build-time execution points, two unpinned surfaces and two manifests inside the cooldown,AGENTS.mdtreated as data; nothing installed or run, and the AppWorld figures taken from the results page of the project - benclawbot/open-brain
at
02a7e65a…— MIT declared inpyproject.tomland the README, no licence file; read only; one build-time execution point, two unpinned surfaces, no manifests inside the cooldown,AGENTS.mdtreated as data; nothing installed or run - lna-lab/distill-kura
at
33aec61d…— read only; one unpinned surface and AGENTS.md read as data; nothing installed or run, and the retention score taken from the README since no result files are committed - Abhigyan-Shekhar/Waggle-mcp
at
4d49f2f6…— read only; three MCP manifests that auto-start, one test collection hook and five unpinned surfaces; nothing installed or run - sanonone/kektordb
at
addc5f0c…— read only; three build-time execution points, one unpinned surface, and no dependency file inside the cooldown on a full clone; nothing installed or run - sdsrss/claude-mem-lite
at
0e31b3db…— read only; five plugin, hook and MCP manifests that auto-run, two dependency files inside the cooldown; nothing installed or run, and the LongMemEval figures taken from the README since their result files are not committed - Fmarzochi/EGC at
a46dd1b2…— read only; eight auto-run surfaces, three build-time execution points and three dependency files inside the cooldown; nothing installed or run - riponcm/projectmem at
e8d73137…— read only; one test collection hook, one unpinned surface and one dependency file inside the cooldown; nothing installed or run - diqierjia/StrataGate-AgentMemory
at
f79e986a…— read only; four package lifecycle scripts, four unpinned surfaces and five dependency files inside the cooldown; nothing installed or run - ipiton/agent-memory-mcp
at
ceef5851…— read only; one MCP server manifest and a Makefile, nothing unpinned or inside the cooldown; nothing installed or run - cyberlife-coder/VelesDB
at
614722aa…— read only and scoped to thevelesdb-memorycrate; three auto-run surfaces, eight build-time execution points, seventeen unpinned surfaces and fifty dependency files inside the cooldown; nothing installed or run - omdsh-dev/dsh-mnemon
at
432d69c2…— read only; one build-time execution point, eighteen unpinned surfaces and twenty dependency files inside the cooldown; nothing installed or run - yantrikos/yantrikdb-hermes-plugin
at
c301188e…— read only; two test collection hooks, one unpinned surface and one dependency file inside the cooldown; nothing installed or run - inite-ai/inite-brain-service
at
e57752a0…— read only, from a shallow clone; six auto-run surfaces (a Claude Code plugin manifest, an MCP server manifest declaring a start command, and the plugin underplugins/inite-brain/with hooks and an MCP server), three build-time execution points, five unpinned surfaces and seven dependency files inside the seven-day cooldown across fifteen scanned files, plusAGENTS.mdread as data; nothing was installed and nothing was run - hjqcan/GoodMemory
at
416c15b4…— read only, from a shallow clone; one auto-run surface (an MCP server manifest declaring a start command), one build-time execution point, eleven unpinned surfaces and seventeen dependency files inside the seven-day cooldown across thirty-six scanned files, plusAGENTS.mdandCLAUDE.mdread as data; nothing was installed and nothing was run - AVIDS2/memorix at
f7ed6218…— read only, from a shallow clone; three auto-run surfaces (.gitmodules, an.opencode/directory and an MCP server manifest declaring a start command), five build-time execution points, three unpinned surfaces and four dependency files inside the seven-day cooldown across thirty-five scanned files, plusCLAUDE.mdandGEMINI.mdread as data; nothing was installed and nothing was run - markhuangai/dense-mem
at
939c86b2…— read only, from a shallow clone; one auto-run surface (a.githooks/directory), no build-time execution points, two unpinned surfaces and ten dependency files inside the seven-day cooldown across sixteen scanned files, plusAGENTS.mdread as data; nothing was installed and nothing was run - BYK/loreai at
620b8248…— read only, from a shallow clone; no auto-run surfaces, two build-time execution points, seven unpinned surfaces and ten dependency files inside the seven-day cooldown across twenty scanned files, plusAGENTS.mdread as data; nothing was installed and nothing was run - itsXactlY/mazemaker at
25b40641…— read only, from a shallow clone; no auto-run surfaces, no build-time execution points, one unpinned surface and one dependency file inside the seven-day cooldown across two scanned files; nothing was installed, built or run - memtomem/memtomem
at
d844f08c…— read only, from a full clone; seven auto-run surfaces (a.claude-plugin/directory, an MCP registry record,server.json, and two plugins underpackages/, one registering hooks and one declaring an MCP server fetched at run time), two build-time execution points, two unpinned surfaces and five dependency files inside the seven-day cooldown across nineteen scanned files, plusCLAUDE.mdread as data; nothing was installed and nothing was run - ScriptedAlchemy/tracedecay
at
9e2f7bed…— read only, from a shallow clone and scoped to the memory subsystem; three auto-run surfaces (a.githooks/directory, a.gitmodulesand an MCP server manifest), nine build-time execution points, three unpinned surfaces and forty-nine dependency files inside the seven-day cooldown across sixty-eight scanned files, plusAGENTS.mdandCLAUDE.mdread as data; thecodegraphsubmodule was not fetched, and nothing was installed, built or run - RamaAditya49/titen at
a68ce063…— read only, from a shallow clone; two auto-run surfaces (a.claude-plugin/directory and an MCP server manifest), no build-time execution points, two unpinned surfaces and no dependency files inside the seven-day cooldown across thirteen scanned files, plusAGENTS.mdandCLAUDE.mdread as data; nothing was installed and nothing was run - jeffdafoe/llm-memory-api
at
36eb2fb2…— read only, from a full clone; no auto-run surfaces, no build-time execution points, one unpinned surface and two dependency files inside the seven-day cooldown across six scanned files, plusCLAUDE.mdread as data; nothing was installed and nothing was run - latebit-io/demarkus at
f57b348e…— read only, from a full clone; eight auto-run surfaces (.claude-plugin/marketplace.jsonand the plugins underplugins/, two of them declaring hooks inline), one build-time execution point, four unpinned surfaces and thirteen dependency files inside the seven-day cooldown across twenty-five scanned files, plusCLAUDE.mdread as data; nothing was installed and nothing was run - JinyangWang27/people-context
at
f2bfd5ca…— read only, from a shallow clone; three auto-run surfaces (a.claude-plugin/directory, an.mcp.jsonand an MCP server manifest), two build-time execution points, two unpinned surfaces and nine dependency files inside the seven-day cooldown across twenty scanned files, plusAGENTS.mdread as data; nothing was installed and nothing was run - putervision/state-memory-mcp
at
5af4bc3d…— read only, from a shallow clone; four auto-run surfaces (a Cursor MCP config, a Cursor rules directory, a Copilot instructions file and an MCP server manifest), one build-time execution point, one unpinned surface and two dependency files inside the seven-day cooldown across eight scanned files, plusCLAUDE.mdread as data; nothing was installed and nothing was run - code-ministry-ltd/the-librarian
at
c644d25b…— read only, from a shallow clone; five auto-run surfaces, among them plugin hooks inintegrations/claude/hooks/hooks.json, seven build-time execution points, twelve unpinned surfaces and twelve dependency files inside the seven-day cooldown across twenty-nine scanned files, plus the agent-instruction files read as data; nothing was installed and nothing was run - dnotitia/akb at
f3aba459…— read only, from a shallow clone; ten auto-run surfaces, among them plugin hooks inplugins/claude/akb-claude-code/hooks/hooks.json, five build-time execution points, three unpinned surfaces and ten dependency files inside the seven-day cooldown across twenty-five scanned files, plus the agent-instruction files read as data; nothing was installed and nothing was run - gluonfield/jaz at
a99018ab…— read only, from a shallow clone, with thejazmemengine read at4d801b95…, the exact commit itsgo.modpins; eight files scanned, no auto-run surfaces, one build-time execution point, one unpinned surface and four dependency files inside the seven-day cooldown; nothing was installed, built or run - openairymax/agentrt at
2682bfc6…— read only. The seven runtime directories are submodules with relative URLs, so a shallow clone of the superproject leaves them empty;daemonswas fetched by full sha and read atdb4962ad…andheapstoreatd3130dde…, the exact pins the superproject records;openairymax/atomsreturned 404 on GitHub and atomgit.com returned 403 to a non-browser fetch. Nothing was installed, built or run - hhyqhh/inno-agent
at
4fe5cc9f…— read only, from a shallow clone; ten files scanned, no auto-run surfaces, five dependency files inside the seven-day cooldown, six unpinned surfaces including twopackage.jsonfiles with no lockfile beside them and anxlsxdependency from a vendored tarball, and theCLAUDE.mdread as data. Nothing was installed, built or run - rlaope/oh-my-hermes at
4129002f…— read only, from a shallow clone; nine files scanned, one auto-run surface, three build-time execution points, one unpinned surface, one dependency file inside the seven-day cooldown, and theCLAUDE.mdandAGENTS.mdread as data. Nothing was installed, built or run - Bitterbot-AI/bitterbot-desktop
at
cd4562a7…— read only, from a full clone; no auto-run surfaces, five build-time execution points, thirteen unpinned surfaces and thirteen dependency files inside the seven-day cooldown across forty-eight scanned files. Nothing was installed, built or run - yantrikos/yantrikdb at
49c7aac1…— read only, from a shallow clone; the engine repository in its own right, having previously been read only as a pinned dependency of yantrikdb-server at tagv0.22.0. A dependency surface had changed inside the seven-day cooldown. Nothing was installed, built or run - NodeDB-Lab/nodedb
at
124cc53a…— read only, from a shallow clone; a dependency surface had changed inside the seven-day cooldown. Nothing was installed, built or run - offendingcommit/openconcho
at
b5e25646…— read only, from a shallow clone; seventeen files scanned, one auto-run surface, three build-time execution points, three unpinned surfaces, nothing inside the dependency cooldown, and theCLAUDE.mdandAGENTS.mdread as data. Nothing was installed, built or run - sageox/ox at
304ab68a…— read only, from a full clone; 27 files scanned, eight auto-run surfaces, among them hooks declared inline inclaude-plugin/.claude-plugin/plugin.json, one build-time execution point, one unpinned surface, seven dependency files inside the seven-day cooldown, and theCLAUDE.mdandAGENTS.mdread as data. Nothing was installed, built or run - maximem-ai/maximem_synap_sdk
at
e0402c9c…— read only, from a shallow clone; the repository states it is generated and synced out of a private monorepo, so the service behind these clients was not inspectable. Eighty-seven files scanned, no auto-run surfaces, twenty-two build-time execution points, thirty-one unpinned surfaces and thirty-six dependency files inside the seven-day cooldown. Nothing was installed, built or run - saxenauts/syke at
62c1c9cf…— read only, from a shallow clone; six files scanned, no auto-run surfaces, three build-time execution points, no unpinned surfaces and nothing inside the dependency cooldown. Nothing was installed, built or run - Ariestar/sivtr at
a26dc8a3…— read only, from a shallow clone; thirteen files scanned, no auto-run surfaces, one build-time execution point, two unpinned surfaces, seven dependency files inside the seven-day cooldown, and theCLAUDE.mdandAGENTS.mdread as data. Nothing was installed, built or run - UnknownAlienHuman/eliot-memory-os
at
3590b344…— read only, from a shallow clone; 195 files scanned, no auto-run surfaces, three build-time execution points, no unpinned surfaces, and 187 dependency files inside the seven-day cooldown. The repository's documentation protocol andAGENTS.md, both addressed to reading agents, were read as data and not followed. Nothing was installed, built or run - dfrostar/neuralmind at
434efc69…— read only, from a full clone; open-core, MIT exceptneuralmind/tier2/, which is source-available under a Commercial Modules License and was read as source. Sixteen files scanned, no auto-run surfaces, one build-time execution point, three unpinned surfaces, one dependency file inside the seven-day cooldown, and theCLAUDE.mdread as data. Nothing was installed, built or run - DanceNitra/inspeximus
at
2a6fe710…— read only, from a full clone; twenty-five files scanned, five auto-run surfaces, two build-time execution points, eight unpinned surfaces and one dependency file inside the seven-day cooldown. The README's comparative figures against other systems are the project's own measurements and were not reproduced. Nothing was installed, built or run - crustyhacker/pi-jarvis
at
1dab7a41…— read only, from a full clone, at the head ofmain, the v1.14.0 release commit of 11 October 2026. MIT, no rider. Screened before reading: no auto-run surface, no build-time execution point,package.jsonandpackage-lock.jsoninside the seven-day cooldown, three floating dev-dependency ranges against a present lockfile, and anAGENTS.mdread as data. Nothing was installed, built or run. - prjct-app/pi-memory at
b0e913df…— read only, from a full clone; six files scanned, no auto-run surfaces, one build-time execution point (aprepublishOnlyguard that exits unless run in GitHub Actions), one unpinned surface and four dependency files inside the seven-day cooldown. Nothing was installed, built or run - acoz-labs/mandalore at
c28d2e60…— read only, from a full clone; the project describes itself as the memory-only successor toacoz-labs/my-friday, which is not in this atlas. Six files scanned, no auto-run surfaces, no build-time execution points, no unpinned surfaces and two dependency files (go.mod,go.sum) inside the seven-day cooldown;AGENTS.mdread as data. Nothing was installed, built or run - kannaka-labs/kannaka-memory
at
4bd8db6e…— read only, from a full clone. Licensed under the bespoke SPACE CHILD LICENSE v1.0, whose field-of-use restrictions make it not an open-source licence under the OSI definition. Seven files scanned, one auto-run surface (a Claude Code plugin manifest), two build-time execution points, no unpinned surfaces and two dependency files inside the seven-day cooldown. Nothing was installed, built or run - repairman29/chump
at
c532a7fa…— read only, from a full clone. Thirty-nine of the seventy-eight markdown write-ups at the top ofdocs/eval/are stubs recording that the content moved to a private repository; the figures cited come from the thirty-nine that remain public. Ninety-nine files scanned, three auto-run surfaces, three build-time execution points, seven unpinned surfaces and five files inside the seven-day cooldown, withCLAUDE.mdandAGENTS.mdread as data. Nothing was installed, built or run - MarcelRoozekrans/LongtermMemory-MCP
at
7f7f064d…— read only, from a full clone; nine files scanned, four auto-run surfaces, one build-time execution point, one unpinned surface and one dependency file (package-lock.json) inside the seven-day cooldown. Nothing was installed, built or run - OWASP/www-project-agent-memory-guard
at
a1f60687…— read only, from a shallow clone; a defensive middleware rather than a memory store, recorded for its threat taxonomy. Twelve files scanned, one auto-run surface, no build-time execution points, five unpinned surfaces and six dependency files inside the seven-day cooldown. Nothing was installed, built or run - Cipher208/a-memory at
598e2ab1…— read only, from a full clone; ten files scanned, two auto-run surfaces (.cursorrules,hooks/), one build-time execution point (tests/conftest.py), no unpinned surfaces and two dependency files inside the seven-day cooldown (pyproject.toml,uv.lock);AGENTS.md,CLAUDE.mdand.cursorrulesread as data. Nothing was installed, built or run - phanijapps/memex
at
069cd03b…— read only, from a full clone; seven files scanned, no auto-run surfaces, one build-time execution point (tests/conftest.py), no unpinned surfaces and no dependency file inside the seven-day cooldown;AGENTS.mdread as data. Nothing was installed, built or run - yachen4ever/yacmemo at
66fb7866…— read only, from a full clone; re-screened at this pin: no auto-run surfaces, two build-time execution points, two unpinned surfaces and four files inside the seven-day cooldown. Nothing was installed, built or run - ali-ulu/levh at
95dec5b4…— read only, from a full clone; ten files scanned, no auto-run surfaces, one build-time execution point, one unpinned surface and five dependency files inside the seven-day cooldown. Nothing was installed, built or run - ldclabs/anda-db at
e2a2c051…— read only, from a shallow clone; twenty-nine files scanned, no auto-run surfaces, three build-time execution points, three unpinned surfaces and twenty-two dependency files inside the seven-day cooldown. Nothing was installed, built or run - matrixarkai/TemporalStore
at
5eb2c914…— read only, from a shallow clone; thirteen files scanned, six auto-run surfaces, among them plugin hooks inintegrations/claude-plugin/hooks/hooks.json, two build-time execution points, no unpinned surfaces and seven dependency files inside the seven-day cooldown. Nothing was installed, built or run, and no benchmark was executed - MatthewSherlin/mushroomdb
at
3c471986…— read only, from a full clone; thirty-four files scanned, six auto-run surfaces, among them plugin hooks inpackaging/plugin/hooks/hooks.json, two build-time execution points, four unpinned surfaces and no dependency file inside the seven-day cooldown. Nothing was installed, built or run - tpsdev-ai/flair at
0777bda1…— read only, from a full clone; thirty-six files scanned, no auto-run surfaces, twelve build-time execution points, five unpinned surfaces and twelve dependency files inside the seven-day cooldown. Nothing was installed, built or run - theurian/theurian
at
6c3c2827…— read only, from a full clone; sixteen files scanned, no auto-run surfaces, eight build-time execution points, one unpinned surface and three dependency files inside the seven-day cooldown. Nothing was installed, built or run - yantrikos/yantrik-os
at
f063fcef…— read only, from a full clone, with the YantrikDB engine read at the revision the pin names,9aa58992…; 116 files scanned, no auto-run surfaces, 25 build-time execution points, one unpinned surface and five dependency files inside the seven-day cooldown. Nothing was installed, built or run - qilunuojiang9-hue/Huiran-cerebro
at
2f48deb2…— read only, from a full clone; two files scanned, no auto-run surfaces, no build-time execution points, one unpinned surface and nothing inside the seven-day cooldown. Nothing was installed, built or run - DevEstacion/light-mem
at
6c96cb65…— read only, from a shallow clone; eleven files scanned, three auto-run surfaces, one build-time execution point, two unpinned surfaces and three dependency files inside the seven-day cooldown. Nothing was installed, built or run - MegaWiz-Dev-Team/Bifrost
at
936957b3…— read only, from a shallow clone; seven files scanned, no auto-run surfaces, no build-time execution points, one unpinned surface and five dependency files inside the seven-day cooldown. Nothing was installed, built or run - takecchi/mnemora
at
472ea321…— read only, from a full clone; 21 files scanned, no auto-run surfaces, no build-time execution points, four unpinned surfaces and no dependency file inside the seven-day cooldown. Nothing was installed, built or run - genomewalker/chitta-field
at
5e8b30ed…— read only, from a full clone; two files scanned, no auto-run surfaces, one build-time execution point (build.rs, which writes embedding constants intoOUT_DIR), no unpinned surfaces and nothing inside the seven-day cooldown. Nothing was installed, built or run - danielmarbach/mnemonic
at
dbac069d…— read only, from a full clone; nine files scanned, three auto-run surfaces, one build-time execution point, one unpinned surface and two dependency files inside the seven-day cooldown. Nothing was installed, built or run - Who-Visions/NouGenShards
at
b570cf2f…— read only, from a full clone; twenty-nine files scanned, two auto-run surfaces, two build-time execution points, four unpinned surfaces and four dependency files inside the seven-day cooldown. Nothing was installed, built or run - fagemx/edda at
ce8b98e0…— read only, from a shallow clone; forty-three files scanned, no auto-run surfaces, two build-time execution points, two unpinned surfaces and thirty-two dependency files inside the seven-day cooldown. Nothing was installed, built or run - asuramaya/osiris
at
4c781169…— read only, from a full clone, at the head ofmain, a commit of 5 October 2026. AGPL-3.0 with no rider. Eleven files scanned, three auto-run surfaces (.claude/settings.json,.githooks/,.mcp.json), one build-time execution point (tests/conftest.py), no unpinned surfaces and nothing inside the seven-day cooldown;CLAUDE.mdwas read as data. Nothing was installed, built or run - Deathburgerz013/HOLO-Invariant
at
1dd96b3a…— read only, from a full clone, at the head ofmain, a commit of 12 October 2026. MIT with no rider. Five files scanned, no auto-run surfaces, one build-time execution point (experiments/os_core/Makefile), one unpinned surface (pyproject.toml) and nothing inside the seven-day cooldown;AGENTS.mdread as data. Nothing was installed, built or run, and no benchmark was executed - kunickiaj/codemem
at
6391c66b…— read only, from a shallow clone; thirty-three files scanned, six auto-run surfaces, among them plugin hooks inplugins/claude/hooks/hooks.json, one build-time execution point, eight unpinned surfaces and fourteen dependency files inside the seven-day cooldown. Nothing was installed, built or run - TianpeiLuke/Tessellum
at
6e167169…— read only, from a shallow clone; four files scanned, no auto-run surfaces, no build-time execution points, one unpinned surface and two dependency files inside the seven-day cooldown. Nothing was installed, built or run - The-Geek-Freaks/NEOTH
at
efdeaad9…— read only, from a full clone; 47 files scanned, no auto-run surfaces, three build-time execution points, no unpinned surfaces and eight dependency files inside the seven-day cooldown. Nothing was installed, built or run - TRUE-BLUE-INDUSTRIES/hungry-hippa
at
3cddd2ad…— read only, from a shallow clone; two files scanned, no auto-run surfaces, no build-time execution points, one unpinned surface and one dependency file inside the seven-day cooldown. Nothing was installed, built or run - adea-ai/cortana at
f26a1ac2…— read only, from a full clone; twenty-three files scanned, one auto-run surface (a committed pre-commit hook, inert untilcore.hooksPathpoints at it), one build-time execution point, three unpinned surfaces and fourteen dependency files inside the seven-day cooldown. Nothing was installed, built or run - cdeust/Cortex at
d02917d4…— read only, from a shallow clone; twenty-five files scanned, eleven auto-run surfaces, among them hooks declared inline in.claude-plugin/plugin.json, four build-time execution points, no unpinned surfaces and four dependency files inside the seven-day cooldown. Nothing was installed, built or run - TAIPANBOX/engram
at
240a4d9d…— read only; three files scanned, no auto-run surfaces, no build-time execution points, one unpinned dependency surface and one dependency file inside the seven-day cooldown. Nothing was installed, built or run.CLAUDE.mdis addressed to a reading agent and was recorded as data. Apache-2.0 - claudin-io/claudinio-brain
at
6b6e5741…— read only; nine files scanned, three auto-run surfaces (a Claude Code plugin manifest and two hook directories registering SessionStart, Stop and UserPromptSubmit), no build-time execution points, one unpinned dependency surface and none inside the seven-day cooldown, withCargo.lockpresent and unchanged for fourteen days. Nothing was installed, built or run. MIT - GiulioDER/RE-call
at
ab4d37de…— read only; fifteen files scanned, six auto-run surfaces (the.claude-plugin/marketplace manifest, thehooks/payload directory, an MCPserver.jsonthat launches auvxpackage, and the plugin underplugin/with hooks and an MCP server), three build-time execution points (recall/setup.py, which executes at install time,tests/conftest.py, which runs on pytest collection, and theMakefiledefault target), one unpinned dependency surface underbenchmarks/, and no dependency file inside the seven-day cooldown, withuv.lockpresent. Thehooks/pre-commitpayload is uninstalled and inert.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run, and no PostgreSQL was started, so every claim in the report is read from source. AGPL-3.0-only, with a commercial licence beside it - okf-memory/okf-agent-memory
at
2649a282…— read only; eight files scanned, two auto-run surfaces, two build-time execution points, no unpinned surfaces and one dependency file inside the seven-day cooldown.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run. MIT - lets-order-some-fries/loreweave
at
303a4183…— read only; four files scanned, one auto-run surface (server.json, an MCP manifest that launches the package throughnpx), one build-time execution point (prepublishOnly), one unpinned dependency surface behindpackage-lock.json, and nothing inside the seven-day cooldown. Nothing was installed, built or run. MIT - suanlab/temvera at
81cde831…— read only; four files scanned, no auto-run surfaces, no build-time execution points, one unpinned dependency surface and no dependency file inside the seven-day cooldown.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run, and none of the paper's verification scripts were executed. Apache-2.0 - bnomei/mindreader
at
d7d1bb39…— read only; six files scanned, one auto-run surface, no build-time execution points, no unpinned surfaces and three dependency files inside the seven-day cooldown, withCargo.lockpresent.AGENTS.mdis addressed to a reading agent and was recorded as data. Nothing was installed, built or run and no Neo4j server was started. MIT - aureliocpr-ctrl/verimem
at
2635d28d…— read only; five auto-run surfaces, three build-time execution points and two unpinned dependency surfaces, nothing inside the seven-day cooldown.CLAUDE.mdis addressed to a reading agent and was recorded as data. Nothing was installed, built or run, no judge model was fetched, and the benchmark figures in the report are the project's own measurements rather than reproductions. Dual-licensed AGPL-3.0 with a paid commercial option, and the licensing file carries no rider restricting analysis - thedatasense/anatid at
aa7edcdf…— read only; no auto-run surfaces, two build-time execution points, two unpinned dependency surfaces and two dependency files inside the seven-day cooldown. Nothing was installed, built or run and no DuckDB file was opened. MIT - memhtml/memhtml at
a8fa9950…— read only; no auto-run surfaces, no build-time execution points, one unpinned dependency surface and eighteen dependency files inside the seven-day cooldown, withpnpm-lock.yamlpresent.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run, no integration installer was executed and no AWS credential was present. Apache-2.0 - Bitwarelabscom/bwmem
at
1d0acee2…— read only; no auto-run surfaces, one build-time execution point, one unpinned dependency surface and two dependency files inside the seven-day cooldown, withpackage-lock.jsonpresent. Nothing was installed, built or run, and no PostgreSQL, Redis or Neo4j was started. AGPL-3.0 - ali-ulu/huqan at
26cf8e66…— read only; two auto-run surfaces (a devcontainerpostCreateCommandrunningnpm ci, and.github/copilot-instructions.md), one build-time execution point, one unpinned dependency surface and two dependency files inside the seven-day cooldown.AGENTS.mdis addressed to a reading agent and was recorded as data. Nothing was installed, built or run and the quickstart was not executed. AGPL-3.0 - yifanfeng97/ontomem at
154bf488…— read only; four files scanned, no auto-run surfaces, one build-time execution point, no unpinned surfaces and nothing inside the seven-day cooldown, withuv.lockpresent. Nothing was installed, built or run and no embedding model was loaded. Apache-2.0 - yantrikos/yantrik-mind
at
7fa2c04b…— read only, from a full clone; thirty files scanned, one auto-run surface (a Codex MCP config), two build-time execution points, no unpinned dependency surfaces and nothing inside the seven-day cooldown, withCargo.locktracked. Reviewed without a licence file. The YantrikDB engine it pins was cloned at tagv0.23.0to check the storage and scope claims. Nothing was installed, built or run - mnesio/mnesio at
5831aa0e…— read only; one auto-run surface, three build-time execution points, three unpinned dependency surfaces and twenty-five dependency files inside the seven-day cooldown. Nothing was installed, built or run; the install script was read but not executed and no benchmark was reproduced. Apache-2.0 - richard-wollyce/ulpia
at
1842f3c9…— read only; four auto-run surfaces, no build-time execution points, two unpinned dependency surfaces and twelve dependency files inside the seven-day cooldown.CLAUDE.mdis addressed to a reading agent and was recorded as data. Nothing was installed, built or run and no benchmark was reproduced. Apache-2.0 - jkubo/gaius at
520c2eb1…— read only; four auto-run surfaces, one build-time execution point, no unpinned dependency surfaces and no dependency file inside the seven-day cooldown. Nothing was installed, built or run and no session transcript was extracted. Apache-2.0 - taeyun16/aidememo
at
21f7d1a8…— read only; six auto-run surfaces, among them plugin hooks inplugins/claude/hooks/hooks.json, five build-time execution points, five unpinned dependency surfaces and two dependency files inside the seven-day cooldown, withCargo.lockpresent.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run and no benchmark was reproduced. MIT OR Apache-2.0 - balaianu/CogZ at
edb40d72…— read only, from a full clone. Six files scanned, one auto-run surface (server.json, an MCP registry manifest declaring an OCI image), no build-time execution point, no unpinned dependency surface, andCargo.tomlandCargo.lockinside the seven-day cooldown;AGENTS.mdread as data. Nothing was installed, built or run. MIT - asanabrial/leteo
at
78bc1738…— read only; nine auto-run surfaces (a Claude Code marketplace manifest, an MCP server manifest, and the plugins underplugin/claude-code/andplugin/zcode/, each with hooks and an MCP server), one build-time execution point (build.rs, which runsgitfor the build identity), no unpinned dependency surface, and five dependency files inside the seven-day cooldown, withCargo.lockpresent.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run and no benchmark was reproduced. MIT; the embedding model files are Apache-2.0 - wuisabel-gif/MemWhale
at
a124b102…— read only; no auto-run surface, one build-time execution point and one unpinned dependency surface, with one dependency file inside the seven-day cooldown and bothpackage-lock.jsonandCargo.lockpresent.AGENTS.mdis addressed to a reading agent and was recorded as data. Nothing was installed, built or run and no benchmark was reproduced. MIT - Rememora/rememora
at
58ac331e…— read only, from a full clone so dependency ages are the project's own; four auto-run surfaces, among them a pluginSetuphook inplugin/hooks/hooks.json, one build-time execution point, two unpinned dependency surfaces and two dependency files inside the seven-day cooldown, withapp/src-tauri/Cargo.lockunchanged for 143 days.AGENTS.mdandCLAUDE.mdare addressed to a reading agent and were recorded as data. Nothing was installed, built or run and no benchmark was reproduced. MIT - MachineWisdomAI/fava-trails
at
10f689f7…— read only; one auto-run surface in the editor configuration, one build-time execution path in a pytest conftest, two manifests inside the seven-day cooldown, andAGENTS.mdandCLAUDE.mdtreated as data. Nothing was installed, built or run — no uv, no pytest, and no Jujutsu repository created. Apache-2.0 - FreePeak/LeanKG at
fabca1fe…— read only; one auto-run surface, two build-time execution paths, one unpinned surface, two manifests inside the seven-day cooldown, andAGENTS.md,CLAUDE.mdandGEMINI.mdtreated as data. Nothing was installed, built or run — no go build, no make, no npm. Apache-2.0 - CodeSoul-co/Hypha
at
ac77fa9b…— read only; no auto-run surface, one build-time execution path, sixteen workspace manifests carrying floating version ranges, nothing inside the seven-day cooldown. Nothing was installed, built or run — no npm, no vitest, no jest. Apache-2.0 - 23blocks-OS/ai-maestro
at
e68294a4…— read only; two auto-run surfaces both verified benign (an uninitialised plugins submodule, and ahooks/directory holding React hooks rather than git hooks), one manifest inside the seven-day cooldown, one build-time execution path, two floating dependency surfaces. Nothing was installed, built or run — no npm, no vitest, no database opened. MIT - contextstream/mcp-server
at
cdf0b386…— read only; one auto-run surface (server.json, an MCP manifest declaring a start command), two build-time execution paths (a cargobuild.rsand an npmprepublishOnly), and ten dependency manifests changed inside the seven-day cooldown,Cargo.lockamong them. Nothing was installed, built or run — no cargo, no npm, no binary downloaded, and the install script in the README was read as text. MIT - shuruheel/mnestic
at
352bf205…— read only; one auto-run surface, six build-time execution paths (cargo build scripts and node-pre-gyp), five unpinned dependency surfaces including four Python integration packages with no lockfile beside theirpyproject.toml, and three lockfiles unchanged for eight days so nothing inside the cooldown. Nothing was installed, built or run — no cargo, no npm, no pip, no database opened. MPL-2.0 - topoteretes/cognee-rs
at
2fa09d18…— read only; no auto-run surface, five build-time execution paths including two pytestconftest.pycollection hooks and an npmpostinstall, four unpinned dependency surfaces, and 47 files changed inside the seven-day cooldown. Nothing was installed, built or run — no cargo, no npm, no pip, no server started. MIT OR Apache-2.0 - assafkip/kipi-system
at
fb098216…— read only; 21 auto-run surfaces (a Claude Code plugin marketplace manifest,.mcp.jsondeclaring three npx-launched servers,.claude/settings.jsonwith five hook families, committed git hooks,.codex/config.tomlwith MCP servers, and the plugins underplugins/, four of them registering hooks), four pytestconftest.pycollection hooks, and two dependency files changed inside the seven-day cooldown. The four root surfaces were read as data and none executed;AGENTS.mdandCLAUDE.mdwere read as data rather than as instructions. Nothing was installed, built or run. MIT - beevibe-ai/beevibe at
81530cca…— read only; one auto-run surface, no build-time execution path, seven package manifests declaring floating ranges with no lockfile beside them, and a rootpnpm-lock.yamlunchanged for 37 days. Nothing was installed, built or run — no pnpm, no vitest, no database started, and the committed compose files were read as text. Apache-2.0 - dat999zx/knowl at
9065ed1f…— read only; three auto-run surfaces, one build-time execution path, 32 floating dependency ranges behind a committed lockfile, four files changed inside the seven-day cooldown, andCLAUDE.mdread as data. Nothing was installed, built or run — no npm, no vitest, no benchmark executed; the committed result files were read as data. Apache-2.0 - LucieEveille/kiwi-mem
at
b01a0c50…— read only; no auto-run surface, no build-time execution path, one unpinned dependency surface, one file inside the seven-day cooldown, andAGENTS.mdandCLAUDE.mdread as data rather than as instructions. Nothing was installed, built or run — no pip, no Docker, no database started. AGPL-3.0 - Beever-AI/beever-atlas
at
7d791af2…— read only; two auto-run surfaces (.mcp.jsonand aserver.jsonMCP manifest), three build-time execution paths including aMakefiledefault target and two pytestconftest.pycollection hooks, two unpinned dependency surfaces, and three lockfiles unchanged for 77 days. Nothing was installed, built or run — no uv, no pytest, no Docker, no store started. Apache-2.0 - major7apps/pensyve at
9ec26ade…— read only; six auto-run surfaces (a Claude Code plugin marketplace manifest, aserver.jsonMCP manifest, asmithery.yamlpackaging manifest, and the plugin underintegrations/claude-code/with hooks) and four dependency manifests changed inside the seven-day cooldown includingCargo.lock. Nothing was installed, built or run — no cargo, no uv, no Postgres started, and the live-database suite was read rather than executed. Apache-2.0 - kkollsga/kglite at
68bc723a…— read only; every dependency manifest in the workspace,Cargo.lockincluded, changed on the day of the reading, so the whole surface is inside the seven-day cooldown. Nothing was installed, built or run — no cargo, no pip, no server started. MIT - Meridiona/meridian at
a1004682…— read only; two auto-run surfaces (a.claude/settings.jsoncarrying session hooks and four committed git hooks) and three build-time execution paths including two cargo build scripts and an npmprepublishOnly. Both auto-run surfaces were read as data and neither executed; nothing was installed, built or run, and no capture was started. MIT - MihaiBuilds/memory-vault
at
84987337…— read only; one auto-run surface (aserver.jsonMCP manifest), one build-time execution path (a pytestconftest.pycollection hook), and three dependency manifests changed inside the seven-day cooldown. Nothing was installed, built or run — no pip, no Docker, no Postgres started, and the committed pentest script was read rather than executed. MIT - ardiannurcahya/open-graph-memory
at
cf7b0d23…— read only; every dependency manifest in the tree changed on the day of the reading, so the whole surface is inside the seven-day cooldown. Nothing was installed, built or run — no uv, no npm, no Docker, and the runtime gates were read rather than executed. MIT - huggingface/funes
at
942caf87…— read only; no auto-run surface, one build-time execution path (a cargo build script), three dependency manifests changed on the day of the reading, andAGENTS.mdread as data. Nothing was installed, built or run — no cargo, no npm, no TruffleHog, no index built. Apache-2.0 - sliamh11/Deus at
2f24c38a…— read only; two auto-run surfaces (a.claude/settings.jsonwith five hook families and four committed hook scripts) and several build-time execution paths including an npmpreparethat runs husky and a migration script and three pytestconftest.pycollection hooks. Every auto-run surface was read as data and none executed; nothing was installed, built or run. MIT - open-webui/open-webui
at
0a7c1583…— read only, from a full clone so dependency ages are the project's own; no auto-run surface, two build-time execution paths and two unpinned dependency surfaces, nothing inside the seven-day cooldown. Nothing was installed, built or run — no npm, no pip, no Docker, no vector store started, and no embedding call made. Read as a memory system rather than as a chat front-end: the judgement coversmodels/memories.py,routers/memories.pyandutils/memory.py, and the 662 Svelte files around them were not inspected. Open WebUI License, a BSD-3 variant whose added condition governs branding in deployments above fifty users - eleboucher/memini
at
72a7377b…— read only; six auto-run surfaces (a Claude Code plugin manifest, a devcontainerpostCreateCommand, and the plugin underplugin/with hooks and an MCP server), four floating dependency surfaces, and every manifest inside the seven-day cooldown after a run of dependency updates; nothing installed, built or run, and the benchmark table'sresults/source confirmed absent from every commit in the clone's history - mambo-wang/CodeWiki-Plus
at
e06cd5ba…— read only; no auto-run surface, one build-time execution path (tests/conftest.pyat pytest collection),pyproject.tomlanduv.lockinside the seven-day cooldown, and anAGENTS.mdaddressed to a reading agent read as data; nothing installed, built or run - taylorsatula/mira
at
e401d59b…— read only; no auto-run surface, no build-time execution, nothing inside the seven-day cooldown, one unpinned dependency surface with thirty-six requirements not pinned with==, and anAGENTS.mdaddressed to a reading agent read as data; nothing installed, built or run, and the absence of any memory test confirmed withfind . -name "*test*" - text2future/flowix at
d3f5b812…— read only; no auto-run surface, one build-time execution path, two floating dependency ranges and anAGENTS.md-style instruction file read as data, with every manifest inside the seven-day cooldown as an artefact of a--depth 1clone; nothing installed, built or run, and every withheld mark named in the report rather than left silent - conorbronsdon/agent-context-os
at
c3b91a3c…— read only; three auto-run surfaces (agent hooks and an OpenCode command bundle), unchanged since the first pin, and two instruction files read as data, with no build-time execution and nothing inside the seven-day cooldown; nothing installed, built or run, and the committed benchmark tables checked against the rescoring tests - quantamixsol/graqle at
04f05a60…— read only; five auto-run surfaces, among them plugin hooks inplugins/claude-code/graqle/hooks/hooks.json, six build-time execution paths, one floating dependency range and an instruction file addressed to a reading agent read as data; nothing installed, built or run, and the patent notice in the governance middleware recorded as a rider rather than an exclusion - rajkripal/cashew
at
9c886cec…— read only; no auto-run surface, one build-time execution path intests/conftest.py, one unpinned dependency surface changed five days before the reading, and aCLAUDE.mdaddressed to a reading agent read as data; nothing installed, built or run, and the absence of any epistemic state field confirmed against the node columns the repository enumerates itself - zqiren/Orbital at
6b499944…— read only; five build-time execution paths, two instruction files addressed to a reading agent read as data, non-registry and floating dependency sources in the web and demo packages, and every manifest inside the seven-day cooldown as an artefact of a--depth 1clone; nothing was installed, built or run, and the retractions module reported as having no live consumer was confirmed by grepping each of its four public functions across the tree - Astrix-Labs/papez
at
3ef91dd1…— read only; one auto-run surface in an MCP server manifest, two unpinned dependency surfaces, no build-time execution and no instruction file addressed to a reading agent; nothing installed, built or run, and the renamed predecessorgenesys-memorychecked against the corpus before scaffolding - macanderson/stella at
111aff2c…— read only, from a full clone; three auto-run surfaces (committed git hooks and an agent harness's hooks), seven build-time execution paths, floating ranges in the website package, seven manifests inside the seven-day cooldown, and two instruction files addressed to a reading agent read as data; nothing installed, built or run, and the one production producer of edge validity and the one production construction of the recall scope traced at both pins - joslat/agent-memory-dotnet
at
1fe5105c…— read only; three auto-run surfaces (a Copilot instructions file and two VS Code settings files), four unpinned MSBuild reference surfaces, no build-time execution path, and anAGENTS.mdaddressed to a reading agent read as data; nothing installed, built or run, and the two existingagentmemoryreports checked and confirmed to be different projects by different authors - falcoschaefer99-eng/muse-brain
at
a5a98ae7…— read only; one build-time execution path in a publish hook, four unpinned dependency surfaces, three lockfiles unchanged for seventeen days, and no instruction file addressed to a reading agent; nothing installed, built or run, and the CC BY-NC-SA licence on the code recorded in the report as standing policy - arc-labs-ai/brain-db
at
32a77b85…— read only; one auto-run surface in a devcontainer configuration, no build-time execution path, no floating dependency surface and no instruction file addressed to a reading agent, with bothCargo.lockfiles unchanged for forty-seven days; nothing installed, built or run, and every claim taken from the 148-file specification checked against code before being repeated - raphasouthall/neurostack
at
0616b2b6…— read only; one auto-run surface in an MCP server manifest, four build-time execution paths, one unpinned dependency surface, and aCLAUDE.mdaddressed to a reading agent read as data; nothing installed, built or run, and the two files namedsetup.pyconfirmed by reading their headers to be a client-configuration command rather than a distutils script - chopratejas/invalidate
at
edaa56e1…— read only; one build-time execution path in a pytest conftest, two unpinned dependency surfaces, and no instruction file addressed to a reading agent; nothing installed, built or run, and the absence of any tool schema confirmed by reading both provider integrations, which are client wrappers rather than tool surfaces - headroomlabs-ai/headroom
at
bc21c937…— read only; seven auto-run surfaces including a plugin manifest, a devcontainer, a Copilot instructions file, an MCP server manifest and the plugin hooks inplugins/headroom-agent-hooks/hooks/hooks.json, with build-time execution paths and unpinned dependency surfaces across a large polyglot tree and every manifest inside the seven-day cooldown as an artefact of a--depth 1clone; nothing installed, built or run, and the reading scoped to the memory subsystem rather than the compression layer that is the bulk of the repository - mathomhaus/guild
at
139cab9b…— read only; one build-time execution surface in a Makefile whose default target was checked, two instruction files addressed to a reading agent read as data, and a committedgo.sumunchanged for twenty-three days; nothing installed, built or run, and the divergence between the two read paths' status defaults confirmed by reading both where clauses - alexahern0808/RecallWeave
at
9acde4a3…— read only; one build-time execution surface in a Makefile whose default target was checked and two floating ranges with no lockfile in the TypeScript viewer, with no instruction file addressed to a reading agent and an empty Rust dependency list; nothing installed, built or run, and the README badge naming a different account resolved by following the redirect — a rename, not a fork - mkupermann/throughline
at
01975e76…— read only; one build-time execution surface in a Makefile whose default target was checked, two pytest conftest files, three unpinned dependency surfaces and twenty-two floating ranges with a lockfile beside them, and no instruction file addressed to a reading agent; nothing installed, built or run, and the rename fromclaude_memorytraced through the changelog and confirmed distinct from the twoclaude-memreports already here - xg-gh-25/SwarmAI
at
a032aafa…— read only; two auto-run surfaces in an agent harness's hook scripts and settings, and a large set of manifests inside the seven-day cooldown across the backend, the desktop application and the skill templates; nothing installed, built or run, and the absence of any agent-reachable approval route confirmed by reading the repository's one MCP server - Ghost-Frame/Kleos
at
7ce95482…— read only; two committed hook directories inert unlesscore.hooksPathpoints at them, one build-time execution point, three unpinned manifests and nothing inside the cooldown; nothing was installed, built or run, and the Elastic License 2.0 text was read in full for a rider. - ldclabs/anda-brain at
3b176ca0…— read only; no auto-run surface, one build-time execution point, one unpinned surface and five manifests inside the seven-day cooldown, so nothing was installed or run. The reading also openedanda_kipat the=0.13.0this repository pins, fromldclabs/anda-dbat tagv0.13.0, rather than describing the graph model from Brain's call sites. - LeandroPG19/Memorys at
b110ac22…— read only; two auto-run surfaces, one build-time execution point, one unpinned surface and four manifests inside the seven-day cooldown, plus anAGENTS.mdaddressed to a reading agent that was treated as data. Nothing was installed or run, so the retraction described in section 10 of its report is the project's own account rather than a re-measurement. - majiayu000/remem
at
335bb294…— read only; one auto-run surface, two build-time execution points and three manifests inside the cooldown, so the committed eval harness and benchmark were read rather than executed. - oomkapwn/enquire-mcp
at
0db770a4…— read only; one committed git hook payload inert until installed, two build-time execution points and nothing inside the cooldown. The repository shipsllms.txt,llms-ctx.txtand anAGENTS.mdaddressed to reading agents, all of which were read as data. - roboticforce/sugar at
eade1694…— read only; three manifests inside the seven-day cooldown, so nothing was installed or run. Dual licensed AGPL-3.0 or commercial; the Anthropic references in itsTERMS.mdare a trademark disclaimer rather than a rider, and the reading proceeded on that basis. - kargarisaac/lerim
at
5fed45a5…— read only; nothing was installed or run, so the committedbenchmarks/tree was read rather than executed. - Ardha-Eco-System/synapse
at
64c8b14a…— read only; nothing was installed or run, so the string-interpolation surface described in section 9 of its report is traced from the source path rather than attempted. - ddong8/memento at
9f25d7fb…— read only; no auto-run surface and nothing inside the cooldown, and nothing was installed or run. - escoffier-labs/brigade
at
f2b56bc0…— read only; nothing was installed or run, so the committed retrieval-eval harness and its fixtures were read rather than executed. - agentic-os-org/ANOLISA
at
b95908b9…— read only, and scoped to one component: the report coverssrc/agent-memoryand not the other twelve components of the operating system around it. Nothing was installed, built or run, and the crate is Linux-only. - jagoff/memo at
b4d16ca5…— read only; the screen reported six auto-run surfaces, which is inherent to a product that installs hooks and scheduled units, and nothing was installed or run. - context-graph-ai/contextdb
at
e6cf60cf…— read only; nothing was installed, built or run, and the committed benches tree was read rather than executed. It is a database rather than a memory system, and its report says which marks are therefore the caller's to earn. - jayzeng/agentmemory at
901b60dd…— read only; nothing was installed or run, so the probe outcomes in its report are read from the committed dataset rather than from a run. Its slug carries a suffix because the atlas already holds a report for a different repository of the same name. - M4F-S/gomaa at
00ee124d…— read only; nothing was installed or run. - mycelium-hq/ai-brain-starter
at
f22c46e4…— read only; three auto-run surfaces, which is what a hook harness is, and nothing was installed or run, so its guards were read rather than exercised. - jpicklyk/task-orchestrator
at
9f228716…— read only; nothing was installed, built or run. Included rather than excluded as workflow tooling because its notes are durable agent-authored content, full-text indexed and read back across sessions. - ennisaaaaaaaa-stack/tideline-memory
at
07fbd678…— read only, and the screening script reported it could not see an execution surface in this tree, so it was read by hand and the report says so. PolyForm Noncommercial 1.0.0: commercial use is outside the grant. - hermes-labs-ai/zer0dex
at
58776ccd…— read only; taken from an unreported scout shortlist entry rather than a fresh triage selection, the day's allocation having been spent. Nothing was installed or run. - FreshHillyer/xiaoO at
3acadbb3…— read only; taken from an unreported scout shortlist entry dated 2026-09-11 rather than a fresh triage selection, the day's allocation having been spent. The licence is MulanPSL-2.0, declared inCargo.tomland the README and granted inLicense/LICENSE; the GitHub API reports this repository as unlicensed because the file sits in a subdirectory, so the licence was read from the tree rather than taken from the API. Nothing was installed or run. - verrysimatupang99/codex-dev-mcp-suite
at
8a39bce8…— read only, from the day's triage selection at version 3.5.1. MIT. Screened before reading: no auto-running configuration, no build-time execution point, no.gitattributesand no.gitmodules, and five manifests declaring@modelcontextprotocol/sdkat^1.0.0with no lockfile beside any of them. Nothing was installed and nothing was run, including the project's own test runner — the findings about that runner and about the clean-restore path are read from the source. - Sherlockwz/T-Mem
at
dd9e1527…— read only; no auto-running configuration, no build-time execution point, and two unpinned surfaces (pyproject.tomlwith no lockfile, thirteen requirements at>=). Nothing was installed and nothing was run, so the paper's reported accuracies are not reproduced here. MIT. - zai-org/ZCode at
872ad960…— read only, at the repository's only commit. Apache-2.0. Screened before reading: 2 auto-run surfaces (both VS Code configuration, neither declaringrunOn: folderOpen), 2 build-time execution points (prepare: huskyand apostinstallrebuilding node-pty prebuilds), 35 dependency surfaces inside the seven-day cooldown and 29 unpinned manifests;.gitattributeswas read before checkout and carries nofilter=, and there is no.gitmodules.AGENTS.mdis present and was treated as data. Nothing was installed, built or executed. - trycua/cua at
9bbfa7dd…— read only, at the head of the default branch. MIT. Screened before reading: 1 auto-run surface (.vscode/settings.json, carrying formatter, interpreter and colour settings; norunOn: folderOpenexists anywhere in the tree), 23 build-time execution points (four Rustbuild.rs, eightconftest.py, asetup.py, five npm manifests and a Makefile), 152 dependency surfaces inside the seven-day cooldown and 75 unpinned manifests;.gitattributescarries nofilter=and there is no.gitmodules.AGENTS.mdandCLAUDE.mdare present and were treated as data. Nothing was installed, built or executed — no benchmark was run and no recording was made. One finding was reported to the maintainers through the private channelSECURITY.mdrequires. - volotat/mini-AGI
at
7361e7a5…— read only, at the head of the default branch. MIT. The screen reported NOTHING SCANNED, and a hand read of all 56 committed files explains it: no dependency manifest of any kind, noconftest.py, noMakefile, no.envrc, no.gitattributes, no.gitmodules, and.github/holding onlyFUNDING.yml— no auto-run surface, no build-time execution point and no agent-directed file. Nothing was installed, built or executed; the model was never trained or served, and the forgetting probe was not run - strands-agents/harness-sdk
at
15da9dca…— read only, at the head of the default branch. Apache-2.0, Amazon. Screened from a full clone before reading: 0 auto-run surfaces, 27 build-time execution points (19conftest.py, the rootpackage.json'sprepare: husky, and seven example manifests whosepreparerunsnpm ci --prefix ../../..), 32 unpinned dependency surfaces and 19 inside the seven-day cooldown, dated by their own commits..gitattributescarries* text=auto eol=lfand nofilter=; there is no.gitmodules;.claude/and.kiro/hold only symlinks to.agents/skillsand.agents/references, with no settings file and no hooks;.husky/pre-commitruns the project's own lint, build, test, format and type-check scripts, and since 23 September 2026 a staged-Python lint that fetchesruff>=0.16.0,<0.17.0throughuvx; it is inert in a clone.AGENTS.mdandCLAUDE.mdwere treated as data. Nothing was installed, built or executed - elizaOS/eliza at
a7e56b58…— read only, at the head of the default branchdevelop. MIT. Screened before reading: 1 auto-run surface (.gitmodules, declaringelizaOS/llama.cppandelizaOS/electrobun; the clone used--recurse-submodules=noand both were left uninitialised, so every absence claim in that report is scoped to the superproject), 44 build-time execution points including a rootpostinstallrunning three vendored-package patch scripts, 155 unpinned dependency surfaces and 170 inside the seven-day cooldown — that last count is an artifact of a--depth 1clone dating every file to the tip..gitattributescarrieseol=lfnormalisation and nofilter=.AGENTS.mdand twoCLAUDE.mdfiles were treated as data. Nothing was installed, built or executed - gastownhall/gastown at
649b832b…— read only, at the head ofmain, a commit dated 23 July 2026. MIT. Screened before reading: 1 auto-run surface (.githooks/, inert unlesscore.hooksPathpoints at it), 2 build-time execution points (Makefile, an npmpostinstall), no unpinned surface and nothing inside the cooldown;AGENTS.mdwas treated as data. The storage engine was read in gastownhall/beads atv1.0.5, whose screen reported six auto-run surfaces; that clone was read withgrepandsedonly. Nothing was installed, built or executed. - gastownhall/beads
at
a1bc167b…— read only, at the head ofmain, a commit dated 25 September 2026. MIT. Screened before reading: 7 auto-run surfaces (.claude/settings.jsonwith two PreToolUse command filters,.claude-plugin/,.devcontainer/,.githooks/,.github/copilot-instructions.md, andplugins/beads/.claude-plugin/plugin.jsonwith inline SessionStart and PreCompact hooks), 3 build-time execution points and 11 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip;AGENTS.mdandCLAUDE.mdwere treated as data. Only the memory plane was read. Nothing was installed, built or executed. - petabridge/memorizer
at
0c043e4c…— read only, at the head ofdev, a commit dated 11 September 2026. MIT. Screened before reading: no auto-run surface, no build-time execution point and nothing inside the cooldown; three unpinned surfaces, each a.csprojwhose versions are pinned exactly inDirectory.Packages.propsby central package management.AGENT.mdandCLAUDE.mdwere treated as data. Nothing was installed, built or executed. - yantrikos/yantrikdb-mcp
at
364e19a5…— read only, at the head ofmain, a commit dated 19 September 2026. MIT. Screened before reading: 3 auto-run surfaces (.mcp.json,mcp.jsonandserver.json, each launchinguvx yantrikdb-mcp), no build-time execution, 2 unpinned manifests and 2 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip; no agent-instruction file. The engine it installs was read at yantrikos/yantrikdbv0.23.1, the newest release in the manifest's range before the pin, from a partial checkout whose screen showed onebuild.rsand three files inside the cooldown. Nothing was installed, built or executed. - oleksiijko/pmb at
59b6800c…— read only, at the head ofmain, a merge dated 23 September 2026. Apache-2.0. Screened before reading: 1 auto-run surface (server.json, an MCP registry manifest naming the PyPI package, with no command), 3 build-time execution points (Makefile, an npmpostinstall,tests/conftest.py), 2 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 1 unpinned surface (pyproject.toml);.claude/launch.jsonwas treated as data. Nothing was installed, built or executed. - spectrayan/spector at
b9012992…— read only, at the head ofmain, a commit dated 25 September 2026. Apache-2.0, with aNOTICErequiring visible attribution. Screened before reading: no auto-run surface, 2 build-time execution points (npmprepublishOnlyin two packages), 9 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 4 unpinned surfaces; the screen does not parse Maven, andAGENTS.mdwas treated as data. Nothing was installed, built or executed. - rergards/mempalace-code
at
3594fbce…— read only, at the head ofmain, a commit dated 21 September 2026. Apache-2.0. A hard fork of MemPalace; upstream was read at the last shared commit,c30bc9e7…, to separate inherited code from new. Screened before reading: 2 auto-run surfaces (.claude/settings.json, whose hooks run the test suite and linters ongit commit;hooks/, registered by nothing in the tree), 1 build-time execution point (tests/conftest.py), 4 dependency files inside the cooldown, over-counted by the depth-1 clone, and no unpinned surface;AGENTS.mdandCLAUDE.mdwere treated as data. Nothing was installed, built or executed. - nekyialabs/resonant-mind
at
9a08410b…— read only, at the head ofmaster, the v4.0.1 merge dated 19 September 2026. Codependent AI Source-Available License, personal and non-commercial use only; the tree was Apache 2.0 until81bb4d1e…on 30 March 2026. Published as Mind Cloud up to v2.3.1. Screened before reading: no auto-run surface, no build-time execution point, no unpinned surface, andpackage.jsonandpackage-lock.jsoninside the cooldown — the lockfile changed on 19 September 2026 by the API, not only by the depth-1 clone's tip date; no agent-instruction files. Nothing installed, built or run. - nekyialabs/resonant at
4f59e107…— read only, at the head ofmain, the merge of 11 October 2026. Apache-2.0 with a NOTICE crediting Codependent AI; no rider. Moved fromcodependentai/resonant. Screened before reading from a full clone: no auto-run surface, no build-time execution point, nothing inside the cooldown, and three workspace manifests without a lockfile beside them against the rootpackage-lock.json, unchanged for 98 days; no agent-instruction files. Resonant Mind's registry, protocol and auth files were fetched at9a08410anddbee319to check the client against the server. Nothing was installed, built or run. - NickCirv/engram at
df445d31…— read only, at the head ofmain, a commit dated 22 September 2026. Apache-2.0. Screened before reading: 2 auto-run surfaces (.cursorrules, an engram-generated structure summary, andserver.json, an MCP manifest naming theengramxnpm package), 3 build-time execution points (a banner-onlypostinstall, twoprepublishOnlybuilds), 5 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 3 unpinned surfaces;.cursorrules,CLAUDE.mdandCONTEXT.mdwere treated as data. Only the mistake, decision and pattern memory and the storage it shares were read. Nothing was installed, built or executed. - ohad6k/emulo at
a8552916…— read only, at the head ofmain, a merge dated 25 September 2026. MIT. Named Ditto until v0.5.0. Screened before reading: 3 auto-run surfaces (.claude-plugin/manifests with no hooks,server.jsonandsmithery.yamldeclaring the MCP start command), no build-time execution point, 3 unpinned surfaces and 6 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip. Nothing was installed, built or executed. - RMANOV/sqlite-memory-mcp
at
f5d04e6e…— read only, at the head ofmain, a merge commit dated 25 September 2026. MIT. Screened before reading: 1 auto-run surface (hooks/, seven scripts a plugin manifest could register, with no manifest in the tree), 1 build-time execution point (tests/conftest.py), 2 dependency files inside the cooldown — every file in the depth-1 clone dating to the tip — and 2 unpinned surfaces; noAGENTS.mdorCLAUDE.mdpresent. The debate protocol, task manager and private-extension contract were not read beyond what the memory paths touch. Nothing was installed, built or executed. - verygoodplugins/automem
at
0e8c4174…— read only, at the head of the default branchdevelop, a commit dated 28 August 2026. MIT. Screened before reading: no auto-run surface, 3 build-time execution points (Makefileand twoconftest.py), 4 unpinned surfaces, nothing inside the cooldown, andAGENTS.mdandCLAUDE.mdrecorded as data. Its MCP client verygoodplugins/mcp-automem was read at its pin9a0bbf75…for the integration surface; its screen showed 2 auto-run surfaces (.claude-plugin/,server.json), 2 build-time execution points, 1 unpinned manifest with a lockfile and nothing inside the cooldown. Nothing was installed, built or executed. - mex-memory/mex at
5b6e02c9…— read only, at the head ofmain, a commit dated 25 September 2026. MIT. Screened before reading: 1 auto-run surface (.claude-plugin/marketplace.json, a skills marketplace entry), 1 build-time execution point (npmprepare), 5 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 5 unpinned surfaces;AGENTS.mdandCLAUDE.mdwere treated as data. The code graph was read only where Wiki groundings depend on it. Nothing was installed, built or executed. - skynetcmd/m3-memory at
651ae92a…— read only, at the head ofmain, a commit dated 22 September 2026. Apache-2.0, with a NOTICE requesting attribution for the architecture. Screened before reading: 7 auto-run surfaces (.claude-plugin/,.claude/settings.jsonholding only a permission allowlist, a Git LFS rule in.gitattributesmatching no file,.githooks/,hooks/andhooks/hooks.json,server.json), 3 build-time execution points (setup.py, twoconftest.py), 7 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 6 unpinned surfaces;AGENTS.md,CLAUDE.mdandGEMINI.mdwere treated as data. The corememory_itemsstore was read; the chat-log, file-ingestion, wiki and PostgreSQL-sync subsystems only where they touch it. Nothing was installed, built or executed. - ruvnet/RuVector at
5356a84e…— read only, at the head ofmain, a commit dated 23 September 2026. MIT. Screened before reading: 4 auto-run surfaces (.claude/settings.jsonhooks that post commit messages and session summaries topi.ruv.io,.claude/hooks/,.githooks/inert until installed,.gitmoduleswith three submodules left uninitialised), 71 build-time execution points, 79 unpinned surfaces and 594 dependency surfaces inside the cooldown, every file in the depth-1 clone dating to the tip;CLAUDE.mdwas treated as data. The npm hook store, the Shared Brain server and theruvector-agent-memoryandAgenticDBlibrary APIs were read; the vector engine was not. Nothing was installed, built or executed. - off-grid-ai/OGAD
at
7f073cad…— read only, at the head ofmain, a commit dated 25 September 2026. AGPL-3.0-only; thepro/submodule, pinned atd30893ee…ofoff-grid-ai/desktop-pro, is a private repository and was not read. Screened before reading: 4 auto-run surfaces (.claude/settings.json, a permission allowlist with no hooks;.gitattributesLFS filters, checked out with the filters disabled;.gitmodules, left uninitialised;.vscode/settings.json), 2 build-time execution points (an npmpostinstalland apreparethat setscore.hooksPath), 5 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 2 unpinned surfaces, seven of whosefile:dependencies resolve outside the repository;AGENTS.mdandCLAUDE.mdwere treated as data. Nothing was installed, built or executed. - timothywarner-org/context-engineering
at
0f07bdbd…— read only, at the head ofmain, a commit dated 19 September 2026; onlysrc/warnerco/backend/is covered, the labs, notebooks and slide decks being course material. MIT. Screened before reading: 1 auto-run surface (a.gitattributesLFS filter on.zipand.pptx, checked out with the smudge filter disabled), 1 build-time execution point (tests/conftest.py), 14 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 6 unpinned surfaces;CLAUDE.md,.claude/and.github/agents/were treated as data. Nothing installed, built or run. - AEndrix03/Graft at
25485e22…— read only, at the head ofmaster, the v0.2.0 release merge dated 5 October 2026. Apache-2.0. Screened before reading from a full clone: 5 auto-run surfaces (.gitmodules, four third-party submodules left uninitialised; a.claude-plugin/marketplace; and the plugin underplugins/graft/, whose SessionStart and UserPromptSubmit hooks run thegraftbinary), no build-time execution point, 1 dependency file inside the seven-day cooldown, and 2 unpinned surfaces (the MCP server'spyproject.tomlwithout a lockfile, the viewer's floating ranges); an emptyCLAUDE.mdwas treated as data. The committed benchmark results were recomputed from their rows; nothing was installed, built or run - star-ga/mind-mem
at
ddcd7c01…— read only, at the head ofmain, a commit dated 24 September 2026. Apache-2.0. Screened before reading: 5 auto-run surfaces (.cursorrules,.githooks/pre-commit,.github/copilot-instructions.md,hooks/andhooks/hooks.json, whose Stop hook runs capture and can read~/.claude/projectstranscripts), 7 build-time execution points (Makefile,deploy/Makefile,setup.py, threeconftest.py, an npmprepublishOnly), 7 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 3 unpinned surfaces;AGENTS.md,CLAUDE.md,.cursorrulesandAUDIT_FINDINGS_FOR_CLAUDE.mdwere treated as data. The governed write path, admission, recall, namespaces and the MCP ACL were read; the training scripts, benchmarks, SDKs and web console were not. Nothing was installed, built or executed. - paperclipai/paperclip
at
01d9a121…— read only, at the head ofmaster, a commit dated 26 September 2026. MIT. Only the LLM Wiki plugin was scored; thepara-memory-filesskill, the memory connectors and the unimplemented memory-binding design are described in the report and not scored. Screened before reading: no auto-run surface, 1 build-time execution point (a root npmpostinstall), 46 unpinned surfaces and 53 files inside the cooldown, every file in the depth-1 clone dating to the tip;AGENTS.mdwas treated as data. Nothing was installed, built or executed. - google-research/rrsi
at
be50316e…— read only; Apache-2.0; no auto-run surface, no build-time execution point, two dependency files inside the cooldown (a depth-1 clone dates every file to the tip) and one unpinned manifest,pyproject.tomlwith no lockfile;SKILL.mdandPATTERNS.mdread as data; nothing installed, built or run - automatika-robotics/emem
at
82e3da61…— read only, at the head ofmain, a commit dated 22 May 2026. MIT in theLICENSEfile; the README's last line claims all rights reserved. Screened before reading: no auto-run surface, 1 build-time execution point (tests/test_harness/conftest.py), 2 unpinned surfaces (harness/requirements.txt,pyproject.tomlwith no lockfile) and nothing inside the cooldown; no agent instruction files. The paper (arXiv:2606.03374, v2) was read in full; nothing installed, built or run. - taeilkim2465/agentic_memory_distillation
at
2895d10c…— read only; no licence file, so all rights reserved by default;bfcl/common/memory/,toolsandbox/common/memory/, the two harness overlays and the AppWorld baseline trees, with the paper read from the arXiv v1 PDF. No auto-run surface, three build-time execution points (onesetup.pyper AppWorld tree), nothing inside the cooldown, six unpinned surfaces; nothing installed, built or run, and no published figure recomputed — no run output is committed - GoldenGait/FARM-Project
at
2fcaf860…— read only, at the head ofmain, the repository's only commit, authored 27 July 2026. AGPL-3.0-or-later, the licence text with no rider. Screened before reading: 1 auto-run surface (.gitmodules, the YOLOE fork, left uninitialised), 1 build-time execution point (ros/mapping/setup.py), 1 unpinned surface (pyproject.tomlwith no lockfile) and nothing inside the cooldown;CLAUDE.mdwas treated as data. The paper, arXiv:2606.15476, was read at v3. Nothing was installed, built or run. - paolorv/lgr-agent
at
3593e6a4…— read only; Apache-2.0, with the vendoredremembr/under NVIDIA's non-commercial licence and compared with NVIDIA-AI-IOT/remembr by blob hash; screened with no auto-run surface, five build-time execution points and five unpinned dependency surfaces; nothing installed, built or run - NovasPlace/living-mind-cortex
at
f8bdb805…— read only, at the head ofmain, the archive commit dated 5 August 2026. No licence file:README.mdclaims Apache 2.0 and links aLICENSEabsent from the tree. Screened before reading on a full clone: no auto-run surface, 1 build-time execution point (tests/conftest.py), 3 unpinned surfaces (requirements.txt,dashboard/requirements.txt,dashboard/Crucible/requirements.txt) and nothing inside the cooldown; no agent-instruction files. The consuming hook in NovasPlace/CSM was read at9c7cfb22…. Nothing was installed, built or run. - bks-lab/open-bridge at
5f1fe878…— read only, at the head ofmain, a merge commit dated 27 September 2026. MIT. Screened before reading: 3 auto-run surfaces (.claude/hooks/,.claude/settings.jsonwith one Stop hook,.github/copilot-instructions.md), 4 build-time execution points (conftest.pyfiles), 2 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 2 unpinnedpyproject.tomlsurfaces;AGENTS.md,CLAUDE.mdandGEMINI.mdwere treated as data. The memory base, its scripts and the proposal ledger were read; the A2A agent runtime was not. Nothing was installed, built or executed. - Vortx-AI/emem at
4b26f9ef…— read only, at the head ofmain, a commit dated 28 September 2026. Apache-2.0;TERMS.mdcovers only the hosted instance. Screened before reading: 3 auto-run surfaces (.claude-plugin/,.gitmodulesnaming four reference-list submodules left uninitialised,server.json), 3 build-time execution points, 27 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 6 unpinned surfaces;AGENTS.mdwas treated as data. Nothing was installed, built or executed. - cucupac/shellbrain at
aacf66b2…— read only, at the head ofmain, a commit dated 24 September 2026. No licence file in the tree and none declared inpyproject.toml. Screened before reading: no auto-run surface, 14 build-time execution points (conftest.pyfiles), 2 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 2 unpinned surfaces (pyproject.tomlwith no lockfile,pytest>=8.0,<9.0inrequirements.txt); theonboarding_assets/skill and rules files were treated as data. Nothing was installed, built or executed. - PCIRCLE-AI/memesh
at
dd77d78e…— read only, at the head ofmain, a commit dated 28 September 2026 (UTC). MIT. Screened before reading: 3 auto-run surfaces (.claude-plugin/,hooks/,hooks/hooks.json), 2 build-time execution points (npmprepublishOnlyin the root and OpenClaw manifests), 5 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 3 floating surfaces;AGENTS.mdandCLAUDE.mdwere treated as data. No checkout filter and no submodules. Only the memory layer was read; the agent-messaging subsystem is out of scope. Nothing was installed, built or executed. - jungjaehoon-lifegamez/MAMA
at
6738c694…— read only, at the head ofmain, a commit dated 28 September 2026. MIT. Screened before reading: 4 auto-run surfaces (.claude-plugin/marketplace.json, an empty.gitmodules, and the plugin underpackages/claude-code-plugin/, with hooks declared inline and an MCP server fetched at run time), 2 build-time execution points (a huskyprepareand the plugin'spostinstall), 8 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 6 floating surfaces;AGENTS.mdandCLAUDE.mdwere treated as data. The memory tier ofmama-core, its MAMA OS consumers and the Claude Code MCP server and hooks were read. Nothing was installed, built or executed. - Nabzx/mnemosyne at
431f1f0e…— read only, at the head ofmain, a commit dated 28 September 2026. Apache-2.0. Screened before reading: 1 auto-run surface (.githooks/pre-commit, inert unlesscore.hooksPathpoints at it), no build-time execution point, 8 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 4 Python manifests with no lockfile;AGENTS.mdwas treated as data. Nothing was installed, built or run. - tigerless-labs/autoharness
at
f74a9fb4…— read only; four auto-run surfaces (the plugin manifest,.mcp.json,hooks/andhooks/hooks.json), no build-time execution and no dependency manifest, so nothing inside the cooldown and nothing unpinned. Nothing was installed, built or run and no benchmark was reproduced. MIT - 0xK3vin/MegaMemory at
e0bb3c27…— read only, at the head ofmain, tagged v1.6.2 and dated 3 May 2026. MIT. Screened before reading: no auto-run surface, 1 build-time execution point (the npmprepublishOnlyscript), 1 unpinned surface (ten caret ranges inpackage.json, resolved by the committed lockfile) and nothing inside the cooldown, every file in the depth-1 clone dating to the tip; no agent-instruction file is in the tree, and the installer's instruction text and slash commands were treated as data. Nothing was installed, built or executed. - kagura-ai/memory-cloud
at
adefcff4…— read only, at the head ofmain, the v0.82.0 release commit dated 28 September 2026. Apache-2.0 inLICENSE; the Claude Code plugin manifest declares MIT. Screened before reading: 5 auto-run surfaces (claude-hooks/hooks.json,.claude-plugin/,.claude/settings.jsonwith formatter, secret-guard and memory-sync hooks,.github/copilot-instructions.md,server.json), 9 build-time execution points (Makefileand eightconftest.py), 4 dependency files inside the cooldown with every file in the depth-1 clone dating to the tip, and 1 unpinned surface (frontend/package.json, lockfile present);CLAUDE.mdwas treated as data. Nothing was installed, built or run. - Prismer-AI/PrismerCloud
at
5337ca14…— read only, at the head ofmain, a commit dated 29 September 2026. MIT for the SDK; the server backend is closed-source and not in the tree, so only the daemon undersdk/prismerwas read. Screened before reading: 1 auto-run surface (.claude-plugin/marketplace.json, which installs a plugin from npm and is inert unless added as a marketplace), 4 build-time execution points, 11 unpinned surfaces and 15 dependency files inside the cooldown, every one an artifact of the depth-1 clone;CLAUDE.mdwas treated as data. Nothing was installed, built or executed. - memseekai/memseek
at
c2ec72ab…— read only, at the head ofmain, a commit dated 28 September 2026. Apache-2.0. Screened before reading: 6 auto-run surfaces (.claude-plugin/marketplace.json,.vscode/tasks.jsonwith norunOn, and the plugin underintegrations/claude-code/with hooks and an MCP server), 3 build-time execution points (Makefile, twoconftest.py), 3 unpinned surfaces and 7 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip; by history the newest manifest change is dated 16 September 2026. No agent-instruction file is in the tree. Themcp2.0.0 server was read at its tag for argument validation. Nothing was installed, built or executed. - Artexis10/exomem
at
c44eaa0b…— read only, at the head ofmain, a commit dated 30 September 2026; published askb_mcpand renamed in release 0.2.0. AGPL-3.0. Screened before reading: 7 auto-run surfaces (the.claude-pluginmarketplace entry, theserver.jsonMCP manifest, the plugin underplugins/claude-code/with hooks inhooks/hooks.json, and a generated hosted.mcp.json), 4 build-time execution points (asetup.pyunderbenchmarks/and threeconftest.py), 12 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 1 unpinned surface (one caret range resolved by a committed lockfile);AGENTS.md, a symlink toCLAUDE.md, was treated as data. Nothing was installed, built or executed. - d-o-hub/rust-self-learning-memory
at
67edf6ce…— read only, at the head ofmain, a merge dated 29 September 2026. MIT, with aLICENSEcopyright line naming a different holder thanCargo.toml's authors. Screened before reading: 5 auto-run surfaces (.claude/settings.jsonwith hooks runningcargo check,cargo buildandcargo test,.claude/hooks/,.githooks/,.opencode/,.vscode/settings.json), no build-time execution point, no unpinned surface, and 16 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip;AGENTS.md,CLAUDE.mdandGEMINI.mdwere treated as data. Nothing was installed, built or executed. - qyiun666/MemHop at
5e1e1f68…— read only, at the head ofmain, a commit dated 25 September 2026. MIT OR Apache-2.0. Screened before reading: no auto-run surface, 1 build-time execution point (Makefile), no unpinned surface, andgo.modandgo.suminside the cooldown, every file in the depth-1 clone dating to the tip; the per-packageagent.mdfiles were treated as data. Nothing was installed, built or executed. - XBlueSky/cortexes
at
ff2eaeb5…— read only, at the head of the defaultpluginbranch, a merge dated 22 September 2026. Apache-2.0. Screened before reading: 3 auto-run surfaces (.claude-plugin/,hooks/,hooks/hooks.jsonregistering SessionStart and SessionEnd), 1 build-time execution point (cortex-vec/tests/conftest.py), nothing inside the cooldown and 1 unpinned surface (cortex-vec/pyproject.toml, no lockfile); no agent-addressed files. Nothing was installed, built or executed. - hraness/wordcell
at
818e6abc…— read only, at the head ofmain, a commit dated 29 September 2026; published as@hraness/kbuntil release 0.20.0 renamed it. MIT. Screened before reading: no auto-run surface, no build-time execution point, 5 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 4 unpinned surfaces (non-registry Git and release-tarball sources pinned by commit, tag or version, and caret ranges; the rootpackage.jsonwas listed as having no lockfile althoughbun.lockis committed beside it);AGENTS.mdandCLAUDE.mdwere treated as data. The pinned Oh and QMD engines were not read. Nothing was installed, built or executed. - TencentCloud/octop-memory
at
8b6abc3b…— read only, at the head ofmain, the 1.0.0 release merge of 24 September 2026. MIT. Screened before reading: 1 auto-run surface (.githooks/pre-commit, inert unlessmake install-hookssetscore.hooksPath), 1 build-time execution point (Makefile), 2 unpinned surfaces and 5 dependency files inside the cooldown, which a depth-1 clone inflates;AGENTS.mdwas treated as data. Nothing was installed, built or run. - AliceLJY/recallnest at
d1f4915a…— read only, at the head ofmain, a commit dated 25 September 2026; started as a fork of memory-lancedb-pro and not marked as a fork on GitHub. MIT. Screened before reading: 2 auto-run surfaces (the.claude-plugin/marketplace entry launchingscripts/start-server.sh, and.mcp.jsonwith an empty server list), 1 build-time execution point (npmprepublishOnly), 2 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 1 unpinned surface (seven caret ranges resolved by a committed lockfile);CLAUDE.mdwas treated as data. No checkout filter and no submodules. Nothing was installed, built or executed. - AndrewNgo-ini/memoose
at
7708331e…— read only, at the head ofmain, a commit dated 25 September 2026. Apache-2.0. Screened before reading: 4 auto-run surfaces (.claude-plugin/,mcp.json, the plugin manifest, which starts an MCP server fetched at run time, and theharness/hooks/hooks.jsonit names), 1 build-time execution point (tests/conftest.py), 2 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and no unpinned surface;CONTEXT.mdand the skills were treated as data. The project was namedmnemothuntil 9 September 2026. The committed LoCoMo rows were recomputed with a short script; nothing from the tree was installed, built or executed. - zensation-ai/zenbrain
at
9854155a…— read only, at the head ofmain, a commit dated 26 September 2026. Apache-2.0; the paper is CC BY 4.0. Screened before reading: no auto-run surface, no build-time execution point, 11 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 9 floating-range surfaces;AGENTS.mdwas treated as data. The paper's abstract was read from the arXiv API; the Zenodo deposits were not read. Nothing was installed, built or executed. - Obelyth/cortex at
ec57124a…— read only, at the head ofmain, a commit dated 17 September 2026. AGPL-3.0-only. Screened before reading: 1 auto-run surface (.devcontainer/devcontainer.json,postCreateCommandnpm ci --ignore-scripts), no build-time execution point, nothing inside the cooldown and 1 unpinned surface (package.json, 12 floating ranges withpackage-lock.jsonpresent); no agent-addressed files. Nothing was installed, built or executed. - lktiep/cortex-hub
at
e47a1577…— read only, at the head ofmaster, a commit dated 28 September 2026. MIT. Screened before reading: 4 auto-run surfaces (.claude/hooks/,.claude/settings.json,.claude/settings.local.json,.cursorrules), 0 build-time execution points, 10 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 9 unpinned surfaces resolved by the rootpnpm-lock.yaml;AGENTS.md,CLAUDE.mdand.cursorruleswere treated as data. No checkout filter and no submodules. Nothing was installed, built or executed. - mindscale-noah/MindMemOS
at
186db4a7…— read only, at the head ofmain, a merge ofdevelopdated 29 August 2026. MIT as stated in the README; the tree has noLICENSEfile and GitHub reports none. Screened before reading: 0 auto-run surfaces, 4 build-time execution points, 0 dependency files inside the cooldown and 5 unpinned surfaces;skills/mindmemos-cli/SKILL.mdwas treated as data. Nothing was installed, built or executed. - LindaHaviv/second-brain
at
4890df9f…— read only, at the head ofmain, a commit dated 20 September 2026. MIT. Screened before reading: 1 auto-run surface (.claude/settings.json, a PreToolUse hook blocking agent edits to.envfiles), no build-time execution point, nothing inside the cooldown and 1 unpinned surface (oracle/agent/requirements.txt);AGENTS.mdandCLAUDE.mdwere treated as data. The default backend'soracleagentmemorypackage, which publishes wheels only, was not read. Nothing was installed, built or run. - rexleimo/aios at
6e2910a9…— read only, at the head ofmain, a commit dated 28 September 2026. MIT. Screened before reading: 1 auto-run surface (.gitmodules, pulling therex-harnesssubmodule, which was not cloned), no build-time execution, 14 dependency files inside the cooldown — every file in the depth-1 clone dating to the tip — and 6 unpinned surfaces;AGENTS.md,CLAUDE.mdandGEMINI.mdwere treated as data. Only the memory subsystem was read. Nothing was installed, built or executed. - 1173591564/Dynamics-memory
at
9ee06f66…— read only, at the head ofmain, a commit dated 28 September 2026. No licence file, and GitHub reports none. Screened before reading: 1 auto-run surface (.opencode/plugin/memory-bridge.ts, which spawns the sidecar when opencode starts in the tree), no build-time execution point, 12 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 3 unpinned surfaces; tenAGENTS.mdfiles inside the vendored opencode packages underagent/were treated as data. Nothing was installed, built or executed. - JunNanLYS/dsh-layered-memory
at
69028fbe…— read only; MIT; no auto-run surface, no build-time execution, nothing inside the cooldown, one floating surface (package.jsonranges under a committedpnpm-lock.yaml), four subdirectoryAGENTS.mdfiles read as data; nothing installed, built or run, and the committed benchmark scores were summed from the result JSON with Python - Playa-Cyrene/Cyrene-Agent
at
be6ce1f8…— read only, at the head ofmaster, a commit dated 28 September 2026. MIT; the bundled Live2D model is credited separately inMODEL_LICENSE.md. Scoped to the memory subsystem (src/main/memory,src/main/social-contextand the retrieval code they call). Screened before reading: no auto-run surface, no build-time execution point, 7 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 2 unpinned surfaces; no agent instruction files in the tree. Nothing installed, built or run. - neomjs/neo-agent-brain
at
83c0e09e…— read only, at the head ofdev, a commit dated 29 September 2026. MIT. Screened before reading: no auto-run surface, 1 build-time execution point (the npmpreparescript), 8 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 5 unpinned surfaces, includingneo.mjsfrom a GitHub archive; no agent-instruction file in the tree. Only the Memory Core was read. Nothing was installed, built or executed. - Muvon/octobrain at
ccc1d53a…— read only, at the head ofmaster, the 0.14.4 release commit dated 30 September 2026. Apache-2.0. Screened before reading: 1 auto-run surface (server.json, an MCP registry manifest declaring a start command), 2 build-time execution points (Makefile,benches/Makefile), 3 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and no unpinned surface;AGENTS.mdwas treated as data. Nothing was installed, built or executed. - RodCor/kimetsu at
b5705fb2…— read only, at the head ofmain, a commit dated 10 September 2026. MIT OR Apache-2.0. Screened before reading: 1 auto-run surface (.githooks/pre-commit, inert unlesscore.hooksPathpoints at it), 2 build-time execution points (crates/kimetsu-cli/build.rs, an npmprepublishOnly), 1 unpinned surface and nothing inside the cooldown, every file in the depth-1 clone dating to the tip; no agent-instruction files. Read withgrepandsed; nothing was installed, built or executed. - RooAGI/Lint-AI at
a1919f1d…— read only, at the head ofmain, a merge dated 30 September 2026 UTC. Apache-2.0. Screened before reading: no auto-run surface, 2 build-time execution points (both ordinary modules namedbuild.rsundersrc/, not Cargo build scripts), 5 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and no unpinned surface reported althoughCargo.lockis gitignored;.claude/skills/lint-ai-memory/SKILL.mdandINSTALL_FOR_AGENTS.mdwere treated as data. Nothing was installed, built or executed. - mrveiss/AutoBot-AI at
2b88c1c2…— read only, at the head ofmain, a commit dated 30 September 2026; the memory stores, their routes and tasks inautobot-backend/were read and the rest of the platform was not. Apache-2.0. Screened before reading: 3 auto-run surfaces (.claude/hooks/,.claude/settings.json,.vscode/settings.json), 30 build-time execution points, 39 unpinned dependency surfaces and 50 dependency files inside the cooldown, which a depth-1 clone inflates because every file dates to the tip;CLAUDE.mdwas treated as data. Nothing was installed, built or executed. - nano-step/nano-brain
at
fc58b4b7…— read only, at the head ofmaster, a commit dated 7 September 2026. MIT. Screened before reading: 3 auto-run surfaces (.claude/settings.jsonwith one PreToolUse hook that runs a harness check only ongh pr create, its script under.claude/hooks/, and an.opencode/bundle whose five third-party MCP servers are disabled), 2 build-time execution points (Makefile, an npmpostinstallthat downloads the release binary), 2 floating ranges and nothing inside the cooldown;AGENTS.mdandCLAUDE.mdwere treated as data. Only the memory half was read; the code-intelligence packages were not. Nothing was installed, built or executed. - mmethodz/dreamgraph at
563d10c8…— read only, at the head ofmain, released as v13.4.0 and dated 30 September 2026. DreamGraph Source-Available Community License v2.0, non-commercial; production and commercial use need a separate licence. Screened before reading: 1 auto-run surface (.github/copilot-instructions.md, treated as data), 0 build-time execution points, 9 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 5 unpinned surfaces beside a root lockfile. Nothing was installed, built or executed. - Nocetic/flowly at
a5dc7c30…— read only, at the head ofmain, a commit dated 17 September 2026. Apache-2.0. Screened before reading: no auto-run surface, 5 build-time execution points (threesetup.py, twoconftest.py), 3 unpinned surfaces (twopackage.json, one skillrequirements.txt) and nothing inside the cooldown; no agent-instruction file in the tree. Only the memory subsystem was read. Nothing was installed, built or executed. - ozankasikci/global-agent-memory
at
53480fd2…— read only, at the head ofmain, a commit dated 1 September 2026. MIT. Screened before reading: 1 auto-run surface (server.json, an MCP registry manifest naming the PyPI package), 1 build-time execution point (Makefile), 1 unpinned surface (dashboard/package.json, lockfile present) and nothing inside the cooldown;dashboard/AGENTS.mdand the integration snippets were treated as data. Nothing was installed, built or executed. - MikeK184/Recollect at
6a85f6a1…— read only, at the head ofmain, a commit dated 30 September 2026. Apache-2.0. Screened before reading: 1 auto-run surface (.opencode/, six agent prompt files), no build-time execution point, 10 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 1 unpinned surface (web/package.json, lockfile present);opencode.jsonand.codex/config.tomldeclare MCP servers launched withnpx -y, which the screen does not flag;AGENTS.mdwas treated as data. Read withgrep,sedandawk; nothing was installed, built or executed. - RightL/RightMemory at
0cd5e868…— read only, at the head ofmain, a commit dated 30 September 2026. Apache-2.0. Screened before reading: no auto-run surface, no build-time execution point, one unpinned surface (pyproject.tomlhas no lockfile) and three dependency files inside the cooldown, every file in the depth-1 clone dating to the tip;AGENTS.mdwas treated as data. Nothing was installed, built or executed. - SawyerHan-AI/TideMind
at
29cef627…— read only, at the head ofmain, dated 30 September 2026. MIT. Screened before reading: 0 auto-run surfaces, 2 build-time execution points (an npmpostinstallrunningelectron-rebuild, and abinding.gypnative addon), 5 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, 4 unpinned surfaces beside a root lockfile, and no agent-instruction file. Nothing was installed, built or executed. - 20alexl/windvane
at
69dc824f…— formerly 20alexl/claude-engram, which went private; its earlier pina7903274…was read from the archive fork. Read only, at the head ofmain, the 1.0.18 commit dated 12 October 2026. MIT. Screened before reading: three auto-run surfaces (the.claude-plugin/manifest, thehooks/module andhooks/hooks.json), one collection-time execution point (tests/conftest.py), one dependency file inside the cooldown and one unpinned surface (pyproject.toml, without a lockfile); the second plugin underkeeper/, which the screen did not list, was read by hand;CLAUDE.mdwas treated as data. Nothing was installed, built or executed. - diegoxtr/ctx-open
at
c31d84e0…— read only, at the head ofmain, a commit dated 21 September 2026. CTX Source-Available License v1.0: local, self-hosted and on-premise commercial use granted, hosted or competing services barred without a separate agreement. Screened before reading: 1 auto-run surface (.devcontainer/devcontainer.json,postCreateCommandandpostStartCommand), no build-time execution point, no unpinned surface and nothing inside the cooldown across 14 files scanned; no agent-instruction files, andprompts/was treated as data. Nothing was installed, built or executed. - roampal-ai/roampal-core
at
211e7e05…— read only, at the head ofmain, a commit dated 26 September 2026. Apache-2.0. Screened before reading: no auto-run surface, 4 build-time execution points (threeconftest.pyfiles androampal/cli/setup.py), 1 unpinned surface (pyproject.tomlwith no lockfile) and 1 file inside the cooldown, every file in the depth-1 clone dating to the tip; no agent instruction files were in the tree. The companion paper was read aspaper.mdin roampal-ai/roampal-labs at6b20c0d8…. Nothing was installed, built or executed. - rmk40/opencode-session-recall
at
8a5ccd63…— read only; MIT; no auto-run surface, two build-time execution points inpackage.json(prepare: husky,prepublishOnly), no file inside the cooldown, one unpinned surface of fourteen floating ranges under a lockfile, two inert.husky/hook payloads,AGENTS.mdread as data, and nothing was installed, built or run - aoci-spec/aoci-code at
fdb4cb9b…— read only, at the head ofmain, a commit dated 29 September 2026. FSL-1.1-MIT (source-available, converting to MIT two years after each release). Screened before reading: 0 auto-run surfaces, 2 build-time execution points (Makefileand the vendored openGauss connector'sMakefile), 9 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 2 unpinned surfaces in black-box fixtures;AGENTS.mdwas treated as data. Nothing was installed, built or executed. - alex-feel/mcp-context-server
at
ed6a24d8…— read only, at the head ofmain, a sync commit dated 30 September 2026. Elastic License 2.0 in the tree; the project states releases up to v2.2.2 were MIT. Screened before reading: 1 auto-run surface (server.json, an MCP registry manifest naming the PyPI package), 4 build-time execution points (conftest.pyfiles), no unpinned surface and 2 dependency files inside the cooldown, an artefact of the depth-1 clone;CLAUDE.mdwas treated as data. Nothing was installed, built or executed. - TerminallyLazy/Tree-Ring-Memory
at
31d7aaf5…— read only, at the head ofmain, a commit dated 17 September 2026. MIT. Screened before reading: 4 auto-run surfaces (.claude-plugin/marketplace.jsonand the plugin underplugins/tree-ring-memory/, whose hooks call thetree-ringbinary), no build-time execution point, no unpinned surface and nothing inside the cooldown, the depth-1 clone dating every file to the tip; twelveAGENTS.mdfiles were treated as data. Nothing was installed, built or executed. - edg-l/engram-mcp
at
71d945d8…— read only, at the head ofmaster, a commit dated 23 September 2026. Apache-2.0 per the LICENSE file;Cargo.tomldeclares MIT and the README MIT OR Apache-2.0. Screened before reading: one auto-run surface (hooks/, a README and JSON payload fixtures, nothing executable), no build-time execution point, nothing inside the cooldown, no unpinned surface (Cargo.lockpresent);CLAUDE.mdand the twoskills/files were treated as data. Nothing was installed, built or executed. - jasen215/dsh-continual-harness
at
403451a2…— read only; MIT; no auto-run surface, no build-time execution, one floating surface (package.jsonranges under a committedpnpm-lock.yaml), two dependency files inside the cooldown in a depth-1 clone where every file dates to the tip, an uninstalled git hook payload underscripts/githooks/, no agent-instruction file; nothing installed, built or run - mlapeter/counterparts
at
928b9d30…— read only, at the head ofmaster, a commit dated 30 September 2026. MIT. Screened before reading: no auto-run surface, no build-time execution point, one dependency file inside the cooldown (package.json, every file in the depth-1 clone dating to the tip) and one unpinned surface (three caret ranges inpackage.json; the screen did not recognise the committedbun.lock);CLAUDE.mdwas treated as data. Nothing was installed, built or executed. - mlapeter/claude-engram
at
91edd7e5…— read only, at the head ofmain, a commit dated 17 July 2026. AGPL-3.0-only. Screened before reading: one auto-run surface (hooks/, five scripts that run only onceinstall.shregisters them in~/.claude/settings.json), no build-time execution point, nothing inside the cooldown (bun.lockunchanged for 75 days), and one unpinned surface (caret ranges inpackage.jsonwithbun.lockcommitted); no AGENT file.install.shwas read by hand. Nothing was installed, built or executed. - Maurdekye/orgtree
at
0151d66e…— read only, at the head ofmain, release 3.0.6 dated 1 October 2026. MIT. Theengine/mailhubsubmodule, Maurdekye/orgtree-mailhub (MIT), was read at its pinned commit6e856eec…. Screened before reading: 1 auto-run surface (.gitmodules), 1 build-time execution point (engine/native/store-schema/build.rs),FRESHonpackage.json,package-lock.jsonand Cargo manifests underengine/native/in a full clone, andFLOATonpackage.jsonwith a lockfile present; the mail hub's screen foundFLOATonrequirements.txtonly. NoAGENTS.mdorCLAUDE.mdis in the tree. Nothing was installed, built or executed. - vn-envy/Smriti at
16c5571a…— read only, at the head ofmain, a commit dated 26 September 2026 (release 0.4.2), core andenterprise/package. Apache-2.0. Screened before reading: no auto-run surface, 1 build-time execution point (an npmpostinstallinlaunch-video/), 4 dependency files inside the cooldown — every file in the depth-1 clone dating to the tip — and 3 unpinned surfaces; no agent-instruction files. Two committed benchmark result files were tallied with a standalone Python one-liner. Nothing was installed, built or executed. - mainline-org/mainline
at
79f4be3b…— read only, at the head ofmain, a merge commit dated 2 October 2026, after v0.5.1. Layered licence: Apache-2.0 for the CLI, skills, hooks, SDKs and specs, CC-BY-4.0 or Apache-2.0 for documentation, brand and hosted surfaces excluded; no rider on analysis. Screened before reading: 2 auto-run surfaces (.cursor/rules/,.github/copilot-instructions.md), 1 build-time execution point (Makefile), 2 files inside the cooldown (go.mod,go.sum), every file in the depth-1 clone dating to the tip, and no unpinned surface;AGENTS.mdandCLAUDE.mdwere treated as data. Nothing was installed, built or executed. - xinchen03/minta at
a4201db8…— read only, at the head ofmain, a commit dated 20 September 2026. Apache-2.0, as the open kernel of an open-core product whose closed tier holds three modules the code imports. Screened before reading: no auto-run surface, 1 build-time execution point (server/tests/conftest.py), 3 unpinned dependency surfaces and nothing inside the cooldown; no agent-instruction file, and a Jinja template for aCLAUDE.mdwas read as data. APScheduler3.11.0's scheduler base was read through the GitHub API to settlenext_run_time=None. Nothing was installed, built or executed. - uudam42/agent-memory-engine
at
6e345342…— read only, at the head ofmain, a merge commit dated 1 October 2026. MIT. Screened before reading: no auto-run surface, 1 build-time execution point (tests/conftest.py), 2 dependency files inside the cooldown (pyproject.toml,uv.lock), every file in the depth-1 clone dating to the tip, and no unpinned surface;CLAUDE.mdwas treated as data. Nothing was installed, built or executed. - alphaonedev/ai-memory-mcp
at
948fe999…— read only, at the head ofmain, a commit dated 2 October 2026. Apache-2.0. Screened before reading: 3 auto-run surfaces (.claude/settings.jsonwith an LSP block and a write deny-list but no hook command,hooks/session-start.sh, theserver.jsonMCP manifest), 3 build-time execution points (three deployMakefiles), 13 dependency files inside the cooldown — every file in the depth-1 clone dating to the tip — and 3 unpinned surfaces;CLAUDE.mdwas treated as data. Only the SQLite memory path was read in depth. Nothing was installed, built or executed. - masondelan/selvedge at
10458144…— read only, at the head ofmain, a commit dated 3 October 2026. MIT. Screened before reading: 5 auto-run surfaces (.claude-plugin/,.mcp.json,hooks/,hooks/hooks.json, aserver.jsonlaunching throughuvx), 2 build-time execution points (selvedge/setup.py,tests/conftest.py), 2 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 1 unpinned surface (pyproject.tomlwith no lockfile);CLAUDE.mdwas treated as data. The committed dogfood database was opened read-only. Nothing was installed, built or executed. - Blackcat-Informatics/gmeow-ontology
at
38f568b0…— read only, at the head ofmain, a commit dated 2 October 2026. AGPL-3.0-only for the tooling and CC BY 4.0 for the ontology, with commercial licences reserved. Screened before reading: 2 auto-run surfaces (.cursorrules,.github/copilot-instructions.md), 9 build-time execution points, 65 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 1 floating range;AGENTS.md,CLAUDE.mdand.cursorruleswere treated as data. The claim store was read in Blackcat-Informatics/purrdf at3954ae24…, therust-v3.0.0tag the lockfile pins, whose screen reported one auto-run surface (.githooks/). Only the MCP claim store was read. Nothing was installed, built or executed. - studiomeyer-io/local-memory-mcp
at
a2437ddb…— read only, at the head ofmain, v2.4.4, a commit dated 21 September 2026. MIT. Screened before reading: 1 auto-run surface (server.json, an MCP manifest declaring a start command), 1 build-time execution point (prepublishOnly), 1 floating-range surface withpackage-lock.jsonpresent, nothing inside the cooldown; noAGENTS.mdorCLAUDE.mdin the tree. Nothing was installed, built or executed. - babarmuhammad/archeus
at
a52ccb47…— read only, at the head ofmain, a commit dated 28 September 2026. MIT. Screened before reading: 1 auto-run surface (.claude-plugin/marketplace.json, a plugin manifest whose commands runarcheusover Bash), 1 build-time execution point (tests/conftest.py), 8 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 4 unpinned surfaces;www/AGENTS.mdwas treated as data. Only the memory layer was read. Nothing was installed, built or executed. - emiliomartucci/marvis
at
166c4466…— read only, at the head ofmain, a commit dated 22 September 2026. BSL 1.1 with an additional use grant barring third-party hosted or managed service, converting to Apache 2.0 on 1 January 2030; no rider on analysis. Screened before reading: no auto-run surface, no build-time execution point, nothing inside the cooldown (every file in the depth-1 clone dates to the tip, 11 days before the screen), 4 unpinned surfaces (two npm manifests with lockfiles,core/mcp-pir/package.jsonandpyproject.tomlwithout), andAGENTS.mdandCLAUDE.mdtreated as data. Nothing was installed, built or run. - Smart-AI-Memory/attune-ai
at
2e3e4f1b…— read only, at the head ofmain, a commit dated 1 October 2026. Apache-2.0. Screened before reading: 10 auto-run surfaces (.claude-plugin/,.claude/settings.json,.devcontainer/devcontainer.json,.mcp.json, and the plugins underplugin/andplugins/attune-help/, with hooks inplugin/hooks/hooks.jsonand MCP servers fetched at run time), 17 build-time execution points, 12 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 6 unpinned surfaces;AGENTS.mdandCLAUDE.mdwere treated as data. The curated-digest hydrator lives in anattune-agent-memorycheckout not found on GitHub, and theattune-ragranking dependency was not opened. Nothing was installed, built or executed. - AbsoluteMode/session-recall
at
0f3600bc…— read only; MIT; five auto-run surfaces (.claude-plugin/,.mcp.json,mcp.json,hooks/,hooks/hooks.json), one build-time execution point (tests/conftest.py), no file inside the cooldown, one unpinned surface (pyproject.tomlwith no lockfile),AGENTS.mdandCLAUDE.mdread as data, and nothing was installed, built or run - madgodinc/mgi-mind at
8069652a…— read only, tagv2.9.0at the head ofmain, a commit dated 6 November 2026. Apache-2.0. Screened before reading: one auto-run surface (server.json, an MCP server manifest naming the npm package), one build-time execution point (the npm wrapper'spostinstall, which downloads the release binary and checks it against the release's own.sha256), three dependency files inside the cooldown (Cargo.toml,Cargo.lockandpackaging/npm/package.json, each changed only by the version bump), and one unpinned surface (clients/python/pyproject.tomlwithout a lockfile);AGENTS.mdwas treated as data. Committed LongMemEval-S per-question files were recomputed with a standalone script. Nothing was installed, built or executed. - n24q02m/mnemo at
3086abf9…— read only, at the head ofmain, v2.18.13-beta.1, a commit dated 3 October 2026; formerlyn24q02m/mnemo-mcp. Apache-2.0 with MIT portions. Screened before reading: 5 auto-run surfaces (.claude-plugin/,hooks/andhooks/hooks.json,server.json,smithery.yaml), 1 build-time execution point (tests/conftest.py), 4 dependency files inside the cooldown in a depth-1 clone, no unpinned surface;AGENTS.mdandCLAUDE.mdrecorded as data. hull-core's auth modules read atabc27ed4…through the GitHub API. Nothing was installed, built or executed. - liliang-cn/cortexdb at
0a11f804…— read only, at the head ofmain(v2.119.1), a commit dated 3 October 2026. MIT. Screened before reading: 5 auto-run surfaces (.claude-plugin/and the plugin underplugins/cortexdb/, with hooks and an MCP server), no build-time execution point, 12 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 2 floating ranges with lockfiles present;SKILL.md,.agents/and the plugin's skills and commands were treated as data. The memory API, plugin hooks, change feed, graph temporal layer and scoped-key server were read;pkg/agentmem,pkg/hindsightandpkg/memoryflowwere not. Nothing was installed, built or executed. - SynapseLayer/synapse-layer
at
196733ca…— read only, from a shallow clone; Apache-2.0, open core, so the hosted Forge engine behind the client and the MCP manifests was not inspectable. Nine files scanned, two auto-run surfaces (server.json,smithery.yaml, both naming the remote MCP URL with no local command), one build-time execution point, two unpinned surfaces and no dependency file inside the seven-day cooldown. Nothing was installed, built or run - mirkofr/FERNme at
320a9edf…— read only, at the head ofmain(0.4.2), a commit dated 1 October 2026. Apache-2.0. Screened before reading: 1 auto-run surface (.claude-plugin/marketplace.json), no build-time execution point, 4 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 3 unpinned surfaces;AGENTS.mdand the plugin skills were treated as data. The memory core, review queue, audit chain, prior, MCP and REST surfaces were read; the document, photo and Obsidian adapters and the React UI were skimmed. Nothing was installed, built or executed. - voxmastery/FluctlightDB
at
25556df0…— read only, at the head ofmain, a commit dated 1 October 2026. MIT OR Apache-2.0. Screened before reading: 2 auto-run surfaces (.claude/settings.jsonregistering a project MCP server,.githooks/), 1 build-time execution point (Makefile), 12 dependency files inside the cooldown, every file in the depth-1 clone dating to the tip, and 4 unpinned surfaces;AGENTS.mdandCLAUDE.mdwere treated as data. The engine crate, the Python SDK, the MCP and HTTP servers, the tests and the provenance-conflict results were read; nothing was installed, built or run. - lpaiu-cs/osk-system at
edf9523f…— read only, at release v4.1.3, a commit dated 3 October 2026. MIT, with a Korean rider declaring the governing documents the author's own work. Screened before reading: no auto-run surface, 3 build-time execution points (twosetup.pyfiles andtests/conftest.py), 1 dependency file inside the cooldown, every file in the depth-1 clone dating to the tip, and 1 unpinned surface (requirements.txt); no.gitattributesfilter driver or submodules, anddocs/INSTALL-AGENT.mdwas treated as data. Nothing was installed, built or executed. - johnnyjoy/pluribus at
e869aa2b…— read only, at the head ofmain, a commit dated 15 September 2026. Pluribus License v1.0, source-available and service-restricted; the file is headed Purinus License. Screened before reading: no auto-run surface at the root, two build-time execution points (Makefile,control-plane/Makefile), nothing inside the cooldown, and two unpinned surfaces (sdk/python/pyproject.tomlwithout a lockfile, caret ranges in the VS Code extension); the Claude Code plugin hooks underintegrations/were read as data. Nothing was installed, built or run. - gonzaroman/IHMT-MEMORY
at
ba0c4557…— read only, at the head ofmain, a commit dated 30 September 2026. MIT. Screened before reading: 4 files scanned, no auto-run surface, 1 build-time execution point (ihmt_gui/setup.py, a GUI module named like a setuptools script), andrequirements-mcp.txtboth inside the cooldown and unpinned (mcp[cli]>=2.0), the repository having been created on 30 September 2026;CLAUDE.mdwas treated as data. The long-term memory path, the timeline, the navigator, the MCP server and the tests were read from a full clone; nothing was installed, built or run. - LinkedParticles/particles-engine-py
at
806de74b…— read only, at the head ofmain, release 1.224.6, a commit dated 1 November 2026 (UTC). Apache-2.0. Screened before reading: 2 auto-run surfaces (hooks/, mkdocs build hooks;server.json, an MCP registry manifest), 2 build-time execution points (particles/observability/setup.py,tests/conftest.py),pyproject.tomlunpinned, andpyproject.tomland the web interface'spackage.jsonandpackage-lock.jsoninside the cooldown; no agent instruction file is committed. The pinned core was read in LinkedParticles/particles-core-py atdec9ca22…(tagv1.224.6; 1 build-time execution point,pyproject.tomlanduv.lockinside the cooldown of a depth-1 clone, a lockfile present), and the specification in LinkedParticles/particles-standard atdef85468…from a depth-1 clone. The LongMemEval figures were recomputed from committed JSON with a standalone script. Nothing was installed, built or executed. - ZyGan1999/self-evolving-harness-as-learning
at
9f7e8178…— read only, at the head ofmain, a commit dated 25 September 2026, beside arXiv:2609.36892. No licence file, so all rights reserved by default. Screened before reading on a full clone: 2 files scanned, no auto-run surface, no build-time execution, nothing inside the cooldown, no unpinned surface; no agent instruction file is committed. Nothing installed, built or run; the trigram similarity check used a standalone re-implementation of one function. - FernandoJRR/archiver-rag
at
72e6d82b…— read only, at the head ofmain, a documentation commit of 28 September 2026 one commit after the 0.2.2 release. MIT. Screened before reading from a full clone: no auto-run surface, one build-time execution point (tests/conftest.py), nothing inside the seven-day cooldown, one unpinned surface (pyproject.tomlwithout a lockfile);CLAUDE.mdandAGENTS.mdwere treated as data. Nothing was installed, built or run - imshaikot/browsentic
at
868fd857…— read only, at the head ofmain, 17 commits past the v0.8.0 tag, dated 8 October 2026. Apache-2.0 with no rider. Screened before reading from a full clone: 1 auto-run surface (server.json, an MCP registry manifest namingnpx browsentic mcp), 2 build-time execution points (apostinstallofwxt prepareand the Tauribuild.rs), 2 dependency files inside the seven-day cooldown, and 2 floating-range surfaces against present lockfiles. Nothing was installed, built or run - SebastiaanBoon/cloud-alter-ego
at
37687bbb…— read only, at the head ofmain, a commit of 8 October 2026. MIT. Screened before reading from a full clone: the screen scanned one file and found nothing, because the hooks are installed into the user's own settings bytools/install.pyrather than declared in the tree;tools/and.gitattributes(a built-inmerge=uniondriver) were read by hand. Nothing was installed, built or run - tigerless-labs/agent-memory
at
3698e601…— read only, at the head ofmain, a merge commit dated 12 October 2026. MIT with no rider. Screened before reading from a full clone: 18 files scanned, no auto-run surface, two build-time execution points (tests/conftest.py, and a host-configuration module namedsetup.pythat the hatchling build never executes), three dependency files inside the seven-day cooldown, and sixpyproject.tomlfiles without a lockfile beside them against the rootuv.lock;CLAUDE.mdwas treated as data. Nothing was installed, built or run - TheWariend/MuscleMemory
at
51946bd8…— read only, at the head ofmain, a commit dated 16 October 2026; first read at4c7b01b4…. Apache-2.0 with aNOTICEwithholding the trademarks and no rider. Screened before reading from a full clone: no auto-run surface, one build-time execution point (tests/conftest.py), five dependency files inside the seven-day cooldown, and two floating-range manifests without a lockfile beside them (apps/dashboard/package.json,packages/sdk-typescript/package.json). Nothing was installed, built or run; the committed benchmark totals were recomputed from their JSON with a separate script, and no benchmark file changed between the two pins - remembra-ai/remembra
at
49ae5f54…— read only, at the head ofmain, a commit dated 11 October 2026. MIT with no rider. Screened before reading from a full clone: 2 auto-run surfaces (hooks/, inert pre-commit and pre-push payloads;server.json, an MCP registry manifest launching a PyPI package throughuvx), 3 build-time execution points (sdk/typescript/package.jsonprepublishOnly, twoconftest.pyfiles),uv.lockinside the cooldown, and 6 unpinned surfaces. Nothing was installed, built or run; the committed LoCoMo summary was recomputed from its per-question rows - mordechaipotash/brain-mcp
at
78d8a4fd…— read only, at the head ofmain, a commit dated 4 October 2026. MIT with no rider. Screened before reading from a full clone: one auto-run surface (server.json, an MCP registry manifest naming the PyPI package), two build-time execution points (Makefile,tests/conftest.py), one manifest without a lockfile (pyproject.toml), and nothing inside the seven-day cooldown.plugin/hooks/hooks.jsonregisters Stop, SessionEnd and PreCompact hooks that fire only once installed as a Claude Code plugin. Nothing was installed, built or run - Ar9av/obsidian-wiki at
7a3d143e…— read only, at the head ofmain, a commit of 12 October 2026 twelve commits past v2026.10.2. MIT with no rider. Screened before reading from a full clone: five auto-run surfaces (.claude/settings.jsonhooks running the two.claude/hooks/scripts, a.claude-plugin/manifest,.cursor/rules/,.github/copilot-instructions.md), each read and found to touch only the local vault and transcript; one build-time execution point (tests/conftest.py); nothing inside the cooldown and no unpinned surface. The mcp 2.2.0 server source was read at its tag for the auth finding. Nothing was installed, built or run - projectmentor/hive-mind
at
739b63e9…— read only, at the head ofmain, a manifest re-signing commit of 15 October 2026 after the contract 4.3 merge. AGPL-3.0 with a contributor licence agreement; no rider. Screened before reading from a full clone: no auto-run surface; two build-time execution points (tests/conftest.py,tests/integration/conftest.py);requirements.txtinside the cooldown with one floating range,requests>=2.32.4,<3;AGENTS.mdread as data. Nothing was installed, built or run. - wrg32786/aigent-os at
dd912104…— read only, at the head ofmaster, a commit of 13 October 2026, 84 commits past v1.1.0-rc.1. MIT with no rider. Screened before reading from a full clone: eight auto-run surfaces (a.claude-plugin/marketplace naming two fleet plugins, thehooks/scripts a manifest can register, and each fleet plugin's manifest andhooks/directory, whosehooks.jsonloads a TypeScript module); the marketplace and the roothooks/scripts were read; the memory hooks are registered only by a settings template the installer copies. No build-time execution point, nothing inside the cooldown, one floating range under a lockfile indaemons/semantic-search/package.json;CLAUDE.mdtreated as data. The companion paper inwrg32786/governed-agent-organizationswas read for its memory claims. Nothing was installed, built or run - AskTheWay/dsh-auto-memory
at
5bcf1c6d…— read only, at the head ofmain, the v0.7.2 commit of 14 October 2026. MIT with no rider. Screened before reading from a full clone: no auto-run surface, one build-time execution point (the npmpreparescript runningtsdown),package.jsoninside the seven-day cooldown, and 16 floating ranges against apackage-lock.jsonunchanged since 26 September 2026. A different owner and store from the other DeepSeek Harness plugins in the atlas, and no rename or fork notice. Nothing was installed, built or run - gambletan/cortex
at
951aca3e…— read only, at the head ofmain, a commit dated 8 October 2026. MIT with no rider. Screened before reading from a full clone: 3 auto-run surfaces (.claude/settings.jsonwith.claude/hooks/skeptic-suggest.sh, a SessionStart hook that readsgit logandgit statusand prints a directive addressed to the reading agent;server.json, an MCP registry manifest naming a Docker image), 2 build-time execution points (npm/package.jsonpostinstall,openclaw-plugin/package.jsonprepublishOnly), nothing inside the cooldown, and 3 unpinned surfaces;.claude/CLAUDE.mdand.claude/agents/were treated as data. Nothing was installed, built or run - FlatbreadLabs/flatbread
at
0d506bc8…— read only, at the head ofmain, a merge commit of 25 September 2026; the report covers the Proof package and the CLI read path. MIT with no rider. Screened before reading from a full clone: two auto-run surfaces (.cursor/rules/, seven agent-directed rule files, and.vscode/settings.json, a TypeScript SDK path), both read; two build-time execution points (preinstall,prepare); 11 unpinned manifest surfaces beside apnpm-lock.yamlunchanged for 63 days; nothing inside the cooldown.AGENTS.mdand the Cursor rules were treated as data, and no rename was found. Nothing was installed, built or run - amrlazw/hermes-fleet-memory
at
87ce8978…— read only, at the head ofmain, the merge of 24 September 2026. MIT with no rider. Brandedhermes-fleet-synapsebetween 11 and 16 September 2026; thefleet_synapse_*tools survive as deprecated aliases. Screened before reading from a full clone: 1 auto-run surface (.cursorrules, setup instructions for a reading agent, treated as data withAGENTS.mdandCLAUDE.md), 2 build-time execution points (setup.py, which launches the setup wizard for any argument it does not recognise as a build command, andtests/conftest.py), nothing inside the cooldown, and 1 unpinned surface (pyproject.tomlwith no lockfile). Nothing was installed, built or run. - jordiboehme/crystalline
at
16689611…— read only, at the head ofmain, the v0.26.0 release merge of 14 October 2026. MPL-2.0 with no rider. Screened before reading from a full clone: no auto-run surface; two build-time execution points (crates/cli/build.rs, which sets linker arguments, andcrates/service/build.rs, which copies the built web UI), read rather than executed; six dependency surfaces inside the seven-day cooldown, among themCargo.lockandfluid/package.json; one unpinned surface,fluid/package.json's floating ranges behindpnpm-lock.yaml;AGENTS.mdtreated as data. Nothing was installed, built or run - mpazik/Binder at
e4066d75…— read only, at the head ofmain, a commit dated 21 September 2026. MIT with no rider. Screened before reading from a full clone: one auto-run surface (.vscode/settings.json, which sets onlybinder.devMode), one build-time execution point (packages/cli/package.jsonprepublishOnly), nothing inside the seven-day cooldown, and five unpinned surfaces, three of them workspace manifests (packages/cli,packages/repo,packages/utils) without a lockfile beside them against the rootbun.lock;AGENTS.mdwas treated as data. Nothing was installed, built or run - semantification-org/Ontofelia
at
a9313c0f…— read only, at the head ofmain, a merge of 14 October 2026. Apache-2.0 with no rider. Screened before reading from a full clone: no auto-run surface, one build-time execution point (packages/reasoner/build.rs), nothing inside the cooldown, and 23 unpinned surfaces, most of them workspace package manifests resolved by the rootpnpm-lock.yaml. Nothing was installed, built or run - kaminocorp/elephantasm-core
at
3dc935e5…— read only, at the head ofmaster, a commit dated 7 September 2026. Apache-2.0 with no rider. Screened before reading from a full clone: no auto-run surface, nothing inside the cooldown, no unpinned surface, and 2 build-time execution points (tests/conftest.py,tests/integration/conftest.py). The tree imports billing and organisation modules it does not contain, so neither the server nor its integration suite imports as published. Nothing was installed, built or run - screenpipe/screenpipe
at
ada8f2fa…— read only, at the head ofmain, a commit dated 15 October 2026 and 94 commits after the nominated01aac0d5…, with every cited memory path identical at both. Screenpipe Commercial License, source-available, with no rider on analysis. Screened before reading from a shallow clone: 2 auto-run surfaces (.devcontainer/devcontainer.json, and the LFS filter in.gitattributes, which this machine's git-lfs ran at checkout), 14 build-time execution points, 15 unpinned surfaces, and 72 dependency files dated inside the cooldown by a clone that dates every file to the tip;AGENTS.mdandCLAUDE.mdread as data. Nothing was installed, built or run - louis030195/hyperconsciousness
at
0f0c8653…— read only, at the head ofmain, a commit of 14 October 2026, 42 commits pastd2152ce. Formerly Brainmesh; protocol domains keep that name. MIT with no rider. Screened before reading from a full clone: no auto-run surface; one build-time execution point (the npmpostinstall, which builds the crate withcargo);Cargo.toml,Cargo.lockandpackage.jsoninside the seven-day cooldown; one unpinned surface,dashboard/package.json's floating ranges behindbun.lock.AGENTS.md,dashboard/CLAUDE.mdand a header comment addressed to AI agents in 147 tracked files were treated as data. Nothing was installed, built or run - Infinibay/ken at
6286d910…— read only, at the head ofmain, a commit dated 22 September 2026, version 0.17.0. MIT with no rider. Screened before reading from a full clone: no auto-run surface, nothing inside the cooldown, no unpinned surface, and 3 build-time execution points (tests/conftest.py,tests/parsers/conftest.py,tests/ranker/conftest.py);AGENTS.mdread as data. Nothing was installed, built or run - Tencent-Hunyuan/Hy-Memory
at
d2e9cdaf…— read only, at the head ofmain, the merge releasing MemHub 1.0.6 on hy-memory 2.0.13, dated 2 November 2026 and 306 commits after the single-commit snapshot of 16 October. Apache-2.0 under a Tencent preamble with no rider, unchanged. Screened before reading from a shallow clone with the 16 October pin fetched beside it: no auto-run surface, 4 build-time execution points (conftest.pyfiles), 13 dependency surfaces inside the seven-day cooldown by their last-commit dates (the shallow clone reported 17), and 11 unpinned surfaces. The two trees were diffed locally; the SDK's reconcile, write, delete and history paths, the Hermes provider, and MemHub's SDK cutover, broker, envelope parser, recall and write routes were read against the committed tests; the Hugging Face weights for Hy-Memory-30B-A3B were not downloaded. Nothing was installed, built or run - apache/maka at
d14cec57…— read only, at the head ofmain, 17 October 2026, from a shallow clone (--depth 1), with history and dates from the GitHub API. Apache-2.0 with an incubator DISCLAIMER-WIP; LICENSE, NOTICE and DISCLAIMER-WIP read in full, no rider. The podling proposal names its earlier home,maka-agent/maka-agent, which the atlas did not hold. Screened before reading: one auto-run surface (.github/copilot-instructions.md, read as data), 3 build-time execution points (npmpostinstallandprepare, onebuild.rs), 29 dependency surfaces inside the seven-day cooldown, a count the shallow clone inflates by dating every file to the tip, and 9 unpinned surfaces. The fact store, extraction engine, recall, MEMORY.md bundle and the personal assistant's memory network were read against their tests; the Terminal-Bench artifacts indocs/eval/were not recomputed. Nothing was installed, built or run - google-research/harness2
at
68688175…— read only, at the head ofmain, 2 November 2026, from a full clone. Apache-2.0, LICENSE read in full, no rider. Screened before reading: no auto-run surface; one build-time execution finding,harness2/cli/setup.py, theharness2-setupconsole script rather than a setuptools file; nothing inside the cooldown; one unpinned surface,pyproject.tomlwith no lockfile. The library, scheduler, selection, reflection and context-building paths were read against the seven unittest cases intests/test_workflow.py, the only file that asserts on the library; the paper (arXiv:2610.14224) was read for its library sections and Table 3, and no result is committed to recompute. Nothing was installed, built or run - makecindy/cindy at
e1bed897…— read only, at the head ofmain, 2 November 2026, from a shallow clone (--depth 1) with the earlier pin fetched beside it, the Git LFS smudge filter disabled and media excluded by sparse checkout; history and dates from the GitHub API. Apache-2.0; LICENSE and NOTICE unchanged since the earlier pin, no rider; no.gitmodules. Screened before reading: the same two auto-run surfaces, a.gitattributesGit LFS filter, whose five sqlite-vec binaries stayed pointer files, and a DCO hook left inactive. There are 4 build-time execution points, 83 dependency surfaces inside the seven-day cooldown, a count the shallow clone inflates, and 42 unpinned surfaces. Maker Memory, thecindy_memoryMCP server, session-start injection, teammate memory, nightly learning,session_searchand the unwired review and ledger were diffed against the earlier pin and read against their tests; no paper. Nothing was installed, built or run - GabrielMartinMoran/mind
at
4e9a41e9…— read only, at the head ofmain, the v1.7.0 release commit of 26 October 2026, from a shallow clone (--depth 1); history and dates from the GitHub API. MIT, LICENSE read in full, no rider; no.gitmodules. Screened before reading: no auto-run surface; two build-time execution points, theMakefileand aprepare: husky installscript; 14 dependency surfaces inside the cooldown, a count the shallow clone inflates; two unpinned surfaces withbun.lockpresent. The store, search pipeline, MCP handlers, checkpoints, agent setup, autosync and HTTP API were read against their tests; the two committed LoCoMo runs were recomputed from their rows, the OmniMemEval run was checked through the API for job outcomes only, and there is no paper. Nothing was installed, built or run - CIRISAI/CIRISAgent at
7de0d36e…— read only, at the head ofmain, the 2.19.0 merge of 1 November 2026, from a shallow clone (--depth 1); history and dates from the GitHub API. AGPL-3.0, LICENSE and NOTICE read in full, no rider; NOTICE adds trademark and patent-pending notices and a contributor CLA; no.gitmodules. The storage engine, CIRISAI/CIRISPersist, was read at tagv59.1.2(94a7b157…), the version CIRISServerv0.5.243pins; AGPL-3.0-or-later in its manifests, no rider. Screened before reading: one committed git-hook directory, inactive; 27 build-time execution points (sevensetup.py, twenty conftest files); five dependency surfaces inside the cooldown, a count the shallow clone inflates; five unpinned surfaces. The memory service, handlers, context builder, deferral approval, audit chain, consent decay and the engine's graph and audit modules were read against their tests; the memory benchmark measures RSS and commits no result, and the README's Zenodo paper does not evaluate memory. Nothing was installed, built or run - teresaz05/librarian-agents
at
27c9d863…— read only, at the head ofmain, 16 October 2026, from a shallow clone (--depth 1); history from the GitHub API. MIT, LICENSE read in full, no rider; no.gitmodulesand no agent-instruction file. Screened before reading: no auto-run surface, no build-time execution, nothing inside the cooldown, one unpinned surface,pyproject.tomlwith no lockfile. The paper, arXiv:2610.22273, was read from its PDF for the method, appendix and tables. The committed reuse, BRIGHT and hierarchy score rows were recomputed with a script of my own that imports nothing from the repository; nothing from the repository was installed, built or run - deepseek-ai/dsh-superagent-prototype
at
6337fc82…— read only, at the head ofmain, the repository's only commit, 31 October 2026, from a shallow clone (--depth 1); history from the GitHub API. MIT, LICENSE read in full, no rider; no.gitmodules. Screened before reading: no auto-run surface, no build-time execution point, no unpinned surface;package.jsonandpnpm-lock.yamlinside the cooldown, exact rather than inflated since the history is one commit. The Store, prompt and settings versions, resource reads, both tool registries, the settings guards and their tests were read; the article the README names, published on DeepSeek's WeChat account, was not, and there is no paper in the tree. Nothing was installed, built or run - bcmyguest/openmem
at
af42d8ca…— read only, at the head ofmain, 31 October 2026, from a shallow clone; history from a treeless bare clone. Apache-2.0, LICENSE read in full, no rider; no.gitmodules. Screened before reading: one auto-run surface,server.json, an MCP registry manifest; twoconftest.pyfiles; three manifests with floating ranges behind lockfiles; five dependency surfaces inside the cooldown by history, a sixth inflated by the shallow clone. The facade, hooks, policy readers, wizard seed, indexer, proxy core, both session-store writers, the MCP search and SQL tools were read, and the two README ContextBench headlines were recomputed from the committed per-cell means; the Hindsight, mem0 and Cognee engines were not read, and nothing was installed, built or run - chenxiachan/textfold
at
5fc941dc…— read only, at the head ofmain, 31 October 2026, from a shallow clone; history from a treeless bare clone. Formerly PaperFold; the old GitHub name redirects here. Apache-2.0, LICENSE and NOTICE read in full, no rider; no.gitmodules. Screened before reading: four auto-run surfaces,.claude-plugin/marketplace.jsonand the plugin underplugins/textfold/, whosehooks.jsonloads a TypeScript module; no build-time execution; five unpinned surfaces; five dependency surfaces inside the cooldown by history, four more inflated by the shallow clone. The levels, storage backend, notes and re-anchoring, reply cache, WebMCP tools, thegetandadaptcommands and both plugins were read; nothing was installed, built or run - 9fpqm4vqvq-ops/agent-creator-master
at
e1e94d17…— read only; no auto-run or build-time surface, two agent-instruction files read as data, four dependency manifests inside the seven-day cooldown and one unpinned surface, so nothing was installed, built or run. The vault, freshness auditor and QA review were read fromagent_hub/memory.py,agent_hub/freshness.pyandagent_hub/core.pyagainsttests/test_v03.pyandtests/test_v04.py; the four packages undervendor/were noted and not read as the subject - openai/codex at
0a2d5f55…— read only, from a shallow clone; one auto-run surface, ten build-time execution paths, three unpinned surfaces and every dependency file inside the seven-day cooldown. Nothing was built and nothing was run. Apache-2.0 - Egonex-AI/Understand-Anything
at
4e6d3299…— read only; four auto-run surfaces (the.claude-plugin/marketplace manifest, the plugin's own manifest underunderstand-anything-plugin/, and itshooks/directory, whosehooks.jsonregisters aSessionStartand aPostToolUsehook), one build-time script, five unpinned manifests and nothing inside the cooldown. Nothing was built and nothing was run. MIT - waldnzwrld/llm-harness-memory
at
f60469fc…— read only, from a shallow clone; no auto-run, build-time or unpinned surface in the checkout and anAGENTS.mdread as data. The hooks it installs are written byinstall.shinto the user's harness settings, and were read there. The engine, outl, was read at97aa72bd…, its last commit before the pin, for delete and trash semantics only. Nothing was installed, built or run, and the three test runners were not run because they need outl. MIT - Shaf2665/mem-mastero
at
f0221b27…— read only, from a full clone, at the head ofmainon 1 November 2026; four auto-run surfaces, all the plugin's own (the.claude-plugin/marketplace and plugin manifests, thehooks/directory, andhooks/hooks.jsonregistering SessionStart, Stop and SessionEnd commands), no build-time or unpinned surface, andpackage.json, which names no dependencies, inside the seven-day cooldown. Nothing was installed, built or run, and the 25 test scripts were not run. MIT - KianJRoss/UltimateAssistant-release
at
814a589a…— read only, from a full clone, at the head ofmainon 2 November 2026; no auto-run surface, one execution point on pytest collection (apps/assistant/conftest.py), two floating requirements files (apps/assistant/requirements.txtwith 13 unpinned entries andcomponents/canvas-overlay/requirements.txtwith 4), nothing inside the seven-day cooldown and no agent-instruction file. Herald, whichsetup.ps1installs from SHA-256-pinned wheels named inherald.json, was not downloaded or read. Nothing was installed, built or run, and no tests were run. AGPL-3.0-or-later - calasdan-sketch/monomem
at
292a312c…— read only, from a full clone, at the head ofmainon 3 November 2026; no auto-run surface, one build-time script (prepublishOnlyrunningnpm run build), four caret ranges behind a committed lockfile, andpackage.jsonandpackage-lock.jsoninside the seven-day cooldown.SKILL.md,skills/monomem-mem/SKILL.mdand.github/were read as data. Nothing was installed, built or run, and neither the 114 test files nor the benchmark was run. MIT - sh1618112233/Sol0mon
at
2bd65e33…— read only, from a full clone, at the head ofmainon 13 October 2026; no auto-run or build-time surface, an execution point on pytest collection in each copy'stests/conftest.py(Sol0mon/andSol0mon-Windows/), nothing unpinned, nothing inside the seven-day cooldown and no agent-instruction file.Sol0mon/was read;Sol0mon-Windows/differs from it in three files. Nothing was installed, built or run, and no tests were run. No licence: no LICENSE file, and the README says none has been selected - linxuhao/ActiveMemoryIndex
at
22f8287c…— read only, from a shallow clone, at the head ofmainon 16 October 2026, with commit and author counts from the GitHub API; no auto-run, build-time, cooldown or unpinned surface.README.md,RELEASE.md,SUBMISSION.mdanddocs/were read as data, and the cited Zenodo preprint's abstract and metadata were read. Nothing was installed, built or run, and neither the 31 test files nor the offline bench was run. MIT - wenxiaof345-ctrl/vanilla-rag-memory
at
31ab7bf9…— read only, from a shallow clone, at the head ofmainon 11 August 2026; history from the GitHub API. No auto-run or build-time surface, nothing inside the seven-day cooldown, no agent-instruction file, and two unpinned surfaces (pyproject.tomlwith no lockfile,requirements.txtwith ranges). The server, store, admin script, replay and smoke scripts and the offline FAISS path were read; the tokenizer pattern was re-typed into a scratch script and run on sample strings. Nothing was installed, built or run, and no tests were run. No licence: no LICENSE file, and no licence statement in the README orpyproject.toml - imlrz/ReFind at
a80175ca…— read only, from a shallow clone, at the head ofmainon 14 August 2026, with commit and author counts from the GitHub API; no auto-run, build-time or cooldown surface, and one unpinned surface,pyproject.tomlwith no lockfile beside it. The paper, arXiv:2608.12888, was read on arXiv for its method and ablation tables, and the leaderboard page for its stated process. Nothing was installed, built or run, and the eight pytest cases were not run. MIT - jalemieux/bot_board at
9d77791b…— read only, from a full clone of the GitHub mirror at tag v1.0.251; no auto-run, build-time or unpinned surface, andrequirements.txtinside the seven-day cooldown.AGENTS.mdis addressed to a reading agent and was recorded as data. Nothing was installed, built or run. MIT - tonydzi/sqlite-graph-memory
at
cff9420d…— read only, from a full clone, at the head ofmainon 10 November 2026, 64 commits past the nominated378baf0c…; one auto-run surface (server.json, an MCP Registry manifest launching the PyPI package throughuvx), no build-time surface, three unpinned surfaces (requirements.txt,bench/requirements.txt, andpyproject.tomlwith no lockfile beside it) andpyproject.tomlinside the seven-day cooldown. The Claude Code Stop hook is an example snippet underexamples/, not registered in the tree, andAGENTS.mdwas read as data. The bench figures were recomputed from the committed result files with a separate script, and the Zenodo preprint's abstract and metadata were read. Nothing was installed, built or run, and the 224 pytest functions were not run. MIT - Perseus-Computing-LLC/kibisis
at
e9ddf611…— read only, from a full clone, at the head ofmainon 5 November 2026, six commits past the v0.1.0-alpha.14 tag; no auto-run surface, one execution point on pytest collection (tests/conftest.py), no unpinned surface, and seven manifests and lockfiles (pyproject.toml,uv.lock,bindings/python/pyproject.tomland bothCargo.tomlandCargo.lockpairs) inside the seven-day cooldown. Perseus Vault's pinned tree was fetched by sha from the atlas archive and compared: no shared commit and no identical file. Nothing was installed, built or run, and neither the 411 Python nor the 31 Rust test functions were run. MIT - Mnemoclaw/immune
at
28248347…— read only, from a full clone, at tag v5.3.4, the head ofmainon 5 November 2026; no auto-run surface, no build-time execution point, nothing inside the seven-day cooldown, and one unpinned surface,package.jsonwith three floating ranges and no lockfile. The README asks users to registerimmune-inject.jsas aUserPromptSubmithook by hand, and the adapter installs@xenova/transformers@2.17.2itself when the import fails. Nothing was installed, built or run; there is no test suite, and no benchmark figure recomputes from the tree. MIT - memgraph/ai-toolkit at
2e9af39f…— read only, from a shallow clone, at the head ofmainon 5 November 2026, with commit counts from the GitHub API; scoped tocontext-graph/and theunstructured2graphextractor it calls, with the LangChain, LightRAG and MCP integrations,sql2graph,memgraph-toolboxandhygmout of scope. Five auto-run surfaces, all the Claude plugin's own (the root.claude-plugin/marketplace manifest and, undercontext-graph/plugins/memgraph-context-graph-claude/, the plugin manifest,.mcp.jsonstartingmemgraph-context-graph mcp, thehooks/directory andhooks/hooks.jsonregistering 13 events), nine build-time execution points (eighttests/conftest.pyfiles andintegrations/langchain-memgraph/Makefile), fifteenpyproject.tomlfiles with no lockfile beside them, and every manifest anduv.lockinside the cooldown because the shallow clone dates each file to the tip.AGENTS.mdwas read as data. The benchmark headlines were recomputed from the committed baselines with a separate script. Nothing was installed, built or run, and the 1,202 pytest functions were not run. MIT - eugeniughelbur/obsidian-second-brain
at
deff2153…— read only, from a depth-1 clone, at the head ofmainon 5 November 2026, with commit counts from the GitHub API. Four auto-run surfaces, all the plugin's own: the.claude-plugin/marketplace and plugin manifests, thehooks/directory, andhooks/hooks.jsonregistering SessionStart, PostToolUse and a PostCompact command that stays inert until two environment flags are set. One execution point on pytest collection (tests/conftest.py, which sets one environment variable) and one unpinned surface (the Obsidian plugin'spackage.json, lockfile present).uv.lock,package.jsonandpackage-lock.jsonchanged inside the seven-day cooldown. The screen also listedpyproject.toml, whose last change on 27 October 2026 the depth-1 clone dated to the tip. The manifest starts the MCP server throughuv run --with "mcp<2", andCLAUDE.mdwas read as data. Nothing was installed, built or run, and the 908 pytest functions were not run. MIT - ThreatRecall/zettelforge
at
d1484ea6…— read only, from a shallow clone, at the head ofmasteron 5 November 2026, a commit dated 10 July 2026; the repository moved fromrolandpg/zettelforge, which redirects to it, and commit counts came from the GitHub API. One auto-run surface (server.json, an MCP Registry manifest for the PyPI package), one execution point on pytest collection (tests/conftest.py), one unpinned surface (pyproject.tomlwith no lockfile beside it), and nothing inside the seven-day cooldown. The CTI retrieval headline was recomputed by hand from the committed per-category results, and the LoCoMo result files were read. Nothing was installed, built or run, and the 846 pytest functions were not run. MIT - Graphicle-AI/graphicle
at
7b8e41b7…— read only, from a full clone, at tag v0.1.12, the head ofmainon 5 November 2026; one auto-run surface (server.json, an MCP Registry manifest naming release.mcpbarchives by sha256), sixteen cargobuild.rsexecution points, nine manifests and lockfiles inside the seven-day cooldown (threeCargo.lockand fourCargo.tomlfiles,sdk/python/pyproject.tomlandsdk/typescript/package.json), and one unpinned surface,sdk/python/pyproject.tomlwith no lockfile. The README's memory-benchmark figures were not recomputed:docs/benchmarks.mdstates their per-question records are not in the repository. Nothing was installed, built or run, and neither the 2,260 Rust nor the 209 Python test functions were run. Apache-2.0 - mage0535/hermes-memory-installer
at
049d9ac6…— read only, from a depth-1 clone, at the head ofmainon 5 November 2026, with commit history from the GitHub API; no auto-run or build-time surface, nothing inside the seven-day cooldown, and one unpinned surface,requirements.txtwith two floating ranges.install.shpip-installsPyYAML>=6.0when the import fails, and the installer's default mode runs distributionapt-get,dnforyuminstalls of PostgreSQL through a shell; it fetches nothing else, and the Hindsight and GBrain project links it prints returned 404. Nothing was installed, built or run, and the 289 pytest functions were not run. MIT - alex09x/kyb at
0934013b…— read only, from a full clone, at a merge commit dated 3 November 2026, after release 0.3.3; one auto-run surface (server.json, an MCP Registry manifest naming no package), one cargobuild.rsexecution point that concatenates the web console's files, nothing inside the seven-day cooldown and no unpinned surface. The Dockerfile fetches its embedding model from Hugging Faceresolve/mainwith no checksum. The README's search-quality table was not recomputed: its base and per-question results are not in the repository. Nothing was installed, built or run, and the 230 Rust test functions and 14 CI scripts were not run. MIT - friday-memory/friday
at
fad2a61c…— read only, from a full clone, at the head ofmainon 5 November 2026, a commit dated 4 October 2026; the repository's other branches are Dependabot's. Three auto-run surfaces (.cursorrulesand.github/copilot-instructions.md, instructions injected into an agent's context, andsmithery.yaml, an MCP packaging manifest declaring a start command), two build-time execution points (Makefile,tests/conftest.py), and nothing inside the seven-day cooldown. The README's DeepEval table was compared withbenchmarks/benchmark_deepeval.py, where every figure is a literal. Nothing was installed, built or run, and the 67 pytest functions were not run. MIT - ZIZKA-AI-SL/ZizkaDB at
0d3177d9…— read only, from a full clone, at the head ofmainwhen cloned, a commit dated 4 November 2026; scoped tocore/andmcp/, which carry the memory, with the SDKs read as HTTP clients and the dashboard as a viewer. Two auto-run surfaces (.cursor/rules/and.github/copilot-instructions.md), three build-time execution points (twoconftest.pyfiles and an npmprepublishOnly), 23 unpinned surfaces and four dependency files inside the seven-day cooldown;AGENTS.md,CLAUDE.mdandGEMINI.mdwere read as data. Nothing was installed, built or run, no container was started, and the 727 core pytest functions were not run. AGPL-3.0 with no rider; the MCP server undermcp/is MIT - 28naem-del/mnemosyne
at
1bead7fa…— read only, from a full clone, at the head ofmainon 3 November 2026, package version 3.0.0-rc.4; five auto-run surfaces (the.claude-plugin/marketplace,.devcontainer/devcontainer.json'spostCreateCommand,integrations/claude-code/.claude-plugin/plugin.json,integrations/claude-code/.mcp.jsonandserver.json, the last two launchingmnemosy-aithroughnpx), seven manifests and lockfiles inside the seven-day cooldown, one build-timeprepublishOnly, and four unpinned surfaces, two of them consumer-lock packages depending on a local.tgz. The README's LoCoMo recall@10 figures were recomputed from the committed per-question files inreports/matched-run-2026-09-14/andreports/matched-run-2026-10-29-zep/; its LongMemEval-S answer accuracy was not, because its per-question file is not committed. Unrelated tomnemosyne-oss/mnemosyneandNabzx/mnemosynedespite the name. Nothing was installed, built or run, and neither the 1,236 Vitest cases nor the Python tests were run. MIT - fswolf/luna-local-agent
at
ed7f047c…— read only, from a full clone ofmainon 18 November 2026, 28 commits past the first reading at659ddcf2…; scoped tomind/,memory-manager/,core/andllm/and the memory files insenses/,life/,tools/andcommands/, with the portrait, games, plugins and voice stack read only where they write memory. No auto-run or build-time surface and two unpinned requirements files, one of them,installer/requirements.txt, changed inside the seven-day cooldown. Nothing was installed, built or run, and the 1,014 unittest methods were not run. The forget fingerprint's hash and stemmer were re-derived in a separate script and run against the system word list. MIT - Riley-Coyote/mnemos-mcp
at
3108e08a…— read only, from a full clone at the head ofmainon 6 November 2026, a commit dated 4 November 2026. No auto-run surface;pyproject.tomlanduv.lockinside the seven-day cooldown, both last changed on 4 November 2026 by the clone's own history;tests/conftest.pyexecuting on collection; aCLAUDE.mdaddressed to reading agents, read as data. Nothing was installed, built or run, and the 1,754 test functions were not run. Apache-2.0, with a NOTICE carrying the MIT notice for releases before 0.5.0 - ranxianglei/billion-context
at
83bddaa0…— read only, from a depth-1 clone at the head ofmasteron 7 November 2026, the merge of pull request 5755; commit counts and dates from the GitHub API. One auto-run surface, the.claude-plugin/marketplace and plugin manifests, which declare no hooks or MCP servers; theSessionStartandSubagentStarthooks are written into~/.claude/settings.jsonbybili plugin install claude, and a Codex plugin underplugins/codex/, listed by.agents/plugins/marketplace.json, starts an MCP server the screen does not parse. Eight dependency files inside the seven-day cooldown, all dated to the tip by the shallow clone; one npmpreparescript; four unpinned surfaces, two of themfile:packages in the tree;AGENTS.mdread as data. Nothing was installed, built or run, and the 1,299 test files were not run. MIT with an attribution term for user-facing products, which does not restrict analysis - revanthlevaka/OpenYantra
at
7910d7f7…— read only, from a full clone at the head ofmainon 10 November 2026. No auto-run surface;pyproject.tomlinside the seven-day cooldown, with no lockfile beside it;tests/conftest.pyexecuting on collection.yantra mcp setupwrites Claude Desktop and Cursor configs andyantra hook installoverwrites.git/hooks/post-commit, both only on command;install.shfetches files frommainand appends to the shell rc;SKILL.md,PROTOCOL.mdandWHITEPAPER.mdread as data. Nothing was installed, built or run, and the 96 test functions were not run. MIT inLICENSE, with the protocol's schemas and sheet templates under CC0 1.0 inSPEC_LICENSE. - Garyu-tt/noosphere-lite-mcp
at
b7f8c27c…— read only, from a depth-1 clone at the head ofmainon 8 November 2026, the merge of the repository's sixth pull request; commit counts and dates from the GitHub API. No auto-run or build-time execution surface;pyproject.tomlinside the seven-day cooldown, with no lockfile beside it; the README anddocs/read as data. Nothing was installed, built or run, and the 71 package test functions were not run. GPL-3.0-or-later inLICENSEwith no added terms. - GentianLine/clm-mem at
26f9b140…— read only, from a full clone ofmainon 9 November 2026. No auto-run or build-time execution surface;pyproject.tomlinside the seven-day cooldown, with no lockfile beside it;AGENTS.mdand the README read as data. Nothing was installed, built or run, and the 154 test functions were not run. MIT, with no added terms. - Sahil-SS9/Severian at
bdb14b04…— read only, from a full clone ofmainon 9 November 2026. No auto-run surface and nothing inside the seven-day cooldown; build-time execution innative/build.rsandtests/conftest.py, neither triggered;CONTRIBUTING.mdand the README read as data. Nothing was installed, built or run, and the 1,203 test functions were not run. MIT, with no added terms. - Acekorneya/POK-Agent
at
e97bb68b…— read only, from a full clone ofmainon 9 November 2026. No auto-run surface; five Cargo manifests inside the seven-day cooldown; a build-timebuild.rsin the Tauri app, not triggered; the README read as data. Nothing was installed, built or run, and the 786 Rust tests were not run. Apache-2.0, with no added terms. - waifuai/waifu-companion
at
f6f2b92a…— read only, from a full clone ofmainon 9 November 2026. The screen parsed nothing: there is no manifest, no build step and no CI, and by hand the run-time surface is the CDN scriptsapp/index.htmlloads, two of them unversioned. Nothing was opened, installed or run, and the 178 node tests were not run. MIT-0. - CaffeinatedSoftwareLLC/agora
at
737a4b5d…— read only, from a shallow clone ofmainon 9 November 2026. The screen found an OpenCode bundle and a Claude plugin manifest a harness would install, an npmprepublishOnlybuild, and every manifest inside the cooldown, which a shallow clone over-counts. Nothing was installed or run, and the 344 test files were not run. AGPL-3.0. - anthropics/claude-cookbooks
(managed_agents dreaming) at
ce8b2629…— read only, from a sparse clone ofmanaged_agents/; no auto-run surface, one build-time execution point, two unpinned dependency surfaces. Nothing was installed or run; the notebook's saved outputs were read as data. MIT - anthropics/claude-quickstarts
(managed-agents/knowledge-wiki) at
4a4224bd…— read only, from a full clone; no auto-run surface, five build-time execution points, 28 unpinned dependency surfaces across the repository, and the directory'srequirements.txtinside the seven-day cooldown. Nothing was installed or run; the notebook's saved outputs were read as data. MIT - darrenhinde/OpenAgentsControl
at
1ed1dd88…— read only, from a full clone; five auto-run surfaces, two build-time execution points, seven unpinned dependency surfaces, every lockfile unchanged for 25 days. Nothing was installed or run. MIT - maxritter/qualitylayer
at
8635ab90…— read only, from a full clone without a git-crypt key, so 5,022 of 7,613 tracked files were ciphertext, every test among them; one auto-run surface (git-crypt filter drivers, not configured here), eight dependency surfaces inside the seven-day cooldown, one build-time execution point, two unpinned dependency surfaces. Nothing was installed or run. QualityLayer Commercial Source-Available Licence - the-open-engine/zeroshot
at
7353598f…— read only, from a full clone at the head ofmainon 13 November 2026. Three auto-run surfaces: a plugin marketplace file, a Claude plugin manifest and a plugin.mcp.jsonnaming a hosted HTTP MCP server atapi.app.zeroshot.sh, which was not contacted;Cargo.lock, bothCargo.tomlfiles andpackage.jsoninside the seven-day cooldown; five build-time execution points (npm/zeroshotpostinstall, a huskyprepare,sdks/python/setup.pyandconftest.py,zeroshot/build.rs);sdks/python/pyproject.tomlunpinned with no lockfile;AGENTS.mdandCLAUDE.mdread as data. Nothing was installed, built or run, and the 183 Active Memory test cases were not run. The hosted service's Memory operations are not in the tree. MIT, four identical licence files, no added terms. - willderai/willder-core
at
48794d11…— read only, from a full clone of eight commits; no auto-run surface (hooks/holds React hooks), two build-time execution points (memory-service/tests/conftest.py, theprisma generatepostinstall), four unpinned dependency surfaces. Nothing was installed or run; graphiti-core 0.30.2, a pinned dependency, was not opened. MIT - wetwaferworks/bolt-pch-ie
at
570840ea…— read only, from a clone of 11 commits without a checkout; the screen recognises no C++ or CMake manifest and scanned nothing, soCMakeLists.txtwas read by hand: it fetches nothing, and the tree has no hook or agent file. Nothing was built or run; the vendoredthird_party/pch-publicsnapshot was searched, not read. MIT - krishyaid-coder/rakho-
at
21c4acd2…— read only, from a clone of five commits; the screen reported an unpinnedpyproject.tomlchanged inside the cooldown and nothing that auto-runs; nothing was installed or run, and the optionalsluice-taintpackage it adapts was not read. - Filippo-Venturini/ctxvault
at
d612d6e6…— read only, from a full clone of 215 commits; the screen reported an MCP manifest that launches the package throughuvx, apytestcollection hook, eight unpinned requirement files and apyproject.tomlchanged inside the cooldown. Nothing was installed or run; Chroma and sentence-transformers, its two engines, were not opened. MIT - mudassirzulfiqar/Decision-Keeper
at
911ff6b8…— read only, the whole tree of nine files and one commit; the screen found no surface it parses and reportedNOTHING SCANNED, so every file was read by hand. Nothing was installed or run. MIT - sh1zen/reql at
90e1acd0…— read only, from a full clone of 21 commits; the screen reported apyproject.tomlchanged inside the cooldown and unpinned dependencies. Nothing was installed or run; three findings were re-derived in a separate script. Apache-2.0 by its LICENSE file, MIT by its README and metadata - BaaRai/ARTEX at
65045efa…— read only, memory surfaces only, from a full clone of 1,033 commits; the screen reported four manifests inside the cooldown, a build-time script and two unpinned surfaces. Nothing was built or run; the lesson selection, retraction and scope widening were re-derived with lifted SQL on a scratch PostgreSQL. The agent SDK dependency was not opened. AGPL-3.0 - Morditux/llm-memory at
3e9efef6…— read only, the whole tree, from a full clone of 30 commits; the screen reported no auto-run surface, aMakefile, andgo.modandgo.sumchanged inside the cooldown. Nothing was installed, built or run; one merge tie-break was re-derived in a separate script. Of the MCP SDK only the v1.8.0 Streamable HTTP request checks were read, and the SQLite driver was not opened. MIT - peterjohannmedina/heurchain
at
82fa9f6c…— read only, the Go broker underbroker/and the agent-facing documents undernpm/,skills/andmcp/, from a full clone holding 49 commits; the screen reported no auto-run or build-time surface andnpm/package.jsonchanged inside the cooldown. Nothing was installed, built or run; the activation thresholds were recomputed in a separate script. The self-hosted edition, frozen at broker 0.6.1-oss.1; the mainline broker it is cut from is not in the repository. MIT - oritera/Cairn at
8e7e0ea6…— read only, the server, dispatcher, prompts, tests and design documents, from a full clone of 70 commits onmain; the screen reported acairn/tests/conftest.pythat executes on pytest collection and auv.lockunchanged for 170 days, and nothing that auto-runs. Nothing was installed or run; the reopen effect was re-derived with lifted SQL on a scratch SQLite database. The vendored web UI libraries and the unmergeddev-0.3.0branch were not read. AGPL-3.0 - Backboard-io/Backboard-Desktop
at
af5489c6…— read only, the Backboard-owned memory paths inbackboard/cli-ts,backboard/extensions/backboardand the desktop'scliTsagent host, from a shallow clone with counts from the GitHub API; the screen reported a.vscode/tasks.json, npm lifecycle scripts across the VS Code tree andbackboard/cli-ts, and fivebuild.rsfiles underbackboard/cua-driver, none of which runs on clone. Nothing was installed or run; three findings were re-derived on lifted snippets in a separate script. Upstream VS Code, the Copilot extension and the Claude Agent SDK were not read, and the hosted Backboard memory is not in the tree. MIT - vxcontrol/pentagi
at
cffed948…— read only, memory surfaces only, from a shallow clone with commit and contributor counts from the GitHub API; the screen reported a.vscode/settings.json, 101 floating ranges infrontend/package.jsonresolved by a lockfile, and aCLAUDE.mdtreated as data. Nothing was installed, built or run; one file of the pinned langchaingo fork was read for its metadata filter, and the Graphiti service image was not opened. MIT, with an EULA - electricsheephq/lcm-x
at
9f7f0bd3…— read only, the product modules, the Claude Code adapter, the assertion and entity layers and the committed benchmark results, from a shallow clone with history counts from the GitHub API; the screen reported a Claude Code plugin manifest, an MCP server and hook registrations, sixconftest.pyfiles, andrequirements-semantic.txtinside the cooldown with a floatingfastembedrange. Nothing was installed, built or run; the benchmark placements were recomputed from the committed JSON in a separate script. MIT - Vaultite/vaultite
at
55768189…— read only, the write, search, history, provenance, people, archive, MCP and agent-launch paths and their tests, from a full clone of 2,289 commits; the screen reported a Claude Code marketplace manifest, a.claude/settings.jsonSessionStart hook, a nested plugin with its own hook registrations, committed git hooks apreparescript enables, and apackage.jsonand lockfile inside the cooldown. Nothing was installed, built or run; the device-sync engine and Vaultite Cloud's relay were not traced. Apache-2.0, with citeproc-js taken under CPAL 1.0 - diggerhq/opencomputer
at
4129fb16…— read only, the Serverless Agents memory store, its admission and closure protocol, both runtimes' recall and save paths, the owner routes and their tests, from a depth-1 clone with history counts from the GitHub API; the screen reported no auto-running hook, aMakefileand aprepublishOnlyscript, and 28 dependency manifests inside the cooldown, which the shallow clone overstates. Nothing was installed, built or run; the Slack gateway incomputer/was searched for memory and not otherwise traced, and the private code production lays overservices/managed-agentswas not available. Apache-2.0, with both SDK manifests declaring MIT and no MIT licence file in the tree - ClickHouse/loom at
fc930e0c…— read only, from a full clone ofmainon 19 November 2026, first read at39243b1from a depth-one clone on 18 November; scoped toserver/memory/, the identity, auth, erasure, transport and storage paths it calls, the Claude Code plugin and the tests, with the code index, knowledge plane and dashboard read only where they touch memory. Ten auto-run surfaces, each read and none opened, the same ten at both pins. Nothing was installed, built or run, and none of the 28,036 tests were run; the benchmark headlines were recomputed from the CSVs underbench/results/. Apache-2.0 - Spookling/spookling-memory
at
d362ec0a…— read only, the log, judgement, fold, fact, routing, recall, hook, compaction, reset and MCP paths and their tests; nothing installed or run - ontogr/agentic-graphrag
at
757b77bd…— read only, from a full clone ofmainat releasev0.0.7, scoped to the decision, history, candidate, versioning, retrieval-scope, agent-tool and MCP paths and their tests; loaders, resolution and community detection read only where they write what those paths read. No auto-run surface; fifteen build-time execution points, allconftest.pyfiles and a Makefile. Nothing was installed, built or run. Apache-2.0 - caicaiya123/EvoMemNav
at
5770e8cc…— read only, from a full clone ofmain, a single root commit dated 26 October 2026 that does not descend from the earlier placeholder; the experience memory, agent loop, entry point, policy, prompts, recorder and config read in full, the VSMGraph and scene read for what persists, and paper v1 read in full. No auto-run surface and no build-time execution; 20 unpinned requirements inrequirements.txt. Nothing was installed, built or run. MIT; the perception path importsultralytics, AGPL-3.0 on PyPI - Stanford-TML/homebody
at
d7eb2083…— read only, from a--depth 1clone ofmainwith commit counts and dates from the GitHub API, scoped to the photo store, its map binding, therememberandrecallskills, their session injection and tests, the scan prior and the exploration view history;vendor/read only as a dependency list. No auto-run surface and no build-time execution; ranged dependencies inpyproject.tomlwith no lockfile, whose cooldown hits are inflated by the shallow clone;CLAUDE.mdaddresses agents and was read as data. Nothing was installed, built or run. Apache-2.0, with AMO walking-policy weights released upstream for research use only - MohammadAsadolahi/Memory-Reward-Inflation-in-Self-Improving-LLM-Agents
at
f563bca7…— read in full, from a full clone ofmain: all 21 Python files, the README and its history, and the manifests, against arXiv:2608.00017 v1. No auto-run surface and no build-time execution;requirements.txtnames five unpinned requirements. Nothing was installed, built or run. No licence - maximem-ai/maximem_synap_core
at
ecfbb3b0…— read only, from a full clone ofmainafter releasev0.1.0, scoped to the edition module, schema, ingestion stages 3 and 4, knowledge update, graph lifecycle and outbox, retrieval scope and liveness, delete, forget, retention and their tests; compaction, profile and the browser read only where they touch those tables, and the synap-er dependency not read. No auto-run surface; twelve build-time execution points, allconftest.py; two unpinned surfaces,requirements.txtinside the cooldown. The committed LongMemEval records were recomputed with a script kept outside the tree. Nothing was installed, built or run. Apache-2.0
What the licences actually say
A licence is an operational caveat, not a memory mechanism, so it lives in the appendix — but a reader deciding whether they can use something needs it. "Publicly readable source" is not "open source": twenty-three carry a licence that is not open source, each named in its own report and collected here.
| Licence | Systems |
|---|---|
| Elastic License 2.0 — no hosted service, no licence-key circumvention | AgentSwarms, ByteRover, Dexto |
| Business Source License 1.1 — source-available, converts later | Cognis, Empryo, Intaris, MuninnDB, Skales |
| Non-commercial — read and run, do not build a product on it | Memento (PolyForm Noncommercial 1.0.0), Project Golem (its own source-available non-commercial licence), NouGenShards (its own source-available licence; inspection and personal use granted, commercial use, competing hosted services and use to build competing AI memory or retrieval products prohibited) |
| Conditional MIT — three added conditions, revocable at the author's discretion | Z-Waif (a 2% royalty on gross income above $100,000 lifetime; an "ethical treatment" clause "DEFINED AT SugarcaneDefender's SOLE DESCRECION"; and — the one that constrains the memory itself — no collection or storage of "user logs, character configurations, or other user data" without consent obtained through terms the user "MUST ACCEPT UPON OPENING" the software) |
| Conditional BSD — branding may not be altered above fifty users | Open WebUI (the "Open WebUI License": BSD-3 plus a fourth clause making removal of the branding "a material breach" in any deployment reaching fifty end users in a rolling thirty days, absent a written permission or an enterprise licence) |
| Commercial source-available — read, evaluate and fork to contribute; a subscription to run; no redistribution or reuse | QualityLayer (its own licence, under German law; the public tree is a deliberate projection and most of it is encrypted) |
| All rights reserved with a research-use grant — run to reproduce one preprint, and nothing else | Aura (the grant was added on 9 November 2026; no copying, products, derivative works or model training) |
| All rights reserved with a run-as-distributed grant — read the source and run the plugin as shipped, nothing else | Spookling Memory (no
copying, modification or redistribution without written permission;
package.json says UNLICENSED) |
| All rights reserved — publicly readable, no grant at all | Nova AI ("Viewable, Not
Reusable"), OptMem, 7layermem (whose README asserts MIT
with no licence file under it), SESA (no
licence file, which defaults to this), Master Agent System (no
licence file at the root, beside vendored packages that carry their
own), Sol0mon (no licence file, and a
README saying none has been selected) and Vanilla RAG Memory (no licence
file, and no licence statement in the README or
pyproject.toml) |
Two things this table is not. It is not a complete licence taxonomy of the corpus: it collects what the reports happened to record, and a report is written about mechanisms, so a permissive licence usually goes unmentioned. The rest have not each been checked — the honest claim is that twenty-three are known non-open-source and the others are unrecorded, not that the others are MIT. And it is not a reason to skip those twenty-three: every mechanism in this atlas is described so it can be re-implemented rather than copied, which is the only way a restrictively licensed system can be read usefully. What changes is what you may do with the code afterwards, and that is worth knowing before you open the file rather than after.
Commands Used
Representative local inspection commands:
find . -maxdepth ... -type drg --filesrg -n "memory|recall|remember|search|embedding|vector|MCP|Block|Passage|Representation|drawer|palace|wing|room|claim|evidence|retrieval_event"sed -n ...wc -lcmpjqgit show -s --format=fuller HEAD
Every mechanism claim in the comparative report, the system families and the matrix comes from the checked-out code it names. The published literature the report argues with — the surveys, the benchmarks, the papers cited by arXiv id — is read from the sources linked inline.
Known Limitations
- The Daimon report said the forget scrub of
events.jsonlremoves no row and that the relation ledger's only reader-facing surface is the viewer's History lane, and the benchmarks page said nothing in the Daimon repository references this atlas; corrected 2026-10-08. At3e525689…every ledger rewriter split text withstr.splitlines(), which also breaks on the U+2028, U+2029 and U+0085 thatensure_ascii=Falserows hold raw, so a forget tore such a row into fragments: the refutation, amendment, request and relation deleters dropped them,scrub_event_fieldswrote them back as separate lines no reader parses, and the privacy audit, splitting the same way, reported the file clean. The same scrub took no lock, and its docstring accepted that an append racing its read-and-rename was lost. Both were closed upstream in #1139 and #1145. Thedaimon relations listandshowverbs printed the relation ledger at that pin as well. The README has cited this atlas since 2 September 2026 (#910); the deletion-durability test the benchmarks page discusses was committed on 29 July 2026, so the convergent-arrival reading stands. The overview's integration entry namedcli.py, which has been a package of verb-family modules since the 2026-08-16 pin. - The Munder Difflin report counted 110 test files at a pin
that had 107; corrected 2026-10-04. At
c7c8921f…the Munder Difflin report gave 110 in its summary, risks field, sections 9 and 10 and its Recorded Searches table, and the verdict, the homepage card and this page repeated it.test/held 110 entries, three of them not test files: a TypeScript loader, a manual benchmark and the fixtures directory. The command the table recorded,ls test/*.test.cjs | wc -l, returns 107 at that pin, so the row's result disagreed with its own command. The figure was an over-count by three, written to correct a false absence claim; the finding it carried, that no test reaches the condensation gate, held. The same report gaveMemoryManager293 lines;src/main/memory.tsis 447 at that pin. It also carriednegative_eval, awarded on cases that guard a log write, a delivery state and a deletion rather than retrieval, which was wrong at that pin; the mark is withdrawn 2026-10-04. - GitHarness (arXiv:2609.36789) was
examined and has no report: no code is released.
GitHarness: Git Init Your Harness Working Memory for Perpetual User
Requirements (Zhibang Yang, Xinke Jiang and ten co-authors, 29
September 2026) proposes the shape this atlas looks for under
correction: requirement states and the harness work states that answer
them are kept as a branchable version history, and when a user
completes, adds or shifts a requirement a trained Git Agent picks a
semantically compatible past state, restores it and opens a new branch,
so obsolete evidence is excluded and compatible work inherited rather
than rewritten. It reports results on MTAgentBench, its own benchmark
across mathematical reasoning, text-to-SQL, agentic search, software
engineering and research synthesis. The paper's reproducibility
statement says the implementation, trajectories and evaluation scripts
will be released to
anonymous.4open.science/r/GitHarness-7A2E; on 4 October 2026 that mirror lists one file, aREADME.mdreading "Coming soon." Searched: the arXiv HTML for code links (only that mirror); GitHub repositories forGitHarness(three unrelated matches, one a figure-study repository) andMTAgentBench(none); and the GitHub accounts returned for the first two authors' names, none holding the code. What the atlas would read for is whether a restored branch is a filter on what the harness may use, and whether a requirement the user withdrew can come back on a later branch; neither is checkable from the paper alone. facebookresearch/context-language-modelswas examined and has no report: the context it manages lives for one task, and the one artifact that outlives a run is an instruction tuned offline. Read at18dc1111…, 9,150 lines of Python, CC BY-NC 4.0, the code for Context Language Models (arXiv:2609.37725, Shao et al., 29 September 2026). A CLM keeps its working context as a file it may rewrite without restriction,LIVE_CTX_MAIN.txtunder/tmp/.live_ctxinside the task sandbox (clm/clm_harness/context_env/paths.py:23-24), mirrored to a host temporary file (context_env/env.py:113-125). The only path that reads a context back isresume_from, a warm restart of the same interrupted trial from its own directory (clm_agent/harness.py:232-235,utils/resume.py:6-30); nothing carries a context into another task. What does outlive a run isclm_icl/evolve.py: a command-line loop in which a proposer model writes candidateSKILL.mdfiles from contrastive rollouts, scores them on development tasks, and gates one in as the incumbent, marking the restrejectedand the old oneretired(evolve.py:280-312). That is offline optimisation of one context-management instruction, run by a researcher, not memory an agent writes while it works, so it sits with conversation-window management. The paper names the risk this atlas cares about from the other side: an editable context is another channel through which a prompt injection or a self-written instruction can persist across turns. Screened before reading: no auto-run or build-time surface, twopyproject.tomlfiles inside the cooldown with unpinned ranges; nothing was installed, built or run.Blooshoo/BlooRecallwas examined and has no report: it is a search index over a person's own notes, the agent's only verb is search, and every stored row is a snapshot that the next refresh rebuilds from disk. MIT (Bloo), 2,355 lines of Python underbloorecall/with 65unittestmethods in three files, two commits by one author on 4 October 2026 (UTC), read at6a7ee8e5….refreshwalks configured roots, chunks Markdown by heading, embeds each chunk through a local Ollama model and writessources,chunksandvectorstables to SQLite (bloorecall/store.py:15-52); search blends BM25 with cosine similarity. The MCP server registers one tool,bloorecall_search(bloorecall/mcp_server.py:31-48), which opens the index withmode=ro(bloorecall/store.py:95-98,bloorecall/search.py:57). The only write connection is opened inindexer.refresh(bloorecall/indexer.py:98), reached from the CLIrefreshcommand (bloorecall/cli.py:99-104) and a cron wrapper. The default exclusions skip path parts namedmemory,memories,sessionsandconversations(bloorecall/config.py:80), and a query containing "personal memory" is refused (bloorecall/search.py:31). The part that transfers is the read-time check: before results leave,verify_hitsre-hashes each hit's file against the hash stored at index time and labels itstrong,rebuilt,weakorstale(bloorecall/trust.py:83-137,bloorecall/search.py:128-150). It is the per-hit verdict Heimdall computes, credited in the module docstring, with one difference: Heimdall sorts by verdict first, while here ranking finishes before verification and nothing re-sorts or drops astalehit (bloorecall/search.py:363-372), so the verdict annotates and withholds nothing. A drifted file is corrected by re-indexing what the person wrote, which is the document-index case. Searches run at this pin withgit grep:-nE "@server\.tool|\.tool\("(one registration);-nE "connect_write"(one caller);-nEi "remember|forget|supersed|tombstone|retract|correct"overbloorecall,scriptsandbin(nothing);-nEi "arxiv|bibtex|@article|@misc|doi\.org|CITATION"(nothing). Screened before reading: no auto-run or build-time surface, one FRESH and one FLOAT finding, both onpyproject.toml; nothing was installed, built or run.- The Hillock report described several mechanisms that had
changed before the pin it was published at. At
94e6ae1b…its body scored the gate as a bundled-query cosine, which late interaction replaced in v0.6; described conversational fact writes, removed on 2026-08-12; said correction reachedborn_inthrough a five-predicateDELETE, which that pin had commented out; criticised a pooled gate metric the harness had split into separate rates on 2026-08-23; credited the hard negatives with inline reasons, removed on 2026-08-13; and quoted the v0.4.1 row of the README's version table as current. The errors run both ways: the write and correction surfaces were overstated and the benchmark's reporting understated, while the gate's length dependence survives the change of scoring. Corrected 2026-10-03 in the report, at a new pin, with the gate scores recomputed. - The aimee report said
pendingmemories never enter a current read; corrected 2026-10-03. At6cd13694…the aimeetrust_stateevidence record listedpendingbesidearchived,supersededandretiredas states no current read admits.pendingmarks an open commitment with a TTL, and the session recall bundle serves it in its commitments section at that pin and at the next (server-go/modules/memory/recall.go:273). The error ran in the awarding direction; the mark holds on the other three states, and the record and section 6 of the report state the commitment read. kiagentkronos-cell/openclaw-visual-memorywas examined and has no report: it is an open hook around a memory whose code is not published. MIT, 1,776 lines of TypeScript undersrc/with 93 test cases, 17 commits between 29 September and 1 October 2026, read atd5f59e1e…. It is an OpenClaw plugin that, for every inbound message carrying an image, runs a local Visual Memory check and injects the verdict into the same prompt turn, as[Visual Memory] Treffer: <Name> (kind, confidence, score)orkeine Treffer. The README says the plugin "contains no register logic" and is "a thin hook wrapper" around a Visual Memory CLI that "owns faces, embeddings, thresholds, and the SQLite register" (README.md:9-11). The code agrees: the only call into that CLI isspawn(pythonPath, [scriptPath, "check", imagePath])(src/checker.ts:97), with the script expected atscripts/visual-memory/vm.pyinside the operator's workspace (src/config.ts:69-70,README.md:25-28), so the plugin never enrolls, corrects or deletes anything. What it writes is a rotating decision log (src/diaglog.ts) and one JSONL transcript per processed image (src/transcript.ts), records of runs rather than of beliefs. The register, its enrollment path and thedreamingsettings the README documents (README.md:119-138) belong to that tool, and its source is not in this tree, not among the account's other public repositories, and not found by a GitHub repository search for the name or a code search forvm.py check; the README links to no repository at all. The privacy section (README.md:182-194) is the part worth keeping: the register holds face embeddings and reference crops of real people, enrollment is explicit and a third party's requires consent, and erasure is deleting the CLI's database files. Screened before reading: no auto-run, build-time or unpinned surface, one manifest inside the seven-day cooldown; nothing was installed, built or run.- The NexusMem report omitted the Claude Code capture and
recall hooks, called a source prune unaudited, gave the MCP server four
read-only tools, called the VS Code extension read-only, said shell
commands were stored unredacted, and described the vector arm as
filtered after a global fetch; corrected 2026-10-02. At the
previous pin
0003e243…,src/agent/recall.tsandsrc/adapters/claude-code/were in the tree, added on 11 September 2026 and described in the README, so the report's statement that the pre-commit hook was the only read selected by what the user is doing understated the system. In the same treerunPruneSourceswrote aprune_sourcerow tomutation_audit(src/cli/commands/sync.ts:666); the MCP server registered six tools, among themsync_projectwith a confirmed prune andresolve_stale_suggestion; the extension called that tool from a stale-review view;shell-history.tspassed every command throughredact()(:73); andnodes_veccarriedproject_idas a vec0 partition key (src/store/schema.ts:294). The pre-commit warning was also misquoted, and its churn line was printed as a dim note, not aWARN. The test count, 835 in 57 files, was low: the same counting method gives 1,011 declarations in 78 files at that pin. The NexusMem report, its verdict entry and its homepage card are corrected ate1842964…. No capability mark moved. - The Daimon report said a re-extracted forgotten value is
suppressed on read, that nothing rewrites the event log, that there is
no within-session write, and that the model can neither resolve nor
forget; it also carried five wrong line citations, three stale counts
and seven altered or misattributed quotations; corrected
2026-10-02. At the previous pin
c967baa7…,store.write_checkpointran every checkpoint throughpolicy.drop_forgotten, which removes a forgotten value before it reaches disk (plugin/daimon_briefing/store.py:1354-1355,policy.py:94-107, in the tree since 29 July 2026). The Daimon report, the rejected-value tombstone page and the families page therefore understated the system by calling its tombstone suppression at read. Three claims ran the other way:scrub_event_fieldsredacts event fields in place after a forget, the Codex and KimiStophooks serialize mid-session, andforgetchecks for a terminal only when it would remove an active ruling, while an agent'sresolve --by agentis confirmed by a transcript quote. The fourworldcheck.pyprobe citations sat thirty lines early and the reverify citation pointed at an unrelated line;field_table.pywas 745 lines, the schema document 705, andtest_worldcheck.pyheld 128 tests; one quotation was in no file, four altered the source's words, and two were commit-message text presented as source. The test census countsdef test_at any indentation, which the report's method note had described as line start. NVlabs/SoL-Piwas examined and has no report: it is context engineering for one Pi session, and nothing it stores outlives that session or could turn out to be false. MIT, 3,250 lines of TypeScript undersrc/with 143 test call sites in 20 files, 39 commits between 8 September and 1 October 2026, read ate1a586af…; it accompanies arXiv:2609.20519. It is an extension for the Pi coding agent with four opt-in mechanisms, and three of them write files. ObservationPack stores a text tool result over 10 KiB under an id hashed from the tool name, call id and content, sends it whole on its first two requests, then swaps in a placeholder with a 1 KiB excerpt;obs_recallpages the original back by byte offset, and aledger.jsonlrecords each send and recall (observation-pack/index.ts:64-197,observation.ts:13-17,:105-106). The Evidence-Preserving Reducer accepts a model-written log receipt only when every quotation occurs byte for byte in the archived log, and otherwise returnsunverifiable-quoteand keeps the original (evidence-preserving-reducer/receipt.ts:110-122). Online Context Compact prices a compaction against the requests it expects to remain (online-context-compact/economics.ts:129-229). Every one of those paths is rooted atruntimeRoot, which issol-pi/plus the session id inside Pi's session directory, or a fresh temporary directory when the session has none (src/sol-pi/runtime-paths.ts:13-30); no code reads another session's root.git grep -n -i -E 'memor(y|ies)|remember|long-term|cross-session|across sessions|previous session|prior session'over the tree, lockfile excluded, returns only in-memory session and one documentation link. What is stored is a verbatim tool output, which happened and cannot be corrected, so this sits with conversation-window management. The reducer is the part that transfers: a derived summary admitted only when its quotations verify against the retained source is the check evidence before belief asks of a memory write. Screened before reading: no auto-run, build-time or unpinned surface;AGENTS.mdandCLAUDE.mdwere treated as data; nothing was installed, built or run.fabro-sh/fabrowas examined and has no report: it is a workflow orchestrator whose durable state is a record of runs, and the only text it hands an agent as memory is the repository's ownAGENTS.mdand its relatives, loaded read-only. MIT (LICENSE.md, Lithos Computer Co. and Qlty Software Inc.), about 221,000 lines of Rust outside test directories and 5,655 commits onmain, read from a depth-one clone at81bbe204…with the commit count from the GitHub API. A run executes a Graphviz DOT graph of agent, command and human-gate stages on the workflow enginepetri, a git dependency locked atf30a12df…, whose context is run-scoped: completed node instances and a run-scopedkvthat only the engine'sapplywrites (crates/core/engine/src/context.rs:1-14there), and which "starts empty at the beginning of a run" (docs/public/execution/context.mdx:10). What persists is an event-sourced run store of events, checkpoints, stage outputs and a conclusion per run, with artifacts in a content-addressed blob store. It is read back byfabro inspect, the DuckDB insights page, resume of the same run, and eight MCP tools (lib/apps/fabro-mcp-server/src/server.rs), of whichfabro_run_searchandfabro_run_get(:134,:156) let an outer agent, or an in-run agent whose worker token carries the run-tools scope (lib/apps/fabro-cli/src/commands/run/runner.rs:135-153,lib/components/fabro-workflow/src/run_tools.rs:13-18), find and read earlier runs. Those are records of what a run did, which can be archived and cannot turn out to be false, so they are records of runs rather than of beliefs, like the per-image transcripts in theopenclaw-visual-memoryentry above. The agent loop is the externalpebble-coding-agentcrate, locked at0f361448…; itsProjectMemoryreads the files an application names into the system prompt within a 32,768-byte budget (crates/pebble-coding-agent/src/memory.rs:1-18,:139there), and Fabro'sproject_memorynode attribute switches that on forAGENTS.md,CLAUDE.mdand their relatives (docs/public/reference/dot-language.mdx:223). The loader only reads. Variables shared across runs are written through the server's REST handler (lib/apps/fabro-server/src/server/handler/variables.rs:11-16), not by an agent tool. The product's own account of why it exists sets memory aside: "memory files make no guarantees" (docs/public/getting-started/why-fabro.mdx:16). Searches run at this pin with/usr/bin/git grep:-n -i -E 'remember|forget|recall|lesson|learning' -- 'lib/**/*.rs' ':!*test*'(printer state, a checkpoint-commit cache and a worker-acknowledgement map; no memory verb);-c -E 'name = "fabro_' -- lib/apps/fabro-mcp-server/src/server.rs(8);-n -E 'AGENTS\.md|CLAUDE\.md|project_memory' -- '*.rs'(three DOT strings inlib/components/fabro-petri/tests/stall.rs, each settingproject_memory=false);-n -i -E 'arxiv|bibtex|@article|@misc|doi\.org|CITATION' -- . ':!Cargo.lock' ':!bun.lock' ':!THIRD_PARTY_NOTICES.txt'(three prose uses of citations indocs/public/examples/clone-substack.mdx). In the two dependencies, the GitHub trees API at their locked revisions lists one memory-named source file each: pebble's loader and petri'scrates/core/store/src/memory.rs, an in-memory run store for tests and hosts that keep no run of record. Screened before reading: one auto-run surface,.claude/settings.json, aPostToolUsehook runningcargo +nightly fmton edited.rsfiles; sixbuild.rsexecution points; four floating surfaces; FRESH findings on every manifest, inflated by the shallow clone dating each file to the tip;AGENTS.mdandCLAUDE.mdtreated as data. Nothing was installed, built or run.krishyaid-coder/Miss-Mewas examined and has no report: it measures whether a Claude Code session's context window still holds facts the user pinned, and what it stores is the answer key, which by design never reaches the agent. MIT, 1,705 lines of TypeScript undersrc/and 38 test cases in two files, nine commits between 13 October and 5 November 2026, read at1e30c786…; by the author of Rakho. A pin writes one of at most five facts (src/core/types.ts:87) to.miss-me/state.jsonin the project, where it outlives the session untilmiss_me_unpinremoves it. The only reader of a stored fact is the scorer (src/core/score.ts:100): every eighth prompt, before compaction, and on a compact or resumeSessionStart, a hook hands the model the anchors' ids and labels and tells it to callmiss_me_checkwith what it remembers (src/cli/hook.ts,src/core/nudge.ts:32-35). The memory under test is the window, and what persists is an oracle for testing it rather than anything the agent recalls, so this sits with conversation-window management. The other half, guards, appends a line to.miss-me/access.jsonlfor each file-touching tool call that reaches a guarded path, tiered as a named read, a search sweep or a shell mention, and blocks nothing; it is a record of tool calls, not of beliefs. Three defects at this pin bear on what it measures. The scorer counts as remembered any recollection whose normalised text is a substring of the fact (src/core/score.ts:52): against the README's example pin The API is FastAPI with Postgres, a re-derivation ofrecallHitin a separate script scoreseandisas remembered, and the 0.55 token-coverage threshold (:72) passes The API is FastAPI with MySQL; the committed wrong-restatement case (src/core/score.test.ts:21) shares no token with its fact. The answer key and every earlier guess sit in a plain file inside the project, which the agent's own Read tool reaches, and nothing guards.miss-me/unless the user adds it. Andmiss_me_trailfilters tosessionId()(src/mcp/server.ts:147), which isCLAUDE_SESSION_IDor"default"(src/core/cwd.ts:9), while the hook records the id Claude Code passes it (src/cli/hook.ts:48);initregisters the server with no environment (src/cli/init.ts:66,:95), so unless the host exports that variable to MCP servers, the tool's default per-session count misses every event the hook recorded.recordCheckcopies each check into the busiest hook session to bridge the same split for health (src/core/store.ts:134-145), and theStophook's own trail report uses the hook's id, so only the tool is affected. Searches run at this pin with/usr/bin/git grep:-n -E '\.fact([^a-zA-Z]|$)' -- src(one reader, the scorer);-n -E 'miss-me/|state\.json' -- src/core/guard.ts src/core/match.ts src/cli/hook.ts(none; the same pattern counts two lines insrc/core/store.ts);-n -i -E 'arxiv|bibtex|@article|@misc|doi\.org|CITATION' -- . ':!package-lock.json'(none). Screened before reading: no auto-run or build-time surface, four floating ranges inpackage.jsonbehind apackage-lock.jsonunchanged for 35 days; nothing from the tree was installed, built or run.- The virtual-context report awarded
scope_enforcedon every relational read path, called its audience receipt a read-side guard, said nothing measured a mechanism on its own, and gave the project's LongMemEval caveat as LoCoMo only; corrected 2026-10-01. Atf5adda09…the MCPdomain_statustool and both topic resources called the store without a conversation id (virtual_context/mcp/server.py:338,:361,:373), listing every conversation's tags and segment refs with the summary text withheld; from27b0202the resource returns the text, and the virtual-context report withdraws the mark.effective_attested_audienceguards replay and attestation only.benchmarks/jev/RESULTS.mdheld per-seam results for rerank, intent, temporal, safety and admission. The README labelled the 95/100 run historical, with run-provenance limits. The recorded predicate counts, 354 and 85, reproduce as 347 and 64. - The mini-AGI report said
train.pycarries four subcommands, that the README cites an uncommittedtools/expand_corpus.py, that the README's reference list has seventeen entries, and that the dry-read writeback is live on the published model; corrected 2026-10-01. At the first pin201852d3…,train.pyregistered three subparsers (read,stream,ponder-probe);tools/expand_corpus.pywas named only in a.gitignorecomment, while the README's pipeline ran the committedpython3 -m corpora expand; the acknowledgments held sixteen entries citing eighteen papers; and the README said the weights were not published, so the 174–175 experts it reported described the training run. Three of the four overstated what the tree held and one misplaced a citation; none bore on a mark. - The Aura report said nothing reads its persisted
contestedflag, withheldnegative_eval, and described two belief rules the code had replaced; corrected 2026-11-16. At19cf16e8…and at every earlier pin,SelectiveMemoryBridgerefuses a contested record at the latent-cortex ingress, andtests/test_rlc_epistemic_memory.py, committed on 22 July 2026, asserts that contested, expired and mis-scoped records are not admitted. The Aura report said repetition promotes a belief totrusted; since 2 August 2026 that needs two distinct evidence references. It said nothing callsreconcile;core/capabilities/conversation_revision.pyhas called it since 5 July 2026. It said no surface lets a person adjudicate a memory; a panel and five routes have existed since 4 June 2026, and they resolve a service whose class lacks the methods, so the mark stays withheld for a different reason. - The Decision Keeper report overstated the installer's
repository-root refusal and what its recorded hashes describe; corrected
2026-11-18. At
911ff6b8…, the only commit upstream, the Decision Keeper report said the installer refuses any directory that is not the top level of its git repository.install.py:177runs that check only whenshutil.which("git")findsgit, and skips it otherwise. It called all twenty-three SHA-256 values atinstall.py:41-85hashes of earlier skill files; eighteen are, three are of Codex subagent definitions, and two, inLEGACY_GUIDANCE_HASHES, are of an earlier Teach Me instruction block. No mark depended on either statement, and all seven stay withheld. - The Aura report called its receipt chain the only
hash-chained audit in the atlas, and gave two test censuses from other
pins; corrected 2026-10-01. At
cf84a733…the Aura report, its card, its verdict and the families and tensions pages called the chain unique; aimee and Midas carry hash-chained audits too. Its sections 1 and 10 gave 44,104 and 21,206 test functions; at this pingit grep -c -E '^[[:space:]]*(async[[:space:]]+)?def test_' -- 'tests/*.py'gives 46,060 across 4,077 files. Its "I ran it" also went without a commit: the 16 audit-chain tests ran at the first pin,e8866f4, and were read, not run, afterwards. - The Mercury Agent report said nothing was known to move a
memory into or out of its
subconscioustier; corrected 2026-10-01. At781daac2…the Mercury Agent report left the question open, and two pattern pages repeated it as an absence. The agent's heartbeat callsprune()(src/core/agent.ts:4291), which callsmoveToSubconsciouson everyactiveordurablerow unseen for 30 days (src/memory/second-brain-db.ts:480-493), andretrieveRelevantcallspromoteToConsciouswhen fewer than three conscious matches clear the recall threshold (src/memory/user-memory.ts:248). The same report said scores were assigned once with no path to revision;mergeRecordraises them withMath.max(user-memory.ts:505-507). - The openvurp report awarded
scope_enforcedon a per-agent directory, and its description and section 9 said a correction typed to an agent reaches the platform's learning log; corrected 2026-10-01. Atfc68e643…,memorieshas no scope column (core/vector_memory.py:66-75) and neither the FTS nor the vector query carries a predicate; the agent id reaches storage only as the directoryMemoryManageropens (core/memory.py:32). That is a physical partition, so the openvurp report'sscope_enforcedmark was too generous and is withdrawn. A correction typed to a roster agent reaches no learning log at all, because the hook lives inAgent.runand a direct chat bypasses it, so the description named the wrong destination. - The gh-aw report awarded
scope_enforcedon an integrity lattice that is a partition by name, said the level is assigned by the trigger so a fork PR reads what a merged run remembered, and said comment-memory content is injected into the prompt; corrected 2026-10-01. At9259aea1…, the level is the workflow's compile-timetools.github.min-integrityenum, emitted as a literalGH_AW_MIN_INTEGRITY(pkg/workflow/cache_memory.go:120), and it prefixes the cache key that every restore key keeps (pkg/workflow/cache_integrity.go:163-179,pkg/workflow/cache_steps.go:111-133). A cache-memory store therefore never crosses levels, and the read-down merge does work only on a drive two levels share. No file carries a level and no read applies one, so the gh-aw report'sscope_enforcedmark was too generous and is withdrawn.injectCommentMemoryPromptwrites file paths, not content. Each error overstated the system. - The Microsoft Agent Framework report grounded
scope_enforcedon the harness memory's owner directory and said the Cosmos checkpoint store refuses an ambiguous checkpoint id; corrected 2026-10-01. Atc030fa35…,MemoryTopicRecordcarries no owner and no read filters on one, so the harness isolation in the Microsoft Agent Framework report is a physical partition selected by path, which the mark excludes. The mark holds onRedisContextProvider, which storesapplication_id,agent_idanduser_idon every document and ANDs a tag equality for each configured id into its search (python/packages/redis/agent_framework_redis/_context_provider.py:319-322,:363-371). The checkpoint refusal is onloadonly;deleteremoves the first document matching the id (python/packages/azure-cosmos/agent_framework_azure_cosmos/_checkpoint_storage.py:311-343), which the report overstated. No mark moved. - The OpenSRE report awarded
scope_enforcedon a directory per actor and said the store had four memory types, two of them grounded; corrected 2026-10-01. At730ebc1a…,MemoryRecordcarries no owner and every read globs the directorymemory_dir()resolves, so per-user isolation in the OpenSRE report is a physical partition selected by path, which the mark excludes; the mark is withdrawn and one remains,negative_eval.OPENSRE_MEMORY_DIR, when set, files every actor in one directory.MemoryTypehas five values, andrepositoryis grounded besideinfrastructureandinvestigation_learning(core/agent_harness/session/memory_extraction.py:52), which the report understated. - The breadcrumbs report awarded
trust_stateon a status no read filters on, and said an as-of replay shows an oracle verified after the cutoff; corrected 2026-10-01. Atbf0b6a2b…,build_context()emits every fact that passes its time and scope masks and readsstatusonly to choose the label (templates/ledger-tools/memory_engine.py:620-632), and no other read in the tree filters on it, so the breadcrumbs report'strust_statemark was too generous and is withdrawn. The replay claim ran the other way:verify_fact()stampsverified_atand the replay masks a later stamp toasserted, so a re-verification after the cutoff hides the earlier verification rather than showing the later oracle. The report also described the promotion gate as refusing empty evidence alone, where it refuses five ways, and its sections 4 and 5 still arguedscope_enforcedandbitemporalwere withheld while the report carried both. - The CSM report awarded
scope_enforcedbeside a cross-project read it described; corrected 2026-10-01. At9c7cfb22…the CSM report credited the mark to a search path that fails closed, while its own body said the lesson-trigger cache selects up to 50 lessons from the samememoriestable with noproject_idpredicate and injects them into the system prompt on every turn. An injection read over the same store that cannot carry the predicate withholds the mark, so it is withdrawn and the search path is the near-miss. - The Create Context Graph report awarded
scope_enforcedon REST read paths while the agent's query tools read the same graph unscoped; corrected 2026-10-01. At707b168d…the create-context-graph report credited the mark to a null-permissive domain predicate on nine REST read paths. The agent's domain tools run fixed Cypher with no domain predicate through the same query function against the same graph, and its free-form Cypher tool applies one only when the model writes it. An agent-reachable read over the same store that cannot carry the predicate withholds the mark, so it is withdrawn and the routes are the near-miss. - The Janus-Graph report's
bitemporalevidence record said the graph-search endpoint putsinvalid_at IS NULLin its Cypher traversal and drops any invalidated row; corrected 2026-10-01. At5a66516f…the condition isrel.invalid_at IS NULL OR true(daemon/search_engine.py:133), so every relationship passes, as the report's own section 6 said; the record had repeated the module docstring. The filtered reads aresearch_memoryover MCP and the daemon'sGET /search/memory, both throughengine/search_memory.py:91-93. The mark stands: Graphiti stores validity beside record time. See Janus-Graph. - The Prismer Cloud report awarded
scope_enforcedwhile its own section 9 showed the turn-start digest injecting hub summaries with no visibility check; corrected 2026-10-01. At5337ca14…,buildMemoryDigestwrites every hub's path and its description or first body line from the samememory.dbthat search filters, through a provider that takes only a workspace id, and the Hermes adapter appends it to every system prompt by default. An injection path over the scoped store that cannot carry the predicate withholds the mark; the report now carriesnegative_evalalone. - The OpenZync Core report said every read path imports one
shared temporal predicate, that the organisation key reaches the two
BM25 search legs and not the vector ones, that row-level security fails
closed beneath search, that the GiST constraint enforces non-overlap,
and that nothing runs the cross-tenant suite; corrected
2026-09-30. At the previous pin
da95554b…,_effective_at_clausehad three repository callers and both fact search legs restated its three clauses inline, so the OpenZync Core report's headline overstated the system. The organisation-keyed methods it contrasted are repository methods off the search path, and the vector pair had takenorg_idsinceb6d635e3…on 13 September 2026; hybrid search's four SQL legs filter on the project alone. Row-level security binds only a role that does not own the tables, and the tag-deploy workflow migrates with the URL the API serves on. The exclusion constraint is keyed per source episode..gitlab-ci.ymlrunspytest tests/security/, added in the commit that removed the skip, which understated the system. The report also counted GET requests as audited, cited two mocked unit tests as integration cases, recordedrg -i 'tombstone'as empty over four files, and carried a census measured at the first pin. No mark moved. - The Zep report awarded
bitemporalon a misreadcreated_at, said nothing in the tree stores or forgets memory, that nothing injects it and that the model only reads, described a Community Edition purge tier that nothing calls, and put its LoCoMo graders in the wrong order; corrected 2026-09-30. At495bf728…, which is upstream HEAD,created_aton a triple is the caller's event time —zep-cloud3.28.0 documents it as "The timestamp of the message" — and no code in the tree tracks either time axis, so the Zep report'sbitemporalmark was too generous and is withdrawn; the Community Edition's publicFactkeeps one timestamp,valid_atwhere present, and dropsinvalid_atandexpired_at(legacy/src/lib/graphiti/service_ce.go:37-42,legacy/src/models/fact_common.go:9-14). The other errors ran the opposite way, absences over committed code.ZepContextTool.process_llm_requestpersists each user message and appends the returned context to the system instruction (integrations/adk/python/src/zep_adk/context_tool.py:309-408), and four integration packages register a model-callable write tool. The Community Edition keeps sessions and messages in Postgres, extracts through a Graphiti service, and purges throughpurgeDeletedResources();purgeDeleted()has no caller and no Go file carries a build constraint. The accuracy grader runs after the answer (benchmarks/locomo/evaluation.py:166-171).benchmarks/longmemeval/is the code for arXiv:2501.13956, which the report did not cite. - The widemem.ai report credited its LoCoMo harness with an
independent judge and a scored adversarial category, described
uncertainty modes that decide abstention, presented YMYL decay immunity
as a default, said the sanitizer runs at four stages, and said the
history test walks the whole source; corrected 2026-09-30. At
fdf736fc…, which is upstream HEAD, the judge-separation, abstention and full-context controls live inbenchmark/honest_core.py, which no runner imports, andval.py,mini_locomo.pyandrun_ws1.pyskip category 5 and default the judge to the answerer.MemoryConfig.uncertainty_modehas no reader,YMYLConfig.enableddefaults toFalseand neither server sets it,sanitize()has one call, at extraction, andtest_no_unlogged_mutation_siteparsescore/memory.pyalone. The widemem.ai report also placed deduplication before resolution, listed a Claude Code skill that lives in another repository and a console script that runs benchmarks only, and said a default install persists FAISS under~/.widemem/. Each overstated the system; no mark moved. - The LangMem report said a background extraction could
restate what the agent deleted through its tool, listed
graph_rag.pyas a Graph/RAG extra, cited paths under alangmem/prefix, and itsscope_enforcedrecord said tests cover namespace substitution; corrected 2026-09-30. At9d033b47…, which is upstream HEAD,MemoryStoreManager.ainvokereadsitem.value["kind"], which tool-written items lack (extraction.py:1066), so the LangMem report's two writers sharing items raiseKeyError.graph_rag.pyis comments only. Paths aresrc/langmem/…from the repository root. No test names the template, and the docstring harness asserts only that examples do not raise, which overstated the coverage. The report also missed that the manager's default query is the last message alone, that remote reflection forwards onlythread_idand anamespacekey that no imported module reads, and that PostgresStore's prefix predicate was unanchored before 30 July 2026. No mark moved. - The DiffMem report said git's subcommand allowlist held six
read-only subcommands, that its basename check kept path-prefixed
binaries out, that every segment of a chain is validated, that
baseline.pywas a comparison path, and that no licence grant exists; corrected 2026-09-30. At48ecbb61…, which is upstream HEAD,WHITELISTED_GIT_SUBCOMMANDSholds seven, includinggrep, whose-Oruns a named program, and--output=onlog,diffandshowwrites a file.Path(tokens[0]).nameadmits a binary with an allowlisted name from any directory, and the splitters never break on a single&or a newline, so a validatedgrepcan carry an unvalidated command; all three overstated the sandbox. The DiffMem report also missedPOST /memory/{user_id}/run-command, which exposes the router over HTTP with authentication off by default, and the writer's uncontained entity paths.baseline.pyis the deterministic context every call loads and the agent's fallback. Thenegative_evalrecord cited a commitment parser with no production caller; the mark stands on the open-item case. The report said history is not consulted by default, where the retrieval prompt requires a diff or log in every plan, which understated the system. MIT is declared by a README badge andpyproject.toml, where the report said all rights were reserved. No mark moved. - The M-flow report credited three deterministic gates,
version diffs, active-version reconciliation, usage statistics and a
sensitivity screen that no file imports, put writes behind a worker
queue, and cited a procedural eval as a negative assertion; corrected
2026-09-30. At
0d585cda…, which is upstream HEAD, and at the first pinda2766c5…, the M-flow report's headline was that the procedural trigger, conflict detector and worth-storing screen each put a zero-cost check before a model call. Their packages, withgenerate_version_diff,reconcile_active,update_usage_statsandsafety/sensitivity.py, have no importer, and the live write path sends every summary to a model router, so the report overstated the system. The Modal write queue runs only withMFLOW_DISTRIBUTED=trueon the Neo4j and pgvector adapters, and the caller, not an orchestrator, names the recall mode. The report said no validity time sat beside record time; every node carries an event-time interval, which understated it, thoughbitemporalstays withheld. The procedural eval ingests no fixture and no workflow runs it, sonegative_evalrests on the permission and multi-tenancy tests alone. - The CORE report said
invalidatedBynames the statement that ended one, called its graph store three swappable providers behind an enum defaulting toln, said twelve read paths ingraphModels/filterinvalidAt IS NULL, and split the aspects six and six; corrected 2026-09-30. At4a5b18d8…, which is upstream HEAD, the only caller passes the new episode's UUID asinvalidatedBy(graph-resolution.logic.ts:261), so the statement-to-statement pointer the CORE report offered as its most reusable component does not exist.GRAPH_PROVIDERdefaults toneo4j, and the factory throws forfalkordbandhelix, which overstated the system.graphModels/holds oneinvalidAt IS NULLfilter, and the V1 search coercesincludeInvalidatedto true, so it never applies its own.Taskis in both aspect lists, and the tree holds 38 connector packages, not forty-plus. The report also missed a third route to BM25,POST /api/v1/search, said a caller can pass an as-ofvalidAtwhere none does, and missed that the end stamp has no guard and can be overwritten. - The Open Brain report said memory search had no identity
filter and used full text, that the one memory update stamped
attribution, that nothing incremented assertion feedback counters, and
that staged imports fed the memory table; corrected 2026-09-30.
At
02a7e65a…, which is upstream HEAD, MCP and REST store and search throughsrc/db/attribution.py, whose search takes an optionalcaptured_byfilter, and the text fallback isILIKE; the Open Brain report cited the olderqueries.pycopies.attribution.py:192regenerates embeddings.save_context_feedbackincrementsuseful_countandharmful_count, which understated the system. Staged imports stay inimport_record, and the maintenance orchestrator generates no lifecycle proposals, which overstated it. The report also missed that context packets are empty in any deployment built from the code, so three of its four adapters never recall what they remember. No mark moved. - The memv report called it Apache-licensed, drew an unused
SQL query as its as-of read path, said an inverted interval cannot be
stored, withheld
negative_evalover committed must-not-return cases, and said no benchmark result is committed; corrected 2026-09-30. At21891376…, which is upstream HEAD, and at the first pinfd314bac…,LICENSEis MIT. The memv report drewWHERE valid_at … AND expired_at IS NULLfeeding retrieval and credited it with filtering validity before ranking;get_valid_athas no caller outsidetests/, and the retriever filters in Python after fusion, so an as-of query can return fewer thantop_k, which overstated the system.check_temporal_rangeguards onlyKnowledgeInput, the injection model.tests/test_retriever.pyandtests/test_memory_e2e.pyassert that another user's statement, an expired one and an out-of-interval one are not retrieved, which understated it by one mark.notes/PLAN.mdcarries a 30-question LongMemEval baseline at 36.7%. The report also said the cold-start prompt reads the narrative, which it does not, and calledextraction.py200-odd lines; it is 151. - The KektorDB report put eight dependency files inside the
screening cooldown, gave its version as 0.6.1, said setup covered
OpenCode and Hermes and installed
skills/kektordb, and cited a vacuous case in itsnegative_evalrecord; corrected 2026-09-30. Ataddc5f0c…, which is upstream HEAD, the KektorDB report's screen line countedgo.mod,go.sumand the Rust lockfile among eight files changed within seven days of the pin. The full history dates seven of the eight between 27 November 2025 and 5 August 2026; onlynative/compute/Cargo.toml, changed on 10 September 2026, was inside, so the screen overstated the risk. HEAD is three commits past the v0.6.2 tag, although the CHANGELOG and version string read 0.6.1.kektordb setupwrites MCP configuration for six clients, and Hermes receivesinternal/setup/plugins/hermes/SKILL.md, a different file. Thenegative_evalrecord also citedTestListReflectionsHistoricalExcluded, which seeds only a historical reflection and passes on an empty result; the mark stands on two populated engine-search cases. It also missed that the dashboard's status filter and the core-fact detector's grouped filter hit the same OR-before-AND parser limit asrecall_memory. No mark moved. - The Token Savior report credited
audit_logto a feedback ledger, withheldnegative_evalover committed must-not-return cases, said its bandit decides injection and learns from that ledger, and placed tsbench in a public repository; corrected 2026-09-30. At73e9c7f5…, which is upstream HEAD, the Token Savior report awardedaudit_logonledger_events, which records injections, misses and blocks rather than mutations, and its evidence record cited a diff-summary closure and a budget-diagnostic JSONL reader; that overstated the system. It described a LinUCB bandit that decides which memory to inject, trained onacted_on,ignoredandwas_visible. The bandit ranks only thememory_indextool, its reward is a constant 1.0 on amemory_getwithin 30 minutes, and four of the ledger's five outcome columns have no writer, which overstated it again. It said the suite had no negative eval;tests/test_vector_distance_floor.pyand a session-rollup scope case assert exclusion over populated fixtures beside positive controls, which understated it. It placed tsbench atMibayy/tsbench; the README at that pin says the harness is not public, and that URL returns 404. It also missed that every prompt-time hook scopes to the project with the most observations. - The claude-code-memory-setup report called chat import
manual, counted 66 keyword-map entries, said the link guard never
re-wraps an existing link, and said
/savepushes the hook's log; corrected 2026-09-30. Ata89c275e…, and at the first pinc5f2e0b5…, the wrapper runsclaude-extract --alland then the importer with--move, and the README schedules both for 22:00 daily with a crontab line. The claude-code-memory-setup report said a person exports and runs the importer and that nothing ran in the background. The extractor names each file by session, so every nightly run re-imports each Claude Code chat onto the same path and overwrites edits made in Obsidian.KEYWORD_TAG_MAPhas 63 entries. The(?<!\[\[)and(?!\]\])guard tests adjacency, so a shorter name inside a longer inserted link is nested. The frontmatter table omittedsource,processed,statusandtype, and the guide never makes the vault a git repository for/saveto push. The direction is an understated risk; no mark moved. - The obsidian-mind report withheld
scope_enforcedin its prose while its frontmatter awarded it, said its notes had no confidence and no supersession, and overstated itsnegative_evalandaudit_logrecords; corrected 2026-09-30. Ataf615d10…, which is upstream HEAD, the obsidian-mind report's section 6 called the exposure policy a path rule and said thescope_enforcedmark was not earned, contradicting the mark its frontmatter, verdict and card carried onisVisibleTo. Section 5 said there was no confidence and no supersession; cross-repo captures carry a caller-setconfidenceand asuperseded_bylist thatrecalluses to sink or withhold a retired capture, which understated the system. Thenegative_evalrecord said each of three scope cases carries its positive half, andmemory-recall.test.ts:222calls the predicate with no retrieval result. Theaudit_logrecord said the log covers refusals; the near-duplicate andrecord_workfolder refusals write no line, the file rotates at 5 MB keeping one generation, and the frontmatter edit supersession makes is not named. Both records overstated the system, and thereasontool, whose spawned session can read every project's captures under a prompt-only boundary, went undescribed. - The unreported-repositories bullet said
neomjs/neohad "a documented 'Memory Core' with no implementation to review"; corrected 2026-09-30. Atbcde8e5b…, a neo commit dated 27 July 2026, when the bullet was first written, the tree held 223 paths containingmemory-core, among themai/services/memory-core/MemoryService.mjsand the MCP server underai/mcp/server/memory-core/. The implementation moved toneomjs/neo-agent-brain, created on 23 August 2026, and neo commitc623b2f6…removed 257memory-corefiles on 26 August 2026. So the first version of the bullet was false when written, and the re-check at178d25a3…was true only of a tree the code had already left.neomjs/neois removed from that bullet, and the Memory Core now has a report. The search that would have caught it isgit ls-tree -r --name-onlyat the first pin, piped togrep -c memory-core. - The GitLord report awarded
negative_evalfor a test over context assembly, credited the wrong class with rebuilding its index, and called an MCP client a server; corrected 2026-09-30. At8bfe0aa3…the GitLord report carriednegative_evalontest_summary_turns_excluded, which keeps a summarized turn out of an assembled message list; a turn is an event that cannot turn out to be false, so by the scope test that withdrew the same shape of mark from OpenHands SDK the mark was one too many. It namedDedupIndex.rebuild_from_logas the rebuild of the retrieval index; the assembler never reads itsDedupIndex, and the indexes rebuilt from the log areIndexBuilder's JSON and Chroma indexes. It describedmcp.pyas an MCP server exposing GitLord;MCPMonis a client that supervises external tool servers. It read_commit_turn'srebuild(old_parent)as the basis of forking; it is a compare-and-swap retry, and forking isrewind. It said no entry point could produce a summary turn;append_summary_turnis documented public API of a library whose other writes also come from the embedding application. It counted fifteen test files; there are 13 plus two MCP fixtures. The mark and the MCP and forking descriptions overstated the system; the summary claim understated what a caller can reach. - The HoloAgent exclusion said its code was not yet released
and that
agentic_robot/held the earlier FSR-VLN stack; corrected 2026-09-30. Atef14d315…, a commit titled "feat: release Holoagent-0 code", the README line the exclusion quoted is a News entry dated[2026.06], and line 29 checks off HoloAgent-0 code update. The parent,e824d32f…, has noagentic_robot/directory and leaves that line unchecked; the release commit created it, adding the AgentOS skills and the OVO mapper that replaces HOV-SG. The exclusion stands on another ground: the scene graph the robot queries is built offline into a timestamped snapshot that the navigation node loads read-only from a hand-set path. The chatbot'stask_memoryYAML is written per session and read back only to rewrite its own index (agentic_robot/chatbot/g1/g1chat_demo_multirobot_dag.py:352-364). The published reason was wrong; the outcome is unchanged. - The Pydantic AI Harness report counted three bundled stores,
said
_recoverrolls back and CAS exhaustion raisesMemoryConflictError, cited anegative_evalcase that cannot fail on isolation, and restedscope_enforcedon a Postgres predicate no test exercises; corrected 2026-09-29. At58400a1d…, whose memory package and tests are tree-identical to the new pin, the Pydantic AI Harness matrix named threeMemoryStoreimplementations;SqliteMemoryStoreis a fourth.FileStore._recoverrolls an interrupted operation forward or refuses, never back, and sixteen CAS conflicts end inModelRetry. Thenegative_evalrecord cited'secret'absent from analicesearch, which the scan budget guarantees whatever the scope filter does; the mark stands on superseded-line, stale-fact and store-level cross-tenant cases. The Postgres tests use a fake that applies the prefix itself, so the predicate the scope record named was untested; the mark stands on the SQLite predicate, which a real-database test holds. Two docs anchors were four lines off. Each overstated the evidence or misdescribed the code; no mark moved. - The Slowave report's section 9 awarded
human_reviewafter the mark was withdrawn, itstrust_staterecord cited a ranking test and miscountedneeds_review, its census overcounted authors and tables, itsnegative_evalrecord said every must-not case was paired, and it calledraw_eventsappend-only; corrected 2026-09-28. At8d538b37…the Slowave report's section 9 read "Human review — awarded" while its frontmatter, verdict and card carried three marks without it, so the body overstated the system. Thetrust_staterecord citedtests/unit/test_retrieval_matching.py, which tests rank fusion and names no status, and saidneeds_reviewappears eleven times outside the tests; it appears 62 times in 14 Python and SQL files underslowave/, and none of them writes the status. The census gave two contributors, 28 tables and a 623-lineschema.sql; the history shows one author committing under three names, and the schema held 27 tables in 606 lines. Thenegative_evalrecord said each must-not case is paired with a must-return case;hard_negativeandknown_absentassert an expected-empty result, which passes on an empty retrieval by design. The report calledraw_eventsappend-only in its summary, diagram, matrix and audit reasoning; a repeatedcommitrewrites a session'stask_completeevent (ops.py:1003at that pin), and the procedure delete strips the procedure from it and scrubs its id from other raw events' metadata (dashboard/app.py:1938), so the report overstated the log. - The Skales report said its scanner does not deduplicate,
that a user changes memory only on the memory page, and that the page
can show provenance; corrected 2026-09-28. At
ce47854a…, and at every earlier pin, whose memory files are byte-identical, the Skales report said the same sentiment in two conversations becomes two memories.isDuplicatedrops a candidate at a Jaccard token overlap of 0.55 against stored and same-scan memories, andnotandnoare stop words, so a reversal with a long object is discarded. It said everything the user can do to memory happens on the memory page;extractMemoriesFromInteractionruns after every chat turn, stores an episodic record of it, and adds long-term memories and known facts from phrases such as "remember that". It saidsource_conversation_idlets the page explain a memory; no code reads the field. One mechanism was under-credited, one writer missed and one field over-credited. - The Huiran-cerebro report credited
trust_stateto a status no shipped entry point writes and keyword search does not read; corrected 2026-09-28. At08644a7e…the Huiran-cerebro report awardedtrust_stateonstatus='merged', saying the recall, listing, summary and relation paths each filtered onstatus='active', so a merged fragment was withheld from every search. The six filtered reads it cited were the listing, the conflict and lifecycle scans, the dedup's own scan and the vector indexer.search_memory, behind the MCPrecallandsearchtools, applies no status predicate (cyber_brain.py:653-674at that pin). The only caller ofdedupe_fragments,lifecycle --dedupe, passesdry_run=True(:1650-1656), so nothing reachable writesmerged. The direction is an over-credited mark. The report also counted two smoke scripts where the tree held three, and placednamespaceon entities, which declare no such column. - The Nova AI report called its confirmation gate spoken, said
every audit entry reached
logs/concepts.jsonland thatweerlegrecorded a reason, called the gate the only path to a stored relation, and kept criticisms the project had closed; corrected 2026-09-28. Atda6b9161…the Nova AI report described a spoken yes/no; input is a terminalinput(). Only concept creation and hard deletes are mirrored to the JSONL log, noweerleghandler passesreason, and_auto_extract_is_aand the Wikipedia teacher appendunverifiededges without asking and without an audit entry. Section 5 said no status field existed while the frontmatter awardedtrust_state; section 7 saidadd_relationhardcoded its source, which a parameter had replaced on 13 August 2026; section 11 called the save non-atomic and the store without a removal path. The test census was the 15 August one, 27 files, where the pin held 44 files and 625 test functions. The report also missed two paths around the refusal:upgrade_unknown_senseruns before the rejected check inTeachEngine.teach, and awikirefresh resets a confirmed sense and replaces its relations, rejected edges included. Its 2026-09-16 History entry said the branch had been rewritten;5d989252…is an ancestor of4ad85507…, and the one rewrite came after 18 September. The errors ran both ways — the gate and the log were overstated, the save and the removal path understated — and every mark stands. - The CLIO report put the 0.3x tier penalty on the injection
path, described a 12,000-character ranked dump the code had replaced,
cited a deleted test, and withheld
negative_eval; corrected 2026-09-28. At1d9acc7d…the CLIO report saidscore_entry's0.3weight made unverified entries compete badly for injection, thatrender_budgeted_sectionput every entry into the system prompt under a 12,000-character budget atPromptManager.pm:1566, and that consolidation ran from the prompt builder.5193abc6…had replaced that path on 10 September 2026:ContextBuilder::score_ltmselects at most five entries per request by keyword overlap, with no tier term, andscore_entry's one caller orders eviction under the hard caps. The same commit deletedtest_ltm_autocapture.pl.disabled, which the report described as present, and a system-prompt sentence the report quoted was removed on 12 September 2026. Those overstated the tier's reach. Withholdingnegative_evalunderstated the system: three committed relevance tests assert that an unrelated memory is not selected from a populated store beside a control that is. The report's size figures also came from an earlier pin. The project's owndocs/MEMORY.mddescribes the penalty the same way; a search for callers ofscore_entry(would have caught it. - The Scope Recall report cited a release-gate fixture its
pinned tree did not hold, misdescribed its suppression test, and its
homepage card described the 2.x provider; corrected 2026-09-28.
At
abe54277…the Scope Recall report and its verdict saidtests/eval/public_fixture.jsonlholds two rows flagged"simulation": true. The sentence is the README's;c718f6a6…deleted the file on 16 September 2026, and the pinned tree has no such path. The report saidtests/contract/test_v11_deletion.py:83exercises the other branch of theorbeside_inherits_suppression; the cited-source rule is a separate function,link_source, and the test's restatement satisfies both, so it isolates neither. The card said the model can promote its own candidates, against the report'shuman_reviewmark from 2026-09-19. The first two overstated what the tree carried and what the test reached; the third named a risk the code had closed. A star count cited in the report and verdict is removed. - The Reasonix report said
SubjectKeydisplaces an older answer, cited a benchmark task that cannot pass as its negative assertion, and kept a homepage card describing a design the 1.x line had replaced; corrected 2026-09-28. At86d2424c…the Reasonix report said a new fact claiming a heldSubjectKeydisplaces the old one.validateSubjectKeyrefuses that save and names the holder's id to update, at that pin and at both earlier ones, so the report misdescribed the mechanism and understated its guard. It quotedmb-contradictionas the assertion behindnegative_eval; that verification forbidsnpm installwhile requiringpnpm install, which contains it, so the task cannot pass, and the report overstated the benchmark. The mark stands on four satisfiable must-not pairs. The homepage card still described prompt folding at boot and a disregard instruction after the 2026-09-15 reading found the session-context snapshot. Piping the required answer through the forbidden pattern once would have caught the second. - The Hivemind report overstated its session boundary, and its
verdict kept a CI claim the report had dropped; corrected
2026-09-28. At
1c932540…the Hivemind report saidmemory_queryreads the caller's session withscope = ? AND session_id = ?, so a client could read any session it could name.Store.QueryandListMemoriesadd the session predicate only for a non-empty id (internal/store/memory.go:255-258and:149-152at that pin) and no handler rejects an empty one, so a client naming no session read every session's entries. The direction is an overstated boundary. Separately, the verdict's maturity line said the project had no CI from the first reading on, while the report's 2026-09-20 audit had found a four-platform matrix running the suite on every pull request. - The CSM report said search returns superseded and archived
memories, counted 26 AgentBook event types and seven of nine
self-referential Recent Work entries, and called
memory_eventsa record of every mutation; corrected 2026-09-28. At9c7cfb22…the CSM report's headline risk was thatbuildWhereClausefilters on neithersuperseded_bynorarchived_at.09e42f98…, closing issue #99 on 17 September 2026, added both predicates to that builder, the two fallbacks, list, cascade and graph recall with a populated test; the re-pin to that commit on 2026-09-18 carried the criticism forward, which understated the system. The gap that remains is the lesson-trigger cache.AgentBookEventTypedeclares 25 values at all three pins, and the committed Recent Work list has ten entries, eight from CSM's own tools; both miscounts date from the first reading.memory_eventsrecords creation, deletion and retention cleanup only, which overstated the audit trail. The open question aboutCSM_LIVING_MIND_URLwas answerable from CSM's own first commit, which names the Living Mind Cortex and its port. - The OmniIntelligence report called its framework three
private repositories and
omnibase-corea git-rev pin, cited a node inventory deleted before its pin, and missed a seeding writer; corrected 2026-09-28. At274f097f…the OmniIntelligence report saidomnibase-core,omnibase-infraandomnimarketwere not publicly readable and thatpyproject.tomlpinnedomnibase-coreto an unreleased commit. That override was removed on 20 August 2026; at the pinuv.lockresolved all four framework packages from PyPI releases uploaded on 18 September 2026, each with source. The repositories were public too: the Wayback Machine holds public GitHub pages foromnibase_coreandomnibase_infrafrom 3 April 2026 and anomnimarketfile from 26 July 2026, and all five OmniNode repositories the pin depends on carry public forks from between November 2025 and April 2026, still attached, which GitHub splits off when a public repository is made private. The claim overstated the adoption cost and left unread the enum ordering the headline finding rests on; read, it holds. The git-rev claim was true at the first reading's pin,8c67665a…; the privacy claim was wrong at every reading. The report also citeddocs/reference/NODE_INVENTORY.md, deleted on 2 September 2026 and kept in the project's public knowledge base, and said status moves only throughapply_transition, missing an operator script that inserts rows bornvalidatedandmeasured, which overstated the ladder. - The spatial-memory round said EmbodiedLGR carries no repository; corrected 2026-09-28. The spatial-memory bullet written on 2026-09-05 listed arXiv:2604.18271 EmbodiedLGR among the papers that "carry no URL of their own at all", as a paper with no repository to pin. The paper links none, in its abstract page or its v2 text, but its first author, Paolo Riva, published the code at paolorv/lgr-agent on 19 November 2025, five months before the paper's first version, under a README whose title is the paper's title; it now has a report. The recorded search read only the paper's own text. A GitHub search on the exact title, or a look at the first author's repositories, would have found it.
- The spatial-memory round said FARM links no code; corrected
2026-09-28. The round's bullet recorded arXiv:2606.15476 as linking
a project page and no code. The paper's text does carry only the project
page,
goldengait.github.io/farm/, and no repository URL. The page links GoldenGait/FARM-Project, whose only commit,2fcaf860…"FARM: initial public release", was committed on 28 July 2026, before the 5 September 2026 examination. The search ranrg -oover the paper's extracted text and stopped at the paper; one more hop — fetching the project page and grepping it forgithub.com— would have found the code. The system now has a FARM report. - The Agent Memory Distillation bullet said the method had no
released implementation; corrected 2026-09-28. The code was
public before the 2026-08-15 examination:
taeilkim2465/agentic_memory_distillationwas created on 18 June 2026, and every file except the README is unchanged from that day to2895d10c…, dated 10 August 2026. The paper's PDF prints no repository URL; it prints the project page, agent-memory-distillation.github.io, whose only GitHub link is that repository. A search of the paper text forgithub.comreturns nothing, so it could not have caught this. Opening every URL the paper prints would have, and so would a GitHub search for the arXiv id, which the repository's README cites. The system now has a report. - The spatial-memory round recorded eMEM's repository as
missing; corrected 2026-09-28. The round's bullet said
automatikarobotics/emem, the repository arXiv:2606.03374 names in its code footnote, answeredHTTP/2 404on 5 September 2026. That URL does 404, in both versions of the paper, because the organisation's handle has a hyphen: the code was public at automatika-robotics/emem, created 7 March 2026 with a first commit reading "Initial public commit", and published to PyPI asememfrom 13 April 2026 with that repository as itsRepositorylink. The paper's URL was taken as the repository's address rather than a pointer to it; one PyPI lookup of the package name, or a GitHub repository search foremem, would have found it. The system now has an eMEM report. - The aimee report put a poison gate on memory writes, gave
the lifecycle flag pair a reader, called fact promotion implicit with no
approve verb, and called the refusal table's privilege check a startup
refusal; corrected 2026-09-28. At
bedabac6…the aimee report placedintegrity_ingress_decideat eight sites across five boundaries, memory among them, quoting a comment the tree did not hold; there were six sites over four boundaries. It saidmemory_lifecycle_enabledand_hide_archivedgatememory_list; neither accessor had a caller. Both overstated the system. It said no queue is presented to a person, while/v1/console/typed_facts/assertionoffered approve, reject and undo, which understated it. And it calledscripts/memory-governance-pg-test.sqla shipped check refusing to start when the runtime can erase refusals; it is a CI gate run asaimee_kb_runtime, and the schema grantedDELETEon that table toaimee_store_runtime, the Go store's role. - The SelMem report cited a latent-trace walker as a latent
skip, called
corefrozen, described both binaries' model client as speak-only, and miscountedMemoryTrace's fields; corrected 2026-09-28. Ata4ace34a…the SelMem report listedencode/identity.rs:71among four read paths that skipLatent; that line is the loop inpaint_latentthat selects only latent traces, so the claim inverted the code. It saidcoreis frozen at encode, whilemerge_closeappended up to four words of an absorbed core to the survivor's. It said the model is reached only through a speak-only client;selmemdandselmem-chatattachedHttpNarrator, which also reconstructs, rewrites and distils axioms through the model, so the report understated the model's reach. It counted twenty-two fields onMemoryTrace, which has twenty-four. - The ThoughtDAG report kept "Human review — awarded"
in its section 9 and three marks in the families page after
human_reviewwas withdrawn, and undercounted its CLI tests; corrected 2026-09-26. Atf05fc44d…the ThoughtDAG report's frontmatter carriedaudit_logandnegative_eval, while section 9 kept the withdrawn mark's paragraph and the families page listed three marks, one of them "the canvas as review surface"; both overstated the system against the report's own record. The report counted 54 CLI tests in seven files by matchingtest(andit(, which misses the seven DeepSeek Harness cases declared through atalias, so the figure at that pin was 61, an understatement. - The Soul of Waifu report said nothing deletes its memory,
that a declined batch skips every write and that moving the diary guard
would close the redirect, and treated its per-chat lock as working;
corrected 2026-09-26. At
747048b3…the Soul of Waifu report said there is no delete path of any kind; its recorded grep coveredsoul_memory.pyonly.SoulMemoryViewer, in the app since 25 July 2026 and so present at both pins, edits the index, profile, topics and diaries and deletes topic and diary files, which understated the system;human_reviewstays withheld because the viewer edits after the write lands. It saidno_significant_changeskips every write; the diary agent runs on the declined batch. It offered moving the guards below the redirect as the fix; the guard tests lowercasediary_and the redirect returnsDiary_<date>.md. It said the audit log distinguishes parse failures, that diaries are injected whole, and that the day's diary competes as a passage about the current delta; parse failures reach only the application logger, the read path takes a diary's last 2,500 characters, and the write path embeds a diary's opening 600. Its per-chatasyncio.Locklives on an agent built per call, so runs for one chat can overlap. - The XERJ report awarded
scope_enforcedto a reserved index per namespace behind an authorizer, miscounted its MCP tools and misfiled a positive control; corrected 2026-09-26. Atf54eead8…the XERJ report creditedscope_enforcedto the authorization check above the per-namespace index, reading the expansion of a wildcard read over the credential's visible indices as a read predicate. A memory document carries no namespace field; the namespace is the index name, and the check decides which partitions a credential may open. That is a partition with an authorizer, not the mark, so the report over-credited the system and the mark is withdrawn. The report said the MCP server exposed eleven tools; it registered ten at that pin. It placedcat_indices_keeps_the_rows_it_shouldinbrain_is_a_security_boundary.rs; it is inscoped_keys_get_intact_responses.rs. It did not say that a memory write's audit entry names_memoryrather than the namespace. Two of its recorded greps used?without-Eand searched for literal text; re-run with-Eat both pins, they return nothing. - The ReMe report cited benchmark files and figures deleted
before its pin, said a malformed integration receipt fails, withheld
negative_evalover two committed cases, and called its default search FAISS-backed; corrected 2026-09-26. At9ad3dafc…the ReMe report quotedbenchmark/result-longmemeval.mdandresult-beam.md, a 26.7% preference score and a 0.100 prompted contradiction score; both files were deleted on 5 August 2026, and the tables at that pin read 0.633, 0.438 and 0.391 with no prompted configuration. The benchmarks page repeated the BEAM figure. The report said a failed integration lands infailed_units; since 11 August 2026 a malformed receipt with one changed digest file is accepted, which over-credited the verb. It withheldnegative_evalwhiletest_keyword_only_upsert_removes_old_chunks_and_docsandtest_zvec_delete_removes_vectorsassert an edited or deleted note is not returned beside a positive control, which under-credited the system. It also called the default store FAISS-indexed (the shipped config is BM25 only), auto-dream corpus-scaled (it reads two days of changed notes), and skills rather than MCP the integration surface; those three held at the first pin,550317c3…. The searches that would have caught the first two:git ls-tree -r --name-only <pin> benchmarkandgrep -n _record_recovered reme/steps/evolve/dream/integrate.py. - The AI Agent Automation report credited provenance fields
that record the chat model, called its similarity floor untested while a
committed case asserts its absence, and misdescribed its length guard
and its type writers; corrected 2026-09-26. At
86b6072d…the AI Agent Automation report namedembeddingProviderandembeddingModelits best idea, as the row recording which provider and model produced the vector.storeMemorycopies the agent's chat provider and chat model, theAgentschema has noembeddingModelpath, andrunEmbeddingpicks its own provider and a default model, so on the default Groq agent both fields name something that did not embed; that overstated the system from the first reading. It said the unreadminScorewas untested; the populated case atmemoryService.handler.test.js:132-159passes 0.45 and expects a row scoring 0 back. It said the length guard wastes an embedding; every caller passes a JSON envelope of at least 26 characters, so the guard never fires. It said the schema default is the only writer ofconversation; all three writers set it. It cited an empty-mock case as thenegative_evalcontrol, and carried "twenty files, none covering memory" and v0.11.0 into a pin with 42 test files, one on memory, at v0.12.0. - The Project N.E.K.O. report put an LLM rerank after its
recall hard filter, called its ban-topic list prompt-only and its event
log a journal of every mutation, and carried the first reading's census;
corrected 2026-09-26. At
b51d4532…the Project N.E.K.O. report drew recall as BM25 and cosine, RRF, a hard filter, then an LLM rerank. Therecall_memorypath runs the hard filter before both rankers and has no model stage; the LLM rerank belongs to the pool that feeds Stage-2 signal detection. The report said the ban-topic list works only by asking the model; since 1 September 2026 a proactive draft naming an active term is dropped before delivery, which understated the system, while the families page and the retrieval-hysteresis pattern said the list withholds a term from recall, which overstated it. Theaudit_logrecord said every view mutation is journaled and nothing rewrites the log: writes tofacts.jsonemit no event, ten of the fifteen declared event types have no emitter, and an uncalled compaction helper would rewrite the file. The mark holds. The report also put evidence counters on facts, which carry none, called the QQ plugin the one place the model may recall when the main loop registers its ownrecall_memory, asked for two directive tests that were committed, and kept the 29 July figures of 24,000 lines and 7,936 tests. - The Qwen MM Plugins report called
omni-memory's supersession wired at both ends, withheldnegative_evalover a committed case, and called the embedding-width check a startup error; corrected 2026-09-26. Atad8139d5…the Qwen MM Plugins report said_resolvestamps the losing triple superseded and four reads exclude it. The stamp lands on adict(lose)copy that only a log count reads,set_semanticdrops superseded rows before writing, and a contradiction that wins under a different key leaves the old row active, so the filters exclude nothing; that over-credited the system. It said nothing tests the hybrid search; four cases do, andtest_search_filters_by_node_typeasserts event and on-screen-text nodes absent beside a present entity over a populated index, so the mark was withheld in error.load_toolkitcatches the width check and falls back to BM25 with a log warning. It also described a JSONL checkpoint (a JSON array), two build phases (three), seven dataclasses (eleven), an unboundedenumerate_events(capped at 300), 256-text embedding batches (10), a possibly local embedding backend (DashScope only), anomni-avcapability merged intoapibefore that pin, and 21 test files where there were 39. Thevideo-memoryerrors held at the first pin,f4e02952…. The searches that would have caught the first two:grep -rn superseded src/capabilities/omni-memoryandgrep -n 'def test_search' tests/test_build_memory.py. - The Portable Handoff report said a capsule cannot declare
itself verified, that the budget's losses are recorded inside the
capsule and that
loadrenders the whole capsule; corrected 2026-09-26. Atec5f203b…the Portable Handoff report saidcap_trustmeans a stranger's capsule cannot declare itself verified and that model-authored records claiminggitare rewritten totest. The cap refusesverifiedonly beside a conversational or inferred provenance, which the draft author also writes, so a claim declaredtoolandverifiedpasses; file and evidence records are not capped, and thegitrewrite covers verification records only. That overstated the system. It saiddropped[]is part of the document;finalizeprints it and the capsule does not keep it. It saidloadrenders the whole capsule; the briefing is a fixed subset. It creditedtest_export_emits_one_half_not_bothwith pinning the export, which it does not assert, and said the README leaves the shell-less trust consequence unstated, which the README states. Each held at the first pin too,4c9b7f73…. - The OpenLore report called every session read confined to
the granted docsets, and missed that the
historycommand skips the nested-docset carve-out; corrected 2026-09-26. Atdbd44007…the OpenLore report creditedscope_enforcedto "every session read" and said history queries were scope-filtered throughhistoryReadable. That function is a plain prefix test over the granted docset roots, with/covering everything, andhistoryis a read-class command every session holds. An identity granted the root docset lists the paths, principals, actions and content hashes of changes inside nested docsets it cannot read. That overstated the boundary; the mark holds on the filesystem wrap, with the limit stated. The report also said nothing outsidepkg/okfreads OKFstatus;lore metapasses every frontmatter field through to its output, and no read filters on it. Both held atd1038017…. - The Rekal report withheld
scope_enforcedover an author filter on both recall paths, and misstated its timestamp column, its session mutability and its ranking weights; corrected 2026-09-26. At4550e602…the Rekal report said recall applies no scope predicate at all.rekal -a <email>applies theuser_emailevery captured and synced session row carries, as SQL in filter mode and per candidate in hybrid mode; the recorded search looked forbranchonly, so the mark was withheld in error. It saidcaptured_atholds the session start for three adapters and the ingest clock for two. The commit capture path writes the capture clock for all seven, and the adapters' start times reach only cross-repo imports, where four adapters use the import clock. It called sessions immutable; a continuing conversation gains turns at the next capture. It gave the benchmark calibration's weights as the shipped ones and omitted a fourth, facet layer that feeds confidence. Its screen putgo.modandgo.suminside the cooldown; they last changed on 16 July 2026, and the finding was a shallow-clone artifact. - The Moltis report called its session capture sanitized, said
memory had no scope beyond the indexed directory, and credited a
reranker, a batch embedder and hash-addressed citations the default path
does not use; corrected 2026-09-26. At
8f633cc3…the Moltis report took "sanitized" fromsession_export.rs, which nothing calls; the livesession-memoryhook writes the last 50 messages raw. That overstated the system. On scope it understated it: the agent's memory tools filter results to the agent's workspace path, and the default-on prefetch does not, soscope_enforcedstays withheld on that split rather than on an absent key.LlmRerankerandBatchEmbeddingProviderhave no caller,resolve_file_by_hash_prefixresolves qmd document ids rather than citations, andcrates/cron/src/store_memory.rsis a test cron store. Three model extraction turns and a checkpoint before every agent write went unreported. All of it held at the first pin,1f53cd27…. - The MenteDB report said MQL can express agent scope, that no
case asserts cross-user absence, and that a query without
AS OFkeeps rows valid now; corrected 2026-09-26. At4ba993dc…the MenteDB report saidAgentandSpaceareFieldmembers, "so the language can express it". Both parse, andfilter_matcheshas no arm for either and returnstruefor an unhandled field, soWHERE agent = <id>returns every agent's rows; that over-credited MQL. Itsscope_enforcedrecord said no committed case asserts a cross-user recall returns nothing;user_isolation.rsasserts it twice with positive controls, which under-credited the system. Its diagram said a query withoutAS OFkeeps rows valid now; the MQL executor applies no window. The mark was anchored on the entity reads and is re-anchored on the hybrid recall core thatprocess_turnandrecall_for_injectioncall. It also counted the four withheld marks as three and the four AS OF negatives as three. The searches that would have caught the first two:grep -rnE "Field::(Agent|Space)" --include="*.rs" .andls crates/mentedb/tests/. - The Linggen Memory report withheld
negative_eval, did not assessbitemporal, and missed the archive its merges write; corrected 2026-09-26. At2abbd4ff…the Linggen Memory report withheldnegative_evalon a cosine-floor test. It passed overexpire_archives_instead_of_deleting, committed on 17 August 2026, which asserts that a superseded row stays out of a populated default list. It did not assessbitemporal, althoughsinceanduntilfiltered onCOALESCE(occurred_at, created_at)besidecreated_at. Both errors ran in the withholding direction, and both marks are awarded. It said a merge left only asuperseded_bypointer and that the same fact extracted again is a new row. Merges archived semantic losers withexpired_at, and the exact-content dedup lookup matches archived rows, so a byte-identical re-add is folded into the archive. It also placeddoc/memory-spec.mdin this repository rather than the siblinglinggenone, credited the daemon with a per-account dream whose accounts route has no caller in the tree, and described an ANN index the tree never builds. - The Memex report withheld
negative_evalover committed cases, and overstated where its credential gate and archive check reach; corrected 2026-09-26. At453c0e33…the Memex report said no test asserts that material must not be retrieved and that the read path has no filter; its recorded grep coveredtests/lib/only.tests/commands/search-manifest-filter.test.tsasserts named cards absent beside named cards present under a category, tag, author and date pre-filter, over a populated fixture, so the mark was withheld in error. The report said the gate runs on the write path; it runs in thewritecommand, and three CLI writers call the store without it. It said archiving refuses when a card of that slug is already archived; the check fires only when no live card exists, and otherwise the move overwrites the earlier copy. It also said cards have no frontmatter schema, counted nineteen test files where there are 43, and counted five auto-run surfaces where the screen found six. - The MCP-Memory report withheld
audit_logfrom a change log every store writes, overstated the namespace filter behindscope_enforced, and carried the first pin's anchors and tests into the second; corrected 2026-09-26. Ata50a8770…the MCP-Memory report saidnamespacewas applied in SQL on every search, retrieve and delete, partitioned the on-disk directories, and was exercised by the tests.memory_searchtakesnamespace: Optional[str] = Noneandsearch_memoriesadds the predicate only when one is passed, so an unqualified search reads every namespace; adefaultkey containing a slash shares a mirror path with a named namespace; and no test writes to two namespaces. The mark holds on the narrower evidence of retrieve and delete, which always apply the predicate.audit_logwas withheld in error for lacking an actor, a before/after value and a reader, none of which the definition asks for, over alog.mdthat every store and delete appends to; it is added. The line anchors, file sizes and account of the tests were those of4514d1fd…, including the claim that the only negative assertion was a post-delete lookup. The scope claim over-credited the system and the audit withholding under-credited it. The search that would have caught the scope overstatement:grep -n -E 'namespace: Optional|if namespace' memory_server.py db.py. - The Lemmalog report called its escalation list unresolvable
and its differential tests uncommitted, and miscounted two other things;
corrected 2026-09-26. At
74d428a2…the Lemmalog report said nothing resolves an escalation and no operation clears one;resolve_escalation(idx)dismissed one by index at that pin, andtests/agent_test.rscalled it. It withheldhuman_reviewon that absence; the mark stays withheld because the escalating write admits both values and nothing waits on the decision. It presented the 450 differential programs as a status-table claim and asked whether they were committed;tests/differential_test.rsran them with fixed seeds. It counted twenty-seven shipped status rows (there are thirty-one), called the defaultcurrentrule the only rule in the tree readingedgewhen an example'sconflictrule readsasserted_at, and described the change feed as covering derived views only, when it records base additions and retractions and is not persisted. It also left out the README's MemEval and LoCoMo results. The searches that would have caught the first two:grep -rn 'resolve_escalation' src testsandls tests/. - The brain.md report awarded
scope_enforcedto a per-project directory, said no page read takes a path and that a belief cannot change without saying why, and credited an uncalled counter; corrected 2026-09-26. At8064f333…the brain.md report creditedscope_enforcedfrom the first reading on 2026-08-07. The boundary is one resolved directory per project, with no key on a record and no predicate on a read, which is a physical partition and not the mark; it is withdrawn.read-pageand four write subcommands pass an unvalidated id topagePath, so../reads any.mdfile andarchive-pageandset-tagscan write frontmatter into one. Theupdate-truthreason is a fixed sentence when--summaryis omitted, and the replaced text is not kept.countTimelineEntrieshas no caller..brain-md-installedis a per-bundle marker, not a manifest, and an agent, not the CLI, copies the pre-commit hook. Each error over-credited the system. - The Elastic Atlas report withheld three marks present at
every pin, cited an unused retrieval module, and described consolidation
as manual and ungated; corrected 2026-09-26. At
d84f9235…the Elastic Atlas report said supersession chains, bi-temporal validity and any end state were absent.write_memorystampssuperseded_by,superseded_atandretracted, every default read excludes superseded facts, andvalid_from/valid_tosit besidecreated_at; all of it was present at the first pin,0bd36a7b…, sobitemporalandtrust_statewere withheld in error. So wasnegative_eval, over stress scenario B5 and the eval's gated isolation sweep. The report citedretriever_builder.pyand its 1,097-line test as the retrieval path; nothing on the memory path imports it. It said consolidation runs on demand from the inspector with no gate; it runs after every turn and drops assistant-only claims in code. It said no benchmark figures were committed;docs/improvements/RELEASE-1.mdstates them. It called the project Elastic's; it is MIT-licensed under the author's personal account. Every error ran in the direction of under-crediting, and the report missed that nothing on the write path reads a retracted value. - The Compartment report called record time unfilterable and
named the relation filter wrongly; corrected 2026-09-26. At
26861970…the Compartment report saidcreatedis stored and not filterable, so the vault could say what was true in March and not what it believed in March, and listed an unqueryable record-time axis as a risk. The claim understated the system:Vault.searchfiltered records oncreatedthroughsince/until(vault.py:1183-1186), and the MCPmemory_searchtool exposed that window beside a separatediscoveredone. The test thebitemporalrecord cited sat just belowtest_the_two_date_filters_are_independent, which asserts the save-date filter. The limit that holds is on supersession, which stamps an id and no time. The report also named the relation filterfind_relations; it isStore.query_relations. The recorded search was scoped tostore.py, and the filter is invault.py:grep -n 'row\["created"\]' src/compartment/vault.py. - The AuraOS report credited a health flag that cannot be
false, and called two things absent that the tree holds; corrected
2026-09-26. At
81dffa9b…the AuraOS report recommended/health'score_loadedas a way to expose a missingcore/; it isbool()of a non-empty fallback string and always true (server/main.py:123). It said a grep found no reader of the distiller's output anywhere in the tree; the committed bytecode__pycache__/server.cpython-314.pycreads it into a global no function uses, so the conclusion that it reaches no prompt held and the absence did not. It said the README's user-carriedHISTORY.txtdesign was not implemented;indexworking.htmlimplements it, against a server committed only as that bytecode. It put.tmp.driveupload/at 98% of the file count; it is 77% (2,214 of 2,887). It also omitted the server's allow-every-origin CORS default. Three of the errors overstated an absence or a strength and one a proportion; no mark depended on any of them. - The AgentOS report missed a
negative_evalcase and a second memory stack, and misdescribed four mechanisms; corrected 2026-09-26. Atf66718d6…the AgentOS report withheldnegative_evalover a soft-delete case with a pre-delete control (MemoryStore.brainhydration.test.ts:306-343). It calledcognitiveMechanismsa workingagent()option, whichagent()reads only for a warning, and omitted theMemoryfacade thatsouledAgent()wires, whose recall carries nobrain_id. It said traces carry no status and no principal key; they carryscope,scopeIdand a three-flag trust policy. It said correction only lowers weights; conflict resolution soft-deletes the loser and writescontradictedBy. It missedvalidTobesidevalidFrom, creditedCompactionLogwith dropped content its default level discards, and dated apnpm-lock.yamlchange of 20 July 2026 to the day before the pin. The search that would have caught the mark:grep -rn "not.toContain\|toEqual(\[\])" src --include='*.test.ts'. - The Agent-MemoryForge report credited an unwired value
filter, an MCP memory surface and LangChain adapters, and cited the
owner check at the wrong sites; corrected 2026-09-26. At
770b4eef…the Agent-MemoryForge report saidconversation_value_filter.pydecides whether a conversation is worth distilling before the worker's model call, and the verdict named it the most reusable component; nothing on the gateway or worker path imports it. It saidagent_memory_mcp_server.pyexposes memory as MCP tools; it registers five skill tools and no memory tool. It named LangChain and LangGraph adapters that do not ship. It cited six_actor_can_read_privatesites as read-path evidence forscope_enforced; three guard writes, and search filters through_hit_is_visible_to_actor, which it did not name. The mark holds on the corrected sites. It also said the two vector arms can be narrowed differently (they receive identical filters), that the service refuses to start without its key (each memory route returns 500), and that the unit suite is about sixty files (it is 81). In the other direction, it missed a working-memory overwrite by task id, the distillation worker's unaudited writes, the pgvector tenant predicate, a second negative case intests/integration/, and a preference confirmation step whose queue nothing fills, which sharpens thehuman_reviewwithholding. The search that would have caught the first:grep -rn 'conversation_value_filter' --include='*.py' .. - The KITE by Memoket report called plan sorting its
contradiction mechanism, and misstated several smaller facts; corrected
2026-09-26. At
8745feda…the KITE by Memoket report said the compiled plan sorts by event time and takes the head, that this is the entire correction mechanism, and that one model call compiles the plan. The library's default compile prompt never shows thesortoperator, three candidate plans are sampled and the one returning the most rows is kept, and a keyword channel is fused beside the plan, so on the default path the reader settles contradictions under one prompt line over a date-ordered pack. The report also understated how far the benchmark configuration sits from the default, placed the premise gate on the default path, and said the suite has no skip path; two harness tests skip. The searches that would have caught it aregrep -rn '"sort"' src/memoket_kite/promptsandgrep -rn 'pytest.skip' tests. - The ZeroStack report withheld
negative_evalover committed cases present at every pin, and misdescribed its search, its backups and its writers; corrected 2026-09-26. Atefd142b3…the ZeroStack report said no negative retrieval assertion was found. From the first pin,90986c5c…,scratchpad_write_then_inject_open_items_onlyand its sibling assert that a closed scratchpad item stays out of the injected block beside a present open one; the error ran in the withholding direction. The report calledmemory_searchan unranked case-insensitive regex; its terms are escaped and its files ranked. It said a backup precedes every content-destroying mutation; note overwrites and daily or note edits take none. It said writes are only the model's tool calls; every compaction appends its summary to the daily log outside the permission gate. It counted 65 test functions where 58 are tests. It left/memoryunread, and itseditorsubcommand emptiesMEMORY.mdbefore opening it. The search that would have caught the mark:grep -n 'assert!(!' src/tests/memory_tests.rs. - The Atomic Agent report called its advanced memory layers
default-off and withheld
negative_evalover committed cases; corrected 2026-09-26. From the first pin,d69332c5…, the Atomic Agent report said phases 2–7b and the v2.5 features shipdefault: falsepending an evaluation campaign, and credited the project with that discipline.USER_CONFIG_DEFAULTShad enabled links, evolution, lessons, procedures, consolidation, voting and the query rewriter since810b96c6…on 21 May 2026; the report tookMEMORY_FABRIC_V2.md§10 at its word, which upstream corrected on 22 September 2026. In the other direction,lesson-store.test.tsasserted a deprecated lesson out of recall beside an active control, andmemory-store.test.tskept two project directories apart, at every pin read. The report also recorded no retrieval arm over an FTS5 read path, left scope "not traced" in three sections after section 2 traced it, and placed re-distillation in the same cluster, whose episodes the consolidator archives. The verdict, the families paragraph and the overview kept "derived scores" after the report corrected it on 2026-09-25. The checks that would have caught the first two: readUSER_CONFIG_DEFAULTS, not the design table, and grep the tests fornot.toContain. - The Membrane report overstated what a positive
min_salienceexcludes, and misstated several smaller facts; corrected 2026-09-26. Atb3f1f091…the Membrane report said the OpenClaw plugin's default floor of 0.3 does not return a retracted record, and drew a positive floor as excluding one. The floor reaches the root query only:getGraphRecordhydrates graph neighbours with no salience predicate, and the plugin expands one hop and injects the neighbours, so a superseded record can return beside its replacement. The search that would have caught it isgrep -n 'MinSalience' pkg/retrieval/graph.go. Separately, an absence claim was wrong: the report said no projection into the protobuf response consults the revision status;revisionStateToPBcopies it, and the recorded search missed it by matching only.Revision.Status. It also gave the semantic half-life as 1,000 times the episodic one (it is 720) and as thirty days for every semantic record (the ones capture and consolidation derive take one day), said onlyReinforceadvancesLastReinforcedAt(consolidation's reinforcement does too, and the compounding stands), called all fifteen tables children ofmemory_records(thirteen are), put the OpenClaw plugin at 380 lines (itsindex.tsis 464), and did not state that the reinforcement gain is zero on every record the tree creates. No mark moved. - The Hivemind (Activeloop) report overstated where secret
masking runs and understated what install writes before sign-in;
corrected 2026-09-26. At
26bdf69c…the Hivemind (Activeloop) report said masking runs on capture and that an account is required before anything is stored. The pi extension's capture writer calls noredactSecretsat that pin or atce30de7c…, and Cowork ingest had none until 17 September 2026. Install mines up to ten local Claude Code sessions intoSKILL.mdfiles and stages past-session summaries on disk before sign-in. Three smaller claims were imprecise: the skillsscopecolumn is selected by the pull and filtered by no query, not read by none; the resume brief keys on a cwd basename, not the git-remote hash docs search uses; the matrix counted seven tables where eight were declared. - The basemode report overstated where its supersession filter
reached, and understated three other things; corrected
2026-09-26. At
0ace1bae…the basemode report said theFILTER NOT EXISTSonops:supersededBywas spliced into "the serving queries" so only live versions come back. Both hooks that inject rules carried no filter at that pin, which the project's ownsupersede_rules_serving_test.rsmarks red there. The session-start memory block andlearn --listselectstatus "active", which the supersession writer leaves on the old note, so they serve a corrected note at both pins. In the other direction, the report said no decision path readsops:status, when the working set, recall, the memory block andlearn --listall filter on it; called scope the tier file alone, missing the working set's project predicate on a home derived fromops:path; said no committed case pins the change log, overtests/changelog_test.rs; and counted 29 tree-sitter grammars where the requirements list 27. No mark moved. The search that would have caught the first is every reader of the field the filter guards, not every caller of the filter. - The Create Context Graph report missed a writable agent tool
and misplaced its scope key; corrected 2026-09-26. At
707b168d…the create-context-graph report said the generated agent has no tool that writes memory; every framework template's free-form Cypher tool, described to the model as read-only, executes writes on a self-hosted graph. It said every seeded node carries thedomainkey; the CLI's library ingest and the generated importer write none. It overstated three pieces of evidence: a scope integration test with no positive control, a vector index called empty over a property the library writes, and three encoders called held in lockstep when the contract test covers two. It understated the predicate, which sits on nine read paths rather than four. Smaller facts were wrong: ten correction patterns not eight, fourteen redaction patterns not thirteen, 216 matrix combinations not 176, chat history insessionStoragenotlocalStorage. No mark moved. - A report called a memory write unawaited, and the
synchronous call waits on it. The Strands Agents report of 22
September 2026 said the default extraction write "does not block the
agent and is not awaited anywhere." At that pin Python's
Agent.__call__already ran_invoke_async_and_flush, which awaitsmemory_manager.flush()after every synchronous invocation and forces extraction regardless of the trigger. The same report said no documentation example implementsadd_messageswhile its own recorded grep matched the memory guide'sServerSideStore, dated the history from 14 May 2025 rather than 16 May, and published a test census that does not reproduce. It also left out that the PythonFileMemoryStorefails every search over a storage backend whosesearchdoes not take a string. Corrected 2026-09-26 at a newer pin, over unchanged code. The check that would have caught the first: grep every caller offlushbefore calling a write unawaited. - The MemPalace report withheld
negative_evalat three readings over committed cases present at each; corrected 2026-09-26. From the first pin,afd04288…,tests/test_knowledge_graph.pyasserted that an as-of query excludes an employer outside its validity window with the other employer as control,tests/test_hybrid_search.pyasserted a non-empty result holding only the in-scope source from a four-drawer palace, andtests/test_sqlite_exact_backend.pyasserted the one in-scope wing's drawer as the only lexical hit among twelve out-of-scope twins. Froma9f345cc…on,TestSupersessionBoundaryasserted that only the successor returns at a supersession instant. All are collected bytestpathsand run by the CI workflow. The error ran in the withholding direction; the fork mempalace-code carries the mark on the inherited graph pair. Two smaller claims were corrected with it: the write-ahead log records nine operations, not eight, and the file index namedpalace.py,searcher.pyandmcp_server.py, which were packages at the previous pin. Corrected in MemPalace. The search that would have caught it:grep -rn -E 'assert .*not in ' tests --include='*.py'. - The flow report understated its close-out sweep and
overstated its instrument, and misdated its dependency files; corrected
2026-09-26. At
b32b4e6a…the flow report saidflow donespawnsclaude -p, asked whether the sweep ever runs under Codex, and said the user's session is not waiting on it. The sweep dispatches through the task's harness —codex exec --dangerously-bypass-approvals-and-sandboxfor Codex,claude -p --dangerously-skip-permissionsfor Claude — andcmd.Run()blocks the in-sessionflow donecall until the model exits; the approval bypass was not mentioned at all. In the other direction, the report presentedflow statsas counting knowledge-base reads without saying the match is the literal/.flow/kb/over Claude Code transcripts only, so a relocatedFLOW_ROOTor a Codex task reports zero. It named three artifacts disagreeing about the read path; the README is a fourth, on the loaded side. And the screen's two FRESH findings ongo.modandgo.sumwere clone-date artifacts: both last changed on 23 June 2026. No mark moved. - The Gas Town report described a write path that does not run
against any current
bd. Published on 2026-09-25 withgt rememberstoring rows throughbd kv set, it was read against beadsv1.0.5, the versiongo.modnames, whilegtinstallsbd@latestat runtime. Every beads release from v1.1.0 (4 July 2026) refuses amemory.-prefixed key inkv setandkv clear, so at the 23 July pingt rememberandgt forgetexit 1. Corrected the same day in Gas Town. The check that would have caught it: when a subject execs an engine it installs as latest, read the engine at the pin's date, not at the version its manifest names. - The scope note on beads described its issues and missed its
memory. The note in the
scope section declined
gastownhall/beadsas a task database, at a pin whosecmd/bd/memory.goalready definedbd remember,bd memories,bd forgetandbd recalloverkv.memory.*rows injected bybd prime. Those rows state what is the case and can be false, so they are memory by the note's own test. Corrected on 2026-09-25: the issues stay out, and the memory plane has its own beads report beside Gas Town's. The search that would have caught it isgrep -rln 'remember' cmd/. - Eight reports kept the census of an earlier pin in some
sections and a newer one in others. Re-pins updated one
sentence and left the rest; the verdicts then copied whichever they met
first. Re-measured at each report's own pin on 2026-09-25, with each
method first reproducing the old figure at the pin it came from: Perseus Vault is about 156,000
lines of Rust with 1,340 inline tests, not 63,000 and 592; LoreKit has 106 migrations and 298 test
files, not 37 and 90; Arcon 42 commits
and 543 tests; Repowise 1,743 commits
and version 0.51.0; echo-agent 514
test files; Provem 25,506 lines under
src/; PLUR1BUS version 7.12.61 and 472 test files; kwipu 24 commits, with its dependencies pinned rather than floating. No mark moved.check_verdict_census.pynow requires every multi-digit figure in a verdict's maturity line to be one its report states; its first run found 52 that were not. - Twenty-one pattern pages carried 87 wrong claims, and six
carried the wrong stance. An audit on 2026-09-25 checked 353
claims against the reports and, for the load-bearing ones, the pinned
code. The largest group was superlatives the corpus contradicted — among
them Hermes as the only system whose memory design follows from
the prompt cache (Nuum, Reasonix, Hipocampus), Membase as the
only authenticated scope key, CSM as the only audit that
tells considered from injected (RainBox), and every other trust
state machine forcing a winner at conflict (Caura, dense-mem). The next
was pages left behind by re-reads: the trust-state machine
presented Graphify, CLIO and Daimon as working instances after all three
lost
trust_state, and the tombstone page called PLUR1BUS, memoir, Memora and Scope Recall near-misses while all four carried the mark. Code was misread in both directions: Mnemopi's Weibull decay is imported only by a test, LoongFlow's temperature falls as diversity falls, Atomic Agent's vote scores are mutated in place rather than derived from events, and LlamaIndex gives memory blocks no per-block budget. Hand-written counts had drifted on six pages and on the patterns index, which still said 38 … or 19 beside a generated table. The tombstone moved from advocacy to mixed; editing surfaces and source-diverse context to reporting; pluggable provider, skills, retrieval hysteresis and promotion between tiers to mixed; explicit write destination, narrowed to refusing a write with no named destination, to advocacy. The category-bound stance was retired. The audit and every correction are in the note. - Eighteen reports carried a defect the pattern audit
surfaced. Corrected at their unchanged pins with a History
entry each: Mnemopi (the Weibull table
as the live recall curve), LoongFlow
(the temperature direction), Redis AMS (forgetting
off by default, unstated), Context
Mode, nanobot, Helix AGI, Helm, Atomic Agent, Midas, Janus-Graph, MemOS (a promotion formula that is
MemoryOS's and exists nowhere in its tree), OpenViking (a file absent at the pin),
memoir, Memanto, Memory Engine (still recommending
the agent principal its own project removed), Hermes Agent, Empryo and qwen-code. No mark moved in those
eighteen. Three mark questions the audit raised were settled the same
day. ELAI's
bitemporalis withdrawn: no writer sets a validity bound that is not a record time, the test on which Helm and Atomic Agent were refused. llm-wiki-memory'shuman_reviewstands, because it rests on a write-gate hook that reads the user's own turn and is on by default, not on its editor. openyak had no such mark to question: its body still credited the editor withhuman_reviewa week after its History withdrew it, and that sentence is corrected. - Thirteen family paragraphs kept counting marks their reports
had moved. Re-reads between 2026-09-17 and 2026-09-20 withdrew
human_reviewfrom eight systems andtrust_statefrom Flair, and awarded atombstoneto OpenZync Core and Scope Recall,human_reviewto Auto Company andnegative_evalto yacmemo. Each report, its frontmatter and its verdict moved; the paragraph on the families page did not. Four also described what the re-read had overturned: OpenZync's called the retraction check blind, Scope Recall's described the 2.x provider the project rebuilt, teamai-cli's a merge-request path nothing in the tree creates, and Auto Company's the code before its guard. All thirteen were corrected on 2026-09-25, andcheck_family_marks.pynow compares each paragraph's count withcapabilities:. - A re-pin withdrew a mark and two pages kept counting
it. PLUR lost
human_reviewat the 2026-09-19 re-read:capabilities:, section 4 and the verdict entry were updated, while the report's executive summary still opened "Six of seven marks" above a paragraph headed "The other five" that listed four, and this overview's family paragraph still said six. Both now say five.check_verdict_marks.pyholds the verdicts page to its reports, andcheck_mark_agreement.pydeliberately counts nothing in a report body, because "N marks" there means four different things; the fraction form, "N of seven marks", is the one a count check could read without guessing, and nothing reads it in report or overview prose. - A report said a repository had no tests, and 395 test files
were sitting in it. AgentSwarms's section 10 opened
"There are none. No test file matching
*.test.tsor*.spec.tsexists anywhere in the repository, for the memory subsystem or for anything else." At the commit that claim was published against,tests/held 395 files acrossunit,integration,differentialandjourney. The tell was in the report's own structure: its Recorded Searches appendix carries a command and a result for every other absence it asserts —usage_counthas no writer,scoreis a constant,expires_athas no sweeper — and none for this one. An absence nobody enumerated is an assumption wearing a finding's clothes, and this atlas's appendix convention exists precisely to stop that. Corrected 2026-09-19 on a re-read at the next pin: section 10 rewritten, three searches added to the appendix, and thescope_enforcedevidence strengthened withtests/unit/rlsPolicies.test.ts— which replays the migration history rather than grepping it, after its own first version reported two tables as world-readable that had been dropped and replaced, and whose lesson applies directly to this atlas: "Reading a migration directory is reading a HISTORY; only the replayed end state means anything." The re-read also found what that suite does not do: the memory table is protected only by two exhaustive assertions and is absent from the list of tables whose row-level security is explicitly required, so RLS could be dropped from it with every assertion still passing. - The same error, three readings deep, in a report with no
appendix at all. Munder
Difflin was read four times between 2026-08-17 and 2026-09-15. Every
reading but the last stated that the repository contains no tests — in
the executive summary, in the risks field, in section 9 as the
counterweight to its condensation gate, and as the whole of section 10.
It has 107 test files, in a top-level
test/directory, andgit rev-parse <pin>:testreturns the same tree hash at all four pins, so they were there each time. Unlike the AgentSwarms case there was no appendix row to be missing: the report carried no Recorded Searches table, so nothing in its structure marked the claim as unchecked. The correction improved the finding rather than retiring it — the suite does not loadreflect.ts, so the gate really is unexercised, and it lands harder next to must-not cases already written a directory away for the palace reaper. It also surfaced what the false claim had hidden:npm run test:focusedappears inCONTRIBUTING.mdand the pull-request template and in no workflow, while a separate workflow blocks merges over missing before-and-after screenshots. Two conclusions for this atlas. A sweeping absence claim is most dangerous in the reports where it feels least worth checking, and a report without a Recorded Searches appendix has no mechanism for catching one at all — which is the argument for the convention being a requirement rather than a habit. - A report told readers an MIT grant was missing, and the
LICENSEfile was at the root. PRO-LONG stated in section 1 and again as an antipattern that the licence was "asserted and absent" — a trove classifier inpyproject.tomlwith no file behind it — and compared the situation to Membase. Anls LICENSEat the published pin returns an MIT licence, "Copyright (c) 2026 PRO-LONG authors." Of the error classes on this page this is the one that does the most damage, because it argues a reader out of reusing code they are entitled to reuse. The same report also said no assertion existed anywhere in its tree, which was true of theresearch/subtree it read and false of the repository it published over. Both are withdrawn, and the second was replaced by a sharper finding: the half that ships to other people's machines is tested and the half the paper's numbers come from is not. Found by the same sweep as the two entries above — an absence claim about a file is checkable in one call against the trees API at the report's own pin, and five other no-LICENSEclaims in the corpus were checked at the same time and held. - A false absence claim is worst when it is load-bearing for a
second one. Hivemind's
section 10 read "I did not run them; there is no CI configuration in
the tree."
.github/workflows/ci.ymlrunsmake check— lint plusgo test ./...— on macOS ARM, macOS Intel, Linux and Windows, on every pull request and every push tomain. The error is one clause, and the clause was doing work: it was the stated reason for leaving unestablished whether thirteen committed tests pass, so a reader was told a suite was unverified by a project that verifies it on four operating systems. Corrected 2026-09-20 at the unchanged pin. Together with the two entries above this closes a sweep of eighteen mechanically checkable absence claims — twelve about tests, six about licences, and a follow-on pass over claims about CI — of which three were false; the rest held, including five that a looser reading would have flagged, such as a project whose onlytest/matches were Next.jsapi/.../test/route.tsendpoints. The common factor in all three errors is structural rather than careless: none of the three reports had a Recorded Searches appendix, so nothing in their shape marked the claim as unchecked. All three have one now. oceanbase/powercontexthas a rewritten memory layer this atlas has not read, and the report carrying that name does not describe it. PowerMem is pinned to9d1b4844…, the last commit of the system it describes, and is deliberately not tracked to head — the repository was renamed in September 2026 and the README calls PowerContext "the successor to PowerMem". Atd0f669d5…, 250 commits on, the architecture the report traces is gone: there is nosrc/powermem/core/memory.py, nostorage/adapter tree, and the 135KB module the write and retrieval sections cite returns 404. Memory is now an artifact plugin atsrc/powercontext/builtin/artifacts/memory/—canonical.py,extraction.py,fusion.py,reranking.py,protocols.pyand a 57KBservice.py— beside a separatetopic_memory/package, with design RFCs underdocs/en/rfcs/. That is a new reading rather than a re-pin, and it has not been done. The old pin and the archive fork both still resolve, so nothing in the existing report has become unverifiable.- A mark was withheld through three readings and two defences,
and the third defence was a false statement about the code. aimee now carries
human_review. The first reason — the ops "sit in the same route table … with identical flags" — cited a field that is0for every entry in the block under a comment reading "caps derived from the op". The second argued the distinction through the MCP surface, which is not where human review lives and is not meant to be. The third, "the producer clears its own queue", was wrong on the ladder:FACT_ACTOR_MODELis 10 and the promotion floorFACT_ACTOR_SYSTEMis 20, so the model cannot promote its own candidate. The mark was there the whole time, in the write path neither reading opened: a model-authored typed fact landscandidate, no recall returns it, and only an actor above the model clears it — with the model's authority pinned so it cannot be borrowed from whoever is authenticated during the turn. The method lesson is the one this atlas keeps relearning and this is its sharpest instance: a withheld mark is a claim about absence, and the corpus's absence claims fail when the search was scoped to the wrong place. Three readings looked at two API surfaces; the answer was in neither. When a maintainer says the reasoning is on the wrong surface, the reply is to re-derive the verdict from the mark's own words, not to find another surface to be right about. - A report called a committed benchmark a harness, and the
judge's own labels were in the tree. The MenteDB report's section 10 said
benchmarks/longmemeval/"carries a requirements file pinning nothing and calling OpenAI and Anthropic, so the benchmark is a harness rather than a committed result." The first half is true and the conclusion does not follow. At the pinned commit4ba993dc…,benchmarks/longmemeval/results/holds four files, including the official judge's per-question labels —hypotheses_baseline-shared_q0-500.jsonl.eval-results-gpt-4o-2024-08-06, 500 rows. Countinglabel == 1gives 460/500, so the README's 92.0% recomputes from the artifact exactly. Two things produced the error: the requirements file was read as evidence about the results, which it says nothing about, and the report's own recorded command for the adjacent claim wasgrep -rn -i "arxiv|bibtex|@article|citation|doi"— a basic regular expression in which|is a literal character, so it can never match, while the line above it in the same block correctly used-iE. It returned nothing honestly and proved nothing. Both are corrected, and the paper claim survives in a scoped form: the one arXiv link in the README is LongMemEval's, not MenteDB's. - A claim about two committed benchmark files was true of one
of them. The SAGE report
said the documented make targets reproduce neither LongMemEval result
file "because they pass no expansion parameter while both records
carry one". The reranked v7.1 record carries
expand_n: 3; the 0.9053 record has no expansion field at all, written by a harness version that predates the key. So the two runs differ in expansion as well as reranking, and the recall drop between them was never a reranker ablation — which the project's ownbench/longmemeval/README.mdstates from 12 September 2026. Published 2026-09-08, corrected 2026-09-12. It was a positive claim generalised from one file to two, and the appendix's search list, which grounds the report's absence claims, had nothing that would have re-run it. - Terminal-Bench's marker and archive were given more evidential weight than they support. Corrected 2026-09-09: the benchmarks page described ninety-one archived directories as retired tasks and claimed its canary was a guard no memory benchmark on the page shipped, without a comparative source check. At the inspected pin the canary check validates a shared marker's presence, while the archive includes an import from a prior edition. Neither establishes model exposure detection or saturation-driven retirement. The source check and corrected proposal record the evidence and the stronger inference errors in the accompanying note.
- A deletion claim was stated three ways in one report, and
none matched the pin. The no_human report said in its mental model
that a reject deletes a proposal from the outcome or review path, in its
reliability section that an outcome-origin reject is the only product
path that removes a row, and in its description that nothing is ever
deleted. At the pinned commit
LearningQueue.rejectdeletes an unconfirmed proposal from any origin outside its six-member archive set — the outcome path, review and reply — and four further paths,nh rules remove,nh skills removeand theDELETE /api/rulesandDELETE /api/skillsroutes, callStore.delete_memorydirectly on any row an id prefix resolves, with no origin check and nolearning_eventsrow. The report's own absence search counted the oneDELETE FROM memoriesstatement and not its five callers, which is how a one-hit search produced a three-way claim. Corrected on 2026-09-07 in the report, its frontmatter and the family paragraph on System families. - A bi-temporal paragraph was wrong twice in one sentence, and
the subject's own roadmap caught it. The Hippo report said the
memoriestable carriesvalid_from/valid_tobackfilled fromcreated, and that no read-path filter on them was found. Migration 11 addsvalid_fromandsuperseded_byand novalid_to, which exists onpoliciesalone; and both recall pipelines do filter, mapping each entry to its successor'svalid_fromand dropping anything later than the requested instant (src/search.ts:429,:433,:1113,:1117). "A pair of unused columns" was one column, and it is used. The error ran in the direction that understates a system on the very axis the report credits it for. Corrected 19 August 2026 afterkitfunso/hippo-memory's roadmap published a source-verified rebuttal; the claim was checked against the tree here before the correction landed, which is the standing rule for a finding reported by the system's own author. - A capability mark was withheld twice on a search that never
entered the directory holding the evidence. OmniClaude's
negative_evalwas refused at two readings on the strength of the three test files its appendix names, one of which carries a near-miss: a control-cohort case assertingpattern_count == 0before retrieval is attempted — and under a fixture settingdb_enabled=False, so the same assertion would hold for a treatment session.tests/hooks/test_context_injection_api_source.py, byte-identical at all three pins, mocks the transport, runs the real fetch over a page holding one well-formed pattern and one missing itsid, and asserts the survivor by identity, with a positive control in the same file. The mark is carried from 17 September 2026. The withholding was true about the tests that were read and false about the repository, which is the shape a note written the same day had just collected four other instances of — an absence claim is only as wide as the paths it enumerated, and the place to widen it is the appendix. - A capability mark was withheld on a fact about one fixture
schema rather than about the evidence. Hippo's
negative_evalwas refused becausesrc/eval-suite.ts'sFeatureTestCasehas no must-not-appear field. The rubric asks for committed evaluation cases, and they were beside the suite the whole time —tests/l9-tenant-scoping.test.tsassertsnot.toContain(bId)and that a second tenant's entry never acquires the first'sinvalidatedtag. The mark is carried from 19 August 2026, and the lesson is narrower than the fix: a mark is about what the corpus of committed tests asserts, not about whether one harness can express it. - Two counts of the same corpus sat in one paragraph and
disagreed. "Why the two counts differ" opened with the corpus
totals of the day and closed with a pair twenty smaller — the trailing
sentence had been written at an earlier size and was not updated with
the headline.
scripts/check_claim_counts.pybinds 23 count claims to live frontmatter and did not catch it, because it binds the phrasings it knows and this was a free-form restatement. The numbers are gone rather than updated: the headline one sentence earlier already gives both, and a figure stated once cannot drift from itself. Reported by an outside reader and corrected 18 August 2026. - A strict-reading count was quoted against a sample it was not scored on, in the direction that flatters the finding. Finding 4 read "83 of 302 commit a case asserting that particular material must not appear… A 2026-08-08 re-score puts 27 of the then-37 on a read path… Use 27 for the strict reading." The re-score covered only those carrying the mark on that date; the 44 earned since were never re-scored, so 27 is a floor and not the strict total. Instructing a reader to use 27 invited a ratio against 81 that nothing supports, and it made the shortfall the finding describes look larger than the evidence establishes. The text now says so and calls 27 a floor. Same report, same day.
- The benchmarks page said no released benchmark scored
forgetting, and one did. ForgetEval ships inside Lethe as the artifact behind arXiv:2606.15903, scoring
supersede,releaseandpurgeacross thirteen configurations under MIT; it was read on 30 July 2026 and the page's section on it has carried the finding since. The claim was an absence claim about the field rather than about a repository, which is the kind this atlas is least able to support and most likely to get wrong — the honest scope was always "no benchmark this page has found". Recorded here on 17 August 2026, when the correction was found still living in a section heading — "the benchmark this page said did not exist" — rather than in this log. - A paper's headline result was paraphrased wrongly on the scope-boundary page, in the direction that overstates it. The MemAgent entry read "a model trained at 8K extrapolating to 3.5M-token tasks"; the paper's abstract (arXiv:2507.02259) says the model extrapolates from an 8K context and was trained on 32K text. The 8K is the context window the agent runs in, and collapsing the two lengths into one makes the extrapolation sound larger than the authors claim. The claim was quoted without citing the paper at all, which is what let it drift — the entry now carries the arXiv id, the submission and revision dates, and the ICLR 2026 Oral acceptance, so a reader can check the number rather than trust the paraphrase. Corrected 17 August 2026.
- The rejected-value tombstone page described Daimon's key as
a hash of exact text, and it is canonical.
normalize.canonical_textfolds NFKC, case, whitespace and punctuation before the id is taken, so the key is normalised rather than literal — the direction that makes the mechanism stronger, not weaker. The Daimon report recorded the canonical form on 2026-07-30 and the pattern page carried the literal claim until 2026-08-16. - Supermemory's hosted backend implementation was not visible in this checkout; its report emphasizes schemas, clients, SDKs, MCP, and graph UI.
- A Hillock claim was imprecise when published rather than
overtaken. The report described a third monkey-patch in
talon_engine.pyas overridingGLiREL._from_pretrained"similarly" to thecheck_torch_load_is_safebypass beside it. At every commit the atlas has read, that patch defaults two keyword arguments for Hub compatibility and the one beside it supplies missing tied-weight attributes to an olderfastcorefclass. There is one deserialization bypass, applied to two module paths, and the body now says so. The error inflated a security finding, which is the direction a reader is least likely to check. - Some mem0 advanced capabilities appear to be managed-platform-only in the inspected OSS code.
- A second repository was examined and is a client, not a
store.
MontyGovernance/montycat-mcpis an MIT MCP server — 3,400 lines of Python across a server, a bootstrap and a watch loop — exposing twenty-four tools over a memory engine that is not in the repository. The engine is a proprietary package fetched fromdownloads.montygovernance.comas a.pkg, an.msior an APT repo, with a Docker fallback, and the Python client is the PyPI packagemontycat, pinned>=1.2.5,<2. Every governance tool is a passthrough, and the docstrings say so: the policy view reports effective grants but "the engine filters the result and remains the authorization boundary", and the explain tool is "a read-only policy check for planning and diagnostics" whose result does not authorize anything. The only local write in the tree is a credentials file. What is worth reading here belongs to the MCP boundary rather than to memory: four tool-annotation profiles separating read-only, mutating, destructive and installs-software, and an install tool that refuses when the configured host is not this machine because "installing a local one would create a second database and write memories where nobody is looking". Renamed from MemoCat MCP, with a compat shim under the old package name; neither name is reported here. - A repository was examined and carries no memory
implementation to report on.
Dakera-AI/dakera-deployis MIT-licensed deployment infrastructure for the Dakera memory platform — Compose files, Kubernetes manifests, a Caddy template, monitoring and systemd units, plus example scripts that drive a running instance over its public REST API. The engine itself is a closed image,ghcr.io/dakera-ai/dakera, pulled by tag;find . -name '*.rs' -o -name 'Cargo.toml'returns nothing and the only code in the tree is a playground proxy in JavaScript and five Python validation scripts that post tolocalhost:3200. There is nothing here to read for a mechanism, so no report was written. The README's claim — 88.2% on LoCoMo across 1,540 questions, described as the highest score for a self-hosted memory system — is a product claim whose evidence lives on the vendor's own site, and this atlas has not checked it. - Two repositories were examined and their memory belongs to
something the atlas already reports.
letta-ai/trajectorynormalises agent transcripts from fourteen runtimes — Claude Code, Codex, OpenHands, Cursor, Gemini CLI, pi, hermes, droid and others — into one canonical record schema for training and evaluation. It keeps nothing:grep -rli 'memory\|recall\|retriev\|forget\|supersede\|tombstone' srcreturns nothing at the commit read, and the only store it touches is somebody else's, a Deep Agents LangGraph checkpoint it decodes by thread id. Reading a transcript format is not keeping memory.666ghj/MiroFish, read at7657031a…withbackend/unchanged since39d84913…, is an AGPL-3.0 multi-agent simulation engine whose agents are described as having long-term memory; that memory is Zep Cloud, which has its own report. MiroFish's own memory-adjacent code is roughly 476 lines of client policy — a shared client with timeouts and caps, a process-local graph lifecycle lock whose docstring says it does not replace a distributed one, edge paging, and a validator bounding what an LLM may invent as a graph ontology. Its only local database holds the simulation'spostandcommenttables, read back for the interface. Reporting either would credit another system's mechanisms under a second name, which is the thing that makes a capability count mean less than it says. - This is an implementation-oriented static review, not a runtime benchmark.
- A repository was declined on its licence, and the licence is
the only thing read.
Dicklesworthstone/eidetic_engine_cliships an MIT licence carrying an explicit rider, which the file's own title names. The rider defines "Restricted Parties" to cover Anthropic, PBC together with any entity acting "under the direction of" it, states that "no rights are granted to any Restricted Party", and defines "use" to include "benchmarking, testing, analyzing, indexing". This atlas is read and written by an agent operating under that direction and a report is analysis, so the terms exclude it by construction rather than by interpretation. The repository was screened, the licence was read, the clone was deleted, and nothing was published about the system. It is named here because the exclusions are part of the evidence; nothing above or below characterises the code, which was not examined. GitHub classifies the file asNOASSERTION, so a licence filter keyed on SPDX identifiers would not have caught it. - The licence check has not been applied uniformly.
The atlas declines repositories that ship no licence file —
general-agentic-memoryandMemEngineare both named above partly on that basis — but the check was performed at review time rather than as a build invariant, and at least one report was published against a commit that carried no licence. Swafra's original pin,24dba18a, had none; MIT landed later and the current pin carries it, so the entry is sound today, but the omission was the review's and the same gap may be waiting in other early reports. Nothing inscripts/test_site.shenforces it. - Memory held in model weights is covered by two systems, and that is a fact about this corpus rather than about the field. Second Me fine-tunes a model on a person's documents and keeps the documents in SQLite beside it; mini-AGI has no store at all beside the weights, and takes a gradient step on each chat exchange as it happens. MemOS mounts a parametric module alongside four other memory forms, which is a different claim. Two systems, one of them a repository whose history begins on 19 September 2026, is a pair of data points rather than coverage. Model editing, KV-cache reuse and weight-space personalization are a substantial branch of the literature and are essentially unrepresented here, which also means the seven rubric capabilities have only been exercised against token stores. What a low-rank adapter does and does not settle about those capabilities is set out in weights as memory, at adapter granularity below, because the argument needs more than a bullet.
- Four dimensions that matter operationally are not covered systematically here, and a reader choosing a system should investigate them directly. Behaviour under embedding-model change or vector-store migration: only a few systems visibly stamp records with the model that produced them, and a silent re-embedding is a silent corpus-wide quality change. Whether scope survives background derivation: the capability index records that a scope key is applied on the read path, not that consolidation, summarization, and profile building respect the same boundary — a summary spanning two projects has crossed a scope the retriever would have enforced. Recall observability beyond which memories were returned: why they outranked others, and what was dropped by budget truncation. Cost and latency under realistic load, which is treated separately in benchmarking agent memory — as an absence, because it is almost never measured.
- Two marks were awarded to context-window machinery and
withdrawn on 29 August 2026. The first reading of OpenHands SDK led on its
Viewand condenser design and creditedaudit_logto theCondensationevent appended to its event log, andnegative_evalto a test asserting a forgotten id is absent from the view. Both describe which events reach the model within a run. An event cannot turn out to be false, which is the test this atlas's scope boundary uses, so neither mark should have been awarded for that machinery; the report now carries one. The error is worth naming because of its direction: the window machinery there is more carefully built than the memory beside it, and a reviewer follows the engineering rather than the boundary. - A capability mark was awarded against the rubric's own
definition and was withdrawn on 30 August 2026. NexusMem was credited with
trust_stateat its 29 August re-pin on the strength of a real discrete field:trust_state TEXT NOT NULL DEFAULT 'candidate', set toverifiedorrejectedby a human runningnexusmem review, kept out of the upsert path so a re-sync cannot overwrite the verdict, selected on both retrieval arms and tagged into the packed context. What it never does is withhold anything.rank.ts:192multiplies a rejected node's score byREJECTED_TRUST_PENALTY = 0.3and nothing insrc/filters on the column, which is the case the mark's definition exists to exclude — "a confidence number answers 'how sure' and gets used for ranking; a state answers 'may this be acted on' and gets used for filtering." The report's own sections 5 and 9 had said the mark was withheld and were left contradicting the frontmatter, which is how the error stayed visible for a day without being caught. NexusMem carries six marks. The general lesson is the one the OpenHands SDK correction taught two days earlier, one layer down: the definition has to be applied to the mechanism, not to the field's existence. - A redaction claim was overstated and was narrowed on 30
August 2026. NexusMem's
matrix said pattern redaction ran before anything reached the index. It
is called by two collectors of seven — conversation in full, code diffs
on a high-confidence profile — and by neither the store nor
synccentrally, so the shell, docs, git-commit, session and GitHub collectors write unredacted. The scoping turns out to be reasoned rather than accidental, which is why the first reading's summary was plausible: the module's own docstring names the two sources it was built for. The error is the general one — a safety pass that exists was described as though it were global, and the check that would have caught it is counting the call sites rather than reading the module. - The capability flags in the index are the reviewer's judgements against strict definitions, applied to code read at the pinned commits. A flag's absence means the mechanism was not found, not that it is impossible to build on that system.
- Retrieval quality and extraction quality were not independently re-measured; committed benchmark artifacts were inspected for MemPalace but not rerun.
- Swafra was reviewed at commit
24dba18; its full LongMemEval run was not rerun. Static inspection, committed artifact analysis, and a small hash-embedder smoke check exposed thekmismatch and same-title source behavior. llm-wiki-memorywas reviewed at commitb7cc76a4…; its broad test tree and committed latency report were inspected, but the suites and benchmarks were not rerun.- RainBox was reviewed as an application-integrated memory subsystem; unrelated assistant/product features were not exhaustively analyzed.
- The reports prioritize memory-management code paths over unrelated framework/application code.
- Hindsight, Graphiti, Mastra, MemOS, and Basic Memory were reviewed statically at the pinned revisions above; their dependency-heavy integration suites and published benchmarks were not rerun.
- Mastra analysis is intentionally limited to
packages/memoryand the core contracts it directly uses. - MemOS behavior varies materially by memory cube, backend, model, and search configuration; the report does not imply one universal MemOS pipeline.
- agentmemory's source tests and benchmarks were inspected but not rerun; its documented LongMemEval-S numbers are retrieval-only.
- TencentDB Agent Memory's published benchmark gains could not be traced to a committed harness or raw result artifacts in the inspected repository.
- Cognee's dependency-heavy suites and BEAM evaluation were not rerun. The committed 100K report uses a held-out conversation; its 10M routed result is explicitly exploratory and selected on the reported questions.
- Claude-Mem's Bun suite and optional service integrations were not run; no committed end-to-end recall-quality benchmark was found.
- A-MEM's tests were not run because they may download embedding models and call an external LLM. The paper reproduction code and results are outside the inspected package.
holographicandhermes-agentare two reports over one repository at one commit: the first covers the in-tree HRR memory plugin, the second covers Hermes's own built-in memory and provider contract. Neither report's suites were run.- Two open Hermes issues (#4781, #31263) report that the holographic plugin registers without its tools or context injection firing. Only the issue titles were read; they are not treated here as established defects in the inspected code.
- OpenViking's published LoCoMo and tau2-bench figures could not be reproduced or traced to committed raw artifacts at the inspected commit; the harness is committed, the results are not. Those figures are also vendor-run comparisons judged by an LLM, and the native-memory baselines for OpenClaw, Hermes, and Claude Code were not independently verified.
- The
openclawfigures quoted from OpenViking's benchmark are third-party claims about OpenClaw's native memory, not measurements taken from the OpenClaw repository. - ByteRover was reviewed at a commit where the repository is licensed
under the Elastic License 2.0 and packaged as
byterover-cli; descriptions of it as open source are inaccurate as of this commit. No tests were found for its memory or knowledge modules. - Redis Agent Memory Server's
V0/tree is the open reference implementation adjacent to a managed Redis offering; conclusions here apply only to the inspected code, and the managed product may differ. - Retrieval quality was not measured for any of the six systems added in this round.
- Voyager and Generative Agents are frozen research artifacts, last committed in July and August 2023 respectively. Their reports are historical architectural reviews, not assessments of maintained software.
- HippoRAG's
reproduce/tree provides benchmark scaffolding, but no raw result artifacts are committed and no published numbers were reproduced here. - Voyager's and Generative Agents' published evaluations measure task completion and human believability, not retrieval quality; neither repository contains a memory-quality benchmark.
- Generative Agents' retrieval gain weights
(
gw = [0.5, 3, 2]) have no committed ablation; the atlas treats them as hand-tuned constants rather than a derived result. - No suites were run for the three systems added in this round, and no retrieval quality was independently measured.
- Magic Context's verification precision — how often the verify task correctly marks a stale memory stale, and how often it wrongly confirms one — is not measured anywhere in that repository, and was not measured here. It is the central claim of the design.
- Magic Context reads OpenCode's native session database read-only for its retrospective scanner; that behaviour was read in code but not exercised, and the user-consent story around it was not assessed.
- Pi has no memory subsystem, so its report covers session persistence, compaction, and the extension surface only. Third-party Pi memory plugins other than Magic Context were not reviewed; the db0 integration has a closed backend and is not reviewable on this atlas's terms.
- MetaClaw's committed benchmark fixtures and memory ablation scripts were inspected but not run, and no published numbers were reproduced. Its replay metrics are lexical-overlap proxies; no evidence linking them to task outcomes was found in the repository.
- No memory tests or memory-quality benchmarks were located for nanobot, CowAgent, or GenericAgent. Nothing was run for any of the four systems added in this round.
- GenericAgent's memory documentation is written in Chinese; the axioms and rules quoted in its report are the reviewer's translations, with key terms given in the original. Its cited arXiv technical report was not retrieved or assessed.
- Waku Agent's evals were not run, and its retrieval gate's accuracy was not measured — the false-negative rate, which is the figure that matters, is unknown. No system in the atlas measures its gate.
- Nine repositories examined in the same round have no reports.
razzant/ouroborosis cited in the append-only-memory-audit pattern for its "honest journal" fix rather than given a report. (truffle-ai/dexto,Arvincreator/project-golemandopenyak/openyakwere excluded here on licence grounds and have since been reviewed — see Dexto, Project Golem and OpenYak. The openyak entry was also wrong on its facts: that repository has carried an Apache-2.0LICENSEsince 25 May 2026, well before it was examined.)OtterMind/youclawis small.SixHq/Overture's only memory artifacts are.claude/agent-memory/*/MEMORY.md— Claude Code's own memory used while developing the repo, not a system it ships.husu/loomis an AI JSON Schema documentation generator,AaronWong1999/hermesclawa launcher for running Hermes Agent, OpenClaw, and OpenCode on one WeChat account, andKeyID-AI/agent-kitgives MCP clients an email address; none is agent memory. - Neither Atomic Agent's nor MateClaw's suites were run, and Atomic Agent's evaluation campaign was read but not executed; no scored results were found committed for it. MateClaw's scoping and retrieval ranking were not traced in full.
- Eight repositories examined in the same round have no reports.
beita6969/ScienceClawis an OpenClaw derivative whose memory extensions are OpenClaw'smemory-coreandmemory-lancedb, already covered — its runtime skill authoring is cited in the skills pattern instead.litanlitudan/skyagistates that it "implements the idea of Generative Agents" and has been frozen since August 2023, so the original is the better subject.xvirobotics/metabotre-exports a memory client whose backend is not in the repository.Gitlawb/zerohas context reporting and no memory module.thClaws/thClawshas a competent 1,644-line file-entry store that adds little beyond systems already covered, andskalesapp/skales(~1,542 lines) is Business Source License 1.1 with no distinctive mechanism found (it was reviewed later: see Skales).wanxingai/LightAgent's 196-line shared memory with swappable adapters is cited in the pluggable-provider pattern rather than given a report.rush86999/atomhas roughly 976 lines of memory-named Python inside a 459 MB repository dominated by deployment scripts; no coherent memory design was established, and that is a weaker conclusion than the others here. rickey1990/THREADS-reasoning-enginewas examined and has no report: its correctable event ledger lives only in process memory, and nothing in the tree persists it or binds it to an agent. The code is under PolyForm Noncommercial 1.0.0 and the documentation under CC BY-NC 4.0 (LICENSING.md,LICENSE-CODE.txt,LICENSE-DOCUMENTATION.txt; GitHub reportsNOASSERTION), and neither restricts a read-only analysis. At439f8a91…, nine commits by one contributor from 6 to 12 September 2026, thesource/andbenchmarks/directories are present, added at78972439…on 11 September 2026: a 974-line Python packagesrmh, 517 lines of tests and 1,369 lines of benchmarks.Ledgerindexes immutableEvents — subject, relation, object, event time, context, confidence, polarity, lineage — in three dicts (source/srmh/ledger.py:52-57), refuses an id reused for different content (:65-69), and answers a point-in-timelookupwithANSWER,NEGATED,CONTRADICTED,AMBIGUOUSorUNKNOWN(:102-116). ARETRACTaimed at an event id closes that assertion (:89-100), and on a functional relation retracting the latest value leavesUNKNOWNrather than reviving the value it superseded (:8,:95-97). Nothing survives the process: no module undersource/srmh/opens, serialises or loads anything,srmhis imported only bysource/tests/andbenchmarks/, and the only file writes in the tree are result JSON from the runner and benchmarks. The benchmarks titled "Correctable AI/customer memory" and "Agent plan/state recovery" build their history in a freshEngineon each run (benchmarks/applied10_benchmark.py:48-62,:219-237), and the paper in the tree names a memory layer as a possible use (THREADS_paper_spaced.pdf, p. 9) while listing persistence testing among what its benchmarks do not cover (p. 10). Two near-misses matter if the ledger is ever persisted: an untargetedRETRACTis keyed on the value but closes only assertions at or before its own time (ledger.py:98-99), so a later re-assertion is live again; and a negative event on a value is kept beside later positives and turns the answerCONTRADICTED(:97,:104-107), the nearer shape to a value-keyed rejection. Searches run at the tree root:git grep -nE 'open\(|json|pickle|sqlite|shelve|write_text|dump|persist|serial' -- source/srmh(nothing);git grep -lE 'srmh' -- '*.py'(the three test and four benchmark files);git grep -nE 'write_text|json\.dump|open\(' -- '*.py'(result writers inTHREADS_test_runner.pyandbenchmarks/only);git grep -nEi '(^|[^[:alnum:]_])llm([^[:alnum:]_]|$)|openai|anthropic|prompt|embedding|(^|[^[:alnum:]_])mcp([^[:alnum:]_]|$)' -- '*.py'(nothing). The screen found 0 RUNS, 0 EXEC, 0 FRESH and 2 FLOAT (numpy>=1.24inrequirements.txt, andsource/pyproject.tomlwith no lockfile), and nothing was installed, built or run. Nothing was run for Kwipu or craft; craft was read from a depth-one clone with its history from the GitHub API.- LlamaIndex ships two APIs under the name "memory": the newer
block-based
Memoryreviewed here, and an olderChatMemoryBufferfamily that is conversation-window management and out of scope. Its tests were not run and no memory benchmark was found. - No suites or benchmarks were run for open-cowork, Gini, Moltis, or Mercury. open-cowork's eval harness was read but not executed, and no scored results were found committed.
- Gini reimplements the Hindsight memory model locally rather than depending on Hindsight; its recall module cites the source paper's equation numbers, but no check was made that this implementation reproduces the published behaviour.
- Moltis's cross-agent prefetch and its shared-channel tool path were traced by reading and not exercised; whether either reaches a prompt depends on a deployment running more than one agent, or on a channel configured with a trusted audience and a policy tool set.
- Four further repositories examined in this round have no reports:
he-yufeng/CoreCoder(1,166 lines whosecontext.pyis conversation-window compaction with nothing persisted),chrysb/alphaclaw(an OpenClaw deployment harness whose only "memory" reference is host RAM),Intelligent-Internet/ii-agent(a SaaS agent platform with chat context and caches but no durable memory), andAgentsMesh/AgentsMesh(a real pgvector-backed block memory with amemory.retrieveMCP tool, set aside for now because it is licensed under Business Source License 1.1 rather than an open-source licence). pingcap/tidbwas examined and is out of scope: its "memory" is RAM. The repository reached this atlas through a scout shortlist on the strength of thirty-odd memory-named files, and at8b5d4478…every one of the 36 such paths in its 7,703 blobs is resource management for the database process —pkg/util/memory/{tracker,arbitrator,pool,meminfo,memstats}.go,pkg/util/gctuner/memory_limit_tuner.go,pkg/util/cgroup/cgroup_memory.go,pkg/util/memoryusagealarm/,pkg/util/servermemorylimit/,br/pkg/utils/memory_monitor.go, and three design documents on global memory control, a global memory arbitrator, and keeping a priority queue in memory. None of it is a memory an agent reads or writes, and the filter that found it was matching on the word. Recorded so the same shortlist entry is not assessed a third time.- Three repositories examined in the same round were judged out of
scope and have no reports:
KnockOutEZ/wigolo(a web crawl, search, and extraction MCP server whose cache holds external content rather than agent belief),siyuan-note/siyuan(a note application whose agent kernel contains no memory concept — only conversation compaction — and whose MCP surface is note CRUD), andnetease-youdao/LobsterAI(which operates OpenClaw's memory rather than having its own, and is covered inside the OpenClaw report). - Memora's report was wrong about what supersession did, in
the direction that flatters the system. Until 11 August 2026 it
stated, in the matrix and in two sections, that superseded rows were
"hidden from retrieval" at
bc64ff74…. At that commit the exclusion applied only where a caller passedfollow="active"— inside the digest path — whilememory_list,memory_searchandmemory_getpassed the caller's argument through, and an omitted argument meant no lineage filtering. The error came from reading the function that implements a filter and not the callers that decide whether it runs. The project changed the defaults inde8e9e97…on 9 August 2026, so the corrected report describes a system where the claim is true. - Nothing was run for memora or LoongFlow. Memora's pair classifier is
the component that matters — its precision determines which memories get
hidden — and no measurement of it was found; the dry-run mode makes
exactly that measurable, and nothing indicates it has been done.
LoongFlow's tests exist under
tests/agentsdk/memorybut were not run, and no comparison of adaptive against fixed temperature was found, though the code is parameterized for it. - Six repositories examined in the same round have no reports.
TeleAI-UAGI/Awesome-Agent-Memoryis a survey, cited in the correction discussion rather than reviewed as a system.webbrain-one/webbrain(368 lines) is too small to carry a mechanism.AmeNetwork/aseris an agent framework of about 4,000 lines whose 29-lineMemoryclass is a persisted chat buffer, and its entry below gives the pin and the reason.AgentTeam-TaichuAI/ScienceClawis 78 lines with no licence file, and is a different repository from the OpenClaw-derivedbeita6969/ScienceClawnoted above.ArtificialAnalysis/Stirrupandhowl-anderson/agentsilexhave no memory subsystem. - Nothing was run for the six systems added in this round. OptMem is
reviewed without a licence file — all rights reserved
by default — as a deliberate exception to the rule applied to
openyakand others, because it carries mechanisms the atlas has not otherwise found; the exception covers reading it, not reusing it. MemAgent, HiAgent, Mi-Memory and langchain-ai/memory-agent were examined in the same round and have no reports: MemAgent and HiAgent are conversation-window management (MemAgent is discussed in the scope-boundary section),Darwin-Agent/Mi-Memoryis a paper PDF and a landing page with no implementation, andlangchain-ai/memory-agentis a 235-line LangGraph template whose substantive counterpart, LangMem, is already reviewed here. - The framework-native gap is now closed, and closing
it corrected the bullet that named it. CrewAI — the most-cited omission on that
side — is reviewed, as are Agno, CAMEL, the Pydantic AI Harness and Microsoft Agent Framework, which
retires Semantic Kernel as a separate entry since it succeeds it.
Haystack was the error.
deepset-ai/haystackat3cef34f2has no agent memory to review: itsInMemoryDocumentStoreis a RAM-backed document store,components/agents/stateis a typed run-scoped dict with a merge schema and no persistence layer, and the only things it calls memory stores areMem0MemoryStoreandCogneeMemoryStore— adapters that live in the separatehaystack-core-integrationsrepository and are backed by Mem0 and Cognee, both already reviewed here. So this atlas spent several rounds naming as an unreviewed gap a thing that does not exist, and the correct statement is that Haystack is a RAG pipeline framework that mounts other people's memory. With the adjacent contracts — adk-python, AutoGen and LangMem — already read, this atlas no longer has a named framework-native omission. That is a statement about this list, not about the field: the next one will arrive the way all of these did, from somebody naming it. - MemGPT is here under its current name. The project
renamed to Letta, so the OS-style tiered-memory reference implementation
is the Letta report — which covers the
V1 server, archived on 15 August 2026 in favour of
letta-ai/letta-code— and a reader searching this atlas for "MemGPT" will otherwise find only a passing mention in the correction discussion. Recorded because the rename makes the lineage hard to find, not because anything is missing. The paper is arXiv:2310.08560, MemGPT: Towards LLMs as Operating Systems (Packer, Wooders, Lin, Fang, Patil, Stoica & Gonzalez, 12 October 2023), which introduced the virtual-context-management idea — paging between an in-context working set and out-of-context tiers, driven by the model through function calls and interrupts — that the Letta report analyses as shipped code; the atlas judges the implementation, and the paper is the design behind it. Cohexa-ai/agent-coherencewas examined and has no report. It is MESI cache-coherence for shared agent artifacts — single-writer ownership, commit-CAS, a read-generation fence, pinned snapshot sessions — and it stores no memory:CCSStore._apply_putserialises the value to an opaque JSON string and versions it, never parsing, ranking, scoping or correcting it. What it durably holds is coordination metadata. That is the guard-is-not-a-store shape and the operates-rather-than-believes shape at once, and namingmemory.jsonas an example artifact does not change it. Recorded rather than dropped for two reasons. Its premise is a failure this atlas asks about in every report and finds answered in four of two hundred and sixty-one — Mastra prevents lost updates with per-scope locks, Logseq is last-write-wins, the Pydantic AI Harness adds an idempotency receipt so a retried write is a replay rather than a second append, and Prime Agent refuses a harness edit whose target entry changed while the model was planning it — so a whole library existing for it says something about the corpus. And its central claim does not hold: the README says "every spec carries a documented mutant that must fail — the invariants are load-bearing, not decorative", the mutants are written out in the specs' comments, and nothing executes them.make tla-checkasserts six invariants hold; no job asserts a mutated spec fails, which is the standard defence against an invariant passing vacuously. A repository with 60,163 lines of tests documented its negative cases in prose — and the contrast is internal, because its performance claim is committed, checksummed and CI-regression-checked:benchmarks/results/canonical/SUMMARY.mdreproduces its paper's Table 1 with all four figures against tolerances, which is the inverse of the traceability failure this atlas records for Memvid, MemoryOS and FiFA. The same discipline was applied to the speed claim and not to the safety claim. Its paper (arXiv:2603.15183, 16 March 2026) is also worth noting for selling a different thing than the repository does — the paper leads with simulated token savings and the repository leads with preventing silent clobbers, which on this atlas's terms is the better framing of the same mechanism. See the note for what is unusually honest about it, and for the read-generation fence, which is the one mechanism there that memory systems with restartable background passes appear to need and none here has.perplexityai/numbatwas examined and has no report, and what it is worth to this atlas is what it reads rather than what it stores. Apache-2.0, Go, ~99,000 lines over 260 files at63b5a313…, created 29 July 2026. It is endpoint detection for coding agents: local hooks and plugins, a CEL rule engine, opt-in pre-action blocking, and forensic reconstruction of sessions from on-disk artifacts. The scope call is settled by the vocabulary — across the whole treerecallandembeddingappear zero times and every one of the twenty occurrences ofmemorymeans RAM ("cannot exhaust memory", "the in-memory window"). What it durably writes is events, findings, enforcement decisions and case bundles: records of what happened, none of them a claim that could be false and later corrected. Same boundary asUntrivial-ai/agent-orchestrator,os-factory/harandCohexa-ai/agent-coherenceabove. Its coverage matrix is the artifact worth knowing about, because it is an independently maintained, path-level enumeration of where about eighteen agent hosts put durable session state — including seven this atlas has reports on — and two of its entries are evidence for a limitation stated elsewhere on this page. For OpenClaw it discovers "plain retained.jsonl.{reset,deleted}.<timestamp>archives", matched byopenClawRetainedArchiveREininternal/discover/discover.gowith tests for both suffixes: a deleted session survives as readable plaintext beside the live one. And its Gemini CLI extractor skips$rewindTorecords above the comment "A rewind changes resume context, not what already happened", so an undo moves a pointer and leaves the actions recoverable. Neither was verified at this atlas's own pin for those systems, so both are recorded as facts about numbat's extractors rather than folded into the reports they concern.- Nothing was run for Nova AI, and its own suite would not
have helped. Its 21 test files carry five assertions between
them, all in one file, against roughly 230
printcalls — manual scripts a person reads the output of. Nothing asserts the invariant its most careful code exists to hold — that a classifier retrain leavestraining_data.jsonbyte-identical — and nothing pins the refusal path that earns it two capability marks. Its licence is "Viewable, Not Reusable" — all rights reserved — reviewed under the same exception applied to OptMem, because the mechanisms are ones the atlas has not otherwise found in a system that calls no model at all. - Two repositories examined in this round have no reports, and
both are the same misread.
showjihyun/bvwebchatandshowjihyun/bvcounterchatare, respectively, a multi-room web chat server and a browser 3D FPS game; neither application stores agent memory, and everymemorymatch in the latter's source is SQLite's:memory:DSN against a kill/death/playtime stats table. What is substantial in both is the Claude Code development harness beside the app, and the two differ sharply there: bvwebchat keeps.harness/state/with asession.jsonof goal, next steps and open questions, an append-onlydecisions.jsonlwith a single writer, HMAC-signed state that demotes to a fail-closedIDLEwhen tampered, and aSessionStarthook that injects a ≤15-line digest of "what git does not know"; bvcounterchat has none of that machinery, only a markdown ledger and gate hooks. The first passes the letter of this atlas's qualification test — something survives the session and can be corrected — and is still excluded, because what survives is workflow control state: a phase is not a claim that can be true or false, and there is nothing for a correction to be about. Recorded rather than dropped because it is the cleanest example yet of the boundary this atlas draws between a harness that persists and a memory that believes. - One published claim about ALMA was wrong at both earlier pins,
and is corrected. Until 4 September 2026 the report said
"No validity interval exists"; the knowledge graph's
Relationshipdataclass has carriedvalid_fromandvalid_tobesidecreated_at, with aget_relationships_as_ofreader, since v0.9.0 in April 2026, four months before the first reading. The mark is still withheld, on the producer test rather than on absence: nothing in the package assigns either field, the Kùzu, Neo4j and Memgraph backends neither persist nor read them, and no surface imports the graph package — so the report's verdict was right and its reason was wrong, and a reason that is wrong is a search that was never run. The same re-read found the two commits the report had been pinned to no longer served by GitHub, because the project rewrote its history to remove a company adapter; the History section keeps both hashes and says so. - Three published claims about Engram Alpha were wrong at every pin
since the first reading, and are corrected. Until 4 September
2026 the report said approval and pinning were "human acts the
assistant cannot perform";
approve_nodehas been an MCP tool since the commit the first reading pinned,Engine::approvetakes no source and gates on nothing, and the only restraint is the tool's own description — pinning is human-only, approval is human-only by request. The report described storage as "SQLite (with a TepinDB backend beside it)"; every new graph has been born on TepinDB since v0.6.2 on 21 July 2026, two weeks before the first reading, and the SQLite driver is a migration source — the project's own documentation namedgraph.dbas the default until its v0.9.1 sweep, and the reading repeated the documentation instead of readingresolve_db_path. And the open question "does the TepinDB backend match the SQLite one … no parity comparison found" had an answer in the tree at every pin: astore_batteryconformance test has run one sequence against both backends since v0.6.0. The direction is the one the corpus keeps producing: a boundary the documentation draws was credited as one the code draws, and an absence was published without the search that would have refuted it. The report now names which of the two human-only lines is enforced and which is asked for. - Four published claims about iai-pme were wrong when published, and
are corrected. Until 3 September 2026 the report described the
LongMemEval head-to-head as run "in a single harness" with
MemPalace and praised the matched-embedder row as the control that made
it rigorous; the project's own
BENCHMARKS.md, present at the pinned commit, said the baseline numbers "are published and config-matched (not re-run on this host)", andbench/longmemeval_blind.pyhas never had a competitor mode — the row is a control against a published figure. The report said the system had "no trust state, no tombstone, no provenance beyond the episode itself" and "no epistemic status field"; therecordsschema at that commit carrieds5_trust_score,provenance_json,tombstoned_atandlabile_until, and the read path derivedvalid_tofromcontradictsedges and discounted stale hits. It said the committed JSON "covers the embedder comparisons";bench/results/held seven contradiction-benchmark runs with environment tables. And it withheldaudit_logfrom an insert-only, encryptedeventstable that records every forgetting-side mutation. The direction is consistent: the benchmark posture was overstated and the mechanisms understated, because the first reading worked from the README and the file index rather than the schema and the results directory. The report now carries three marks and names the failing gate the committed artifacts record. - A published claim about Cambium was wrong and is
retracted. The report stated the repository had "no worked
instance" of its profile interface and that "an adopter is the first
person to find out whether the rules compose". Both are false:
profiles/examples/agent-atlas/— a 603-line filled reference profile with no placeholder markers — was present at the reviewed commit, andcheck_profile.pypasses on it with all ten interface slots bound. The correct narrower statement, now in the report, is that the repository selects no profile of its own, which is what blockscompose_vocab.pyand leaves everything downstream of a composed vocabulary undemonstrated. Reported by the project's author; verified here at the atlas's own pinned commit before correcting. - A Perseus Vault claim was overstated and is corrected. The report described its tool count as "stale by eleven", which asserts that the documented command's 76 is the canonical figure. It is not: parsing the registry the command is meant to count returns 88, and the canonical/legacy split is synthesized at runtime rather than present in the source, so no static count settles it. What is established is that the count definition and its verification command have drifted apart. Reported by the project's author; verified at the atlas's pinned commit.
- The DeepSeek
Harness report described an opt-in surface as the system's default,
and is corrected. Until 14 August 2026 it framed the harness as
one whose durable memory is "indexed for full-text search across past
sessions and handed to the model through five tools". Both halves are
off in every shipped composition at the pinned commit, and
independently.
packages/bundle/base/cordis.patch.ymlmountssession-query-sqlitewithpath: ':memory:'andopenAt: never, sosearchSessionsandsearchEventsfail withSESSION_QUERY_SEARCH_DISABLEDbefore request normalization andnode:sqliteis never opened; the web-app bundle restates it andapps/cli/tests/lazy-search-startup.compat.spec.tspins both layers. Andtool-session-query, which registers all five tools, is mounted by no bundle — only byexamples/acp-agent/and a test — with its own README stating that "shipped host compositions do not mount it by default." A defaultdshgives the model no history tools and the deployment no content search, while exact reads, titles and lineage traces stay available onctx.sessionQuery. The error was reading the mechanism and not the composition that mounts it — the same shape as the Memora correction above, which read a filter and not its callers, and it is the second time a default has been mistaken for a capability in this corpus. Both capability marks are retained, because the mechanisms are real code in the tree, and the report now says which package they live in. Verified at the atlas's own pinned commit before correcting. HKUDS/Auto-Deep-Researchwas examined and has no report, because its memory layer is present in the tree and unreachable from it. It is a deep-research agent built on the AutoAgent framework — 11,115 lines of Python, dormant since October 2025 — and it does inherit a memory package:autoagent/memory/is 747 lines wrapping a ChromaDBPersistentClient, withrag_memory,code_memory,codetree_memory,paper_memoryandtool_memory. Durable storage, retrieved by query, so it looks like a candidate. The disconnection is what settles it. Every one of the five functions inautoagent/tools/rag_tools.py—save_raw_docs_to_vector_db,query_db,modify_query,answer_query,can_answer— is referenced in zero other files in the repository;autoagent/agents/contains onlysystem_agent; and the RAG imports inautoagent/tools/__init__.pyare commented out rather than merely unused, so the disconnection is a choice someone made rather than an accident. Checked by enumerating each defined function and searching the whole tree for each name, because "nothing calls this" is exactly the claim a single mis-scoped grep gets wrong. Nothing this agent stores survives a session, because nothing reaches the store — which is the genuine exclusion, distinct from a system that stores carelessly. Worth recording rather than dropping because it is a shape nothing else in the corpus names: inherited memory machinery, complete and disabled, in a fork whose parent presumably uses it. A reader evaluating the parent framework should not conclude anything about it from this.ShamGaneshan2008/Kodiakwas examined and has no report, and it inverts the shape of the bullet above. An autonomous GitHub-issue-to-pull-request agent — 50,497 lines of Python over 290 files, 247 commits since 11 June 2026, atc2daf864…— carrying akodiak/memory/package of 3,663 lines with the full cognitive taxonomy: working, short-term, episodic, semantic, procedural, plus consolidation, ranking, retrieval and an experience extractor. It is excluded on the ordinary ground, and it takes three separate checks to establish, because the machinery is arranged so that each one alone would look like an oversight. The named memory package is reachable and ephemeral. All five repositories inpersistence.pyare Python dicts; the one durable driver,JSONFileMemoryPersistence, is only ever given a path byMemoryService(persistence_path=...), and that argument is passed in exactly two places in the repository, both intests/unit/test_memory.py. Every other construction — the three CLI commands, andMemoryIntegration's default — callsMemoryService()bare, soself.persistenceisNone.kodiak memory addtherefore prints "Memory added", andkodiak memory searchbuilds a second empty service in a second process. The durable store is unreachable.kodiak/learning/pattern_store.pyis the real thing — asyncpg over alearning_patternstable it creates itself, with content hashes, aPatternStatusof active/deprecated/pending_review, jsonb tags with a GIN index,frequencyandsuccess_rate— and neitherPatternStorenorPatternExtractor,RewardModel,FeedbackCollectororCrossRepoSyncis referenced anywhere outsidekodiak/learning/, a directory with no__init__.py. And the ORM tables named for both are scaffolds.memorys(sic) andlearningsare five identical columns —id, name, description, status, created_at, updated_at— with no content field, no type and no embedding, generated bycreate_kodiak_full.pyat the repository root and queried by nothing;LearningRecordis not even exported fromdb/models/__init__.py. The hook that would join the halves is written and never supplied:ExecutionEngine.__init__takesmemory_integration: MemoryIntegration | None = Noneand callsrecord_executionunder anis not Noneguard, andMemoryIntegration(appears only in tests.GET /memoryis a nineteen-line router returning a hardcoded[]. What does persist is a ChromaDBPersistentClientindex of the user's source code — a corpus index, the boundary already drawn forVectorSpaceLab/general-agentic-memoryabove, and not a store of anything the agent believes. Two smaller facts are worth stating because a reader would otherwise take the claims at face value:SemanticEntity.embeddingis accepted, stored and carried through updates and never read by any comparison — the only search anywhere in the package is a substring term-count — so the CLI's "search memories by semantic similarity" describes a path that does not exist; andkodiak/auth/audit.py:25importsfrom kodiak.db.models.audit_log import AuditLogat module level, a file absent from the tree, so that module cannot be imported at all. The licence is asserted three times — a README badge, a "MIT — see LICENSE" line linking to the file, andpyproject.toml— and theLICENSEfile is absent, as with Membase andrahvis/cognitive-weavebelow. Recorded rather than dropped because the arrangement is instructive on its own: a complete memory design, a working durable store, and a wired execution hook, none of which are connected to the other two — which is what a scaffold generator plus five subsystems built in parallel produces, and what a reader skimming the directory listing would never guess.- Empryo's maintainer reports
substantial changes in a tree this atlas cannot verify, and the report
is unchanged because of it. They opened a pull request
rewriting the report against commit
aa963f28, in which the memory layer has moved fromsrc/core/memory/into a standalonepackages/memory/workspace that is private. The public repository still carries the v2 layout, and its default branch head is still64ea2ec8…— the exact commit pinned here, so the published pin has zero drift and every path in the current report still resolves. What is reported and not verified: a retrieval-quality benchmark with committed results, a content-hash resurrection path closed after this atlas named it, two further capability marks, and — volunteered by the maintainer — a degradation in provenance, where an optional distillation pass writes model-authored memories into the same table with no ranking distinction from user-dictated ones. Also reported is a measured and unexplained gap between synthetic and real-data recall. None of it is checkable from outside, so none of it is in the report; the maintainer said the same thing first and marked the PR draft. Recorded here so a reader knows the pin is current with the public tree and may lag the project, which is a different claim from the pin being stale. - Core Memory's grounding ceiling, Memanto's conflict-detection precision, Memory Engine's agent clamp, ai-memory's cross-harness continuity claim, ctx's disclosure reachability, and OptMem's cover loss are all directly testable and none was measured here.
- Nothing was run for the four systems added in this round.
gastownhall/beadsandVectorSpaceLab/general-agentic-memorywere examined and have no reports, for the reasons given in the scope section; GAM additionally has no licence file.langchain-ai/memory-agentandakitaonrails/ai-memorywere re-submitted in this round and were already handled — the first rejected as a 235-line template, the second reviewed. - Memvid's headline figures ("+35% SOTA on LoCoMo", "+76% multi-hop", "+56% temporal") could not be traced to committed raw artifacts at the inspected commit and are recorded as claims. MemoryOS commits the LoCoMo dataset beside its harness but no scored results were found. Neither was run here.
- SimpleMem is the same finding at six figures rather than three. Its
README claims a 26.4% average F1 gain and roughly 30× token reduction on
LoCoMo, LoCoMo F1 = 0.613 and Mem-Gallery F1 = 0.810 for Omni-SimpleMem,
and +25.7% on LoCoMo with +18.9% on MemBench for EvolveMem, and offers a
benchmark runner per pillar. The repository contains no
.json,.jsonlor.csvfile of any kind at the inspected commit, so no scored result, prediction dump or metrics table backs any of the six. Nothing was run here either. Its 311 test functions were not executed, and the transforms carrying its contribution — coreference resolution and time absolutisation in the extraction prompt — have no test or metric anywhere in the repository, so how often they are correct is unknown and is the number the whole design rests on. - OpenWorker's stated finding — that models without when-to-remember
guidance "either never call
rememberor save noise" — is quoted from a source comment. Whether it was measured, and by how much guidance moves behaviour, is not established in the repository. OpenHands/OpenHandswas examined twice and has no report, because the memory it appears to have belongs to another repository, and the organisation's own layout says which. That repository is Agent Canvas, an Electron control centre: ten Python files against 2,230 in the tree, acondenser-settings.tsxthat renders whateveragent_settings.condenserschema the backend declares, ause-condense-conversationmutation posting to/api/conversations/{id}/condense, and aCondensationEventtype mirroring a server contract — including aforgotten_event_idsfield it never populates. The standaloneOpenHands/agent-canvasrepository was archived on 27 July 2026, which is when this one became it. The agent code that used to live here is inOpenHands/legacy, archived the same day and reduced toanalytics,app_server,dbandserverwith no memory package;OpenHands/enterprisecarries the same four and declaresopenhands-sdk==1.43.1,openhands-agent-server==1.43.1andopenhands-tools==1.43.1as dependencies; andOpenHands/OpenHands-Cloudis Helm charts and Terraform. Every one of them gets its agent memory from OpenHands SDK, wherecontext/memory.pywas added on 22 July 2026 by a pull request titled "feat: add opt-in persistent memory across sessions" andload_memorywas exposed in the agent-settings schema three weeks later.Tongyi-MAI/Qwen-UI-Agentwas examined and has no report, for the same reason and more plainly. At083fc5ed…the repository is the model's technical-report website — its own README calls it "a concise, application-first website template distilled from the current Qwen-UI-Agent LaTeX draft" — 4,650 lines of TypeScript of Next.js pages plussiteContent.ts, and 444 MB of demo video underpublic/. There is no agent in it:db/schema.tsis a two-line file whose comment reads "Intentionally empty by default. Add Drizzle tables here when the site actually needs a database", the worker is one file, and the only external links in the site content are Bilibili demo videos. The UI agent this site describes lives elsewhere and was not reviewed here. Recorded because the atlas already carries two other Qwen-named systems and the repository name is what a reader would search for.Tongyi-MAI/Qwen-Planner-Agentwas examined and has no report, and it is the harder call of the two, because the design it describes is squarely in scope. At2a924e12…the repository is seventeen files — a 7.4 MB technical-report PDF, a singleindex.html, a README and fourteen PNGs — with no.gitmodules, no licence file, and no source file of any kind in a tree the GitHub trees API returns untruncated. The README says so itself, in an[!IMPORTANT]callout at the top: "This is the blog and technical report website repository for Qwen-Planner-Agent … It is not the release repository for model weights, training code, or the agent implementation." The weights are not published either — the organisation's Hugging Face account carries four models and none is this one, a query of the arXiv API for the title returns no entry, matching the page's own placeholder ("The official citation will be available when the report is released"), and every link in the README resolves to the website, the PDF, or the repository itself. What the 47-page report describes is a memory system this atlas would want to read. Its Persistent Memory Manager separates a compact user model, episodic records, curated long-term memory, prospective memory "for future intentions with explicit activation conditions, scope, expiry, and completion status", and review records that "document maintenance without becoming authoritative memories"; each unit links a structured summary to source metadata and a lossless dialogue record, so the original "permits direct verification of numbers, dates, quotations, contradictions, and changing facts". Model-assisted consolidation proposes rather than decides — "provenance, trust, recency, and conflict checks precede consolidation" — a revised entry "explicitly supersedes the obsolete record rather than leaving competing versions unresolved", recalled material is tagged so it is not re-ingested and cannot inflate its own importance, provenance tiers stay distinguishable and "content cannot promote its own trust level", retrieved memory "does not authorize or execute an action", an invalid summary is "treated as an ingestion failure rather than silently replaced", and low-confidence or release-critical Harness revisions "are routed for human review" with "no candidate update applied autonomously to a serving system" — several of which name mechanisms this atlas awards marks for. Two things are worth separating for a reader who opens the PDF. The privacy-preserving memory safety section is written almost entirely in the conditional: what exists is "service-level authentication tokens and separate administrator credentials, while user-level access enforcement depends on trusted upstream services", and role-based access control, least privilege, encryption, protected audit logs and retention policies are each what the system should do — a design recommendation is not a producer test, and none of it could be credited even with the tree in hand. The report draws the same line itself elsewhere, presenting model–Harness co-evolution "as a development pathway rather than claiming that sustained autonomous co-evolution has already been established". And the long-history results — a memory Harness against a 256K direct-context baseline on LoCoMo, LongMemEval and BEAM, reporting BEAM-10M rising from 21.99% to 67.24% for the 27B planner — are the project's own, with the Mem0 comparison row marked by the authors as externally reported rather than re-run, and no scored artifact backs any of them in the repository, because the repository contains no results file. Recorded rather than dropped because the exclusion is not the usual one: the repositories above are excluded for storing nothing, for storing something unreachable, or for calling RAM "memory", while this one is excluded only because the described system is not anywhere a reader can inspect it, which is a claim about the artifact and not about the design. Searches, so a later reader can re-run them: the trees API at the pinned commit (17 blobs,truncated: false, no.gitmodules, noLICENSE, no.py/.ts/.rs/.go/.ipynb/.sh/.yaml/.toml);https://huggingface.co/api/models?author=Tongyi-MAI(4 models); the arXiv API for the exact title (0 entries); and a grep of the extracted report text foropen.?source|will be released|code is available|we release|checkpoints? (are|will), whose only hits are the website repository's own URL, a table header reading "Open-Source Models", and two bibliography entries.aindilis/autonomous-ai-agentandaindilis/free-life-plannerwere examined and have no reports. Both are components of FRDCSA, a long-running symbolic-AI project. The first is AgentSpeak(L) BDI agents over SWI-Prolog with no licence file, where the three occurrences of "memory" all refer to RAM and compute allocation. The second is a GPL-3.0 Prolog life-management and planning system — calendaring, fluent calculus, a software ontology — whose only belief-related identifier ishasBeliefSystems/2in a list of dynamic predicate declarations. Neither contains a memory subsystem: no capture, retrieval, consolidation, or lifecycle. Both are also not self-contained, carrying 50 and 352 distinct absolute paths respectively into a/var/lib/myfrdcsa/installation that is not in either repository, so neither can be evaluated as it stands.elizaOS/agentmemoryis listed as a representative open-source memory framework in the open-source table of Memory in the Age of AI Agents (arXiv:2512.13564), and the URL returns 404; a search of theelizaOSorganization finds no repository by that name. It could not be reviewed. Note also the name collision: this atlas's agentmemory report isrohitg00/agentmemory, a different project, and anyone reconciling the two lists by name rather than by URL will merge them.nuster1128/MemEngineappears in the same table and earned no report: it has no persistence layer at all, as set out in the inclusion rule, and no licence file.- Oracle's
oracleagentmemorywas suggested for review and has no public source repository — a GitHub search returns only third-party demos consuming the SDK. It cannot be reviewed on this atlas's terms, which require inspectable code at a pinned commit, and is recorded here rather than silently omitted. Its design is now described in a paper — arXiv:2607.13157, Oracle Agent Memory as an Enterprise Memory Substrate for Long-Horizon AI Agents (Alake et al., 14 July 2026): a database-native substrate on Oracle Database with lifecycle-managed memory, an active/passive layered architecture with scope controls, and a reported 93.8% on LongMemEval at about 10.7× fewer tokens than a flat-history baseline. The paper is CC BY-NC-ND and ships no code, so the substrate stays uninspectable and the numbers are the vendor's own, unbacked by a committed artifact. - Agno was read, not run, and its 304 memory-related unit tests were
not executed. Three things a live install would settle: whether the
supersession judge's default threshold is calibrated against anything,
since no calibration was found; how often a typical deployment sets
background_executor, which decides whether extraction blocks the response path or not; and how oftenPROPOSEmode's prompt-level approval rule is actually followed, which is the number that decides whether the mode means anything and which nothing in the repository measures. Its two memory subsystems —agno/memory/andagno/learn/— overlap, and which one a given deployment is using was not established beyond noting that the AgentOS HTTP routes serve the older one. - Seven repositories submitted together on 2026-07-30 were
examined and every one is out of scope — the first batch this round to
produce no report, and instructive for why. Three of the seven
have "memory" in a file path and none of the three is agent memory. smolagents'
src/smolagents/memory.pydefinesAgentMemoryas asystem_promptplus alist[TaskStep | ActionStep | PlanningStep]withreset()andreplay()— an in-process run trace with no persistence layer, which is the call already made for Pi, OpenAI'sSQLiteSessionand LlamaIndex'sChatMemoryBufferfamily. It is named here rather than passed over silently because it is Hugging Face's framework and a reader searching this atlas for it deserves to find why it is absent.Elumenotion/GuideAntsexposes aMemoryToolsclass documented as "static semantic-memory tools", and its three operations areSearchProjectContent,SearchLocalContentandWebSearch— document and web retrieval with no store of agent belief behind it.genepattern/module-toolkit'stest_memory_spec.pyvalidates that a manifest'sjob.memoryfield reads like8Gbor4Mb: RAM allocation, the same false positive already recorded for the FRDCSA repositories. The remaining four have no memory concept at all —F-loat/panerelayrelays a browser to agents,ringlochid/banksiaruns multi-agent teams over aflowstable with norecall,rememberor long-term anything in the package,hamish-mackie/sloopgives each ticket a git worktree and an agent, andTheArtOfSound/qev-desktopis an encrypted vault format whose envelopes can hold "AI output receipts" — adjacent to Lethe's signed purge receipts in intent, and a container format rather than a memory system. The pattern is the point: the word memory in a path predicted the wrong answer three times out of three, which is the whole argument for reading code instead of file listings. - Six repositories submitted alongside TokenMizer and ZeroStack were
examined and have no reports.
Bino5150/lumina's memory module opens with "persistent memory across sessions via SQLite. Write-through to MemPalace on save. Flat table preserved for migration + fallback" — so its durable store is MemPalace, already reviewed here, behind a 291-line client with a flat-table fallback. It is the first system in the corpus whose primary memory is another atlas entry.octelium/cordiumis a Kubernetes sandbox platform for identity-based secretless access to infrastructure; it has no memory concept.faramesh/faramesh-coreand9hannahnine-jpg/arc-gateare both guards rather than stores — Faramesh is a policy daemon that permits, defers or denies each tool call against a declaredgovernance.fms, and itsMemoryBackendis an in-RAMStateobject for single-node deployments; Arc Gate is a runtime proxy whose purpose is preventing agents acting on hidden instructions. Neither durably holds anything an agent later retrieves as belief, which is the guard-is-not-a-store shape already recorded forCohexa-ai/agent-coherence.trumae/meiis a 209-line stateless C99 orchestrator that uses Fossil SCM as its single source of truth — the same instinct as GitLord, at a size too small to carry a mechanism.jaylfc/taOSis dual-licensed AGPL-3.0 and commercial, and itsuser_memory.pyis 193 lines over a base store; the one idea worth citing is its settings block, which lets a user togglecapture_conversations,capture_files,capture_searchesandcapture_notesindependently, so what is eligible to be remembered is a user preference rather than an extractor's judgement — a small instance of the who-decides divergence, at a scale that does not earn a report. - Four repositories submitted alongside Cortex, Mnemopi and agent-afk
were examined and have no reports.
omnigent-ai/omnigentmounts Hindsight as a built-in tool exposing its retain/recall/reflect operations, so its memory is a client for a system this atlas already reviews; the one detail worth keeping is that the memory bank is resolved per invocation from the agent spec, falling back to the run identity, so a single declaration isolates memory per agent.opsyhq/wolli(233 lines of session memory storage) andfischerf/aar(a 165-line session store) are both too small to carry a mechanism.Fagoon-AI/upgradewas read atf027d614and falls outside the inclusion test. ItsWorkflowMemoryis a message row —workflow_id,conversation_id,rolefrom a five-value set,content, metadata, an estimated token count and a TTL — and itsMemoryNodeoffers exactly six operations: add, get all, get, delete, prune and stats. There is no embedding, no vector, no similarity and no search anywhere in either file; the vector tables that migration creates belong toknowledgedocument, the RAG side, not to memory. So what survives a run is the transcript, listed by conversation rather than retrieved, and theconversation_idfield defaults to the execution id — one run. That is the call already made for Pi, for LlamaIndex'sChatMemoryBufferfamily, and for OpenAI'sSQLiteSession. The comparison worth recording is with CAMEL, which did earn a report on a similar-looking message store: CAMEL'sVectorDBMemoryembeds messages and recalls them by similarity across sessions, which is retrieval; this lists them by key, which is storage. The line between the two is one index. - Three repositories submitted in the same round were examined and
have no reports.
ahmadvh/octochainsis a framework for parallel isolated multi-agent reasoning whose stated premise is that shared chat history contaminates independent judgement — it has no memory concept because avoiding one is the design, which makes it the most pointed out-of-scope entry the atlas has recorded. Re-checked on 2026-07-31: every occurrence of memory in it is a patient's memory loss in a sample medical report, a PDF parser reading from memory, or GPU VRAM.aleloro-dev/agois a zero-dependency Go agent library with noMemorytype, no file writes and no database — nothing survives a run. Both are out of scope on their merits; the licence was never the operative reason and should not have been cited as one.Gitlawb/zerowas re-examined atd37de9214bafter growing to roughly 332,000 lines of Go since the earlier pass, and the earlier conclusion holds:internal/backgroundandinternal/swarmcoordinate work, and there is still no memory module. - A mark that was wrong, and how it was found. Mem0Sharp earned
audit_logon 30 July for a history table written only byINSERT. The atlas's Mem0 report, of the system that C# port reimplements, carried onlyscope_enforced— a divergence recorded the same day as a limitation rather than resolved. Re-readingmem0/mem0/memory/storage.pyat the pinned commit settled it: Mem0'shistorytable isid,memory_id,old_memory,new_memory,event,created_at,updated_at,is_deleted,actor_id,role, written only byadd_historyandbatch_add_history, with noUPDATEand noDELETEagainst it anywhere in the file. Mem0 was under-marked and now carriesaudit_log. Worth recording as a methodology note rather than a correction: the defect was invisible for two months and surfaced only because an independent reimplementation of the same design was reviewed and marked differently. A corpus wide enough to contain a system twice is a corpus that can check itself, and nothing in this atlas's process was doing that deliberately. ThunderAgent-org/ThunderAgentwas examined on 2026-07-31 at7ddc8610and is out of scope: it is an agentic inference scheduler, not agent memory. Three occurrences of the word memory in 3,361 lines, all three GPU capacity telemetry; no persistence primitive of any kind. It is filed under the KV-cache scope boundary rather than dismissed, because it is the clearest instance of that particular collision — an ICML Spotlight whose whole purpose is reusing an agent's state across turns, and which stores nothing.unibaseio/membasewas excluded here on licence grounds and has since been reviewed — see Membase. Its licence position is unchanged and stated in that report's first section:README.mdgrants MIT and links to aLICENSEfile that is not in the repository, so the grant is asserted and absent. That is a caveat for a reader, not a reason to leave the mechanisms unread, and the mechanisms turned out to be the point — the retrieval threshold selects the least similar documents, and deletion never reaches the vector index retrieval reads.- Five repositories named in a Reddit thread were examined on
2026-07-31; one became a report and the thread was wrong about
which. Graphify was
dismissed in that thread as one of the repos that "cut down how much has
to be remembered" rather than memory — and it carries the corroboration
gate, the decayed contested verdict and the re-hash-on-read staleness
check described above, so the dismissal was wrong at this commit.
DietrichGebert/ponytail, dismissed in the same sentence, was right: it is a single behavioural rule — write less code — compiled into fourteen-plus harness formats (.claude-plugin/,.cursor/rules/,.clinerules/,.kiro/steering/,.openclaw/skills/, and so on) with no store of any kind.kunal12203/graperootis the entry worth naming, because it is a new shape of the closed-source refusal: the repository is Apache-2.0 and contains launchers, a dashboard, benchmarks and thirteen translated READMEs, while the README states outright that "The graph engine (graperootpip package) is proprietary." Every previous refusal on this ground was for a hosted service; this is an open repository wrapped around a binary dependency, which reads as inspectable until you look for the mechanism.ArtKeyAi/bhived-mcp— the MCP server behind thebhivedproduct placement in the same thread — is Apache-2.0 and 8,315 lines of TypeScript that contain no memory mechanism at all:restClient.tsposts to/v2/queryand/v1/memoriesagainsthttps://mcp.bhived.ai, and the open part is transport, formatters, an agent-config installer and a subscription check.omnigent-ai/omnigentwas already examined and recorded above on 30 July; re-reading it at18fcf67dchanged nothing, and its own store —conversations,conversation_items,agents,files,policies,session_permissions— still has no memory table, its 83 files matching remember being the "don't ask again" permission rule. See the thread note for the rest of that triage. rahvis/cognitive-weavewas examined and has no report, and it is the sharpest instance yet of a published number with nothing behind it. The repository presents itself as "the official implementation" of arXiv:2506.08098, whose abstract claims "a notable 34% average improvement in task completion rates and a 42% reduction in mean query latency when compared to state-of-the-art baselines" — measured, per its section 4, against Standard RAG, MemGPT, A-MEM and Mem0 on Robotouille, Evolving-QA and LoCoMo, with human judges on a Likert scale. It is excluded on the ordinary ground rather than that one: nothing survives the session.main.py:39declaresself.memory_store: List[InsightParticle] = [], the chat loop appends to it, and grepping the tree foropen(,json.dump,sqlite,pickleandwrite_textreturns nothing — the same call already made for Pi, LlamaIndex'sChatMemoryBufferfamily and OpenAI'sSQLiteSession. What makes it worth recording is that the repository says so itself: "Implement memory persistence layer" and "Implement full STRG (Spatio-Temporal Resonance Graph) structure" are both unchecked items on its own To-Do list, and STRG is the mechanism in the paper's title. 568 lines of Python across five files, one empty; retrieval is set-intersection over a stopword-filtered bag of words falling back to the most recent particle;relational_strands,access_frequency,importance_scoreand two of three timestamp fields are declared and assigned nowhere; there is no dataset, metric, result or test anywhere in the tree. This does not establish that the experiments were not run — they may have used a fuller implementation that was never released. It establishes that the figures cannot be checked against the artifact published as their implementation. The licence is asserted in the README and theLICENSEfile is absent, as with Membase. No commit since 5 August 2025. See the note for the component-by-component comparison against the paper.- VISTA was first examined from its published traces alone, a
month before its source was released, and that reading is the corpus's
best argument that a trace can stand in for source. VISTA is a
visual harness from five MIT authors, posted 5 August 2026 with no
harness source at any commit, reporting all 25 public ARC-AGI-3 games
won with a perfect efficiency score. Its memory design is three-part —
raw frames as observation, two markdown notes, and a "lossless
visual memory" holding every frame the environment returned,
recalled through
inspectandread_pixelson the model's own decision. The page shipped 320 MB of per-game run traces recording every message, every region inspected with the question that motivated it, and every memory write with its full content — enough that the entire memory surface was reconstructed without the implementation: two files, 260 writes, full-document replacement in 215 rewrites and not one append, a median note of 1,320 characters. The headline claim recomputes from the same files: 25 of 25 runs carrystatus: "WIN", every scorecard readsscore: 100, andlevelsCompleted == levelCountthroughout. Set besiderahvis/cognitive-weavein the bullet above — examined the same day, claiming 34% and 42% over MemGPT, A-MEM and Mem0 with no dataset, metric or result committed — the two mark the ends of the axis the benchmarks page exists to measure, and the difference is not rigour of prose but whether the evidence was published. See the note, including the check that a cheap reading of the note rewrites would have produced a finding that inspection does not support. The source followed on 5 September 2026 atjoshhhhhan/VISTA, and VISTA is read from it at900aa338…. schema-harness.github.iowas examined and has no report: it is an ARC-AGI-3 harness with no source at any commit. A project page from Impossible Research, Berkeley and CMU, examined on 6 August 2026 beside VISTA, Tycho and Retrodict, which have reports since 18 September (VISTA, Tycho, Retrodict). It describes a model-authoredworld_model.pybeside an append-only timeline — the split the four share, an append-only record the model did not author with a small belief file subordinate to it, written up under Research lineage — and claims "~99%" with no scorecard; its per-run traces are published as a dataset. See the note.shepherd-agents/shepherdwas examined and has no report, and it is the cleanest instance yet of the harness-is-not-a-store boundary. MIT, 120 commits since 25 June 2026, with a paper (arXiv:2605.10913): a runtime substrate that records agent runs as "durable, inspectable" reversible traces so meta-agents can observe, fork, replay and revert a run, with a copy-on-write environment fork it reports at ~5x faster thandocker commitand ~95% KV-cache reuse on replay. Everything about that description sounds like memory — durable, versioned, revertible state — and none of it is. Grepping the tree forrecall,remember, belief, semantic memory or long-term memory returns nothing; the only file namedmemory.pyiscommons-vcs/src/commons_vcs/backends/memory.py, an in-RAM VCS backend. What it durably holds is execution trace events, substrate state and checkpoints — a phase, a fork point, a replayable transcript. That is workflow control state, and the test this atlas applies is whether the stored thing is a claim that can be true or false and therefore corrected; a checkpoint cannot be wrong, only stale. Same call asshowjihyun/bvwebchat's harness and the KV-cache boundary above, and worth recording because the vocabulary overlaps almost completely with a memory system's while the subject matter does not. Its reversibility work is genuinely relevant to memory systems with restartable background passes — the read-generation fence question recorded underCohexa-ai/agent-coherenceis the same shape — but a reader looking for agent memory here will not find it.agent-substrate/substratewas examined and has no report: it persists an agent's process, not its memory. Apache-2.0 (the stock text, no rider), Go, 1,743 commits since 13 May 2026, at4b57dfcb…. It is a Kubernetes runtime that multiplexes sandboxed "actors" onto a small pool of gVisor or Cloud Hypervisor workers, suspending an idle actor to a snapshot in GCS or S3 and restoring it on the next request. What survives is a gVisor checkpoint of the process tree or a microVM memory image, plusDurableDirvolume and rootfs bundles (docs/concepts/architecture.md,api/ateapi/v1/ateapi.pb.go:3949). That is the boundary drawn forshepherdabove: opaque bytes under a snapshot id, which can be stale and cannot be wrong, and nothing in the tree reads them as a claim, retrieves them by content or corrects them. Agent memory appears once, in a load profile:internal/benchmarking/boomer/agentsession/scripts/personal-assistant.yamlmodels a "remember that" request as a 2 MiBwrite_diskand a recall question as a disk read, which is all the runtime sees of a memory system running inside an actor. A store inside a hosted agent survives hibernation intact, so the project bears on deploying the systems reported here and not on their mechanisms. Searched at the pin:git grep -l -i -E 'embedding|recall|remember|vector store|knowledge base|long-term memory|agent memory|memory store' -- . ':(exclude)vendor' ':(exclude)_LICENSES'matches 22 files, every hit an infrastructure comment, a fake node registry in a benchmark, an in-memory test store, an operator doc or one of the two load profiles. Screened before reading, from a shallow clone: no auto-run surface, 27 build-time execution points of which 26 are vendored Makefiles, six unpinned dependency surfaces underbenchmarking/andsite/; nothing was installed, built or run.avarshvir/oxygenwas examined and has no report: it stores nothing at all. Apache-2.0, 486 lines of Python, 39 commits since 24 August 2026, at0a65d56b…. It is a LangGraph pipeline of five role-specialised agents — project manager, researcher, developer, tester, technical writer — driven over a WebSocket, with a human approval gate before code generation. The scope call takes one file:backend/state.pyis aTypedDictholding messages, the LLM config, the requirements, proposal, source, test results, documentation and five UI status strings, and the onlyjson.dumpin the backend writes to the socket. No database, no file write, no store; nothing survives the run. The approval gate is worth naming because it is the thing a reader might mistake for the human review mark.approval_routermatches the user's message against a list —accept,approve,looks good,ok,proceed,yes,go ahead,sure— and routes the graph. A person is approving a proposal inside a run, not adjudicating a stored claim, and the two are different surfaces however similar the word is.arXiv:2608.25593andbingreeky/JITwere examined together and have no report, and the one thing in the paper that persists across tasks is the one thing the release leaves out. JIT-Agent: Scaling Harness Intelligence via Just-in-Time Harness Evolution (26 August 2026; Zhang, Lu, Xie and thirteen others) trains a 27B model to write an agent harness per task — memory, planning, action and capability orchestration as four Python files plus a prompt — for any off-the-shelf executor, and the repository is MIT, three commits over two days, atababa06c…, with the checkpoint and the training set on Hugging Face. Screened before reading: no auto-run surface, nothing inside the cooldown, three unpinned requirement files; nothing was built or run. The memory module is the boundary this atlas draws for SKILL.state and Self-GC, and the code says so in its own terms:BaseMemoryis an "inside-trial working memory manager" whoseinitializeis "called once at the start of each run" and whoseupdatemay "store, compress, summarize, or fold the step" (scripts/kernel/protocols.py:16-56). The eleven seed implementations span the whole conversation-window repertoire — full history, ReSum-style summarisation at 90% of the context, HiAgent's value-scored sampling with[Omitted]placeholders, MemoBrain's reasoning graph, GAM's memory pages, AgentFold's folding — and none of them writes a file; a grep ofjit/,harness_factory/andscripts/forjson.dump,sqlite,pickleandwrite_textfinds only run reports, traces and the best-of-N selection record. What the paper says does persist is a harness bank: each entry (task, harness, metrics) with reward, latency and cost, a candidate "retained only if it matches or exceeds the current reward frontier and then strictly improves at least one frontier dimension", a reference set retrieved from it per task, and a streaming mode in which "harnesses keep improving at test time while the generator itself stays frozen" — the README's phrase. In the tree,HARNESS_BANK_DIRisharness_factory/harnesses/, the eleven hand-written seeds; the reference set is either the full description catalogue or three seeds drawn byrandom.sample(jit/meta_agent.py:230-240); nothing writes a generated harness back, no metrics are stored beside one, andfrontier,incumbentandstreamname nothing in the source. The archive that makes the paper's title an evolution is an experiment the release does not ship, so on its own artifact this is a per-task generator with a fixed seed bank. Two further gaps between paper and tree: Table 2 lists thirteen seed harnesses and the tree holds eleven, ReAct and AOrchestra absent; and the training pipeline — supervised fine-tuning, repair-trajectory imitation, and a group-decoupled policy optimisation over reward, latency and cost — is described and not released, though the data it consumed is. The discipline worth carrying out is in the runner: a harness is regenerated only when execution raises, and "a harness that merely scores low is never repaired, since that would be optimising against the benchmark" (scripts/run_jit.py:310-312); the seed baselines are run withmax_repairs=0so the number describes the harness as written. The benchmark adapters, configs and task data ship in the repository, so the instrument is reproducible; no result file or run trace is committed, so the numbers are not. Placed on the benchmarks page beside the Binding Constraint Thesis, whose controlled comparison its Table 4 is.zvec-ai/zvec-grepwas examined and has no report, and it is the corpus's cleanest case of a store that can be stale and cannot be wrong. Apache-2.0, 38,327 lines of TypeScript undersrc/with 19,890 lines of tests, 229 commits since 10 July 2026 from eight authors,v0.2.1tagged 1 September 2026, read at81a80f47…. Screened before reading: no auto-run surface,package.jsonand its lockfile changed inside the seven-day cooldown, fifteen floating ranges under a lockfile; nothing was installed, built or run. It is a local-first search layer over a workspace — ripgrep, BM25 and vector search behind one CLI and one loopback MCP endpoint — built to be handed to a coding agent, and it never calls itself memory: a grep ofsrc/forremember,forgetandmemorizefinds nothing, and everyrecallis a per-candidate retrieval trace. What it persists is a derived index of the workspace's own files, under<root>/.zvec-grep/: afiles.zveccollection keyed onfile_idcarryingcontent_hash,last_modified_time,indexed_timeandentity_ids_json; anindex.zveccollection of fragments with a jieba-tokenised FTS field and an HNSW vector; and amanifest.jsonwritten at mode0600because it may hold an embedding API key (src/engine/storage/zvec.ts:593-643,:891-944;src/engine/manifest.ts:12,:40-47). Nothing an agent says enters that store. The default MCP toolset registers one tool,zvec_grep_search; thefulltoolset adds five, and none of the six takes content to keep —zvec_grep_indextakes a root and re-reads the files (src/mcp/tools.ts:327-633). The one epistemic state in the system isfresh/possibly_stale, computed per hit by comparingindexed_timeagainst the file's mtime and then its SHA-256 againstcontent_hash(src/engine/service/zvec-grep.ts:2141-2166), and per search from whether the watcher has pending events or a known-change job is queued (src/daemon/backend.ts:557-562). That is the whole of what can go wrong with an entry, and the repair is the read that built it: a watcher with a 750 ms debounce and a 5 s ceiling, a full reconcile every hour and after a 90 s gap in the clock, bursts above 1,000 exact events widened to directory scopes rather than escalated to a rescan, and acomputeDiffFromFilesthat promotes a file from unchanged to modified only when size, mtime and then content hash all disagree (src/daemon/watch-manager.ts:65,:124,:198,:204;src/daemon/change-set.ts:28;src/engine/pipeline/indexing/index.ts:647-698). A stale fragment is not a false belief; it is a cache miss wearing a status label, which is the line the KV-cache entry draws — a loss that costs latency rather than correctness — and the committed BrowseComp-Plus report prices the latency: 9,721 seconds and 7.9 GB to rebuild the index for 100,195 documents. The integration suite's stale-record case asserts the same thing from the other side — afterrm(goodPath)it checksfilesDeletedis 1 andfilesIndexedis 1, counts on the index, and never searches for the deleted file's needle, because there is no reader for whom its absence would be a correctness claim (test/integration/service.test.mjs:386-469). Two things transfer to memory systems anyway. The remote-embedding consent surface is the one to copy. A search or index that would send text to aqwenprovider is first planned into a disclosure —queryTexttrue or false,workspaceContentofnone,changedorfull— and, absent a standing grant, the MCP server answers withinputRequiredcarrying a signed, single-userequestStateand a form offering allow once, allow for this workspace, use FTS only or cancel, defaulting to cancel; a workspace grant is HMAC-SHA256-signed with a key at~/.zvec-grep/authorization-signing.key, fingerprinted on the canonical roots, provider, model and endpoint, and kept in the workspace's own.zvec-grep/authorization.json(src/authorization/planner.ts,src/authorization/store.ts:46-94,src/mcp/tools.ts:694-825). A memory system that ships its embeddings to a hosted provider faces the same question about the memories themselves, and the shape here — a plan that names what leaves, a default of refusal, a grant bound to a fingerprint and signed by the machine that made it — is the answer. AndtrackEntityIdforces a named entity into the candidate set and records, per route, why it did not come back — "Target entity did not match the FTS query", "Target entity file was excluded by the path filters", "Target entity could not be scored by vector search" — a per-miss retrieval diagnosis of the kind the benchmarks page asks memory systems for and one repository there supplies (src/engine/pipeline/search/index.ts:761-968). Its own benchmarks are read on that page: of two, one commits its run report and one exists as string literals in an SVG generator. The exclusion will not reverse on a release. A search index becomes memory only by storing something other than the files it indexes, and the roadmap's four directions — more formats, graph retrieval, a GUI, mobile — add none.robert-mcdermott/ai-knowledge-graphwas examined and has no report: it is the extraction half of a graph memory, run once, with no reader. Apache-2.0, 2,040 lines of Python, 64 commits from 22 March 2025 to 27 December 2025 by three authors, read at40b70197…; tags0.6.1,0.6.2and0.6.3all carryversion = "0.6.1"inpyproject.toml. Screened before reading: no auto-run surface, no build-time execution, no unpinned manifest,uv.lockunchanged for 478 days; nothing was installed or run. The pipeline is a CLI that takes one text file, splits it into 100-word chunks with a 20-word overlap, asks an OpenAI-compatible endpoint for lower-cased subject–predicate–object triples with predicates of three words or fewer, standardises entity names, infers further edges, and writes one JSON file and one HTML page (src/knowledge_graph/main.py:195-276). Nothing reads the JSON back butjson_to_html.py, which re-renders it —rg -n 'json.load|read_json' src json_to_html.pyfinds that one call — so there is no query, no merge of a second document into a first, no scope, no correction and no deletion: the graph is an artifact, not a store, and the word memory does not occur in the code. Two things in it are worth carrying to the graph-memory systems that do keep a store. First, the one epistemic distinction it makes is stated versus inferred: every edge the inference phase adds carriesinferred: True, drawn dashed and filterable in the page (src/knowledge_graph/visualization.py:109-120,templates/graph_template.html:724-727), and the README's own run says what that flag hides — 209 stated edges and 355 inferred of 564, so 63% of the delivered graph is the inference phase's. Second, where those edges come from: transitive composition mints a predicate from the path (A → B → Cbecomes<pred> via B,entity_standardization.py:344), so the run's second and third most common relations are "advances via Artificial Intelligence" and "pioneered via computing"; and lexical similarity mintsrelates to,related tooris type ofbetween any two entities that share a word of four letters or more or contain one another (:708-749), which is where the run's most common relation, "related to" at 65 occurrences, comes from. Standardisation collapses entities whose first-four-letter stems overlap by more than half (:141-151). None of this is wrong for a visualisation; every one of it would be a false belief in a store an agent recalls from, and a system that borrows this extraction stage inherits the flag and nothing behind it. Two smaller notes: the console line "Added -22 inferred relationships" in the README islen(filtered) - len(triples)printed after deduplication and self-reference removal (:270), and the README's configuration block sayschunk_size = 200andtemperature = 0.2whereconfig.tomlsays 100 and 0.8. This exclusion will not reverse on a release: a store and a reader would make it a different program.- IEEE Xplore document 11554177 was examined and has no report: its agents are reinforcement-learning controllers, its trust is a float, and it releases no code. Adaptive Federated Learning for 6G: A Multi-Agent Architecture for 6G Edge Intelligence (Das, Ali, Pirbhulal, Aloi, Pace and Sodhro; IEEE Network, early access, inserted 8 June 2026, doi:10.1109/MNET.2026.3694694, CC BY 4.0, eight pages, in the magazine's Agentic AI for Next Generation Wireless Networks section — which is the likeliest reason it reached a memory atlas). It proposes MAAFL-6G, a device–edge–cloud hierarchy of agents running a PPO variant (H-MAXPPO) to decide federated-learning participation, training depth, compression and aggregation under battery, link and attack conditions, and reports 99.8% reliability, 0.48–0.55 s latency and 0.0175–0.0195 J per task against re-implemented baselines on twelve simulated runs of fifty clients over three edge nodes, driven by an IEEE DataPort smart-home power-trace dataset. The inclusion test is not close. The agents are policies whose state lives in network weights — the boundary the KV-cache entry above draws, on the model-internal side; the text's "policy repository" and "model repository" are stores of weights. Its trust score is the rubric's counter-example in one sentence: "T_i(r) is the device trust score (higher values indicate more reliable and consistent behaviour across rounds)", a float that enters a device's utility argmax and weights aggregation — a number used for ranking, never a state that withholds anything. Over the 5,437 words of the paper, memory, remember and recall occur zero times, agent 50 times, and GitHub, source code and available zero: no repository, no data-availability statement, and the baselines "were independently re-implemented following the algorithmic descriptions in the cited literature", so nothing here is checkable against an artifact. Recorded so a future search for the id finds a judgement rather than a gap; it would not become a memory system with a release.
arXiv:2609.00829was examined and has no report: it releases no code, and the harness it evolves is a store of falsifiable edits with two gates in front of it. HarnessEvolve: Learning from Reference Trajectories for Reliable Agent Self-Evolution (Jiang, Chu, Tian, Zhang, Yang, Yang, Liu, Lv and Li; Huawei ICT AI Competence Center, Shanghai; submitted 1 September 2026, preprint) optimises an agent's harness — prompts, skills, tools and execution logic — with four decoupled agents. An execution agent runs the training tasks; an evaluation agent marks failures and vets reference trajectories — runs given the ground-truth answer, cached only when they reach it through tool calls rather than by restating it; an optimisation agent compares each failure against its reference to find the first divergent action and clusters error signals by cause, preserving single-member clusters; and a gate agent applies two checks before an edit enters a snapshot pool. The quality gate scores each edited file for whether the failed queries and their answers were written into it (LLM-as-judge, rejected above 0.8) and counts injected in-context examples (rejected above five), returning a rejection reason for up to three revisions. The performance gate accepts a candidate only if it does not fall below the current harness on the current batch — the margin δ is set to 0.0 — and loses no more than 2.5 points on either of the two previous batches; the epoch's best snapshot on a held-out set becomes the harness. Five benchmarks: two in-house (CloudCoreNetwork-QA, Wireless-QA) on an in-house framework (LAMAgent) with a domain-fine-tuned Qwen3.6-27B, three public (SearchQA, OfficeQA, SpreadsheetBench) on OpenClaw with DeepSeek-V4-Flash, where the harness is the skill directory,AGENTS.md,SOUL.mdand tools. An ablation on the in-house set puts the reference trajectories at 29.1 points, the clustering at 18.3 and the quality gate at 6.8. Over 7,260 words of extracted text, GitHub and source code occur zero times and available six, every one about reference trajectories; there is no data-availability statement, so the in-house half is unrepeatable and the public half uncheckable. With a release it would be screened like any skill-evolution repository, and two things would be read first. Askill.mdedit is a claim that can turn out false, and the gates are the shape this atlas asks of any promotion path: the quality gate is a leakage check on a learned artifact — that the optimiser embeds training answers when nothing stops it is what the 6.8-point ablation measures — and the performance gate, as parameterised, admits a tie and bounds regression over two batches only, so an epoch of accepted no-loss edits can drift past the tolerance with only the held-out selection to catch it; the bloat bound is five examples per accepted edit, not per harness. And the abstract's "consistently outperforms state-of-the-art baselines across all benchmarks and settings" is a claim about Tables 1 and 2; the transfer table beside them reads 95.0 to 95.0 on one cell, which the text calls "improve or maintain."SKILL.statewas examined and has no report, and the boundary is the same one Self-GC draws. SKILL.state: Scalable Long-Horizon Agent Skills (arXiv:2608.26263, 26 August 2026; Badhe, Tiwari and Chung, accepted at EMNLP) replaces an append-only conversation history with "an explicit, mutable execution state": at each step the model gets the immutable skill specification, the current state and the latest observation, and "intermediate reasoning is discarded immediately after producing a validated state update." The state is within-run — across InterCode CTF it is a five-field schema (discovered_flags,tested_hypotheses,active_files,working_dir,cmd_summary) merged byΣₜ₊₁ = Σₜ ⊕ ΔΣₜwith null-deletion — and nothing in the paper describes a durable store or anything surviving a run. No code is released. Two things transfer anyway. Schema ownership and validation "reside in the deterministic runtime rather than the model," so a malformed patch triggers a rollback-retry rather than corrupting the state — the code-owns-the-structure rule this atlas keeps finding, applied to state transitions. And the recovery experiment measures something memory systems are rarely asked: after a corrective observation, a mutable state needs zero recovery steps because the wrong value is overwritten, where an append-only history leaves the correction sitting after the claim it corrects. How long a wrong belief keeps being acted on after it has been corrected is a measurable quantity, and this is the clearest instance of it being measured.WikiSkillwas examined and has no report, and its ablation is the finding. WikiSkill: Compiling Agent Experience into Persistent Knowledge for Skill Evolution (arXiv:2608.27454, 27 August 2026; Tang, Rashtchian, Ferng, Tomkins, Juan and Vu) separates raw execution experience, accumulated knowledge and executable skills, consolidating experience into a wiki that later skill updates build on. It is in scope as a design and gets no report for the ordinary reason: no code is released, so there is nothing to read at a pinned commit. Two of its results are worth carrying. The ablations "confirm that persistent knowledge accumulation in the wiki is critical for effective skill evolution" — the memory measured by removing it, which is the rule the benchmarks page keeps arriving at. And skills transfer across models and families, with "skills evolved by other models" sometimes beating self-evolved ones, which makes the accumulated knowledge an artifact separable from the agent that produced it. Read beside OpenKB, which ships the same compile-experience-into-a-wiki idea as a CLI in the same month, with no connection between the two projects.Self-GCwas examined and has no report, and the authors draw the same boundary this atlas does. Self-GC: Self-Governing Context for Long-Horizon LLM Agents (arXiv:2607.00692, 1 July 2026, Xiaohongshu) turns a run's user turns, tool spans and skill state into indexed objects and has a side-channel planner propose fold, mask and prune actions over them, which the harness rehearses and commits only at a safe turn boundary. It governs the active context of a run; the full transcript stays outside that view, and the paper positions the work as "complementary to memory-store methods" rather than as one. Nothing it holds is a claim that could turn out false, which is the test, and no code is released. Two things in it are worth carrying and are traced in benchmarking agent memory. Its no-impact rate asks whether a pruning destroyed something the real future turns needed, judged against those turns with the removed content shown to the judge and withheld from the system under test, reported with Wilson intervals and calibrated on the cases where the judge disagrees with itself. And its planner is told never to compress the latest user turn, audited at 25/330 parsed plans violating that instruction for one backbone, and then overridden in the harness — "the prompt usually works, but the residual risk justifies mandatory last-turn protection" — which is this atlas's most repeated finding reached by measurement.munch2u-a11y/FP-AMBwas examined and has no report, because it is a benchmark rather than a memory, and it is the most useful negative result this atlas has read in one. MIT, 4,416 lines of Python, 24 commits since 26 August 2026, atc7516f36…. It stores nothing durable of its own: a provider implementsingest_turnandretrieve_context, and FP-AMB scores it over 60 sessions, 679 turns and ~512,889 tokens across ten categories. Same boundary as any harness. What earns it a paragraph is that it ships four committed scorecards and the winner is the TF-IDF baseline — 69.7% against real mRAG at 66.6%, the author's own vendored Fractal Memory at 50.2% and MemPalace at 36.1%, with per-question*_misses.txtfailure taxonomies beside each. A benchmark author publishing their own system third, behind a lexical baseline that answers in 3.1 ms against Fractal's 37.9 seconds, is the opposite of the vendor benchmark this atlas usually finds. Two defects in it are worth carrying and are traced in benchmarking agent memory: the Unanswerable & Absent Memory Refusal category scores 35/35 for all four providers because its predicate cannot fail, and the Fractal run is scored over 281 questions where the other three are scored over 262, so those four percentages are not means over one exam. The README's own comparison table lists only the three that share the 262-item exam.os-factory/harwas examined and has no report, and it is the same boundary carrying the atlas's rarest mechanism anyway. Apache-2.0, read three times, most recently at release 1.0.0,3eec6453…: a harness that gives each coding agent its own git worktree, ports and database, runs the project's own checks through one pipeline, and keeps the evidence. The scope call is settled by its schema —control/prisma/schema.prismaheld still through the first two readings and grew by one model at 1.0, thirteen Prisma models covering repositories, slots, sessions, spans, runs, work units, attempts, validation bindings and change batches, and across 16,277 lines ofsrc/the wordsrecall,remember,forget,embeddingandvectorappear twice, both incidental. Nothing stored is a claim that could be false; the intervening work is plugins (Semgrep, Trivy, Gitleaks, Kerno), docs, iOS fixes, node provisioning, a two-signal drift model separating user-edited from upstream-updated, and a 1.0 release turning.har/into a configuration surface — none of which touches the durable-belief question. What makes it worth recording is one of those twelve.UnregisteredRepositoryis a rejected-value tombstone in a repository registry:deleteRepositorywrites the path into it before deleting the row,registerRepositoryconsults it on every write and refuses with a 409 unless the caller passesforce: true— and the client handles that 409 by dropping the path from its own local registry so auto-sync stops re-asserting it, which is a step past where the tombstones in the corpus stop. The failure it closes is the one the pattern page names, a background pass re-reading an unchanged source and restating what a person deleted, and it is keyed on a filesystem path rather than on a natural-language claim, so it never meets the normalization problem that defeated two implementations here. Its mechanism (control/src/server/repositories.ts) is byte-identical since the first reading, but the gap named then has closed: the tombstone is now tested, by three files that did not exist at the earlier commit —tests/control-sync-unregistered.test.tsasserts the client drops the path from its local registry on a 409, andcontrol/src/app/api/repos/route.test.tsasserts the server returns the 409, in a tree grown to 94 test files and 11,893 lines. Two neighbouring mechanisms are recorded in the note: a validation record filed under the hash of the working tree it certifies — so it invalidates itself on any edit, with no expiry column, decay policy or revalidation sweep, and withvalidations/gitignored so writing the record cannot perturb the hash it is filed under — and a propose-review-apply gateway overAGENTS.mdwhose merge refuses when content outside the managed markers would drop below 90% of its non-empty lines, a governed write gateway with a floor on how much a regenerating writer may delete. The self-invalidating key is the one a memory system cannot copy and should read anyway: bi-temporal validity, decay and re-verification exist because memories are keyed by subject rather than by content, and this is what the alternative buys. At 1.0 the schema moved for the first time across these readings, and the scope call survives it. Eighty-one commits addedAgentTrajectoryRecord— a thirteenth Prisma model holding one row per agent trajectory event, uniquely keyed on(repositoryId, source, sourceEventId, contentKey)— and aharvestVersioncounter onAgentSessionUsagewhose comment marks the generation behind a row ("0 = pre-dedupe, reads high"), so counts written by an older harvester are legible as overcounted rather than silently wrong. A trajectory event is still a record of what happened, so none of it is a claim that could turn out false. What is worth carrying is the disclosure class. Every trajectory row is stamped at ingest bycanonicalContentDisclosurewith one offull,truncated,withheldormetadata_only, andserializeTrajectoryForEgressapplies it on the way out — the API route that returns trajectory records maps every row through it — withtrajectory-privacy.tsredacting secret-looking attribute leaves by regex beside it. A per-record classification of how much of it may leave, enforced on the read path rather than at the point of collection, is a shape a memory system with mixed-sensitivity records could take directly, and this atlas has not found it in one.MoonshotAI/kimi-codewas examined and has no report, and it is the clean contrast to a system the atlas does have one for. MIT, ~410,000 lines of non-test TypeScript across seventeen packages, at13d86f8b…. The vocabulary reads like a memory system —memory585 times,persist272,compaction1409 — and every surface traces to something else:agent-core-v2/src/agent/contextMemory/is per-agent conversation history withappend/applyCompaction/undo, i.e. window management; sessions persist towire.jsonland aminidbquery store for replay and resume, i.e. session state; andAGENTS.mdis generated once by/inithanding a brief to acodersubagent and then read back into the system prompt, i.e. instructions.minidbitself is a real embedded database — WAL, generation checkpoints, a trigram text index — but it exists to index sessions, not to hold beliefs. What makes it worth recording is that it has cross-session full-text search and it is the user's, not the model's.kap-server/src/searchis anIGlobalSearchService— "cross-session full-text search over user messages, assistant text and session titles, backed by a single minidb database" — with a background sync coordinator and published index generations, which is the DeepSeek Harness shape exactly. DSH is in the atlas because it registerssession_searchand four siblings as model-facing tools (unmounted by default, but the model is their caller). Kimi Code's search lives in the app server for the UI, and the agent's own tool registry —agent,ask-user-question,cron,edit,fetch-url,goal,os,read-media-file,select-tools,skill,task,todo-list,web-search— contains no memory, recall or session-search tool at all. The human can search their past sessions; the model cannot. The line between a searchable session corpus that is agent memory and searchable session history that is a product feature is exactly whether the model can query it, and these two repositories sit on opposite sides of it with nearly identical machinery underneath. Same boundary asos-factory/harandUntrivial-ai/agent-orchestrator; details in the note. If a release exposes session search or aremember/recalltool to the model — the "graduate into agent-core-v2" the search service's own comment anticipates — the scope call flips.cline/clinewas examined and has no report, and the finding is where its memory turned out to live. Apache-2.0, re-checked at8bbdde2a…. Memory Bank — six markdown files (projectbrief.md,productContext.md,activeContext.md,systemPatterns.md,techContext.md,progress.md) that the agent reads at the start of a session and rewrites at the end — is the most frequently cited long-term memory in coding agents, and the repository describes it in its own words as "a documentation methodology". Grepping the whole checkout formemory.bankormemorybank, case-insensitively, returns two files, both underdocs/: the page itself and the navigation entry listing it. Nothing insdk/,apps/orevals/mentions it, its setup instructions are to paste custom instructions into.clinerules/memory-bank.md, and the tool executors arebash,editor,file-read,search,apply-patchandweb-fetch— so the mechanism is a prompt plus ordinary file editing, with git as the only durability guarantee. That is worth stating precisely rather than dismissively, because it is memory as an editing surface with nothing behind the surface, and the properties it does get — diffable, reviewable in a PR, correctable in an editor, portable to any agent that reads files — are ones most stores here do not have. What it cannot do is consult itself before a write: nothing records that a claim was rejected, so a deletion survives only until the next update pass re-derives the same file. What Cline persists durably is the run — session versioning,checkpoint-diff.ts/checkpoint-restore.ts, and a.clineconfig tree of rules, skills, workflows, agents and hooks beside anAGENTS.md. Details in the note. That exclusion named the condition that would reverse it — Memory Bank becoming a store consulted before a write — and the condition was tested a week and roughly a hundred commits later: the same two documentation files, and the only othermemorpaths are a process-RSS logger and anInMemoryStateAdapterholding maps withexpiresAtfor the life of the process.integry/proprwas examined and has no report, and it is the corpus's cleanest case of an index that is built not to be memory. Apache-2.0, atd537c25e…, 4,280 commits — a self-hosted platform that runs coding agents through the GitHub pull-request workflow, from labeled issue to reviewed PR, in containers on the operator's own server. Twenty-five tables, and they sort into three piles with nothing left over. The run:tasks,task_history,task_drafts,plan_issues,llm_executions,llm_logs,usage_metric_records— the LangGraph-checkpointer boundary. Configuration and people:repositories,system_configs,instance_members,instance_role_audit, plusrepo_todosandrepo_chat_messages, which are human-authored. A summary index of the user's source:file_summariesanddirectory_summaries, LLM-written, one row per path. That third pile is where a memory system would be if there were one, and the invalidation is the reason there is not.file_summaries.commit_hashholds the git blob hash of the file's content, andidentifyStaleFiles(packages/core/src/services/relevance/summaryMinerStaleness.ts) reprocesses every path whose stored hash differs from the current blob and deletes every row whose path is no longer in the tree;directory_summaries.hashis a composite over its children, so a change propagates up. Reads are branch-scoped. The mechanism therefore enforces that the index is a pure function of the checkout — it cannot outlive its source, and a wrong summary is not corrected but regenerated from the file that produced it. That is the sharpest statement of this boundary the corpus has: an entry that a hash can prove stale is not an entry that can be believed, and the systems this atlas reports on are exactly the ones where no hash can settle the question. Nothing in the tree learns across tasks — 296 test files, six touching the summary miner, and no store of lessons, rejected approaches or accumulated preference. Propr enters the day a review finding outlives its pull request as a claim a later task must consult.gromhacks/bonsai-ninjawas examined and has no report, and it supplies the half of the argument above that Propr cannot. MIT, 443,026 lines of Rust across 626 files in 46 crates, 492 commits since 5 May 2026, ata118e6a0…— a local compiler-style static-analysis and code-intelligence engine over twenty language front-ends, which sells itself to agents in this atlas's own vocabulary: "Give agents facts, not file dumps", the smallest useful slice of a repository instead of repeated reading. It durably persists a great deal — an on-diskfactstorewith its own wire format and string pool, content-addressed compiler objects under<workspace>/.bonsai/, an LRU in front of the reader — so it reads as a candidate until the acceptance predicate is read. A cached compiler object is used only when five things match: the workspace-relative path, the selected language, the source digest and source hash (metadata_for,crates/db/src/compiler_object.rs:672), the metadata version, and the frontend semantic ABI (:645,:649), with a sixth check on the pipeline fingerprint. The fifth is the one Propr does not have.COMPILER_OBJECT_CACHE_VERSIONstands at 90, and above the constant are sixty hand-written changelog lines saying what each bump makes stale — v90's names the exact Swift conditional-cast form whose v89 objects "can retain a grammar diagnostic and omit the cast operand from exact value flow". Propr's blob hash enforces that an entry cannot outlive its source; this enforces that an entry cannot outlive its producer either, and states per version what a survivor would have got wrong. Together they are the complete statement of the boundary: a derived entry is discardable exactly because two hashes can prove it stale, and the systems this atlas reports on are the ones where no hash over the inputs settles whether a remembered claim is still true. The finding side settles it a second way. Security results carry SARIFfingerprintsandpartialFingerprints(crates/security/src/report.rs) whose stated purpose is that someone else's system can match findings across runs — the rule id is the sink rule rather than the CWE precisely because "GitHub code-scanning groups by ruleId; using the sink rule gives us per-rule baselines and suppressions". The triage verdict, the thing that would be a durable correctable claim, is deliberately held by the consumer. Nothing in the tree stores a judgement of its own; the single human-authored durable artifact is<workspace>/.bonsai/rules/, a project-local rulepack layered over the bundled one, which is configuration in the sense a linter config is. Its own README leads with a maturity warning — parser gaps, unresolved dynamic behavior, incorrect findings — and calls the analysis "evidence for human review" rather than a guarantee, which is the correct posture for an artifact that is regenerated rather than believed. bonsai-ninja enters the day a triage verdict is stored beside the finding it settles.pingdotgg/t3codewas examined and has no report, and it is the corpus's clearest case of a system that drives memory without having any. MIT, 688,235 lines of TypeScript across a pnpm monorepo (222,667 of them the server), 2,638 commits since 7 February 2026, atcd096b9a…— an agent-harness control surface, in its own words: a mobile, web and desktop front end that runs Codex, Claude Code, Cursor, Grok Build and OpenCode as child processes on your own machine. Five of the agents it drives have reports here, which is why a reader would expect it and why the boundary is worth stating. Its durable state lives under~/.t3in SQLite across forty migrations, and it sorts into four piles with nothing left over: an event-sourced orchestration log (orchestration_events, command receipts), projections of it (threads, turns, messages, attachments, proposed plans,archived_at, plus denormalised counters likepending_approval_countfor the thread list), checkpoint diff blobs against a git worktree, and auth/pairing/session rows. All of it records what happened and what is running — acts and coordination state, none of it a claim that could turn out false and later be corrected. Same boundary asUntrivial-ai/agent-orchestrator,perplexityai/numbat,os-factory/harandCohexa-ai/agent-coherenceabove. Checked rather than assumed: the server tree contains noAGENTS.md/CLAUDE.mdwriter, itsWorkspaceSearchIndexpersists nothing (on-demand scanning, by its own comment), and the only prompt state it owns isCodexDeveloperInstructions, which sets a collaboration mode per turn. The one place memory appears is the finding worth recording.makeMemoryConsolidationNotificationFilter(apps/server/src/provider/Layers/CodexSessionRuntime.ts:550) watches for athread/startedwhosethreadSourceorsource.subAgentismemory_consolidationand suppresses that thread's notifications, so Codex's background memory pass does not surface as a visible thread beside the user's own. A control plane deciding what to show the user about another agent's memory work is a role nothing else in this corpus occupies, and it is the shape to expect as memory moves down into the providers. One screening note, because it is unusual:.repos/holds two entire third-party repositories committed into the tree — 12,961 tracked files acrossalchemy-effectandeffect-smol, each with its own npmpreparescript that an ordinary install would run — while.vscode/settings.jsonexcludes.repos/**from search and file watching, so the execution surface a contributor is least likely to look at is the one the editor is configured to hide.Custodian-Labs/custodian-labs-pythonwas examined and has no report: it is a samples repository for a hosted SDK. Thirteen files atac9b5d07…— five numbered example scripts, two guardian-layer samples, a websocket bridge with an HTML page, and three data fixtures. The screen returnedNOTHING SCANNED— no manifest, hook or agent file exists at any path it knows, which is a finding rather than a pass, so the tree was read by hand: there is no package manifest, no library code and no licence file, which defaults to all rights reserved. Every script importscustodian_labs, a PyPI package that is not in this repository, authenticates withCUSTODIAN_SDK_API_KEYfrom a dashboard, and ends atcustodian.deploy()returning anapp.chat_url— so whatever the product stores, it stores server-side. Grepping the whole tree formemor,recallorrememberreturns nothing; the samples' actual subject is PII handling, with aGuardianLayerthat callsanalyze_proprietaryanddeidentify_text_outputsagainst the same hosted service, and aprivacy_enabledflag on the agent constructor. Nothing here is a memory mechanism, and the SDK that might contain one is closed behind a wrapper — the exclusion this atlas draws for a mechanism with no inspectable code at a pinned commit. It enters if the SDK is opened, or if a local store appears in these samples.arcee-ai/nacwas examined and has no report, and the word to be careful about is episode. Apache-2.0, at70666a09…, 76 commits, ~108,600 lines of Rust across three crates plus a web dashboard. Its architecture is genuinely interesting and worth naming: "a central orchestrator plans and decomposes work but cannot execute commands or edit files; it only launches threads, which return episodes — structured summaries of what they accomplished", a capability boundary drawn between planning and acting rather than assumed. An episode here is a run record, not episodic memory. Theepisodestable carriesthread_name,session_id, anaction, the summarycontent, and astatusconstrained took | error | timed_out | cancelled— an execution outcome, not an epistemic state — and every read of it isWHERE e.session_id = ?, withDELETE FROM episodes WHERE session_id = ?1when a session goes. The same key governs everything else durable:threads,worksetsandworkset_items(the plan and its acceptance criteria),workspace_revisions,session_run_recovery.orchestrator_compaction_checkpointsis conversation-window management done carefully — a summary, a tail start index, and SHA-256 hashes of both the source prefix and the system policy so a checkpoint cannot be reused against a prompt it was not built from — which is the boundary this atlas already draws, one layer up from a raw transcript. The two things that outlive a session are read-only inputs rather than memory:SKILL.mdfiles discovered by scanning project and user directories to a bounded depth and mounted into the sandbox at fixed guest paths, with no writer anywhere in the tree, andAGENTS.mdfiles read with a most-specific-wins override hierarchy. So nothing here stores a claim that could later be wrong, and nothing accumulates across sessions for a correction to name. nac enters the day a thread's episode outlives its session as something a later run must consult — the same condition the atlas set for Kimi's compaction handoff.CodebuffAI/freebuffwas examined and has no report, and it has the most developed prompt for this shape and the least machinery behind it. Apache-2.0, atd3646896…, 8,451 commits — the open source of the Codebuff products, a coding agent across terminal, desktop, browser and GitHub. Its durable memory is knowledge files:AGENTS.md,CLAUDE.mdand anything matching*.knowledge.md, recognised byisKnowledgeFileincommon/src/constants/knowledge.ts, plus a home-directory tier read byloadUserKnowledgeFiles. The loading code is real but thin —selectKnowledgeFilePathsgroups candidates by directory andselectHighestPriorityKnowledgeFilepicks one per directory in a fixed order,AGENTS.mdbeforeCLAUDE.md. Everything else is the prompt, and the prompt is the most developed instance of this shape the atlas has read:knowledgeFilesPromptframes the agent as working in a "Memento-style environment", tells it that knowledge files "were created by previous engineers working on the codebase, and they were given these same instructions", and then specifies when to update one ("if the user gives broad advice to 'always do x'"; "if the user corrects you because they expected something different"), what to include, what not to include, and to "integrate new knowledge into existing sections when possible". That is a genuinely good articulation of the practice — and it is still a prompt plus the ordinarywrite_filetool, with git as the only durability guarantee, which is the call already made for Cline's Memory Bank and for Zoo Code above. There is no store behind the files: no identity separate from the path, no status, no supersession, and nothing that consults a removal when the same claim is written again. One detail is worth recording for the atlas's stored-versus-enforced theme. The home-directory tier is declared off-limits in the prompt — "you cannot edit them because they are outside of the project directory. Do not try to edit them" — and that boundary is an instruction rather than something found asserted on the write path; the CLI resolves writes against a project root without a containment check in the code read here. A boundary whose enforcement is the model's compliance is exactly the distinction this atlas draws between a scope stored and a scope enforced, appearing here one layer up, in the prompt itself. The rest of what persists is run state —cli/src/utils/message-history.tsandrun-state-storage.ts— which is the checkpointer boundary.evals/buffbenchis a substantial coding-task eval suite with committed task sets, and none of it evaluates memory: the word knowledge appears in its fixtures because the repositories under test contain knowledge files. freebuff enters the day a knowledge file gains a record the write path consults.Zoo-Code-Org/Zoo-Codewas examined and has no report, and it has the best editing surface in the corpus with nothing behind it. Apache-2.0, ate064cf05…. It continues Roo Code — stillroo-codein the package manifest — which makes it a fork of a fork of Cline, and its durable state is three piles, none of them a belief store.src/services/code-index/is a semantic index of the user's source, with embedders, a vector store and an orchestrator, regenerated from the thing it indexes: the boundary already drawn forDeusData/codebase-memory-mcpand Kodiak's ChromaDB source index.TaskHistoryStore.tsandsrc/core/checkpoints/store the run, which is the LangGraph-checkpointer boundary. The third pile is where the interest is. Cline's Memory Bank declines as "a prompt plus ordinary file editing"; Zoo Code's rules and skills have a real management layer — a typed CRUD API overRuleMetadatarecords with ids built from(scope, kind, modeSlug, relativePath),globalandprojectbases each split into generic and per-mode directories, a filename pattern enforced on write, and resolution containment-checked twice, before and after anlstatthat accepts symlinks, so a rule cannot escape its scope through a link. Every caller ofcreateRuleanddeleteRuleis a click in the webview. The agent invokes a skill throughSkillTooland never writes one; nothing it concludes reaches the store except through the same generic file-write it could aim anywhere. That is configuration, not memory: a rule the user wrote cannot be wrong in the sense this atlas means, only outdated, and nothing derives it so nothing can re-assert it. It is further along than Cline on every axis except the one that decides the question — see the note.Aider-AI/aiderwas examined and has no report, and it is the cleanest test of the boundary because it does persist something. Apache-2.0, at5dc9490b…..aider.chat.history.mdis written continuously and--restore-chat-historyreads it back:base_coder.py:519splits the markdown into messages and callssummarize_start(), andChatSummaryrecursively summarizes from the oldest end until the tail fits a token budget — so a previous session's conversation genuinely reaches a later session's context. It is still a transcript and a summary of one. There is no unit, no identity and no status; two sessions that contradict each other yield a summary containing both, and no operation means "this was wrong". The other durable artifact isrepomap.py's.aider.tags.cache.v<N>— tree-sitter tags per file, mtime-invalidated, ranked by a personalized PageRank over the identifier graph — a derived index of the user's source.CONVENTIONS.mdis a file the user passes with--read, which is a prompt input. This is the exclusion where a conversation cannot be wrong either, and a summary of one inherits the property has to carry real weight, because the artifact does outlive the session.MoonshotAI/kimi-codeandMoonshotAI/kimi-cliwere examined together and neither earns a report, and the interesting one is the one being retired. They are one lineage:kimi-cli's README states that it "is evolving into Kimi Code CLI" and "will be gradually wound down". The successor is far larger — 107,465 lines inpackages/agent-core-v2/srcand its own embedded storage engine inpackages/minidb— and what both persist is the run: config, workspace state, a session index, cron tasks, the wire log, plans and blobs.contextMemoryis the conversation. Butkimi-cli(Apache-2.0, atcbc15c07…) shipsSendDMail— a tool, backed by a class calledDenwaRenji, that raisesBackToTheFuture— with which the agent picks a prior checkpoint in its own append-only context file, folds everything after it away, and leaves a message for its past self. The cut point is chosen by the agent rather than by a token threshold, which is what separates it from every compaction in this corpus; the reverted trajectory is rotated tocontext_1.jsonlrather than deleted, so the abandoned branch is retained (unboundedly — nothing prunes it); and the prompt names the seam that context-level undo always has, warning the past self that "your future self has already done something in the current working directory". Two caveats belong beside it: the mechanism instructs the model twice never to mention the rewind to the user, and it is commented out in the default agent, enabled only in a built-in agent namedokabe. The successor dropped it — noSendDMail,DenwaRenjiorBackToTheFutureanywhere inkimi-code— and replaced agent-initiated time travel with user-initiatedundo(turns), which is not in the tool registry. What it built instead is a full-compaction prompt that asks the model to carry the epistemic status of its own prior claims through the summary: "If an earlier step claimed something was done but was never verified (tests 'passing', a fix 'working', a file 'created'), say so plainly and treat it as unverified rather than fact" — the self-reinforcement failure named under OWASP Agent Memory Guard above, addressed at the boundary where a party with an interest in the outcome rewrites the record. Unenforced by any code, and still the only instance in this round that treats summarisation as an epistemic hazard rather than a compression problem. Its cron subsystem is the nearest thing to a durable agent-authored record in either repository and still is not memory —CronCreate/CronList/CronDeleteare agent tools writing{id, cron, prompt, createdAt, recurring, lastFiredAt}to a workspace-scoped document store, but the tool's own documentation says tasks "survive a resume of the same session but do not bleed into new sessions", and a schedule is an intent that cannot be false. Two moves in it transfer anyway: the model is told to re-enumerate from the store after a compaction rather than trust what survived in the summary — the right relationship between a lossy context and a durable record, and the opposite of how most extraction pipelines treat a compacted transcript — and a stale recurring task gets one final delivery flaggedstale: truebefore deletion, so expiry arrives as a renewal offer to the party holding enough context to judge it, rather than firing silently while nobody is looking. Recorded with the compaction details in the note.rezabyt.github.io/blogposts/sigreg-tutorial.htmlwas examined and has no report, and it is not a repository. It is a tutorial on SIGReg, the anti-collapse regularizer introduced in LeJEPA, developed from characteristic functions through the Cramér–Wold theorem to a training loop, with LeWorldModel as a temporal-prediction application. This is representation-learning methodology: it constrains an encoder's embedding distribution so it does not collapse during training. There is no store, no retrieval, no correction and no code at a pinned commit — two independent exclusions. Recorded rather than dropped because the collision is instructive: a world model that predicts the next embedding is memory-adjacent in the way a KV cache is memory-adjacent, and the atlas's line holds in the same place. What SIGReg governs is whether an encoder's representations stay spread out during training; what this atlas asks is whether a thing an agent stored last week can be found, scoped and corrected today. The first is a property of a loss function and the second is a property of a store.xataio/xatawas examined and has no report: it is a Postgres platform. The repository is a Go microservices system — 340 files underservices/, Helm charts, kustomize overlays, protobuf definitions — whose README states the two use cases plainly: "create your own internal Postgres-as-a-Service for your company" and "create preview, testing, and dev environments" using copy-on-write storage and scale-to-zero. Nothing in the tree matchesmemoryoragentas a concept, and there is no store an agent writes beliefs into. It is infrastructure a memory system could be built on, which is the same relationship this atlas records for graph databases: a backend the corpus reads as a shared dependency rather than reviews, alongside the layer below delete reading of five vector engines. Recorded by name because a reader meeting a database company's open-source platform in a list of memory candidates deserves to find that out here.metauto-ai/HGMwas examined and has no report: what persists is an optimizer's state. The Huxley-Gödel Machine is a practical approximation of Schmidhuber's Gödel machine, with coding agents that rewrite themselves and a search guided by the aggregated benchmark performance of an agent's descendants rather than its own. Its durable state, intree.py, is a tree whose nodes are git commit ids of self-modified agents plus their utility measures, pickled — read by the outer search loop to decide which modification to expand, and by nothing at task time.self_improve_step.pycalls the model withmsg_history=None, andbest_agent/self_evo.mdis a transcript of the improvement instruction rather than a record the next generation reads, so no generation inherits what its ancestors learned about themselves except as code. That is the guard-is-not-a-store shape at its strongest: the state is far richer than a workflow phase and still holds no claim that could be wrong, so there is nothing for a correction to attach to. Two things are worth taking from it anyway, and both are recorded in the note: judging a node by what its descendants achieve is the credit-assignment discipline the comparative report argues for on the memory side and finds nowhere, and versioning every self-modification as a git commit gets for free the undo Prime Agent builds by hand. It would enter this atlas the day a generation reads a durable record of what its ancestors tried.agentplugins/agent-plugins-sitewas examined and has no report: it is a documentation website. 120 files of Next.js and MDX serving "the official website for the Agent Plugins specification", with the spec itself pulled in throughspecification-source.json. Grepping its markdown for memory returns nothing, so neither the site nor the specification it renders defines a memory mechanism — there is no store, no retrieval and no correction to review. That negative claim has since been re-scoped, because the site is not where the specification lives.specification-source.jsonnames a second repository —agentplugins/agent-plugins-spec, at a pinned commit — as authoritative, and the site vendors its material intocontent/docs/for rendering; so the original grep covered the derived text rather than the artifact it derives from — the atlas's own "none found is a claim about a search" hazard, one level up from a directory and at a repository boundary instead. Read directly, the specification has no memory concept either: what a plugin declares is skills and MCP servers, andFUTURE_CONSIDERATIONS.mddefers a trust model, provenance signatures, secret scoping and "a standard event schema for plugin install, enable, disable, update, and uninstall actions" with retention and access policies — this atlas's vocabulary applied to the plugin lifecycle rather than to anything a plugin remembers. The exclusion holds, and now rests on both repositories rather than on the one whose name matched. The adjacency worth noting for later: a plugin packages Agent Skills, so if this standard is adopted it becomes a distribution format for skills as procedural memory — and nothing in it says whether a skill acquired from a plugin may be rewritten by the agent that runs it, which is the question that would put a future version in scope. Recorded rather than dropped for the same reason the atlas records other near misses by name: a reader who sees an agent-plugin standard in a list of memory candidates deserves to find out here that it is a spec site, not to re-derive it. A name collision worth flagging beside it:techtheist/engram, reviewed this round, is a different project from Engram (Gentleman-Programming/engram) already in the corpus, and is filed under the slugengram-alpha. Anyone reconciling lists by project name rather than by URL will merge them, exactly as theagentmemorycollision recorded above invites.pi-chatis a separate repository and was not reviewed; the claim that it injects two persistent memory files every turn comes from its documentation, not from its code.arXiv:2608.05466was examined and has no report, and its project site is the atlas's first sighting of an audit surface whose fixtures do not contain the artifact. Recursive Synthesis for Long-Horizon Terminal Tasks (5 August 2026, CC BY 4.0) synthesises 37,484 executable terminal-agent tasks over fifteen recursive rounds, and is out of scope on the ordinary basis: what persists is a task corpus, not a store an agent writes beliefs into. It is recorded because of its project site, whose fifth section is an "Audit layer" headed "Don't just trust our metrics. Inspect the task change, model trajectory, and rubric decision for the same case yourself." Read in a browser, the Trajectory Diff's two columns — a failed baseline and a successful run that earned verifier reward 1.0 — are byte-identical at every turn where both render, across four cases checked, and every turn past the baseline's length is blank on the successful side: in case 1 the baseline is 6 turns, the successful run is 21, and turns 7–21 carry no command, no response and no observation. The viewer prints "No Left turn at this index" when the baseline runs out, so absence is expressible and is not used on the other side. The rubric tab scores that case 94.5/100 with all six of its first criteria at the same 86% confidence, citing the same three turns, under a generated sentence calling itself an "evidence-linked deterministic assessment". The viewer repository says it ships "source code and small fixtures only", so these are fixtures behaving as fixtures and nothing here says the underlying runs do not exist — the gap is between what the fixtures are and the sentence they are published under. This atlas already names the harness's own output captured as evidence and published benchmark numbers without committed artifacts; this is the third and the most persuasive, because the first two look like missing work and this one looks like finished work. The paper was then read from its LaTeX source rather than from a rendering, which corrected this atlas's own first reading and found more than it did. Its flagship number disagrees with itself: the RL table and the abstract both give Qwen3.5-27B-RL as 49.44 on Terminal-Bench 2 for a relative gain of +20.00%, and the conclusion says 46.07 for +11.82% — both internally consistent against the 41.20 base, so one is a stale draft figure surviving into the conclusion of a published paper, in the headline cell of the headline result. That is the same hand-written-number-beside-generated-ones class this atlas spent three days removing from its own prose. Hidden-check protection reaches 63.5% at the final round, so roughly 36.5% of tasks still let the verifier check what the instruction does not establish — which is what the contract-validity gate exists to forbid, and it leaves under-specification as an unexcluded explanation for the headline difficulty result of a fixed solver falling from 90% to 2.5% pass@4. Neither that metric nor requirement coverage is defined anywhere in the paper. There is no ablation, no limitations section, and the lineWe release all synthesized tasks, sampled trajectories, and trained checkpointsis commented out in the source. See the note, which also records what the paper gets right and why its lineage-without-retroactive-removal is the tombstone gap in a training pipeline.Untrivial-ai/agent-orchestratorwas examined and has no report, and it is the atlas's own thesis implemented by something that is not a memory system. Apache-2.0, atb6609ae6…: a meta-harness running Claude Code, Codex, Cursor and others in parallel, each in its own git worktree, routing CI failures, review comments and merge conflicts back to the right session. The scope call is settled by the schema and confirmed by the vocabulary. Sixty-five migrations produce sessions, worktrees, cleanup facts, conversations, turns, messages, activities, provider events, projects, PRs, checks, comments, reviews, review runs, notifications, model usage and terminals — every one a record of what happened or what must happen next, none of them a claim that could be false — and across roughly 117,000 lines of non-test Go,recallappears twice andforgetsix times, every instance about the chat window or a terminal attachment. Neither the README, the design document norAGENTS.mduses the word memory about the product at all. Same boundary asos-factory/harandshepherd-agents/shepherdabove. What makes it worth recording is that AO is a derived copy of somebody else's memory, and it treats upstream forgetting as an obligation. When a person rolls back a turn the provider genuinely drops that turn and everything after it from the history it reasons over — "It changes what the agent remembers. AO's rows have to follow" — and following means five statements in one transaction: mark the turnsrolled_back_atrather than deleting them, because "'this exchange happened and was then taken back' is a different and more useful fact than 'this exchange never existed'"; settle a discarded-but-undispatched turn asinterruptedrather than leaving it queued against a history it was never written for; correlate compaction rows written by older AO builds without a provider turn id so the rolled-back filter hides them too; recompute the parent row's derivedcompacted_atfrom the surviving activities rather than patching it; and fail pending approvals inside discarded turns, a statement the comment says exists "so the invariant is enforced rather than argued". The read side filters a rolled-back turn's prose from the snapshot because "a person must never be shown prose the agent has forgotten", keeps AO's own bookkeeping rows visible because "hiding what AO cannot prove belonged to the discarded range would be a guess", and never renumberssequence, because "renumbering to close the gap would rewrite history to look like it never happened". That is the enumerated-derived-copies discipline this atlas asks about in every report and finds in almost none — written out as a list of every place the discarded fact had already been projected. Two smaller mechanisms are in the note:applied_titleas a compare-and-set witness holding "what I last wrote" so an automatic rename can tell its own value from a human's without awas_editedflag, which is the auto-update-versus-human-edit problem every generated profile field has; and compaction stored as a timeline row plus a state column, with the migration arguing why a parallel table was rejected. The doc comment says "the three statements commit together" and there are five, which is the ordinary fate of a count written in prose beside code that grew.Emericen/tiny-qwenwas examined and has no report: it is a model, not a memory system. MIT, at61ff9d42…: a ~1,600-line PyTorch re-implementation of Qwen with int4 quantization and a single-file terminal agentic harness. The scope call is settled by the vocabulary — across the.pytreerecall,remember,persist,store,session,sqliteanddatabaseappear zero times; the sevenmemoryhits are RAM ("peak memory is one tensor"), the twoembeddinghits are the model's token embeddings, and the twohistoryhits arereadline's input arrows. The harness's conversation is aself.messageslist held in process, and the only file writes inrun.pyare quantization output (quant.json, safetensors shards); nothing survives a session, so there is no claim that could be corrected. It is the cleanest kind of exclusion — not a borderline harness but a model implementation whose "memory" is the allocator's — recorded by name because a repository called qwen in a memory-candidate list deserves a stated reason rather than a silent drop.- Helm was read, not run. Three claims in its report are inferences
from code that a live database would settle: that
getAutonomyModereturns the stale pre-supersession row (argued from SQLite's partial-index eligibility and rowid scan order, and consistent with the 82 duplicate supersessions of that one key recorded in the project's own changelog); that the 500-row recall window is reached in practice, which depends on a fact count that is gitignored; and which of the three retrieval quality tiers a typical install actually runs, since the MiniLM model is an explicit opt-in download and all three tiers produce the same output shape. Helm's third memory surface could not be reviewed at all: twelvecortex.*tools are registered and documented as a five-layer memory stack, andworkspace/cortex/is gitignored and absent from the repository. maximem-ai/maximem_synap_sdkwas first examined at an earlier commit, when it was the closed-engine refusal in its purest hosted form; it has a report at a later one, Maximem Synap SDK, and a self-hosted edition of the engine is reviewed as Maximem Synap Core. Apache-2.0, at0fd74edb…: the Python and JavaScript SDKs plus about two dozen framework integrations — LangChain, LangGraph, LlamaIndex, CrewAI, AutoGen, Google ADK, OpenAI Agents, Semantic Kernel and the rest. The README states the boundary itself — "The Synap memory engine itself (ingestion, entity resolution, retrieval, anticipation) runs as a fully managed cloud service operated by Maximem and is not open source. The SDKs in this repo are clients for that service; there is nothing to self-host, and an API key is required." The code confirms it: the durable operations —ingest_transcript,get_compacted,get_context_for_prompt,get_profileinpackages/sdks/maximem-synap/maximem_synap/sdk.py— arehttpxcalls toapi_base_url, and the substantial local modules are client concerns (auth, telemetry, transport, resilience) plus a client-side cache:cache/carries a local BM25 index, a SQLite backend, a short-term store and an anticipation cache that pre-fetches. So everything this atlas asks about — how a stored belief is resolved against an existing one, ranked, scoped, corrected or forgotten — happens in the closed engine, and the SDK caches its results in front of it. That is the closed-source-mechanism-behind-an-open-wrapper exclusion; its nearest neighbours arekunal12203/graperoot(an open repository around a proprietary pip package) andArtKeyAi/bhived-mcp(open transport posting to a closed API) above, and this is the hosted-service version those two are variations on. Its paper is the same system and the same limit. arXiv:2607.21503 — Agentic Context Management, Gaurav Dadhich, 23 July 2026 — names Maximem Synap as its reference implementation, argues that memory is a lifecycle rather than a store, and decomposes it into five primitives (architecting, ingesting, scoping, anticipating, compacting & consolidation). The framing is worth reading and adjacent to this atlas's own taxonomy; the evaluation is not checkable here. It reports 92% on LongMemEval and 93.2% on LoCoMo — the same figures the README leads with under a "#1" banner — run through the company's own separate harness (maximem-ai/memory_and_context_eval_harness) and published on a vendor blog, with no inspectable implementation at a pinned commit to check them against. That is the judge-the-code-not-the-claim posture this atlas applies to every leaderboard boast, and it is why a #1-on-two-benchmarks memory layer with an open SDK still earns a list entry rather than a report: what reads as reviewable is the client, and the thing being ranked is the part that is not there.SWE-agent/mini-swe-agentwas examined and has no report: its only state is the trajectory. MIT (Lieret and Jimenez), ~15,000 lines of Python ata83fcae8…, from the SWE-agent team and deliberately minimal — the agent class is awhile True: self.step()loop over aself.messageslist against a bash environment, with no tools. The scope call is settled by the vocabulary and confirmed by the design: acrosssrc/recall,remember,embedding,vector,forget,retriev,sqliteanddatabaseappear zero times; the threememoryhits are Docker RAM (--memory 4096), and the tenpersisthits are either an in-turn model-response contract (aFormatErrormust not lose the response) or the prompt telling the model that "Directory or environment variable changes are not persistent. Every action is executed in a new subshell." — the opposite of a durable store. Whatsave()writes is the trajectory (.traj.json): the message list, config, cost and exit status, and the README states the identity outright — "there's no difference between the trajectory and the messages that you pass on to the LM." So the persisted artifact is the conversation serialized and replayed by a trajectory browser; nothing is a claim that could be false and later corrected. Same boundary as Pi,shepherd-agents/shepherdandUntrivial-ai/agent-orchestratorabove — a harness that persists a run, not a memory that believes. Recorded by name because a widely-used agent from the SWE-agent lineage in a memory-candidate list deserves a stated reason rather than a silent drop.UOR-Foundation/UOR-Frameworkwas examined and has no report: it is a formal ontology, not a memory system. MIT, a Rust workspace plus 28 Lean4 proof files at51c01382…, encoding the UOR Foundation ontology — "a mathematical framework for content-addressed, symmetric, multi-metric object spaces with algebraic structure based on Z/(2^n)Z" — as typed Rust data inspec/and machine-generating it into JSON-LD, Turtle, OWL, SHACL and a Lean formalization. It is knowledge representation in the OWL/RDF sense: a vocabulary for describing objects — 34 namespaces and 474 classes of it — which is the kind of thing a memory system might be built on top of rather than a store of anything an agent believes. The vocabulary settles the call and also shows the trap.recall,remember,belief,LLMandpromptare zero across the tree, and the counts that look memory-shaped are all mathematics: the 146embeddinghits are algebraic embeddings ("Embedding is a ring homomorphism", "Embedding injectivity", "composition of embeddings is an embedding"), the 45memoryhits are ontology terms and RAM ("memory boundedness" as an axiom, "independent of physical memory layout"), and there is no vector store, similarity search or knn anywhere. Theclients/crate is build tooling —build,conformance,docs,website,crateandleanbinaries that regenerate the serializations from the spec. Nothing is captured, retrieved, scoped or corrected; there is no agent and no session state, only a specification and its proofs. Same relationship the atlas records forxataio/xataand the graph-database backends above — a substrate a memory system could stand on — recorded by name because embedding and content-addressing in a candidate list read as memory until you see they mean the algebra.EverMind-AI/Ravenwas examined and has no report: its durable memory is EverOS, which the atlas already reviews. MIT, ~105,000 lines of Python, a pre-alpha self-improving agent harness atcd686453…built on EverOS — pinned as the dependencyeveros==1.2.1— which supplies the durable user memory, agent memory and world knowledge the README credits. Raven's ownraven/memory_engine/(6,102 lines) is a pluggableMemoryBackendprotocol whose shipped durable backend is EverOS, plus SkillForge, a skills-as-procedural-memory router that RRF-fuses skill hits from local files, an external hub and the EverOS skill source behind a gate, and importers that scan a Claude Code history into memory. So the belief store is a reviewed dependency and Raven's own contribution is routing, importing and skill evolution over it — the same call the atlas makes fornetease-youdao/LobsterAI(operates OpenClaw's memory) andomnigent-ai/omnigent(mounts Hindsight). The EverMind ecosystem's dedicated memory repositories — HyperMem and EverMemBench — are separate and were not examined here. If Raven grows a durable store of its own rather than a router over EverOS, the call flips.zjunlp/SciAtlaswas examined and has no report: it is a literature knowledge graph behind a hosted API, and nothing a user or an agent concludes outlives a run. MIT, 77,560 lines of Python across 214 files from 58 commits between 20 April and 16 July 2026 by five authors, read ata9a345da…, with a paper at arXiv:2605.22878. The graph links papers, authors, institutions, venues, keywords and citations to a four-leveldomain → field → subfield → topictaxonomy, and the repository packages a client for it: the README's own framing is that a user installs withpip, registers a token and works "without setting up Neo4j, maintaining graph data, or touching backend infrastructure". The local pipelines can be pointed at abolt://localhost:7687of your own, and no graph data ships. The scope call is the one already drawn forkivgraphandcodebreaker77/Fullerenes, one domain over: a corpus index of published work, regenerated from the corpus, where correction means re-ingesting rather than revising a belief. Two searches settle it. Across 214 Python files the memory vocabulary is absent — every occurrence ofrecallis the IR metric or a retrieval-arm name (--kg-topk-title-vector, "embedding recall path"), andremember,forgetandepisodicappear nowhere. And nothing reads a prior run:runs/<run_id>/holdsrequest.json,response.json,summary.txtandreport.mdas per-run artifacts, and no code path lists or loads an earlier one. The CLI's "skills" are the nearest thing, and they are hand-edited JSON presets loaded from./skills/,~/.sciatlas/skills/orSCIATLAS_SKILLS_DIR— saved parameter sets a person writes, not procedural memory the system accumulates. Recorded for three things a reader can take. The taxonomy is a retrieval axis rather than a label: a search can propagate along the subfield hierarchy as well as along citations, which is the structural answer to the vocabulary-gap problem several stores in this atlas hit with embeddings alone. Each workflow ships aflashand afullpreset — a cheap first pass and an expensive second, chosen by the caller — which is the gate-the-expensive-path shape applied to research rather than to retrieval. Andagent-skill/packages sevenSKILL.mdfolders that migrate the workflows into Codex and Claude Code, whose stated contract is zero-start: the agent installs the CLI, guides registration, and asks the human only for values a human must supply. Two things sit against it. Every documented endpoint is plainhttp://— the registration page that issues a personal token, the token-status endpoint, and theSCIATLAS_API_BASE_URLthat token is then sent to — so the credential travels in the clear. Andliterature_review_pipeline/kg_search/config.pydefaults its embedding and reranker paths to/home/weiyunxiang/yunx/hf-models/…, a specific researcher's home directory, so the documented defaults resolve on one machine. Screened before reading: no auto-run surface, no manifest inside the seven-day cooldown, no build-time execution path and three unpinned dependency surfaces; nothing was installed or run.codebreaker77/Fullereneswas examined and has no report: it is a code index, and the one thing in it that behaves like memory is the thing that can delete a hand-written file. MIT, 3,774 lines of TypeScript across twenty-five files in three packages — core, CLI, daemon — from eleven commits between 25 and 28 April 2026 by one author, read atcf0bb643…. The README calls it "persistent local memory for AI coding agents"; the store is.fullerenes/graph.dbwith four tables —nodes(functions, classes, modules from tree-sitter),edges(calls, imports, inherits),files(a content hash per path for incremental indexing) and ametakey-value pair holdinglast_indexedand an indexing-statistics blob. Every MCP tool is a graph query —query_codebase,get_callers,predict_impact,get_subgraph— andpredict_impactwalking incoming dependency edges three hops to a blast radius is a genuinely useful thing to hand an agent before it edits. The scope call is the one already drawn forkivgraph,DeusData/codebase-memory-mcpand Kodiak: a corpus index of the user's source, regenerated from the source, where correction means re-indexing rather than revising a belief. Nothing an agent or a person concludes is stored —grep -rn 'CREATE TABLE' packages --include='*.ts'returns those four tables and no fifth. Recorded because of what the generators do to the file the agent actually reads.fullerenes init,fullerenes indexandfullerenes watchall regenerateCLAUDE.md,AGENTS.mdand a Cursor rule from the graph, andpackages/cli/src/generators/files.tsmerges rather than clobbers: it strips its own<!-- BEGIN FULLERENES -->block and keeps whatever else the file held. Then, on the text that survived, it runscleaned.includes('# Codebase context')— and on a match setscleaned = ''. That heuristic exists to clean up unmarked files from an older release, and# Codebase contextis the generated block's own first heading and an entirely natural heading for a hand-writtenCLAUDE.md; the same discard fires on the substringAuto-generated by Fullerenes.fullerenes watchruns the generators on a one-second debounce after any source change, so on a watched repository the check is not a one-off. A hand-written agent-instruction file is the smallest memory a coding agent has, and a substring test is not a safe way to decide it is disposable. No tests of any kind:find packages -name '*.test.ts' -o -name '*.spec.ts'returns nothing, and the twenty-onedescribe(/it(/expect(hits are all.split(andParser.init(matching the pattern. Screened before reading: no auto-run surface, four unpinned dependency surfaces and a lockfile unchanged for 136 days; nothing was installed, built or run.Luqueee/kivgraphwas examined and has no report: it is a code index, and what is worth taking from it is the axis it keeps apart. Apache-2.0, 182,614 lines of Go plus TypeScript and Python workers, 803 commits since 4 August 2026, read at0633a6b5…. A cross-repository code-intelligence MCP server: it resolves edges withgo/types, the TypeScript checker andrust-analyzerrather than by matching names, and serves the result as an immutable graph. The scope call is the one already drawn forDeusData/codebase-memory-mcp,VectorSpaceLab/general-agentic-memory, Kodiak andperplexityai/numbat— a corpus index of the user's source, regenerated from the source, where correction means re-indexing rather than revising a belief. Nothing an agent concluded is stored: the MCP surface is queries plusindex_projectandgraph_status, andinternal/auditstates the property that settles it — "Nothing here writes. A remedy is a proposal… and Kivgraph does not write inside the code it indexes." Across the Go tree every occurrence ofmemoryis RAM, andrecall,rememberandbeliefappear nowhere. Recorded because it implements, one domain over, the shape this atlas asks memory systems for and rarely finds.internal/facts/codes.gofreezes two axes and keeps them apart: six ordered confidence codes —ExactTypechecked,ExactDeclarationMapped,ExactPackageMapped,StructuralCertain,Candidate,Unresolved, ordered "strongest first, so a comparison on the code is a comparison on strength" — beside a separate provenance axis naming which analyzer produced the edge (GoTypesDefinition,GoASTCall,TypeScriptChecker, …). A syntax-only fallback is admitted as a candidate and refused as knowledge — "Syntax-only fallbacks may still provide useful candidate edges, but they must never be published as exact knowledge" — and the axis is not decorative:internal/hotsnapshot/traversal.go:148filters every edge bycodeAllowed(edge.Confidence, options.Confidences), under a committed test named for it. Beside that,SemanticUnresolvedrows carry aReasonfor each reference the analyzer could not resolve, so the index ships its own coverage gaps. Read against the corpus this atlas holds, that is a discrete ordered status that withholds, kept apart from where a claim came from, and applied on the read path — the combination 213 systems here express as a single float, and the reasontrust_stateis the mark most often refused. And the README states the retrieval consequence better than most memory systems state it about themselves: because the edges are type-resolved rather than name-matched, "an empty reference list means nobody calls it, not that nothing was found, andgrepcannot tell those apart." That distinction — evidence of absence against absence of evidence — is what this atlas's negative-retrieval mark asks a test to establish, here made a property of the read path itself. The reversal condition: a store beside the graph holding something an agent concluded about the code rather than something a type checker derived from it.Arc-Computer/ATLASwas examined and has no report: it is an offline training engine, and the store it trains from lives in a different repository. Apache-2.0, 11,250 lines of Python, read atc226386f…, the head ofmainand dated 23 January 2026. Atlas Core takes a JSONL export of agent episodes and trains a teacher checkpoint from it by on-policy distillation or GRPO; the README is explicit that the runtime half — the dual-agent loop that captures the traces, the session review that approves or quarantines them, the Postgres they land in — is the separateatlas-sdk. What remains here consumes run records and emits model weights, which is the scope line already drawn for OpenHands SDK andDevrG03/AgentMesh: a trace of what an agent did cannot turn out to be false, so neither the export nor the checkpoint is a store of claims. The code confirms it rather than the prose alone —src/atlas_core/runtime/is two files,schema.pyis 200 lines of dataclasses that readadaptive_summaryandtriage_dossierback as opaqueOptional[Dict[str, Any]], and nosqlite,psycopg,sqlalchemyorpersonasymbol appears anywhere undersrc/. Every match formemoryin the tree is GPU memory in the vLLM and Ray generation paths. The reversal condition is the sibling repository: the review-and-quarantine gate the quickstart invokes, and whatever persona state it governs, is a memory surface and is not in this tree.DevrG03/AgentMeshwas examined and has no report: it is a workflow execution engine, and nothing it persists is a claim that could be false. A C++20 control plane — 26 headers and 26 translation units, a DAG scheduler with atomic in-degrees, a priority ready queue, a thread pool, and a pybind11 adapter that compiles a LangGraphStateGraphonto it — read atae2e2dac…, 9 commits since 18 August 2026, with no licence file and no licence claim anywhere in the tree, so a reader has no grant to rely on. The scope call is settled by what the store holds.IStateRepositorypersists aWorkflowExecution— an id, aWorkflowState, a map ofTaskExecutionrecords, and start and completion timestamps — into two Postgres tables,workflows(workflow_id, state, started_at, completed_at)andtasks(workflow_id, task_id, state, attempt, result_success, result_output, result_error, …); the only read-back isloadActiveWorkflows(), documented "for crash recovery and scheduling" and filtered to Pending or Running. That a task ran and returned a string is a fact about what happened, and applying the per-mark scope test to it gives the same answer as for OpenHands SDK,os-factory/harandperplexityai/numbat: it cannot turn out to be false, so an audit of it is notaudit_logand a snapshot of it is not memory. The vocabulary confirms it — acrossinclude/,src/,apps/andpython_adapter/, every occurrence ofmemoryis RAM ("memory bloat", "prevent memory leaks",InMemoryStateRepository), andrecall,knowledgeandembeddingappear zero times. Unlike OpenHands SDK there is no memory sitting beside the engine to report on. Recorded rather than dropped for the benchmark artifact.benchmark_analysis.mdpublishes an eight-row matrix against LangGraph — 1,900× on in-memory hops, +5.0% and +2.7% on replayed swarms with paired t-tests, 95% less RAM — and the repository commits exactly one head-to-head result set,benchmarks/langgraph_comparison/results_langgraph.jsonbesideresults_agentmesh.csv, 100 paired runs each. It recomputes cleanly and honourably: 50.77 ms against 39.02 ms, 23.1% faster. It is also not any of the eight published rows, and none of those rows has a committed artifact behind it — the committed file's ownpeak_ram_mbof 83.1 for LangGraph is a third of the matrix's 240 MB, because they are different measurements. The shape is worth naming because it is the inverse of the failure this atlas usually records: not a claim with no evidence, but a genuine committed measurement standing next to a headline table it does not support. The reversal condition, should anyone return to this: a store that outlives a workflow and holds something an agent concluded rather than something the engine did.aimultiple.com/ai-memorywas examined and is not a reviewable system: it is an analyst survey with an embedded benchmark. The page introduces RELC-Bench (100 items over 14 transcripts) and surveys consumer and enterprise memory — ChatGPT, Claude and Gemini memory, Mem0, Zep, LangGraph and others — but it is a web article, not code at a pinned commit, and no committed harness or result file backs RELC-Bench where the atlas can read it. The open, inspectable systems it names are already reviewed here; the rest are hosted products on the closed-engine side of the line. Recorded so a reader arriving from that page finds why it is not itself an atlas entry.DeusData/codebase-memory-mcpwas examined twice and has no report: it is a code-intelligence engine, not agent memory, and the reversal condition set at the first reading is still unmet. MIT, a pure-C native binary re-read at997d087b…, 264 commits on: 158 languages through tree-sitter with a Hybrid-LSP type-resolution layer, full-indexing a repository into a persistent knowledge graph of functions, classes, call chains, HTTP routes and cross-service links, now answering over 32 MCP tools where the first reading found 15. Its durable store is that graph —nodes,edges,file_hashes,index_coverage,lsp_surface— a corpus index of the user's source, regenerated from the source, the boundary already drawn forVectorSpaceLab/general-agentic-memory,ShamGaneshan2008/Kodiak's ChromaDB source index andperplexityai/numbat. The one agent-memory surface is still one document. The first reading said the call would flip if the ADR store "grew into a real belief store — multiple records with status and correction semantics." It has instead grown a better editor:manage_adrgained aset_sectionsmode that "rewrites only the named sections and leaves every other byte of the stored document untouched," with idempotency stated for the case that matters — "setting the same section to the same body twice leaves the document byte-identical, so retrying after a lost response is safe." That is memory as an editing surface done carefully, and it is still a single row:cbm_store_adr_getreadsproject_summaries, whose primary key isproject. No status, no supersession, no per-decision identity, no scope below the project. The table it shares is the tell — the other columns aresummaryand asource_hash, so an authored decisions document and a regenerable derived cache occupy the same row shape. Its own preprint is arXiv:2603.27277, on tree-sitter knowledge graphs for code exploration.arXiv:2309.02427was examined and has no report: it is a framework, not a system. Cognitive Architectures for Language Agents (Sumers, Yao, Narasimhan & Griffiths, 5 September 2023, revised through March 2024) proposes CoALA — a language agent as modular memory components (working, episodic, semantic, procedural), a structured action space over internal memory and external environments, and a generalized decision loop — and uses it to survey the field. It is foundational to how this atlas reasons about memory kinds, but it defines a taxonomy rather than shipping an implementation: its companion repository,ysymyth/awesome-language-agents, is a curated link list, so there is nothing to review at a pinned commit. Recorded as the conceptual lineage behind the working/episodic/semantic/procedural split that recurs across the corpus — most explicitly in Memmy's L1→L2→L3→Skill layering and the cognitive-taxonomy stores — and as the survey a reader should read before the code, not instead of it.developers.openai.com/cookbook/examples/agents_sdk/context_personalizationwas examined and is not a reviewable system: it is an official tutorial. OpenAI's Agents-SDK cookbook demonstrates state-based long-term memory — a structured state object injected into the system prompt at session start, new preferences distilled through tool calls during the conversation, consolidated into long-term storage by an LLM call, and reused next session, with a global-versus-session scope split resolved by precedence (latest input → session override → global default). It is a notebook-style walkthrough over an in-memoryTravelStatedataclass with no persistent backend, not installable code at a pinned commit, so it cannot be reviewed on this atlas's terms. Worth recording because it is OpenAI's own illustration of the inject–distill–consolidate–reuse shape that several reviewed systems build over a real store, and because it names recency-weighting, confidence and TTL as notes a memory should carry — the affordances this atlas keeps checking for — while leaving them to the reader to implement.wangpan-ustc/AtlasVAwas examined and has no report: its "memory" is RL training state, not agent belief. Self-Evolving Visual Skill Memory for Teacher-Free VLM Agents (arXiv:2605.17933), Python over a vendoredverlRL backend atc3e12ea0…. Its three-layer "visual skill memory" — spatial heatmaps, visual exemplars and symbolic text skills — is evolved from a training run's own trajectory statistics into danger and affinity atlases that provide dense, coordinate-aware reward shaping for reinforcement learning on Sokoban, FrozenLake and embodied navigation. The vocabulary settles it:recall,remember,sqliteandCREATE TABLEare zero, whilereward/trajectory/rollout/RLappear ~1,500 times. This is optimizer/training state that produces a policy — the same boundary the atlas draws for the Gödel-machine lineage and for weights as memory — not a store an agent writes a belief into and later corrects across sessions. Memory-branded and paper-backed, so recorded by name; a visual skill memory that shapes RL reward is not what this atlas means by memory.walkinglabs/learn-harness-engineeringwas examined and has no report: it teaches the shape rather than shipping it. MIT, 246 commits, at12fc49c9…— a course on building agent harnesses, 1,729 Markdown files because every lecture is translated into a dozen languages, beside six numbered example projects and askills/harness-creator/. The SQLite andCREATE TABLEhits a probe returns are lecture code samples underdocs/<lang>/lectures/, not a store, and there is nothing to pin a mechanism claim to. One reference page is worth taking,skills/harness-creator/references/memory-persistence-pattern.md, because it states as a rule the crash-ordering property this atlas praises where it finds it. Its two-step save invariant: write the full content to a topic file first, then append the one-line pointer to the index, "if the process crashes between steps, the worst outcome is an orphaned topic file — the index remains consistent". That is PLUR1BUS's ordering discipline — durable before superseded — written as a teaching rule rather than discovered in a diff, and it sits beside a scope-precedence ladder (organization → user → project → local) and a three-layer split of instruction memory, agent-written auto-memory and background session extraction. The course enters the day one of its six projects ships a store rather than an illustration of one.ai-boost/awesome-harness-engineeringwas examined and has no report, for the reason the atlas already gaveysymyth/awesome-language-agents. CC0, 233 commits, atfae9622e…— a curated list: seven Markdown files, a banner, averify_urls.pylink checker, and a 630-line README carrying 224 GitHub links. There is no implementation at a pinned commit, so there is nothing this atlas's method can read. Recorded because a reader who finds it while looking for harness memory should know it is a directory rather than a system, and because a link list that ships its own URL checker is doing more than most.towardsai/ai-tutor-appwas examined and has no report, and it is worth recording as a worked implementation of a retrieval idea rather than as memory. Apache-2.0, 15,330 lines of Python acrossapp/andevals/, 227 commits since 30 January 2025, atb04c0a03…— an agentic RAG tutor behind a LangGraph agent core, and the backing repository for a workshop on context engineering. Its long-term memory is a student profile that does not outlive the process, and the code says so at the definition:STORE = InMemoryStore(), under a comment reading "In-process like the checkpointer: profiles survive across threads/sessions within one server lifetime… Swap for a persistent LangGraph store to survive restarts." The profile has a real identity — namespace("student", <id>), keyprofile, updated by_update_student_profileand appended to the system prompt — so it is the shape of a memory without the durability, and the atlas draws the same line here it drew where nothing survives the process. Everything else in the repository is on the other side of a boundary this atlas already keeps:memory_presets.pybundles summarization and tool-output-clearing middlewares, which is conversation-window management, and the knowledge base is a corpus index of the course's own material. What is worth carrying iskb_shell.py, and it is the same idea as arXiv:2605.05242 — Beyond Semantic Similarity: Rethinking Retrieval for Agentic Search via Direct Corpus Interaction (Li et al., 3 May 2026), which argues that a fixed similarity interface is the bottleneck and has agents search raw corpora with general-purpose tools instead, reporting gains over sparse, dense and reranking baselines on BRIGHT and BEIR. The repository ships that as an agent-facing tool with the hardening the paper does not have to specify: an allowlist of exactlyrg,grep,find,ls,sed,head,catandwc, a refusal of every shell metacharacter that would compose them (|,&&,;,>, backtick and the rest), an eight-second timeout and a 40,000-character output cap. Anyone giving an agent grep over a corpus needs that list; it is a better starting point than writing it from scratch. Itsevals/also holds a named-preset comparison —compaction_study.pyasks whether a long established context is better kept every turn or compacted, holding the rest constant — which is the harness shape the benchmarks page keeps asking for, pointed at context management rather than at memory. ai-tutor-app enters the day the student profile is written somewhere that survives a restart.a40-labs/memory-bench, which GitHub redirects to from its former namea40-labs/memory, was examined and has no report, and its second half is the nearest thing the corpus has to an answer to what this method structurally cannot reach. MIT, 35 commits, atf53ad5f6…. The screen returned NOTHING SCANNED — no manifest, hook or agent file anywhere, because the whole repository is thirteen stdlib Python scripts and thirty-four JSON row dumps. Its measurement half is already on the benchmarks page: per-question rows behind every published table, one verification script per benchmark recomputing each figure against aPUBLISHEDconstant, and averify_all.pythat closes by enumerating the three published scores it cannot check and why. The half worth recording here issystems/file-based/, 1,154 lines that reconstruct Claude Code's auto-memory as runnable stdlib code — a curatedMEMORY.mdindex, topic files with a four-type taxonomy and anoriginSessionId, an index preload cut at 200 lines or 25KB measured after frontmatter and block comments are stripped, a silent-overflow warning, a staleness notice on aged reads, and literal-plus-regex grep with bounded output. It is not a memory system this atlas can report on: nothing in it is a store an agent writes a belief into and later corrects, and the thing it models is closed. What transfers is how it handles that. Its own README states the problem — the best-documented instance of the shape "is closed-source and cannot be lifted", so "fidelity therefore rests on traceability" — and the survey it implements grades every claim it makes about the closed original: 12[official], 3[corroborated], 3[single-source], 1[rumor]. The 22 tests cite the survey section whose claim each one pins. So a reader can see which behaviours are documented by the vendor and which are community inference, rather than being handed a reconstruction and the word faithful. That is the discipline this atlas asks of a capability mark, applied to a system nobody outside the vendor can read — and it is the shape to copy if the hosted systems named above are ever going to be discussed on evidence rather than on their marketing.warpdotdev/warpwas examined and has no report, and it is the cleanest example in the corpus of a published contract with an unpublished mechanism. Dual AGPL-3.0 and MIT, 3,983 Rust files and 278 SQL migrations, 2,120 commits since 28 April 2026, atd13a30f4…— the Warp terminal's own client. It has agent memory, and the memory is the part that stayed on the server:app/src/server/server_api/ai.rsis a REST client againstmemory_stores/{uid}/memories, so extraction, retrieval, deduplication and what a tombstone does to a read are all outside this tree. That is the atlas's stated exclusion — the mechanism closed behind an open wrapper — and it is worth recording rather than passing over, because the contract those serde types describe is more complete than most systems here implement. AMemoryItemcarriescontent, aversion_id, asource, asource_idand asource_run_id— provenance down to the run that produced it — besideis_tombstonedandtombstoned_at. AMemoryVersionItemcarries a full priorcontentand thereasonit changed.CreateMemoryRequestandUpdateMemoryRequestboth takereason: String, not anOption, so the API cannot be called without saying why — a discipline MindCache, Aura and most of the trust-state family do not impose on their own writes. A store has anowner_typeandowner_uid, and agents attach to it through anAgentAttachmentItemcarrying anaccesslevel. Two findings survive being unable to read the server.MemorySourceis an enum with exactly one variant,Manual:source_idandsource_run_idexist on the read model and imply a server that writes memories from runs, and nothing in the open client can produce anything but a memory a person typed. Andis_tombstoned/tombstoned_atare deserialised and read nowhere inapp/— the client is told which memories are dead and does not filter, mark or otherwise act on it, so whether a tombstoned memory stops being retrievable is decided somewhere a reader cannot check. What the client does own is not memory:project_rulesis(id, path, project_root), a registry of which rule files exist with their content left on disk, andagent_conversationsis transcript persistence, which is the conversation-window boundary. One screening note, because a vocabulary probe on this repository lies:tombstone,supersedeandforgetreturn dozens of hits inflated by a committed BERT tokenizer vocabulary and the vendored Alacritty licence, and once those are excluded the remainder are TUI event tombstones, recalling a command from shell history, andcore::mem::forget. Warp enters the day the store behind that API is inspectable at a commit, or a client-side memory gains a correctable identity of its own.google/samwas examined and has no report: it is the network agents talk over, and the one mechanism worth taking is an access-control property, not a memory one. Apache-2.0, 46,820 lines of Go across 145 files, 1,130 commits since 18 April 2026, atb42aaaf2…— Sovereign Agent Mesh, a zero-config, zero-trust libp2p fabric in three components (sam-control-planefor identity registration and policy,sam-routerfor bootstrap and relay,sam-nodefor local transport and MCP sidecar routing) that lets autonomous agents discover each other and invoke each other's tools. The control plane's twelve tables settle it and none of them holds a claim:nodesandroutersare membership,keyring,bootstrap_tokensandenrollment_requestsare key material and joining,users,roles,role_permissions,role_bindingsandpoliciesare RBAC,rotation_lockis a mutex andschema_migrationsis bookkeeping. Identity, authorization and coordination state — the boundary already drawn forUntrivial-ai/agent-orchestrator,perplexityai/numbat,os-factory/harandCohexa-ai/agent-coherence. The vocabulary is clean rather than merely quiet:recall,belief,supersede,tombstoneandforgetare zero, the singlerememberis a comment about caching a failed dial so a node does not retry into a fifteen-second timeout, and all seventeenmemoryhits are in-memory hosts in tests. What transfers is how it says no. Authorization is Biscuit tokens — Datalog policies carried in the credential and verified offline — and a node attenuates its own token from config, addingAttenuation.Policies,.Checksand.Rules(internal/node/config.go:48-66), withAuthorize()enforced atinternal/node/middleware.go:170,internal/controlplane/server.go:863and insideinternal/identity/biscuit.go. Attenuation is one-way: a holder can mint a strictly weaker token and cannot mint a stronger one, and a verifier needs no call back to the issuer to know that. That isscope.caller_cannot_widenas a cryptographic property rather than a code review. Most systems in this corpus implement scope as a predicate the caller supplies, which is precisely the widening hazard the test exists for; SAM enforces the same property at the transport, where the caller cannot reach it. Nothing here remembers anything, and the mechanism is still the clearest answer in the corpus to a question memory systems keep failing. sam enters the day the mesh carries a durable claim about a peer that a later reading could contradict — a reputation, a trust score, a record of what an agent got wrong.Tencent/UI-Matewas examined and has no report: its procedural memory is a file you hand it and a checkpoint you download. Apache-2.0, atd2b2e0ae…, 13 commits since 14 August 2026 — a foundation GUI agent from Tencent HY Frontier with a technical report at arXiv:2608.15930 and checkpoints on Hugging Face, of which this repository is the inference side: 2,020 lines of Python across four files, plus example resources and screenshots. The screen reports NOTHING SCANNED — no manifest, hook or agent file at any path it knows — and reading the tree by hand explains it rather than contradicting it: twenty-nine files, no build file, no dependency declaration. It is here because the pitch is procedural memory almost exactly. "Show the workflow once. Let the agent adapt it to the task at hand": a successful desktop run, already segmented into subtasks, is distilled into per-turn guidance — a subtask checklist, a completion criterion, key milestones — that the model folds into its prompt, with the pointer advancing when it reportssubtask_complete. What settles it is the direction of the arrow, stated in the source's own comment: "the workflow writes them, the agent only reads them." Every reference to atrajectory_captioned*.jsondemonstration is a load, a glob or a raise-if-missing; nothing in the tree writes one, so a completed run teaches the next run nothing.reset()clears an index and a boolean, which is the whole of what survives a step. The rest of what persists is the checkpoint, which is the weights boundary, and a prompt prefix held stable for vLLM's cache, which is the KV-cache boundary. One design note is worth taking even though the system is out of scope, because it inverts the failure this atlas keeps reporting: coordinates from the demonstration are never replayed and the live screenshot is authoritative, so the stored procedure is explicitly subordinate to present observation rather than trusted over it. UI-Mate enters the day a finished run is distilled back into a demonstration the next one consults.zenml-io/kitaruwas examined and has no report: it judges agents, it is not memory for one. Apache-2.0, 72,947 lines of Python and 33,295 of TypeScript over FastAPI and Postgres, 865 commits since 5 March 2026, atf32a0911…— replay-based evaluation from the ZenML team: production runs are recorded or imported from Langfuse, LangSmith, Braintrust or Logfire as sessions, then re-executed against a changed model, prompt or working tree. Twenty-six tables and twelve MCP tools, so a reader would reasonably check. The store is measurement state. Sessions are recorded traces — acts, not claims — cohorts freeze a population, experiments and replays record what was run, and the agent under test never consults any of it as belief: replay answers its tool calls from the recording. Same boundary aspingdotgg/t3codeand the harnesses on the benchmarks page. The vocabulary confirms it rather than merely failing to contradict it:remember,recall,beliefandtombstoneare zero acrosssrc/, the threesupersedehits are a worker's task-claim lease being taken by a newer attempt, and all fourmemoryhits are RAM. The one claim-shaped row is the annotation, and it is worth recording because the atlas's own finding appears here one level up. A human judgment is stored with an owner, aquestion_key, a JSONBselectorpinning it to an exact trace location, and a JSONBvalue— provenance most memory systems in this corpus do not manage for their own beliefs. ThenAnnotationService.update_annotationcallsAnnotation.update_valueand writes the row back, so a revised judgment overwrites the previous one in place and nothing retains what it said: noprevious_value, no supersession, no audit row. The analytics stream is not the missing record either —build_annotation_created_propertiesfires on creation only, and carriesinvestigation_answerandhas_selectoras booleans rather than the judgment itself. These judgments are what calibrate the evaluators, so the one artifact whose correction history would matter most is the one kept without it. kitaru enters the day the agent under test reads a kitaru row as a belief about its task rather than a fixture for its replay.tobi/qmdwas examined and has no report: the agent can search it and cannot write to it. MIT, 40,233 lines of TypeScript acrosssrc/andtest/, 668 commits since 7 December 2025, atfacd35e0…— an on-device search engine over your own markdown, fusing BM25 and vector search with an LLM reranker, every model local throughnode-llama-cpp. Its README calls it "an on-device search engine for everything you need to remember", which is why a reader would expect it here. Four tables settle it:contentis content-addressed by hash,documentsmaps a collection and path onto one of those hashes, andllm_cacheandcontent_vectorsare derived from both — every row regenerates from files the user wrote, and nothing in the store is a claim qmd made that a later reading could contradict. The MCP surface confirms it from the other side:query,get,multi_getandstatus, all read-only, so the model can retrieve a document and cannot deposit one. Same boundary asDeusData/codebase-memory-mcp,VectorSpaceLab/general-agentic-memoryandperplexityai/numbat— a corpus index of the user's own material. The vocabulary is a trap worth naming, because grepping for it would mislead:recallappears 52 times and every one isrecall@kin the benchmark harness, the singletombstonemarks a soft-deleted row whose file has vanished so its content can be collected, andremember,belief,supersedeandprovenanceare all zero. What transfers issrc/trust.ts, and it is better than the approval gates several memory systems here ship. A project-local.qmd/index.ymlarrives with agit cloneand is adopted automatically for any command run inside the tree, so three fields in it can reach outside the project: anupdate:shell command, a collection path, and a model URI. Those three are gated and nothing else is — the user's own global config is never gated, and neither are in-project paths or the built-in model defaults, so the prompt fires where it is warranted rather than everywhere. Approval is recorded per config file and per gated set as a digest intrusted.json, and editing the hook, repointing the collection outside the project or changing the model URI changes the digest and re-arms the gate, which is the property a one-time "trust this folder" prompt does not have.decideLocalConfigGatehas a production call site atsrc/cli/qmd.ts:811, denies by skipping when there is no TTY to confirm on, andtest/update-hook-trust.test.tscovers both decision functions — producer, consumer and test all present, which is more than the corpus's median for a mechanism of this shape. qmd enters the day its own store holds something the source files do not: an agent-written annotation, a status, or any row with a lifecycle of its own.WujiangXu/A-memwas examined and has no report because the atlas already reviews the same system. It is the A-MEM paper's (arXiv:2502.12110) author-side reproduction repository at0c8039f2…— its own README says it "is specifically designed to reproduce the results presented in our paper." The atlas's a-mem report coversagiresearch/A-mem, the lab copy of the same paper's code (capabilities: ""); this is the first author's copy of the same project, a distinct git history rather than a different system. The README points to a third repository,WujiangXu/A-mem-sys, as the "official implementation... for building your agents", which is the one that could diverge from the reviewed copy — it was not examined here, and if it carries mechanisms the reproduction repo does not it is the better subject. Recorded so a reader reconciling three A-mem URLs by name finds they are one paper's code, already reviewed once.Adolanium/hermes-officewas examined and has no report: everything it stores is drawn, and none of it is read back to an agent. MIT, 17 commits since 16 August 2026, at9e960c1b…— a 4,409-line desktop plugin that renders one floor of desks, one per Bot Mode agent, over the same live data Bot Mode already uses. The screen returned NOTHING SCANNED: no manifest, no hook, no agent file, because the repository is one plugin file, a preview tool and a test. It earns a named exclusion rather than a silent drop because it does pass the letter of the admission test and misses its point. Durable, identity-keyed state survives the session in two places —savePrefputs trophies, the monthly and weekly recaps, pending news and dismissed hints through the host's plugin storage, and a finished task callsprofiles.configurewithui_meta.<office-namespace>.stars, a per-bot count written onto the bot's own profile so that, in the README's words, the stars "follow the bot, not the machine", and read back on the next load. That is something stored, with an identity, correctable later. The read side settles it: nothing the plugin stores ever reaches a model. The only text sent to an agent isprompt.submitcarrying the task the user typed into the bar; the star count, the recap and the employee-of-the-month portrait are read by the diorama to draw a nameplate and a wall. The atlas's admission test is shorthand for a store an agent writes a belief into and later corrects, and a scoreboard for paper dolls satisfies the shorthand without being one — which is the useful part, because the same shape describes any interface that persists per-agent decoration beside a real memory system and would read as memory in a directory listing.calibrae/bucciaratiwas examined and has no report: nothing it stores ever reaches the model unasked, and its honesty about one invented number is the reason to record it. MIT, 2,472 lines of Rust, 3 commits since 26 April 2026, at9db66bf5…. It is an MCP server over an mdBook wiki — ten typed tools for status, list, read, write, summary, move, search, delete, image upload and publish — and it says what it is not: "No reqwest, no embedding model — pure filesystem + subprocess." The scope test that settles it is the read path. There is no injection, no session hook and no boot read:wiki_readtakes a slug the model must already know andwiki_searchtakes a query the model must already form, which makes the pair indistinguishable in kind fromfile_readandrg. What survives a session is a published document set — the terminal operation ismdbook build— and the installer creates awikigroup "so any wiki-group editor — human or agent — can update pages", which is the right design for documentation and the wrong shape for a belief store. Compare NanoClaw, whose memory is also Markdown and is memory because two files enter the context window at every new session. What transfers is a design criterion this atlas argues for and rarely sees stated as one: bytes returned to the agent. Every response "drop[s] null fields, omit[s] empty arrays, and skip[s] mdbook's success boilerplate", andwiki_searchships budgets rather than a limit — 3 matches per page, 20 pages, 200-character snippets by default, a hard ceiling of 1000 and a floor of 44 — with truncation flags on both axes, so a capped result reports that it was capped instead of arriving as a short list. That last property is exactly what repowise's vector leg lacked when it returned[]and looked like an empty result. Andsrc/baselines.rsis the contrast worth drawing with the fabricated baseline recorded on the benchmarks page. It is a hardcoded table of what an equivalent SSH-and-bash invocation "would have cost the agent", from whichmcp-gaincomputes savings asbaseline - bytes/4— the same move MemCP makes when it asserts a constant in place of a measurement. The difference is entirely in the handling: the file's own comment reads "These are educated guesses; recalibrate from realusage.jsonldata after a few weeks", the estimate is version-stamped asSOURCE = "estimate@v1", and that stamp is printed in the header of every report the tool emits. A number nobody measured, labelled as such, versioned so its replacement is distinguishable, with the recalibration plan committed beside it — that is what the honest form of an unmeasured constant looks like, and the corpus has more of the other kind.ChrisCanadian/nexus-proof-runtimewas examined and has no report, and it is the corpus's cleanest counter-example to this atlas's most-repeated finding — with the gap in the same file. Apache-2.0, 1,753 lines of Python across eleven modules and a test suite, 4 commits since 24 July 2026, at6223974c…. It is a receipt-backed execution layer for LLM tools, and the README rules itself out of scope before anyone else can: it contains "no Nexus Synapse production source, memory implementation, SSR selection logic, prompts, identity system, live schemas, provider configuration, or operational data." That is accurate —ReceiptStoredescribes itself as an "SQLite evidence store. It records facts, not model-authored success claims", and a receipt of an execution is an observation, not a claim a later reading could contradict. Same call asCorvus-226/RunTrace. The reason to record it is the executor. Every path through_execute_lockedends atself._record(...):SUCCEEDED,FAILED,TIMED_OUT,CANCELLED, andCANCELLED_BEFORE_STARTfor a call cancelled before the handler ran — each with anerror_code, each written to the samereceiptstable with the same columns, each bound to anexecutionsrow whoseUNIQUE (idempotency_key, principal_id, scope, tool_name, tool_version, arguments_hash)makes a retry a replay rather than a second attempt. There is no early return that skips the record. This atlas finds the opposite everywhere — AIPass's governance engine logs the memory it surfaced and never the one it declined, Mem0Sharp's admission gate carries aReasonthe service reads as a boolean and drops, AgentDatabase records mutations and not refusals — and here refusal and success are the same row shape. The second mechanism is theClaimGate, which is evidence before belief applied at the narration boundary: a model may claimtool_succeededorartifact_exists, and the gate resolves the claim against the runtime's own receipt or artifact and against the host-owned principal and scope, returning typed codes —UNVERIFIED_TOOL_SUCCESS,RECEIPT_PRINCIPAL_MISMATCH,RECEIPT_SCOPE_MISMATCH,MISSING_OR_TAMPERED_ARTIFACT— so an application never presents a model's assertion as fact without a runtime-owned record behind it. And the gap is in the same file, one function up.ToolExecutor.executeraises rather than records for everything it refuses before starting:IDEMPOTENCY_KEY_REQUIRED,UNKNOWN_TOOL_VERSION, a policy denial (decision.code) andINVALID_ARGUMENTSall leave no row. So the runtime whose purpose is durable proof keeps a complete record of the calls it ran and none of the calls it declined to run — the same asymmetry, in the one repository built to make it impossible, and the fix is that the receipt table already has astatuscolumn and afacts_jsonblob.fynnfluegge/agtxwas examined and has no report: it is thebeadsboundary in its purest form, and its trust gate is worth the entry on its own. Apache-2.0, 26,552 lines of Rust, 102 commits since 8 February 2026, 738 tests, at6f0d8dec…. It is a terminal kanban board that runs several coding agents in parallel, each in its own git worktree and tmux window, with an orchestrator that plans and delegates — the README calls it "the blackboard for coding agents", and a blackboard is exactly the thing the second boundary declines. The schema settles it in five tables:tasks(title, description, status, agent, project, session, worktree, branch, PR number,cycle,referenced_tasks,escalation_note),transition_requests,notifications,projectsandrunning_agents. Every column is the state of the work or of the process running it; not one holds a claim about the world that a later reading could contradict. A task moving frombacklogtodone, or its branch changing, is the work moving on rather than the store having been wrong. The cross-task context path is the interesting near-miss, because it looks like memory transfer and is not: a task may reference other tasks, and on worktree creation agtx writesgit diff main..<branch>into.agtx/references/<slug>.diffand recursively copies.agtx/skillsand.planningfrom the referenced task's worktree — "if it still exists". Both halves are derivable or ephemeral: the diff regenerates from git on demand, and the copy silently produces nothing once the worktree is cleaned up. Nothing is stored with an identity a correction could name, which is the difference between routing work products and remembering. What is worth recording isTrustStore, and it belongs besidetobi/qmd'ssrc/trust.tsabove as the corpus's second good instance of the same idea. A cloned repository can carry.agtx/config.tomlwith aninit_script, acleanup_scriptandcopy_files; agtx keys a SHA-256 of that file by canonical project path in~/.config/agtx/trusted_projects.toml— outside the project, so the tree cannot mark itself trusted — and on a mismatch suppresses the three dangerous fields and forcesno_init_scriptsfor plugins rather than refusing to open the project, telling the operator which fields were disabled and namingagtx trustas the way back. Editing the config re-arms the gate because the hash changes, which is the property a one-time folder prompt lacks, and(None, None) => truedistinguishes no policy from changed policy — a project with no config file is not treated as suspicious. The gap is that the gate and the precedence key on different files.WorkflowPlugin::loadresolves a plugin name against{project}/.agtx/plugins/<name>/plugin.tomlbefore the global directory, a plugin carries its owninit_script, and plugin init scripts are suppressed only when the config hash mismatches. A repository that ships a project-local plugin directory shadowing the name the operator already has configured globally, and ships no.agtx/config.tomlat all, satisfiesis_trustedby that same(None, None)arm. The fix is one line — hash the plugin directory too, or forceno_init_scriptswhenever a project-local plugin shadows a global one — and it is recorded here rather than left implicit because the atlas keeps finding trust gates whose key is narrower than their blast radius. One note on its benchmark, which is committed rather than claimed:benchmark/RESULTS.mdreports per-instance rows against SWE-bench Lite with duration, tokens, cost and a three-value outcome — ✅, 🟡 for "fix correct but incomplete", ❌ — across roughly ten workflow-plugin configurations, with a header explaining that tokens and cost move independently because cache reads are ten times cheaper than input. Reporting cost beside outcome is the discipline the benchmarks page asks for and rarely gets. It is also two instances of three hundred, mostly one, graded by hand, with a single ✅ in the whole table — so it separates nothing, and the file's value is the shape rather than the numbers.raiyanyahya/llmakerwas examined and has no report: the only thing it calls memory is a capped, expiring transcript, and the interesting part is that its silent failure is a committed contract. Apache-2.0, about 11,000 lines of Go across 72 files with a 5,000-line Python side, 46 commits since 24 June 2026, at683f7a28…. It is a self-hosting platform — one command provisions Ollama, Qdrant and Redis, networked and discoverable — with a FastAPI facade and a LangGraph agent on top.agent/app/memory.pyis 72 lines and is the whole of it: aRedisMemorythat stores a session's messages as one JSON list underllmaker:session:<id>, capped atmemory_max_turns: int = 20pairs and expiring atmemory_ttl_seconds: int = 604800. Nothing is extracted, nothing carries an identity, and a wrong statement in turn three is not corrected but evicted — conversation-window management with a network hop. The vector store beside it is loaded by an explicit/ingestendpoint from uploaded documents and by/itemsfrom a recommendation catalogue; no chat path upserts, so nothing the agent learns during a conversation becomes durable. A grep of the agent package for forget, tombstone, supersede and provenance returns zero. What earns the entry is the degradation contract. Every Redis call is wrapped in a bareexcept Exceptionthat returns[]or passes, described in the module docstring as best-effort — "if Redis is unreachable the agent still answers (with whatever the client sent), mirroring how the vector store degrades" — andtests/test_memory.py::test_memory_degrades_when_redis_errorspins that behaviour, asserting thatload,appendandclearall swallow a raising client. Availability over durability is a defensible choice for a chat buffer. Writing the test is what makes it a contract rather than an oversight, and it is also what makes the loss undetectable: a caller cannot distinguish a session whose history was saved from one that was silently dropped, and now nobody can fix that without failing a test. The shape generalises past this repository — GENOME's automatic fact detector swallows both its model call and its write at DEBUG, with the same result — and the cheap repair in both cases is to return what happened rather than nothing.stablyai/orcawas examined and has no report: it is thebeadsboundary again, and itssrc/main/memory/directory holds RAM accounting. MIT, 9,116 commits since 16 March 2026, atd14923e9…— an Electron orchestrator that runs Codex, Claude Code, OpenCode or Pi side by side, each in its own git worktree, with a mobile companion app. The durable state is the workspace session: tabs, panes, PTY registrations, terminal and tab-group layouts, browser history, sleeping agent sessions, and which worktree an agent is in. Every field is the state of the work or of the process running it; none is a claim about the world that a later reading could contradict, which is the same call recorded forfynnfluegge/agtxabove. The eightskills/are authored instruction files describing how to drive Orca —orchestration,orca-cli,computer-use— not procedural memory the agent writes, and thenotesin the source are review comments a person sends to a running agent. The vocabulary collision is the purest this atlas has recorded, and it is worth naming for anyone screening candidates by directory listing:src/main/memory/containshost-memory.ts,process-memory-metric.ts,windows-process-resource-collector.tsand a PTY registry. It is 2,520 lines about RAM. What transfers issrc/shared/zod-salvage.ts, and it is the finished version of something this atlas keeps finding half-built. The problem it solves is stated at the schema that uses it: a session JSON "is written to disk by older builds and read back by newer ones," and a field type flip or a truncated write "could poison Zustand state and crash the renderer on mount." The policy is tolerance declared on the field rather than at the parse boundary —salvagedField,salvagedOptional,salvagingArray,salvagingRecord— so "a corrupt entry is dropped and the rest of the session survives, because one bad tab record must not cost every worktree its state," while a payload that is not a session at all still falls back to defaults. And unlike every ad-hoc version of this the atlas has read, it tells the caller what it dropped:collectSalvageDrops(parse)returns{value, droppedPaths, droppedCount}with the example paths bounded at a hundred. GENOME's row-skipping decoder makes the same correct trade and reports the loss only to an ERROR log, so the caller sees a shorter list and no count; this is that gap closed, in 132 lines, in a repository that is not about memory at all.NVIDIA/SkillEvaluatorwas examined and has no report: it grades procedural memory rather than holding any, and two of its mechanisms are worth more than that boundary suggests. Apache-2.0, 125,985 lines of Python, 59 commits and 7 contributors since 26 July 2026, ataa195cac…. It is a three-tier evaluation framework for Agent Skills — deterministic validation gates, semantic overlap detection, synthetic eval-dataset generation, and sandboxed live agent runs through Harbor. The scope call is the one already drawn forzenml-io/kitaruabove: it judges agents, it is not memory for them. The vocabulary confirms it and also demonstrates why the probe alone cannot be trusted —forgetis zero, all 35memoryhits are RAM (--override-memory-mb, "in-memory agents data"), and all ten apparentrecallhits are the substring insideIgnoreCallback. What it persists is an embedding catalog of skills built to answer "is this new one a duplicate", which is the corpus-index boundary already drawn forShamGaneshan2008/Kodiak— an index of artifacts, not a store of anything an agent believes. The first mechanism worth recording is that catalog's load contract, which is the strictest embedding-provenance check in anything read for this atlas. A saved catalog carriesschema_version,provider,model,mode(full-bodyordescription), an endpoint fingerprint, a vector dimension, and a SHA-256content_fingerprintper entry;load_catalogrefuses — raises, rather than warning or degrading — on a mismatch of any of them, so the same model name served from a different endpoint is rejected, and a catalog built over descriptions cannot be queried as though it were built over bodies. This atlas repeatedly finds vector stores that silently mix embeddings from different models and compare them anyway; here it is impossible by construction, and the refusal is the whole difference. The second is the Tier 3 lift verdict, which is the ablation the atlas keeps asking for and rarely finds: the same eval dataset is runwith_skillandwithout_skill, and the delta decides whether the skill earned its place. The thresholds are asymmetric and there is a deliberate dead zone — pass at+0.05, fail at−0.10, neutral between — with the reason committed beside the constants: "Small deltas stay neutral because live agent runs are noisy, especially with low attempt counts." A measurement that declines to call a result in the band where it cannot tell signal from noise is the practice the benchmarks page exists to ask for, and a procedural-memory system that cannot say whether its instructions help is the common case. Recorded by name because a repository whose product is evaluating the thing this atlas reviews would otherwise look like an oversight in a candidate list, and because both mechanisms are separable from the framework: neither needs a skill, an agent, or NVIDIA's pipeline to be worth copying.yassinbahri/OnceMeshwas examined and has no report: it caches computations rather than beliefs, and it puts the scope key somewhere this atlas has been asking for it. Apache-2.0, 20 commits, all dated 25 August 2026, atea2911d8…— 8,643 lines of Python under a 3,685-line specification, described by its own README as "an open specification and reference implementation for exact reuse across agent and workflow runtimes" and, in the same paragraph, as "not a semantic prompt cache." The stored unit is a computation, not a claim. An action is{spec_version, operation, inputs, executor, output_schema, vary}; a result manifest is{spec_version, action_digest, artifacts, produced_at, fresh_until, producer}; an artifact is{name, digest, size, media_type}. Beside them sit source-validation records and signed receipts. Nothing in that schema is a subject, a predicate, a confidence or a fate —fresh_untilis a TTL on a computation result, which is the boundary already drawn forPerseus-Computing-LLC/perseus, and revalidation here means re-checking whether an upstream document changed, not revising a belief. The adapters arehttp_fetch,html_markdownandpdf_text. The nearest kin is a remote build cache with attestation. The vocabulary collision is the third the atlas has recorded and the most likely to fool a keyword screen, afterstablyai/orcaabove and the note on a directory named memory:src/oncemesh/store.pydefinesclass MemoryStore, and it is the in-process backend — the user guide's own table lists "Run or memory" as the tier that "disappears with the process and provides no cross-process durability." What transfers is where the scope key lives.derive_authorization_partitionbuilds an HMAC-SHA256 over{profile, tenant, sorted(scopes), subject_partition}under a domain-separated key of at least 32 bytes, andexecution_cache.pyputs the resulting token in the action'svaryobject — whichaction_digesthashes along with everything else. The partition is therefore inside the lookup key: two callers with different tenants or scope sets derive different digests and cannot reach each other's results, rather than reaching them and being filtered. Every scope failure this atlas has catalogued is a filter somebody forgot, widened or short-circuited — aninclude_allparameter, a predicate on one of three read paths, a policy shipped disabled. A key you cannot construct without the scope cannot be constructed without the scope. The cost is stated by the same design: a partitioned result is unshareable across partitions even when it would be safe to share, so the trade is reuse for structural containment. Two smaller mechanics hold it up and are worth copying together._require_exact_keyscomparesset(value) != expectedand so rejects unknown keys as well as missing ones, which is what makes the README's claim to identify a computation "from every input that can affect its output" enforceable rather than aspirational — a field this version does not know about refuses the action instead of being silently excluded from the digest. And the conformance suite carries a dedicatedcanonicalization-negative-v0.json, run by a Node harness so the Python reference is not the only thing checking it, whose negative vectors assert the specific rejection reason (error.message === vector.reason) rather than that something threw — the check that separates refused from refused for a different reason.searchsim-org/cikm26-knowledge-triage, which GitHub redirects to from its former namesearchsim-org/knowledge-triage, was examined and has no report: it is a retention policy rather than a store, and it is the first artifact this atlas has read whose published numbers recompute from committed files. Apache-2.0, 7,229 lines of Python, ata6ceb01a…— the reference implementation behind The Compaction Cliff in Long-Running AI Agent Memory (arXiv:2608.22752, CIKM '26). It holds nothing across sessions.knowledge_triage/kb.pyandoperators.pyclassify the lines of an agent's existing configuration —AGENTS.md,CLAUDE.md,.cursorrules— and decide which survive a compaction, a partition or a retrieval; the knowledge base is the caller's file, not a store this code owns. That is the same boundary drawn forNVIDIA/SkillEvaluatorabove, one step further along: SkillEvaluator grades procedural memory without holding any, and this one governs memory without holding any. Its measurement discipline is the reason for the entry, and it is recorded in full on the benchmarks page: twentyresults/*.jsonfiles beside twenty-two experiment scripts, with three separate abstract claims checked against them here and all three matching at the stated n. The one worth copying isresults/human_verification.json, which reports that of the cases the paper's own automated preservation metric scored as preserved, humans judged 27.6% weakened or lost — the failure rate of their own instrument, published beside the wins. The dataset half,AgentArtifactCorpus, is gated behind a Data Use Agreement and is a pointer rather than something checkable here.chenhg5/agencycliwas examined and has no report: it composes context from authored prompt files rather than accumulating any, and it is the fourth tree in this corpus where the word memory means RAM. AGPL-3.0, 33,831 lines of Go, 233 commits between 16 March and 10 July 2026, atba8b6937…— a CLI and web console for running a team of AI coding agents that "plan, execute, and talk to each other." The durable state is organisational configuration and work state: teams, roles, agents, tasks, milestones, OKRs, environment variables, providers, and a document registry of id, title, file path and tags. The one thing written back from a run is a taskSummary— "what the agent reports on completion (used by workflow routing)" — which steers the next step and is not carried into unrelated later sessions. That is the boundary already drawn forstablyai/orcaandfynnfluegge/agtxabove.internal/ctxbuildis the part worth naming, because it is what a memory layer would have replaced. ItsBuildermerges prompt files in a fixed inheritance order — agency, then each team in the chain top-down, then role, then project — deduplicating skills, with role skills appended last. Deterministic composition of human-authored layers, nothing written back, so there is no correction to review and no forgetting to test. And the naming trap is now a countable pattern rather than an anecdote. A grep of this tree for memory returnsMemoryMB,DefaultMemoryMB = 4096and--memory=%dm: Docker container limits, and nothing else. Withstablyai/orca's 2,520-linesrc/main/memory/about RAM,yassinbahri/OnceMesh'sclass MemoryStorefor its in-process backend, and thememorytier in that project's own durability table, four separate repositories now use the word for hardware or process lifetime. A directory listing and a keyword grep disagree about what a memory system is, and the grep is the one that misleads more often — which is the reverse of the failure recorded for OpenWorker in the overview's History, where the directory was the thing that misled.Weighted Memory Treewas examined and has no report: no repository, and the design it describes would score well if there were one. Weighted Memory Tree: Remembering What Matters for Long-Horizon LLM Agents (arXiv:2608.20631, 21 August 2026), Dao, Kathalkar and Eaton, sixteen pages. No code repository, no dataset, and nothing in the text announcing a release — the same call recorded for EvoHarness-RL: an on-topic paper with no artifact to pin. Two of its fields are ones this corpus scores. A node carries content, node type, parent, retention score, missed-selection count, execution metadata, and a lifecycle state over{ACTIVE, COMPLETED, FOLDED, OBSOLETE}, where "Lifecycle states determine eligibility for prompt construction." A four-value discrete status held apart from a float and deciding what reaches the model is thetrust_stateshape, and the poisoning suite is thenegative_evalshape; neither is markable without code, which is the whole reason this is a paragraph rather than a report. Folding is reversible — completed branches fold into summaries while the system retains "access to folded context," and resumed branches reopen. Its two transferable pieces are recorded where a builder would look for them rather than here: the retention rule, revised by execution outcome and by decaying a memory that was eligible and not chosen, is on the decay pattern page; the nine-metric poisoning protocol and the ablation showing that reducing immediate exposure leaves infection persistence complete are on the benchmarks page. Its reported gains — 9.97 percentage points of accuracy over linear memory and 32.8% fewer prompt tokens on GAIA-Text across three open models — are recorded in both places as unverifiable at any commit.memstate-ai/memstate-mcpwas examined and has no report: the repository is a 215-line proxy and the memory is on someone else's server. Apache-2.0 in theLICENSEfile — the README badge says MIT, which is the kind of discrepancy this list records — 40 commits between 1 March and 1 April 2026, ateceac236….src/index.tsdescribes itself exactly: "Adaptive MCP proxy for Memstate AI. Dynamically proxies all tools, resources, and prompts from the Memstate hosted MCP server — no hardcoded schemas." It forwards tohttps://mcp.memstate.aiwith an API key, and the only local writes in the tree are a config file and scaffolded skill files. Every mechanism the product sells is server-side: the dotted keypaths, the versioning that makes an old value history, theis_latestflag on search results, the conflict detection. None of it is in the repository, so there is nothing to pin and nothing to check — the atlas's second exclusion, a mechanism closed behind an open wrapper, and the same call recorded for the hosted systems above. What is inspectable is the benchmark, and it is worth the entry on its own: a head-to-head against Mem0 claiming 69.1 against 15.4, with the suite and every raw run committed. The blinded judge and the matched-timestamp pairing hold up; the four committed Memstate runs spanning 56.78 to 86.47 do not support publishing 69.1 as a result without an n. It is read in full on the benchmarks page.anthropics/claude-codewas examined and has no report: the memory the product has is not in the repository that carries its name. Read atf275fa28…— 229 files over 744 commits since 22 February 2025, of which 106 are Markdown, 27 JSON, 21 shell, 21 Python and 17 YAML. There is nosrc/,lib/orbin/: the CLI ships as an npm package and the five TypeScript files in the tree maintain the issue tracker (issue-lifecycle.ts,auto-close-duplicates.ts,sweep.ts). This is the Zep shape — a repository around a product rather than the product — and the thing an atlas reader comes for, theCLAUDE.mdconvention and the memory tool, is documented here and implemented elsewhere. What the tree does hold is 149 files of plugins and 38 of examples: skills, commands, agents, output styles and ahookifyrules engine, which under skills as procedural memory is the interesting question. They do not resolve it, for the reason theTencent/UI-Mateentry above gives — the arrow points one way. Every loader in the tree opens these files to read (load_rules,load_rule_file,open(file_path, 'r')), and a grep for anything writing aSKILL.md, a plugin or aCLAUDE.mdback returns nothing, so a completed session teaches the next one nothing that lives here. The remaining hits for memory are the honest kind: a Fargatetask_memoryin MiB in the gateway Terraform, and prose in plugin READMEs describing the feature. Recorded by name because a reader meeting the best-known coding agent in a list of memory candidates deserves to find out which half of it is public. The product's documentation names the two memories that outlive a session:CLAUDE.mdfiles the user writes, and auto memory, learnings the agent saves as it works, of which the first 200 lines or 25 KB ofMEMORY.mdload at the start of each session; sessions themselves are stored as JSONL under~/.claude/projects/and compaction clears old tool output before summarising (How Claude Code works, read 4 October 2026). Neither memory is implemented in this tree.sentrux/sentruxwas examined and has no report: everything it keeps is re-derived from the code it reads. MIT, 33,722 lines of Rust with 77 tree-sitter query files, read at6f8ff3c1…— 318 commits, every one of them between 11 and 18 March 2026, and none since. Screened first: one auto-run surface (.claude-plugin/marketplace.json, the entry a harness installs the plugin from), one build-time execution surface (sentrux-core/build.rs), no unpinned surface and aCargo.lockuntouched for 166 days; nothing was built and nothing was run. It is here because it sells itself to agents as the other half of a memory loop — "the sensor that helps AI agents close the feedback loop" — and ships an MCP server and a Claude Code plugin to do it. What crosses a session is.sentrux/baseline.json, a savedHealthReportandArchReportthat a later run compares against as a structural regression gate, and.sentrux/rules.toml, architectural rules a person writes. Neither is a belief: the baseline is a measurement of the tree that a rescan reproduces, and the rules are configuration. The nearest thing to a memory is the evolution surface, and the tool refuses the promotion itself — its own MCP definition calls git churn, hotspots, bus factor and change coupling "Raw data — not a score", and the panel beside it repeats "no score, just facts from git history." That is theLuqueee/kivgraphcall again, from the measurement side rather than the index side: a projection of a repository goes stale and is recomputed, and there is nothing a correction could name. The reversal condition is a store of judgements — a suppression or waiver keyed on a finding, surviving a rescan — andwaiverandacknowledgeappear nowhere in the tree.oooscoos/Benziwas examined and has no report: the thing in this tree is not memory, and the memory it advertises is not in this tree. Proprietary — "All rights reserved", reverse engineering forbidden — 535 tracked files and 93 commits between 29 July and 28 August 2026, read at85f08cfd…, of which not one is product source: 504 Markdown files, eight Python files that are a benchmark harness, two static pages, and nopackage.json,pyproject.toml,tsconfig.json, CI workflow or manifest of any kind — the screen returnsNOTHING SCANNEDbecause there is no execution surface to scan, which reading the tree by hand confirms rather than contradicts. Benzi is a VS Code extension over a tree-sitter code index served frombenzi.fly.dev, and the harness's own named entry points —benzi_headless.py,benzi_mcp.py,benchmark/swebench_docker.py, pluscoldstart.jsonandresults/transcripts/— are all absent, which is the Zep shape carried a step further, since here not even a client remains. What the README describes falls under theLuqueee/kivgraphcall made above: a compiler-derived symbol map is a projection of the source that goes stale and is rebuilt, not a belief a correction can name. The one thing that would be in scope is a single README bullet — "durable per-repo facts survive restarts; conventions learned once aren't re-derived every session" — and the committed run logs say more about it than the prose does.remember,recallandforgetappear nowhere inREADME.mdorbenzi_landing.html, are absent from the README's own sixteen-tool table, and are named only in the per-runtoolshistograms ofbenchmark/results/runs.jsonland the 500 files underswebench/trajs/— where the asymmetry is the finding:rememberfires 363 times againstrecalltwice andforgetfive times across all 780 recorded runs, a store written and never read. None of it survived the run that wrote it, for a reason the harness states about its index and which applies to anything under.benzi: the cold start is "paid on EVERY run here because every task gets a fresh worktree. In the product it is paid once per repo and cached in .benzi" (benchmark/harness.py:2024-2026). The reversal condition is the extension: publish the VS Code source, or a schema for that per-repo store, and the store it describes is a memory system.- Benzi's committed benchmark artifacts reproduce two headline
numbers exactly and cannot reach the rest. Nothing was run
here. Across the 500 files in
swebench/trajs/the declaredturnssum to 16,091, median 27, andsource_lines_readto 231,574, median 379 — both exact againstREADME.mdandswebench/SWE_BENCH_REPORT.md;swebench/all_preds.jsonlcarries 500 rows with exactly one empty patch,django__django-13513, as the report states; and the recorded verifier verdicts are 494revise, tenagreeand oneno_diff, which supports the report's own claim that it requests a revision on nearly every instance. The headline 391/500 (78.2%), the $37.33 and the token totals are not recomputable, becauseall_preds.jsonlholds onlyinstance_id,model_name_or_pathandmodel_patchwith no grading verdict — andswebench/metadata.yamldeclaresoss: falseandverified: false, so the submission is unverified by its own metadata. The cross-harness lines-read table is weaker still:source_lines_readis recorded on the 280benzi_productrows ofruns.jsonland on none of the 119control, 22opencodeor 2aiderrows, the Claude Code figure is reconstructed bylines_read.pyfrom aresults/transcripts/directorybenchmark/.gitignoreexcludes by policy, and the table's fourth arm — "DeepSeek Harness" — appears in no row ofruns.jsonlat all. The project discloses most of this itself:benchmark/README.mdopens "This is a vendor-run benchmark", its cut OpenCode runs are listed inoc_killed.jsonl, and its.gitignoreexplains at length why transcripts are withheld. The gap is stated rather than hidden, and the cross-harness comparison still cannot be checked from what is published. - A count in the headline findings drifted for want of a
binding, and the hedge beside it is why. The gaps section read
"Sixteen, in this entire atlas, can record that a value was rejected
so extraction cannot bring it back — see the [capability index] for the
live count" while the live figure was twenty-one.
scripts/check_claim_counts.pybinds roughly two dozen count claims to report frontmatter and did not catch this one, because it matches a number against a nearby mechanism noun and the sentence never used the word tombstone — it spelled the mechanism out in prose instead. The pointer to the live count made the staleness feel handled without making it checkable, which is the failure mode of hedging a number rather than binding it. The sentence was rewritten to bind the count to the corpus denominator, so the windowed check catches it — a bare "N systems in this entire atlas" passes only while N coincides with some other live total, which is what it had been doing; corrupting it to another number was confirmed to fail the build before this was committed. Corrected 19 August 2026. - A risk that was overstated, and the grep that would have
caught it. The Mem0Sharp
report of 21 August 2026 — the system renamed itself MagiCore on 5
September — led with a
Dreamingbehaviour that "writes speculation into the same table as fact" and said the value was "not written to the memory, to its metadata, or to the history row" so that "nothing downstream can tell them apart." At the pinned commitMemory.Behaviorwas a field on the row, the Postgres store created and wrote abehavior integer NOT NULL DEFAULT 0column, the Qdrant store filtered on it, and the service's search filter withheld every non-Normalrow unless the caller asked for them — all landed on 11 August 2026 in894b487, ten days before the pin, with a test. The report had read the 27-line prompt file the feature was described from and the Postgres schema the audit was described from, and had not runrg -n Behavioracross the tree; the field name was in the domain model, the store, the filter and a test. The direction matters: the atlas said the store could not distinguish speculation from fact when it both stored the distinction and enforced it by default. Corrected in the report; the mark it bears on,trust_state, is still withheld, because the label is fixed at write and no path moves it. 2501Pr0ject/RAGnarok-AIwas examined and has no report: it evaluates memory systems and is not one. "Local-first evaluation framework for RAG pipelines and AI agents" per itspyproject.toml,v1.11.0, AGPL-3.0 with a separate commercial licence, 251 commits since 24 January 2026 at1d4fcf96…, 146 Python files undersrc/ragnarok_ai— test-set generation, LLM-as-judge evaluators with calibration, drift, baseline and regression tracking, A/B comparison, a tracer, a monitor store — under 2,128 test functions. Twelve of those files mention memory; the only classes so named are aMemoryCacheand a Semantic Kernel memory adapter, andrg -n 'def remember|def recall' srcreturns arecall_at_kmetric. Nothing here is stored by an agent to be retrieved, scoped, corrected or forgotten later; it is the kind of harness the benchmarks page asks memory systems to be run under.nitpicker55555/MapRepairwas examined and has no report: the graph it versions lives for one walkthrough and is never loaded back. The code for Constructing Coherent Spatial Memory in LLM Agents through Graph Rectification (arXiv:2510.04195, v2 8 June 2026; Zhang, Chen, Feng, Jiang and Meng, Technical University of Munich), five commits between 8 April and 9 June 2026 at511937a4…, 14,910 lines of Python and no licence file. An LLM builds a navigation graph step by step from text-game walkthroughs on a cleaned MANGO dataset;VersionControlrecords each step as a commit of edge-level diffs with the observation and the model's analysis, exposesrollback_to,recall_stepanddiff, and builds a reasoning-history tree on which a conflict localiser computes the lowest common ancestor of two conflicting paths and an edge impact score ranks candidates for repair. That is memory-shaped in the way this atlas cares about — a belief that can be wrong, a record of when it was asserted, a mechanism for finding which assertion to retract. What keeps it out is the boundary the taxonomy draws:MapSLAMSystem.save_resultswritesnavigation_graph.jsonandversion_history.jsonat the end of a game, andrg -n 'json.load' *.py experiments/*.pyfinds readers only for the dataset and the experiment scripts — nothing reopens a saved graph to continue it. Androllback_totruncates the chain (version_control.py:140-145), so the versions after the rollback point are discarded rather than kept: the history forgets the branch it abandoned. The committedresults/hold 1,340 files behind the paper's tables. Worth a report the day a run can resume from its own output.- Seven spatial-memory repositories for robots were examined
in one round and have no reports, for one of two reasons.
The memory is per episode and lives inside a policy:
shihao1895/MemoryVLA(arXiv:2508.19236) atd732ea90…keeps a perceptual-cognitive memory bank keyed by episode withresetandclear_episode(vla/memory_vla.py:202-207) and no persistence call;nvidia-isaac/nvblox_mindmap(arXiv:2509.20297) ata76886df…, under the NVIDIA licence, reconstructs a feature map per episode andclears it (mindmap/mapping/isaaclab_nvblox_mapper.py:252);markmusic27/spatial-memeratbbc287c8…, 1,344 lines, builds egocentric maps from poses and keyframes for a MemER-style policy (arXiv:2510.20328) with no store —rg -n 'pickle|json.dump|np.save|torch.save|sqlite' -g '*.py'returns nothing. The map is built once, offline, and never updated:concept-graphs/concept-graphs(arXiv:2309.16650), MIT, at93277a02…, is the batch pipelinecfslam_pipeline_batch.pythat writes per-frame and full-scene.pkl.gzfiles and reads back only detections;IMNearth/Spatial-X(arXiv:2601.06806, arXiv:2603.26837), CC BY-NC-SA 4.0, at9afdacd2…, loads per-viewpoint observations from Matterport scans (spatialx/mp3d_extensions/mp_utils.py:58-119) for a navigation agent;AdnanSattar/Spatial-RAG-Worldmodel, MIT, one commit on 4 December 2025 at6e8597dd…, stores latent world-model states in a Qdrantlatent_memorycollection with a spatial prefilter,deleteandclear— states a model emits, not beliefs an agent could find false.HorizonRobotics/HoloAgent(arXiv:2606.23565), Apache-2.0, atef14d315…is the same case, and that commit is the HoloAgent-0 code release underagentic_robot/. The one caller of its graph writer (agentic_robot/fsr_vln/ovo/integration/hmsg_bridge.py:248) builds the FSR-VLN scene graph (arXiv:2509.13733) offline from a mapping run'sovo_map.ckpt, into a newgraph_directory stamped with the build time (agentic_robot/fsr_vln/memory/hmsg/graph/graph.py:1926-1928). The navigation node loads one such snapshot from a hand-set path (agentic_robot/core/src/navigation/semantic_goal/config/visualize_query_graph_demo.yaml:7) and never writes it, and the streaming mapper starts each run empty (agentic_robot/fsr_vln/run_stream_mapping.py:171-177). Chronotope, DovSG and the robotics plane of MagiCore are the three from the same round that cleared the bar, and EvoMemNav, a single "Code coming soon" commit in that round, has a report at the code released on 26 October 2026. - Five spatial-memory papers from the same search have no
repository to pin, and are recorded so the search is not
repeated. arXiv:2608.04574 When
Memory Lies: An Empirical Study of Spatial Memory Staleness in VLM
Agents (5 August 2026) states "We release the code, all 50 seed
map sets, full model traces" and its text carries no repository URL
— the one
github.comlink is to gym-minigrid; arXiv:2511.18112 EchoVLA (v3 7 August 2026) and arXiv:2605.22283 Spatial Memory for Out-of-Vision Manipulation in Vision-Language-Action (21 May 2026) carry no URL of their own at all; arXiv:2511.20644 Vision-Language Memory for Spatial Reasoning (v2 9 July 2026) links a project page for a memory that is a model's internal state; and arXiv:2604.16482 is a survey of spatial memory representations for navigation (13 April 2026). The search:rg -o 'github\.com/[A-Za-z0-9_./-]*'andrg -o 'https?://[^ ]*'over the extracted text of each. A paper is read here only through the artifact it publishes as its implementation; without one there is nothing to pin. arXiv:2609.18842was examined and has no report: it releases no code, and what it adapts online is a posterior nothing can name. Infinite-Parameter LLMs: Generating and Adapting Weights from Live Data (Hu, Clarke and Zhang of Boltzbit Limited with Hernández-Lobato of the University of Cambridge and Boltzbit; v2, 21 September 2026, CC BY-NC-ND 4.0, the authors' own comment reading "Preprint, containing preliminary results"). A compact hypernetwork turns live interaction data into low-rank modulations of a shared base network's feed-forward weights, attention untouched, and a Bayesian belief over the generator's latent code is updated online so the effective weights are re-derived as the belief evolves. It is recorded here because it argues against retrieval directly — the pitch is that facts and corrections supplied by users are otherwise "placed in the context (by instruction or retrieval) and re-read on every request, only to be discarded afterwards", and that representing them in the weights instead "frees the context window" and "persists updates across turns" — so a reader looking here for weights-as-memory should find why it is absent. The boundary is the granularity, not the persistence. This atlas's test is whether the store holds anything that could turn out to be false, and the absorbed content plainly does; what it lacks is any handle on it. Over 20,376 words of extracted text, across sessions, cross-session, provenance, delete, revert and rollback occur zero times, against 128 for belief and 38 for LoRA; persistence is stated at turn granularity, "persistent weight-space adaptation at turn granularity", inside one session. The "controlled" and "principled forgetting" the paper contrasts with in-context learning is the filter's forgetting factor — an uncertainty-gated update the authors describe as "a derived analogue of elastic weight consolidation" — which resists catastrophic forgetting and is not an operation on a named fact. That makes it a sharper case than the adapter granularity described above rather than an easier one: an adapter at least fails at a stated unit, a whole adapter at a time, whereas a correction here is another Bayesian update over the same latent code, arriving by the same path as the claim it corrects and leaving nothing that enumerates what the posterior currently holds. One gap between the title and the measurement is worth carrying even though the paper is out of scope, and the limitations section states it first: the belief actually evaluated is categorical over a pool of materialised codes, which "chooses among reads rather than moving within the code space", with the continuous-Gaussian belief that would move within it left to future work — so the infinite feasible space the title names is not the thing measured on the five question-answering datasets used (SQuAD, HotpotQA, QuALITY, MuSiQue and 2WikiMultihopQA). No code is released and no code- or data-availability statement appears; github occurs three times in the fetched HTML and all three are inside arXiv's own Report GitHub Issue interface, none in the paper's text.arXiv:2609.02042was examined and has no report: it releases no code, and the skill library it builds is a training-time teacher the deployed policy never consults. Act More, Decide Less: Skill-Guided Adaptive Action Chunking for Long-Horizon LLM Agents (Yang, Jin, Zhao, Wu, Zhou, Wang, Wang, Zhou and Metaxas; Rutgers, Toronto, Hong Kong Polytechnic, Amazon, Microsoft; submitted 2 September 2026, EMNLP 2026 camera-ready) trains an agent to emit variable-length action chunks instead of one ReAct action per round, and the mechanism it takes the chunk boundaries from is memory-shaped. Successful trajectories are segmented by the model into a composite skill of ordered subskill calls, each subskill a Python routine that emits one action chunk; every generated skill passes syntax, compilation and signature checks, is canonicalised to its AST and deduplicated against the library before insertion; the library starts from three hand-written skills on ALFWorld and five on ScienceWorld, caps composite skills at 20 per task category and periodically prunes those "whose long-term success rate remains zero"; and at the start of a skill-augmented rollout retrieval is category-first — composite skills for the task category ranked by a UCB-style score over success rate and usage count, the top three listed with those statistics — with a fallback to the seven most diverse subskills by description similarity. The induction prompt wraps its output in<memory>tags and asks for "compact key_value knowledge items, e.g. object type -> common locations" beside the code. Then the boundary: half of the rollouts on ALFWorld and three quarters on ScienceWorld never see the library, its only product is chunk-boundary supervision distilled into the policy by off-policy regression, and "at evaluation, the model uses only the primitive multi-action interface (no skill access)." That is optimizer state that produces a policy — the line drawn for AtlasVA — and the paper says so itself: "skills serve only as training-time scaffolds." The results are large: on ALFWorld with Qwen3-4B, 99.2 % seen and 96.9 % unseen against GiGPO's 85.2 % and 72.7 %, at 3.7 and 4.4 LLM rounds per episode against 15.9 and 21.7; on ScienceWorld with Llama-3.1-8B-Instruct, 67.2 % and 61.7 % against 35.9 % and 34.4 %. The ablation on ALFWorld with Llama-3.1-8B puts the skills at 9.4 points on the seen split (96.1 % to 86.7 %) and the chunk-aware advantage at 5.5, and plain GRPO handed the same skills at rollout time gains 5.5 points while keeping 19 rounds — the paper's own evidence that the library matters as supervision, not as a retrieval aid. Over 11,899 words of extracted text, github occurs zero times and there is no data-availability statement; the limitations section names "stronger exploration, retrieval, or validation mechanisms" for the induction stage as future work. With a release, the thing to read first would be the pruning rule, because a skill whose success rate falls to zero is the one place this paper's memory can turn out false and be retired — and whether a retired skill can be re-induced from the next successful trajectory is the tombstone question, unanswered in the text.Leonxlnx/unlazywas examined and has no report: what it keeps across sessions is an allowlist of approved shell commands, not anything an agent believes. MIT, 49 commits by thirteen authors between 10 August and 3 September 2026 at16671491…, aSKILL.mdfor Claude Code and Codex with 1,760 lines of dependency-free Node across five scripts and seven test files, self-described as "completion discipline for substantial AI-agent work, backed by runnable gates": an agent writes aGATES.mdledger of acceptance gates before working, each with aCHECK:shell command and anEXPECT:pattern, andgate-check.mjsruns them, records evidence lines carrying a digest of the gate's definition, and refuses to call a gate met unless the process exits zero and the expectation matches. Its one durable store is the approval record — a JSON file per gate under~/.unlazy/approved/, named by the SHA-256 of the ledger path, the gate id and an oracle signature overCHECK,EXPECT, working directory, shell andPATH, which must live outside the repository (gate-check.mjs:382-389) and which--statusnever writes; a second, per-repository store under.unlazy/<scope>/holds pipeline leases and session state for orchestrated runs. Both are records of what a person or a run authorised, keyed on the exact command, and neither can turn out false in the sense this atlas asks: a memory is what an agent came to believe, and unlazy is deliberately built so that its own outputs are never that. Theresearch/validation-protocol.mdfile is worth the visit anyway — it demotes the project's earlier six-run comparison to "design provenance only", states it is "too small for broad model claims", and pre-registers what a rerun would have to record — which is more than most of this corpus says about its own numbers.arXiv:2609.01481was examined and has no report: its released code carries a tester's report from one iteration of a task to the next, nothing crosses tasks, and the only state read back across processes is the previous trial's game workspace. Harness-of-Harness: Multi-Day Autonomous Software Development with Continual Improvement (Yan and eight co-authors, Shanghai Artificial Intelligence Laboratory; preprint, 1 September 2026) wraps Codex, OpenCode or Pi in an outer loop of Project Planner, Developer and QA Tester, and states that it "adopts progressive disclosure rather than a dedicated memory module".Flesymeb/HarnessOfHarnessaddedhoh-lite/inec845b75…on 23 September 2026; atae7cc6fb…(MIT, 75 commits by one contributor) it is 60 Python files and 14,453 lines beside a vendored Godot MCP server. Each run gets a directory named for its task and start time (adapters/gamecraft_bench/runner.py:2491-2495), the runtime refuses one whose receipt exists (core/runtime.py:58-62), and--resume-fromseeds a new run from the last valid trial of the same task (runner.py:2451-2464,artifacts.py:437-482). Within a run, the planner receives the latest tester report cut to eight issues, four bugs, four gaps, three goals and three preserve items of 240 characters each (core/prompts.py:191-217), plus the last three entries of an in-process history list (:107). Two files look like memory and nothing reads them:loop_memory.json(core/prompts.py:506), andevidence_history.json, which the prompt calls the "complete lossless public ledger" (:100-104) and which a resumed run rebuilds from the seed trial's report alone (runner.py:2586-2599). The code settles what is carried forward as true. The next plan is told "Do not remove or weaken" the tester'spreserveitems and any claim review with a pass-like status (core/evidence.py:342-354,:398-417); thedemosandasset_evidencebranches (:356-396) take entries with no status check, though the next-loop contract asks for neither key (adapters/gamecraft_bench/prompts.py:101-111). The whole set is replaced by the next report, so nothing stays settled for more than one loop unless the tester re-asserts it. There is no issue ledger to reopen from: issue ids carry the loop number (core/evidence.py:152,core/stages.py:6-7), so no issue keeps an identity between loops, and "do not reopen an older item" is prompt text (core/prompts.py:103-104). The.gameloop/vcs.jsonbindings and sealed-change receipts in the run's public product,Flesymeb/fusepoint, have no counterpart in the release. The one SQLite file is an FTS5 index over the official Godot documentation (tools/godot_docs.py:1,:141-160). The nine tests in.github/ci/test_hoh_lite.pycover receipts, resume selection, the dry run and planner retries, and none exercises the carry-over. Searches run at the tree root:git grep -n -i -E 'memor|remember|recall|lesson|sqlite|embedding|vector|pickle' -- . ':!hoh-lite/src/gameloop/_vendor'(hits arebuild_loop_memoryand the docs index);git grep -n -E 'loop_memory\.json|evidence_history\.json'(writes and prompt text only);git grep -n -i -E 'reopen|ledger|vcs\.json|sealed' -- . ':!hoh-lite/src/gameloop/_vendor'(the prompt text only). The screen found 0 RUNS, 0 EXEC, 3 FRESH (hoh-lite/pyproject.tomland the vendored server'spackage.jsonand lockfile, all in a subtree added on 23 September 2026) and 2 FLOAT (pyproject.tomlwith no lockfile; caret ranges beside the vendored lockfile), and nothing was installed, built or run.- Prove2Me, the shared theorem library behind the Fermat's
Last Theorem formalization, was examined and has no report: the memory
the agents used is a hosted service whose server is published nowhere,
and what is public is its client contract, a February prototype without
any of the mechanisms, and the output. SiliconANGLE's report of
4 September 2026 and Anthropic's own post, Formalizing Fermat's Last
Theorem, describe a "Claude Code-based multi-agent
harness" of dozens of agents proving 30,300 intermediate theorems
in eleven days for six billion output tokens, whose early attempts
"quickly lost track of the project's state and stopped collaborating
effectively" and contributed about 7 % of the final non-boilerplate
lines, and which then ran on Prove2Me — a platform keeping "a
directed acyclic graph of theorem statements that agents used to decide
what proofs they should attempt next," separating statements from
proofs with the links maintained independently, and holding "a
natural-language description of each theorem statement," which the
post credits with "mitigating memory degradation." The paper
behind it, Prove2Me: An Open Collaborative Platform for Scaling Math
Formalization (Chen, Marwaha, Lu, Yuen and Peng;
arXiv:2608.28433, v1 28 August, v2 31 August 2026, cs.AI, cs.LO, cs.MA), is the memory design in full: every statement is "atomized and immutable, carrying all the context needed to compile on its own," so any proved theorem is importable by any later proof-sketch in any mission; the accumulated corpus is named Formalpedia; a search API indexes the standardised natural-language description every submission must carry, and agents "are also instructed to search before they submit"; a proof is a term whose type must match the target's exactly, a disproof is a term of the negation, and the paper's own example of a memory turning out false is a sketch importinggotsman_linial, disproved by a second agent and replaced bygotsman_linial_with_zero; milestones are the captain's idempotent and authoritative lemma targets so that parallel agents converge on one statement instead of duplicating incompatible ones; and the closing questions are the atlas's — "how agents should search a large, evolving corpus of formal statements" and "how such agents can exchange harnesses, lessons, and context to learn continually remains open." Over 6,904 words the paper links no server repository and the phrase source code does not occur. Three repositories were read.prove2me/prove2me_workspaceat58332c69…(47 commits by one author between 4 July and 5 September 2026, no licence file) is the client side: aSKILL.mdat version 0.9.7 and 2,729 lines of API reference describing the service atprove2.me— keyword search over names and natural-language statements (GET /api/v1/theorems?q=), a per-theorem dependency graph, open leaves and decompositions, a description edit history (description-versions), votes, tags, a saved list, mission discussions whose soft-deleted comments are returned as tombstones on request, verdictsPENDING → ACCEPTED | SKETCH_ACCEPTED | CE | WA | SORRY | FAILED | ERROR, an explanation that is patchable beside a solution that is immutable, and three rules that gate every submission, the second of which is never to import one's own target because "it is stored as asorryplaceholder, and citing it would prove the goal from itself" — plus 279 lines of Lean meta-programs that extract a declaration graph and sketch information from an existing project for upload.marwahaha/prove2meat5ee5b15c…(36 commits by one author between 3 and 24 February 2026, no licence file) is a FastAPI, React and Postgres prototype from before the paper: astatementstable withis_solved,is_disprovedandis_archivedflags, a proof column, tags, comments, a prize that grows over time, and a gatekeeper that sends each new statement to an external prover, Aristotle, during a holding period to attempt a proof or a disproof before people may; its list endpoint filters by tag and sorts by date or prize, the word dag occurs zero times in its backend and search only asre.search, and it has no description field, no sketch, no milestone and no mission.anthropics/fermats-last-theoremataa2d8b34…(one commit, 3 September 2026, Apache-2.0) is the output:Theorems/with 29,511 statements,P2M/Sol/with their proofs, 1,450 definition modules,PROOF-PATH.mdnaming the Lean theorem behind each step, aformalization.yamlrecording zerosorryand the three standard axioms, andP2M/Util.lean, the one piece of the platform's verification visible in the artifact —#p2m_type_eq, which checks a proof's type against its card's up to definitional equality and refuses when the statement's universe parameters had to be specialised to match ("the proof is less general than the card"); the README says a from-scratch build of 60,475 modules took 5 h 32 min at 96 jobs, comparator's kernel replay 14 h 46 min, and an independent Rust kernel checked 1,052,234 declarations. With the server readable, this would be screened as a shared memory whose entries are machine-checked and whose disproof is a first-class status, and the first thing to read would be the search — what the index holds beyond the description text, and what an agent that searched and found nothing is told about near-duplicates — because the paper's own account of failure before Prove2Me is agents that could not find what each other had already proved. youssouf994/LangBrainwas examined and has no report: what it persists is a LangGraph checkpoint and an audit log of actuator changes, and neither is a memory an agent could later correct. A hierarchical-agent boilerplate for a smart-home and medical-homeostasis demo at4b6951f8…(12 commits by one author between 3 and 4 September 2026, 44 files, Polyform Small Business 1.0.0), whose own README opens with a warning that it is a prototype and lists a "persistent in-process checkpointer (file-backed InMemorySaver)" among the changes of 4 September. That checkpointer (app/checkpointer.py) is LangGraph'sInMemorySaverpickled whole to.checkpointer.picklenext to the project — a committed, zero-byte file at this commit — so graph state survives a recompile; it is conversation-window state with no identity a later turn could correct, which is the atlas's boundary. The SQLiteeventstable (app/db/database.py:26-36,app/tools/event_log.py) is an append-only record of actor, action, target, old value, new value, reasoning and anescalatedflag, read back by every agent as "recent history" within a 240-minute window and by the brain to arbitrate conflicts, and rewritten only to prefixRESOLVED_onto a settled escalation; it records what an actuator was set to, which happened, and cannot turn out to be false.rg -n -i 'embedding|vector|recall|remember' appreturns nothing, andmemoryoccurs only as the LangGraph saver's module name. Recorded because a checkpoint file and an audit table are the two artefacts most often mistaken for agent memory in submissions to this atlas, and this repository has one of each and nothing else.AppFlowy-IO/AppFlowywas examined and has no report: its AI chat's memory is an in-process message list with a running summary, and its local retrieval is over the workspace's own documents. A collaborative workspace client at5cf3a365…(AGPL-3.0, 7,210 commits by the GitHub count since June 2021, read from a shallow clone), whoseflowy-aicrate builds each local chat on langchain-rust'sSimpleMemoryor aSummaryMemorythat regenerates a running summary from the messages it holds (frontend/rust-lib/flowy-ai/src/local_ai/chat/llm_chat.rs:49-52,summary_memory.rs:11-45) — conversation-window state with no identity a later turn could correct — and whose local AI answers over the workspace's documents through a sqlite-vec store (flowy-ai/src/embeddings/store.rs).rg -n -i 'memor' frontend/rust-lib/flowy-ai frontend/appflowy_flutter/lib/plugins/ai_chat --glob '!*.arb'finds those two classes, anInMemoryChatControllerand a cache comment, and nothing durable; the hosted side, AppFlowy-Cloud, is a separate repository and was not read.foambubble/foamwas examined and has no report: it is a personal knowledge base for VS Code whose one AI feature ranks similar notes by embedding, and nothing in it is written by an agent or read on an agent's behalf. At97b82e4e…(MIT, 1,656 commits since June 2020, version 0.44.6, 18,812 lines of TypeScript underpackages/foam-vscode/src), the experimental Related Notes (AI) panel embeds each note through anEmbeddingProvider— an Ollama backend is the one implemented — caches the vector by content checksum in the extension's global state (src/ai/model/embedding-cache.ts,src/vscode/features/ai/build-embeddings.ts) and lists the nearest notes to the active one (src/vscode/features/ai/related-notes.ts). That is a similarity index over a store only the person edits; there is no MCP surface, no tool and no write path for a model —rg -l -i 'mcp|copilot|openai|language model' packagesreturns the provider interface and that feature — which is the difference between it and Logseq, whose report exists because an agent can write to the graph.ActivityWatch/activitywatchwas examined and has no report: it records what a machine's user did, in intervals that cannot be false, and no agent reads or writes the store. The meta-repository at88d559ab…(MPL-2.0, 1,145 commits since April 2016) holds its components as submodules, and the store isaw-server-rustatdf9c4fab…: abucketstable and aneventstable ofstarttime,endtimeand a JSONdatain SQLite (aw-datastore/src/datastore.rs:67-97), written by watchers as heartbeats that merge into the previous event when the data is equal and the gap is within a pulse time (aw-transform/src/heartbeat.rs:3-12), filtered before storage by rules that drop an event or redact a field (aw-datastore/src/privacy_filter.rs), queried by its own language, and synchronised between machines. An event is an observation of a window title or an idle state at a time; it is provenance for a memory, never a memory. The one nod to a model is agptme.tomlnaming files an assistant may read.rg -n -i '\bai\b|llm|agent|mcp' README.mdfinds nothing about agents.polmanas1998-star/membenchwas examined and has no report: it is a benchmark harness, and its findings are on the benchmarks page. At57377458…(MIT, twenty commits by one author between 5 and 12 September 2026) it generates 104 facts with a day on which each stopped being true, scores silence after that day as correct, brackets the arms with silent, guessing and oracle witnesses and a scrambled-corpus control, and reports from committed JSON, with a poisoning harness whose fixed clock makes its row a lower bound, a one-vote-per-triple rerun, six rigged environments, a long confinement and an echo chamber added on 7 and 12 September; its subject is the same author'sholomem, an FHRR holographic memory with a 45-day half-life. Nothing in the harness stores a memory;rg -n 'class .*Memory|def store|def remember' membench/*.pyfinds one hit, the scrambled control atmembench/arms.py:120.openrecall/openrecallwas examined and has no report: it is a screen recorder with a search box, and the search reads its own vectors in the wrong width. At62303e09…(AGPL-3.0, 90 commits since June 2024, 1,141 lines of Python) it screenshots every three seconds, drops frames whose structural similarity to the last exceeds 0.9, runs OCR, embeds the text withall-MiniLM-L6-v2, and stores(app, title, text, timestamp, embedding)in one SQLite table.insert_entrywrites the embedding asfloat32bytes (openrecall/database.py:112) andget_all_entriesreads it back asfloat32(line 58), butsearchinopenrecall/app.py:140decodes the same blob withdtype=np.float64, so the query ranks by cosine over vectors of half the length holding reinterpreted bytes. No agent reads or writes the store, nothing is corrected or forgotten, and the seventeen tests cover the cosine function and the table, not the search.rg -n 'agent|llm|mcp' -i openrecall/*.pyfinds nothing.weaviate/weaviatewas examined and has no report: it is the vector database several systems here delegate to, and its two agent-facing features are a database's, not a memory's. At85dbeace…(BSD-3-Clause, 29,229 commits by the GitHub count, release v1.39.2 of 2026-08-26) it carries a Model Context Protocol server inside the binary — read tools for collections, configuration and tenants, a hybrid search tool, and schema and object-upsert tools that register only whenMCP_SERVER_WRITE_ACCESS_ENABLEDis set (adapters/handlers/mcp/server.go:50-126), gated per request by a runtimeMCP.Enabledflag that answers 503 while off (adapters/handlers/rest/handlers_mcp.go:31-73) — and per-collection object expiry: anObjectTTLConfigof adeleteOnproperty plus adefaultTtlin seconds, with expired-but-undeleted objects optionally filtered from results and deletion runs coordinated on the Raft leader so only one is ever in flight (entities/models/object_ttl_config.go:29-41,usecases/object_ttl/object_ttl.go:33-49). An object has no scope key of its own beyond the tenant, no state, no provenance and no supersession; those are the memory layer's to add, which is why Cognee and others sit on top of it.rg -n -i 'agent memory|conversation memory|memory store|long-term memory' README.mdfinds nothing.- A ladder that was schema, and the producer test that would
have caught it. The Noosphere report of 9 August 2026
described a candidate tier whose status "starts at
EPHEMERALand promotes on usage" with five counters driving promotion, and its matrix row said so. At that pin and at the current one, nothing insrc/creates aMemoryCandidaterow, nothing setsPROMOTED,PENDING_REVIEWorREJECTED, four of the five counters are selected and never incremented, the promotion module's review status is a type no table holds, and recall reads articles. The enum, the counters and the module were read as a mechanism; the check theadd-memory-systemskill asks for — work backwards from the field to every assignment — was not run on them. The mark this bears on,trust_state, was withheld on a vocabulary argument and stays withheld on the right one. Found while confirming a re-pin the maintainer submitted as #21, whose own claims all held. - A position claimed from the wrong file. The OpenMake LLM report of 6 September 2026 said the memory block was prepended to the system prompt, "which places it where a provider's prompt-prefix cache would be invalidated by any change to it." At the commit it pinned, the function that assembles the prompt pushed the block after the static guard, artifact and answer-format blocks, under a comment marking the boundary between cacheable and per-user content and giving prefix-cache preservation as the reason. The claim was written from the block builder, which returns a string, rather than from the assembler, which decides where the string goes; a sentence about where memory sits in a prompt is a claim about the caller, and the fix is to cite the line that concatenates. The same reading missed that the data export queried the predecessor table's columns and returned nothing, because it followed the memory's own seven files and not every consumer of the table's name; the re-read of the same day corrected both.
- A layer present at the pin and not described. The
GBrain report of 9 August 2026
described one memory, the
takestable, and withheldbitemporalfor the way its validity window was queried. The tree at that pin also held the v0.31 hot-memory layer of 9 May 2026 — afactstable withvalid_from,valid_untilandexpired_at, arememberpath with a required provenance, a per-kind confidence decay, a cosine-and-classifier deduplicator and a consolidator that promotes clusters of facts into takes, in fourteen modules undersrc/core/facts/— and the report did not mention it. The reading followed the README's framing, which leads with takes, calibration and synthesis; the correction on 7 September 2026 covers both memories, awardsbitemporalon facts, whose window has been read at query time since 1 September, and narrows the takes finding to the scorecard's date window. The check that would have caught it is the table list —rg -o 'CREATE TABLE IF NOT EXISTS [a-z_]+' src/core/migrate.ts | sort -u— read before the README, so that a table the README does not lead with is a question the reading has to answer. zahid23saim/llm-eval-harnesswas examined and has no report: it is an answer-grading script, and nothing it touches outlives one run. At2973d6db…(MIT, three commits between 3 and 7 September 2026, 150 lines of Python plus 91 of tests) it loads a gold JSON array and an{id: answer}object, judges each item by its ownexact,containsornumericrule after lowercasing and stripping trailing punctuation, prints an accuracy line with every miss, and exits 1 on any failure. The only twoopen()calls read the inputs; the only writes in the tree are test fixtures totmp_path. No agent calls it, no model is called by it, and there is no store, so nothing can be scoped, corrected or forgotten — it is the scoring half of an eval, not memory. The one feature that would compare across runs, the regression diff, is sold in a paid kit the README links and is absent from the tree:rg -n -i 'regress|diff|pass@k|json_field' llm_eval.py tests/finds nothing, and.github/holds onlyFUNDING.yml, so the "CI-friendly" claim rests on the exit code alone. Screened before reading: no manifest, hook or workflow to scan; nothing was run.- CompBio and MIRaS were examined and have no report, on two
independent grounds: the code the paper points at is behind a request
form, and the memory is the literature rather than the user.
CompBio and MIRaS — a multi-omic analysis platform built on a
memory-based intelligence engine (Barve, Storer, Hoxsie, Marcum,
McMichael, Lalmansingh, Smith, Johnson, Kuster and Head; Nucleic
Acids Research 54(16), published 24 August 2026, doi:10.1093/nar/gkag833,
CC BY-NC, conflict of interest "None declared"). It reaches a
memory atlas honestly: it is built on a Memory-based Intelligent
Reasoning System, it uses episodic and semantic memory
as its organising terms with the cognitive-science definitions spelled
out, and it opens by drawing this atlas's own boundary — retrieval
augmentation, context augmentation and longer windows "provide
engineering workarounds for this limitation, [but] none represent
genuine persistent, recallable memory." The mechanism is a
Generalized Memory Model: every PubMed abstract and full-text window
from the "Q1, 2025 PubMed release with 38 355 642 abstracts and 6
600 121 full-text articles" tokenised into an episodic memory
across four framework dimensions, with complex memories normalised
against randomly drawn peers to isolate enriched signal, held resident
in server RAM as what the paper calls "memory-as-a-service." A
user submits a gene list; the reasoning component computes a
contextual semantic memory against that model and returns a
knowledge map. Nothing the user submits is written
back, the model is identical for every user and is regenerated
only when the source corpus is, so nothing stored survives a session
with an identity that could later be scoped, corrected or forgotten —
which is this atlas's bar, and the paper does not claim otherwise. The
second ground is the one worth recording for method. The version of
record carries a code-availability statement the December 2025 preprint
does not — "The code for CompBio and MIRaS is available from the
Zenodo repository" — and that deposit (10.5281/zenodo.18602034,
v1 of 15 December 2025, metadata CC BY 4.0, declared C++, PHP and
JavaScript) lists
miras.zipandcompbio.zipand marks them Embargoed: the record shows zero downloads and zero bytes of public data volume, and the files sit behind "If you would like to request access to these files, please fill out the form below." A statement naming a repository is not inspectable code at a pinned commit, and the atlas did not request access, because a request-gated archive would not become one; a search of GitHub, GitLab, Bitbucket and Zenodo for a public mirror under the authors' or the institution's names returns none. The running system is athttps://gtac-compbio-ex.wustl.edu, free to non-commercial users. Two claims are worth carrying for anyone who does get the code: the system is asserted to be "by design … incapable of hallucination," with every result traceable to its source knowledge, and the positive control reports 46 of 50 hallmark gene sets recovered without a curated pathway knowledgebase. xiaoqi-7/MAP-Graph(arXiv:2608.10509) was examined and has no report: its code was released on 25 October 2026, and the store is rebuilt empty at the start of every task, so nothing it holds outlives one four-agent round. No licence file and no licence statement in the README, the manifests or the code, so the tree grants nothing; only the bundled AAAI style files carry terms of their own (CC BY 4.0 inpaper/aaai2027.sty, LPPL inpaper/aaai2027.bst). Read atd94b0bf3…, the repository's only commit, dated 25 October 2026 and authored as YiqiWANG under the noreply address of account 53900555, which isxiaoqi-7, whose profile name is YiqiWANG; with the paper's LaTeX source inpaper/under the same title, the owner appears to be the first author, Yiqi Wang. The tree is 3,307 files: 3,243 synthetic task, ground-truth and transfer-subset JSON files underartifact/data/, the paper and appendix sources, and 12,309 lines of Python, of which MAP-Graph's own backend is 1,789 lines underartifact/src/map_graph/. The screen could see two files, and found nothing that auto-runs, no build-time execution and no unpinned dependency (artifact/requirements.txtpins all eight packages exactly); nothing was installed or run. The paper calls MAP-Graph task-scoped, and the code agrees.AutoGenWorkflow.run_taskcallsreset_taskfirst (artifact/src/agents/autogen_workflow.py:118), which empties the record and source catalogs, replaces the NetworkX graph and opens a newchromadb.EphemeralClient(artifact/src/map_graph/memory.py:155-187). The graph is written to JSON after each task (artifact/scripts/run_mapgraph.py:54-65), and only the evaluator reads that file back (artifact/scripts/evaluate.py:196-199); the paper itself describes the experiments as "within-task coordination rather than cross-session accumulation" (paper/anonymous-submission-latex-2026.tex:208). The two mechanisms the paper credits match the code. A derived record gets the intersection of its references' scopes, falling back to the writer when the intersection is empty (memory.py:716-739). Revocation clears the source's scope and recomputes the records that cite it directly (memory.py:428-458). The filter's revocation check reads only a record's direct references (memory.py:760-769), so a record two derivations below a revoked source passes it. That record is caught by the recursive trust walk instead (artifact/src/map_graph/trust.py:372-410), which multiplies its rank by 0.15 (trust.py:170-171) and makes the gate block any action it supports (trust.py:279-287). The typed graph with ten edge types is not what decides anything: retrieval and the gate walk each record'sderived_fromlist, and the graph is read only bypropagate_affectedandexport(artifact/src/map_graph/graph_builder.py:237-281), both called after the gate has ruled (autogen_workflow.py:258,:294). This explains two ablation rows. Compressed graph barely moves (94.33% task success against 94.96%), and No provenance graph switches off all seven components at once (memory.py:56-66), so its drop measures the whole stack rather than the graph. The headline numbers do recompute. Re-deriving them withpython3 -Ifrom the 21,600 committed per-task rows inartifact/final_results/canonical/main/task_metrics.csv, I reproduced every task-success, decision-accuracy and unsafe-action figure inpaper_table.csv. Each attack, leakage and revocation figure is the rate over that condition's 450 tasks (MAP-Graph 0.00 on each; B6 36.44, 20.44 and 39.33). The seven ablation rows recompute fromper_task/ablation_task_metrics.csv, including No permission filter at 96.00% success and 78.63% accuracy. The 3.2 GB of raw run outputs those rows came from are not committed, as the README says. No test exercises MAP-Graph's backend:artifact/tests/test_paper_baselines.pycovers four of the baselines and the model client. The one store in the tree that outlives a task is the G-Memory baseline (B3), which keeps up to 512 trajectories and its insight graph across the tasks of one process (artifact/src/memory_baselines/gmemory_graph.py:82-109) and rebuilds them from saved outputs on resume (artifact/scripts/run_baseline.py:171). That is an adaptation of another system, and the paper names it as a limitation (anonymous-submission-latex-2026.tex:297). Searches:git grep -n -E 'PersistentClient|persist_directory|sqlite3|pickle|shelve' -- artifact/src artifact/scriptsreturns nothing, againstgit grep -c EphemeralClient -- artifact/src, one line in each of five files;git grep -n -E 'graph_builder\.graph|\.graph\.(nodes|edges|successors|predecessors|in_edges|out_edges)' -- artifact/srcreturns eight lines, six insidepropagate_affectedandexportand two atmemory.py:438-439, a write;git grep -n -E 'MAPGraph|map_graph' -- artifact/testsreturns nothing, against 39 lines for the same pattern overartifact/src;git ls-files | grep -i -E '(^|/)(licen[sc]e|copying|notice)'returns nothing.pantheon-org/agentic-contextwas examined and has no report: it is a reading list about the context window, and it draws the boundary itself. Atd07dac06…, the last commit of 14 April 2026, the tree is sixty-eight Markdown files, three Python scripts that extract PDF text, build a reference index and sync a source, and an Astro site that publishes the result — seventeen per-tool analyses underanalysis/, twenty-one reference summaries under a topic index, aREVIEWED.mdtriage log and aPUNCHLIST.mdof pending dives. Nothing in it stores anything, and nothing reads a store. Its own README states the scope this atlas would have to overlap with and does not: "given a fixed or sliding context budget, how do agents decide what to put in it?", listinglhl/agentic-memoryas the adjacent repository covering "long-term memory: storage/retrieval across sessions." It is worth recording for two reasons. Its subjects are vendored as seventeen submodules undertools/and its analyses are written against them rather than against a README, which is the discipline this atlas asks of itself; and three of those seventeen already have reports here —context-mode,serenaandgraphify, whose submodule URLsafishamsi/graphifyredirects to theGraphify-Labs/graphifythis atlas pins, a rename worth knowing about before anyone treats the two as different projects. Two claims in its README overstate the tree:references/papers/is described as archived PDFs and holds a.gitkeep, andreferences/bib/is described as BibTeX per arXiv id and holds a README. No licence file, and the pin is the head ofmain.lhl/agentic-memorywas examined and has no report: it is a peer to this atlas rather than a subject for it, and the system worth reading is the one it points at. At8bc58aed…, the last commit of 9 May 2026, the repository is a hundred and sixty-three Markdown files and thirty-eight PDFs with no source file of its own outsidevendor/: thirty-nine analyses of arXiv papers, forty-six reference summaries, about twenty analyses of shipped tools, aREVIEWED.mdtriage log, two punchlists and atemplates/directory holding the two document shapes it writes. It stores nothing an agent writes and retrieves nothing an agent reads, which is this atlas's bar. The method is close enough to this atlas's to be worth naming: subjects are vendored as twelve submodules and read at a named commit — Memobase is verified "against source code at commit358c16bb" — a system that fails triage keeps its entry with the reason, and each promoted analysis ends on the gaps it found. Eight of those twelve subjects have reports here as well:cognee,hermes-agent,hindsight,honcho,mem0,memobase,openvikingandsecond-me.benchmarks/sources/is the part most worth borrowing: it collects the sceptical readings of the benchmarks the field quotes — a LoCoMo audit, Zep's "lies, damn lies" post, two MemPalace issues — rather than the scores. The finding that matters for this atlas is downstream of all that. ItsANALYSIS-shisad.mddocuments shisad, its author's own assistant daemon, atv0.7.3and commitf20930b, and describes a formal trust matrix set by the runtime rather than by callers, per-user and per-workspace scoping that fails closed, a consolidation worker whose writes resolve totrust_band=untrustedby construction, and a poisoning-case fixture — several of the marks this atlas grades for. That repository is public and Apache-2.0 atshisa-ai/shisad, and it has moved since the analysis was written, so the analysis is a pointer rather than a substitute for a reading. No licence file on the research collection itself, which leaves its summaries all-rights-reserved despite the BibTeX block inviting citation.carsteneu/ai-memory-comparisonwas examined and has no report: it is a feature matrix, and the useful thing about it is where it disagrees with this atlas. At287316f9…of 9 September 2026 it is MIT-licensed and holds no memory of its own:data.jscarries one record per system with one field per feature,evidence/holds eighty-six Markdown files citing specific source lines,CRITERIA.mdstates what earns each mark, andbuild.jsrendersindex.htmlandcomparison.mdfrom the data in CI. Eighty-six subjects across seventy-nine features on seven axes, under a rule this atlas would recognise — "If a feature isn't documented in the project's public README, docs, or source code, it's marked—. No assumptions, no inferences", with "Code beats docs" as the tiebreak — and a disclosure that its maintainer wroteyesmem, which it lists under the same rules and which is read here. The comparison it invites is worth writing down. Seventy of its eighty-six subjects have reports on this site; sixteen do not, which is the largest single pointer to uncovered ground this atlas has been handed. Three of its repository URLs return 404 —suanmo/memorybear,tele-ai/telememandmemorix-ai/memorix. The first two are live underSuanmoSuanyangTechnology/MemoryBearandTeleAI-UAGI/telemem, the names pinned here, so a join on its URLs would have reported two covered systems as uncovered; the third is a link this atlas would not follow anyway, because the comparison's own row calls it "Generic vector-store SDK wrapping FAISS/Qdrant — NOT agent memory." The disagreement that runs the other way iscampfirein/byterover-cli, which is the post-rename name of the repository pinned here ascampfirein/byterover-cli— a rename recorded on thebyteroverpage on 9 August 2026, and the second time in this appendix that a corpus-to-corpus join has produced a false gap because a URL cannot see a rename. Both directions are the same lesson: resolve every repository URL through its redirect before concluding that either corpus is missing something.harbor-framework/terminal-benchwas examined and has no report: it is a benchmark, and its unit of work is one session. Terminal-Bench is where frontier agent builders compare capability, and at83c7a617…it holds sixty-six live task directories and ninety-one archived ones, each an instruction, a container, an oracle solution, tests and atask.toml. It stores fixtures and results: a task is a thing to be solved rather than a claim that could turn out false, and a leaderboard row records a run that happened. A run is one task in one fresh container graded at the end, nothing an agent works out in one task reaches the next, and a search of the instructions for a second session, a resumption or a prior run returns nothing — so there is no store that survives a session with an identity a correction could name, which is this atlas's bar. It is recorded on the benchmarks page instead, for two reasons that belong there rather than here: the eight-hour per-task budget makes it a long-context benchmark rather than a memory one, which is the boundary that page draws; and its leaderboard reports a confidence interval, a per-trial duration and a dollar cost on every submission, which is the reporting standard the memory benchmarks catalogued there do not meet.EuniAI/ContextBenchwas examined and has no report: it is a benchmark, and its unit of work is one session. ContextBench (arXiv:2602.05892), read at1436c28a…, scores how well a coding agent finds the code an issue needs: 1,136 tasks, each one checkout at one commit with a human-verified gold context, graded on file, definition and line recall and precision. What it stores is a fixture and a run log. A gold context is code to be found, not a claim that could turn out false, and nothing an agent reads in one task reaches the next, so there is no store that survives a session, which is this atlas's bar. It is recorded on the benchmarks page instead, because it scores precision beside recall on the read side of the boundary that page draws, and because its evaluator's micro-averaged aggregate is not the per-task mean the paper and leaderboard publish. Screened before reading: no auto-run surface, 34 build-time execution points and 21 unpinned surfaces, all but three inside the vendored agent frameworks underagent-frameworks/; only the evaluator, the paper and the leaderboard's committed submission were read, and nothing was installed or run.- AgentHorizon (arXiv:2610.11050) was
examined and has no report: it is a benchmark for judges of computer-use
trajectories, and its unit of work is one trajectory.
AgentHorizon: Evaluating Agentic Judges for Long-Horizon
Computer-Use Tasks (Lù, Vattikonda, Hajimiri, Pesaran Zadeh,
BehnamGhader, Darwiche, Kazemnejad, Pal, Drouin and Reddy, v1 8 October
2026), code at
ServiceNow/agenthorizon, read at8584a347…: four commits from 9 June to 6 October 2026, 36 files, about 8,200 lines of Python, and no licence file. It scores whether a judge accepts a successful trajectory and rejects one that completed a similar but incompatible request, built by swapping instructions between paired recordings, so every negative has its positive control from the same recording. Nothing in it stores or retrieves memory across tasks, which is this atlas's bar. One thing about how it runs agentic judges belongs here. In sandbox mode each judge CLI runs with the experiment'ssandbox/directory as its working directory (scripts/evaluate_trajectories.py:1390-1397,:1833), and Claude Code keys its per-project state, the session transcripts and the auto-memory directory among them, by working directory, which the script's own transcript lookup also assumes (:1642-1643). So every task in one experiment shares one Claude Code project, although a comment says each eval "creates a brand-new project dir (via--session-id <uuid>)" (:807-811); whether any judge wrote memory there was not checked, since nothing was run. The same lookup builds the path from the script's own working directory rather than the sandbox, so in sandbox mode it reads a different project from the one the judge wrote to. The screen found no manifest it parses (the tree has no requirements, pyproject or build file), so the scripts were read by hand; nothing was installed or run. - JAZ (arXiv:2609.26891) was
examined and has no report: its long-term memory is the previous agent's
raw REPL history handed to the next one as a variable, inside one run,
and nothing outlives the process. Harness as a Language: A
Minimalist Agent Framework With Maximal Expressivity (Li, Liu,
Vukelic, Shen, Lall, Thakur, Zhang, Khattab, Light and Solar-Lezama, v1
22 September 2026, NeurIPS 2026 TTCL workshop), unrelated to the jaz report. The framework,
jaz-lang/jaz, read at0803d497…, is Apache-2.0, six commits from April to September 2026; the evaluation code,jaz-lang/jaz-evals, read at2ffe7b5e…, is MIT, four commits, and pulls its StuLife and AppWorld environments from two submodule forks on ajazbranch. Everything the model sees is a variable in a code environment, and one primitive,invoke, lets that code call the model again. On StuLife the configured handoff passes a fresh subagentprev_history=globals().get("prev_history", []) + __history__(configs/stulife_jaz.yaml:34-39), and the prompt tells it to search that list with code before acting (prompts/long_horizon/jaz.md). On AppWorld, "continual self-improvement" is one root agent with a four-hour execution budget working through 417 tasks, editing the prompt and tools it hands each subagent between batches (configs/appworld_jaz.yaml:1-2,:21-22;prompts/ttsi/jaz.md:1-9). Neither writes anything that a later run reads:git grep -n -i -E 'pickle|dill|checkpoint|save_state|load_state|sqlite|shelve' -- srcmatches only comments aboutdeepcopyand process spawning in both repositories. The result worth carrying is the comparison the paper draws. Kept whole and searched by code, the raw history beats Letta by 8% at half its cost on StuLife's recall-heavy tasks, inside one session. That makes a lossless transcript the baseline an extracting memory has to beat on recall. It says nothing about correcting or forgetting a fact across sessions, which a variable that dies with the process cannot be asked to do. Screened before reading:jazhas one unpinned surface and nothing else;jaz-evalshas one auto-run surface,.gitmodulesnaming the two benchmark forks; nothing was installed or run. bhensley5/overgraphwas examined and has no report: it is an embedded graph database with vector search that names agent memory as a use case, and the memory semantics belong to the caller. MIT or Apache-2.0 at the user's option, read at13ad827d…, the head ofmainon 10 October 2026 (release v0.17.1). It has 24 commits since 5 March 2026, about 210,000 lines of Rust undersrc/outsidesrc/engine/tests/, and 2,926 Rust test attributes, none run. It is an LSM tree of mmap'd segments with a WAL, dense HNSW and sparse inverted vector indexes, GQL, and native Node.js and Python bindings. Nothing in it defines a memory unit, extracts, embeds or exposes a tool to a model: embeddings arrive from the caller's model, andgit grep -n -i -E '(^|[^[:alnum:]_])mcp([^[:alnum:]_]|$)|remember|recall\(|(^|[^[:alnum:]_])llm([^[:alnum:]_]|$)|openai|anthropic' -- . ':!docs/04-quality' ':!Cargo.lock'matches a query-planner helper namedremember_candidate_probe_warning(src/engine/query_plan.rs:10294, called at:10339) and one roadmap sentence on an MCP server that could be added (ROADMAP.md:118). The README's agent-memory line (README.md:29) and the roadmap's "memory that can change and forget" section (ROADMAP.md:97-108), which says the application should decide what deserves to stay, are where the use case lives. Three engine properties reach a memory built on it. Every edge carries a validity window that the caller may set, defaulting to the creation clock and an open end (src/engine/write.rs:1223-1224); reads filter on it at a reference time (src/engine/mod.rs:3253-3255), andinvalidate_edgecloses a window without deleting the edge (src/engine/mod.rs:6448). A per-querydecay_lambdamultiplies edge weight byexp(-lambda * age_hours), with age measured fromvalid_from, so a back-dated fact ranks as old (src/engine/graph_ops.rs:5064-5071). Named prune policies on label, age sinceupdated_atand maximum weight are stored in the manifest, hide matching nodes at read time and are physically removed with their incident edges at compaction (src/engine/mod.rs:3262-3287;docs/architecture-overview.md:62,:169,:175-182). Tenancy is not modelled:git grep -w -n -i -E '(tenant_id|user_id|agent_id|session_id)' -- src ':!src/engine/tests'matches only an example property in two GQL parser tests (src/gql/index.rs:374-379,src/gql/parser.rs:5193-5200, both under#[cfg(test)]), so a scope is one database directory or a caller convention on labels and properties. Screened before reading, from a full clone: no auto-run surface, two build-time execution points (overgraph-node/build.rs,overgraph-python/tests/conftest.py), seven dependency files inside the cooldown from the release commit, and two unpinned surfaces (three caret ranges inovergraph-node/package.jsonbehind a lockfile, andovergraph-python/pyproject.tomlwith no lockfile); there is no.gitmodules,AGENTS.mdorCLAUDE.md. Nothing was installed, built or run.supermemoryai/smfswas examined and has no report: it is a filesystem client for the hosted Supermemory engine, and extraction, the profile and semantic search all run server-side. MIT, read atf4a0f503…, the head ofmainon 12 June 2026, from 133 commits since 10 April 2026; it was calledsupermemoryfsuntil commit54dc3cd. It is the same vendor's companion to thesupermemorymonorepo, whose report covers the open surface of that engine. The Rust daemon mounts one container tag over FUSE or NFS as a SQLite inode cache (crates/smfs-core/src/cache/schema.sql) and syncs it to/v3/documents. A TypeScript and a Python package expose the same container as a virtual bash tool with ansgrepcommand. What is stored locally is file bytes and sync state, not memories. The search, profile and memory-generation paths arePOST /v4/search,POST /v4/profileand aPATCH /v3/container-tags/<tag>carryingmemoryFilesystemPaths(crates/smfs-core/src/api/mod.rs:359-373,:407-434). The step that turns a file into memory is a server stage this repository does not contain, so the bar's "closed-source behind an open wrapper" exclusion applies. Recorded for what a reader can take.profile.mdis a reserved virtual file rendering the server's static and dynamic memories, and any write or truncate returnsPermissionDenied(crates/smfs-core/src/cache/profile.rs:14,:82,:86). Correction therefore goes through the source files, which is the memory-as-an-editing-surface shape with a read-only derived view. The profile is fetched once, at daemon start (crates/smfs/src/cmd/daemon_runtime.rs:166-167), and not on the 30-second pull. Pull reconciliation lets a local write win when itsdirty_sinceis newer than the remoteupdatedAt(crates/smfs-core/src/cache/fs.rs:239-272). Andpush.rs:54-60records a server behaviour worth knowing: a secondPATCHsent while a document is still processing "silently drops the new content", so the client polls forstatus=donefirst. Two things sit against it. Mounting edits files outside the mount. On first mount the daemon appends a shell function to~/.zshrcthat redefines flaglessgrepas semantic search inside a mount (crates/smfs/src/cmd/daemon_runtime.rs:252-253, body incrates/smfs/src/cmd/init.rs), although the README presents that wrapper as opt-in throughsmfs init. Every mount also writes a delimited block into~/.claude/CLAUDE.md,~/.codex/AGENTS.mdand~/.gemini/GEMINI.mdsteering the agent tosmfs grep(crates/smfs-core/src/agent_hint.rs, called fromcrates/smfs/src/cmd/mount.rs:294); unmount removes it. Its only opt-out,--no-inject-hint, is hidden and documented as "not part of the supported user surface" (mount.rs:87-90). Scope is the container tag sent on every request, and nothing checks it on the way back: documents are reconciled without reading theircontainer_tags, andSearchResultcarries no tag field (crates/smfs-core/src/api/dto.rs:175-181). That is the opposite choice from the exact-match predicate thesupermemoryreport credits inpackages/tools/src/claude-memory.ts, and isolation rests entirely on the API. Screened before reading, from a full clone: one auto-run surface (.devcontainer/devcontainer.json, which builds the rootDockerfilewithcargo build), one build-time execution point (an npmprepublishOnlyinbash/package.json), one unpinned surface (13 caret ranges behindbash/bun.lock) and no file inside the cooldown. There is no.gitmodules,AGENTS.mdorCLAUDE.md. Nothing was installed, built or run.harish-gaggar/mcp-server-gatewaywas examined and has no report: its "durable memory" is a chat log the UI replays to the person and a checkpoint per request, and the agent never reads either back. Apache-2.0, read atf9698059…, the head ofmainon 3 October 2026, 13 commits since 17 August 2026. It is an OAuth MCP gateway (about 5,400 lines of TypeScript undermcp-gateway/src/), three example MCP servers, a PII kit, and a LangGraph agent for JFrog Artifactory (about 9,700 lines of Python underAgents/). The gateway's storage is an OAuth client-registration key-value store with a TTL (mcp-gateway/src/storage/types.ts:9-10, used only byclient-handlers/dcr.ts:56andcimd.ts:92). The agent'sjfrog_agent/memory/package (677 lines, SQLite by default, Spanner optional) writes threads, messages, LLM call telemetry and thumbs feedback (memory/sqlite_backend.py:31-51). The one reader of messages isload_thread, which copies them into the Streamlit chat pane for display (ui/state.py:173-183);run_agentpasses only the new request into the graph (ui/state.py:263-265). The planner's prompt is a system message and that request (jfrog_agent/llm.py:249-252), and the graph nodes read nothing outside the current run's state. The LangGraph checkpointer is keyed by a freshrun_idper message, commented as "each message is an independent graph run" (ui/state.py:259-260;run.py:62), so it lets an approval interrupt survive a restart and carries nothing between requests. The Slack front end keys a thread on the channel and prints "memory: N prior turns", but it importsfrom .ask import ask(jfrog_agent/slack_bot.py:25), and noask.pyexists in the tree or in any commit. Thecontext_optimizerpackage trims and summarises the prompt inside one call, which is context-window management. Screened before reading, from a full clone: no auto-run surface, no build-time execution, nothing inside the cooldown, nine unpinned surfaces (Python requirements with>=ranges and caret ranges behind three npm lockfiles); there is no.gitmodules,AGENTS.mdorCLAUDE.md, and the 17-line LICENSE is the Apache-2.0 notice with no rider. Nothing was installed, built or run.FastBuilderAI/memorywas examined and has no report: it clusters and lexically indexes documents a person supplies, rebuilds that index in process memory on every start, and gives the agent a query tool and nothing that writes. MIT, read at8989fa5c…, the head ofmainon 4 October 2026, crate and wheelfastmemory0.4.10, 48 commits since 25 March 2026. It is about 3,100 lines of Rust undersrc/andtests/. The CLI'sbuild,query,serveandmcpcommands each read one markdown file, parse its## [ID: x]sections into Function, Data, Access and Event nodes, and cluster them with Louvain into nested JSON blocks (src/main.rs:91-121).querymatches a lowercased substring against block names, actions and ids and returns the deepest matching block (src/query.rs:3-43). The REST server and the stdio MCP server hold that JSON string for the life of the process (src/server.rs:9-14,src/mcp.rs:4), and the MCP tool list has one entry,query_memory(src/mcp.rs:30). The--datahostoption for S3, Postgres and warehouses returns a fixed one-section stub containing the URI (src/main.rs:94-95). The PythonSearchMemoryclass, ported from MahaBodi, chunks prose into passages and ranks them with BM25 over exact terms, stems and trigram-fuzzy terms (src/index.rs,src/search.rs:103). Itsadd_documentsappends and rebuilds the in-memory graph and index (src/search.rs:260-289,src/lib.rs:390); there is no method that removes, updates or saves an entry. The README's Neo4j and Access-node security material is prose inproduction.mdandarchitecture.md, and theA_nodes are labels the agent is told to self-regulate on, with no read path that filters by them. This is a retrieval index over user documents with no agent-written memory, which is the out-of-scope case. Screened before reading, from a full clone: no auto-run surface, no build-time execution, nothing inside the cooldown, no unpinned surface;Cargo.lockis present and 13 days unchanged, and there is no.gitmodules,AGENTS.mdorCLAUDE.md. The LICENSE is the MIT notice with no rider. The CLI pings a licence endpoint only when a key orFASTMEMORY_TELEMETRY=1is set (src/telemetry.rs:21-79), and an optional native clustering library is loaded withlibloadingfrom an absolute path (src/louvain_backend.rs:118). Nothing was installed, built or run.AmeNetwork/aserwas examined and has no report: itsMemoryclass is a persisted chat buffer that replays the last few messages stored under a caller id, which is conversation-window management. MIT, read atc2645226…, the head ofmainon 10 October 2026, 104 commits since 25 February 2025; the package was namedesperand thenamerbefore 22 March 2025. It is an agent framework of about 4,000 lines of Python underaser/, most of it web3 toolkits, social-platform bots, multi-agent orchestration and text-to-SQL. The memory module is the 29-lineaser/memory.py, unchanged since 22 March 2025, over three 33-to-49-line backends (SQLite, TinyDB, Supabase) that storekey,roleandcontentand nothing else (aser/storage/sqlite.py:15-21).Agent.chatfetches the newestlimitrows for theuid, default 5, appends them after the system prompt, and writes the user turn and the reply back (aser/agent.py:107-119,:188-192). Nothing is selected by content, no row has an identity a caller can address, and no tool the model sees reads or writes the store. The only removal isclear(key), which drops every row for that id and is wired to a/clearcommand in the Telegram and Discord bots (aser/social/telegram.py:32-35,aser/social/discord.py:38-44). Two keying details: the HTTP API verifies thekeyagainst the header'suidand then reads and writes history under the body'suid(aser/api.py:26-28,:46-47), and the CLI setsself.uidbut callsagent.chat(arg)without it, so every CLI session shares theNonekey (aser/cli.py:21,:37).aser/knowledge.pyis a Chroma index over documents a person loads from files or folders, retrieval over user documents with no agent writer.SelfCodingToolinaser/evolution.pywrites generated tool code to amkdtempdirectory and keeps its registry in a process-local dict, so nothing survives the run.aser/trace.pylogs each call to SQLite for observability and no code reads it back. Screened before reading, from a full clone: no auto-run surface, no build-time execution, nothing inside the cooldown, two unpinned surfaces (pyproject.tomlwith no lockfile, andrequirements.txtwith>=ranges); there is no.gitmodules,AGENTS.mdorCLAUDE.md, and the LICENSE is the MIT notice with no rider. The one committed test,tests/test_mcp_transport.py, covers the MCP transport and not memory. Nothing was installed, built or run.guarismo/openclaw-plugin-multimodal-embeddingswas examined and has no report: it is an embedding provider and a read-only media search for OpenClaw's memory index, and it stores, corrects and forgets nothing of its own. MIT (Igor Guarisma), 554 lines of TypeScript undersrc/with 68 vitest cases in four files, nine commits by one author on 7 and 8 October 2026 (UTC), read atd51fba19…(version 0.3.0). The plugin makes two registrations (src/index.ts:115,src/index.ts:126). The first is an embedding provider that sends text, images and audio to an OpenAI-compatible/v1/embeddingsserver, converting non-native media through ffmpeg over pipes (src/media.ts:8-20). The second is a tool,multimodal_media_search. Every table belongs to OpenClaw'smemory-core: the plugin returns vectors and the host indexes, stores, decays and deletes them. The tool opens the calling agent's database read-only, by theagentIdfrom the tool context rather than from a model argument (src/media-search.ts:51,src/media-search.ts:89). It runs one query,SELECT path, embedding FROMthe host's chunks tableWHERE source = 'memory' AND model = ?(src/media-search.ts:55), and keeps rows whose path ends in an image or audio extension. It ranks them by cosine similarity and drops any hit whose file no longer exists on disk (src/media-search.ts:110). Those rows are user files the host indexed frommemory.search.extraPaths, which makes this the document-index case. The one design point that transfers is the reindex trigger. Every setting that changes a vector, from base URL and prefixes to media label, request format and dimensions, goes into the runtime'scacheKeyData, so a change makes the host ask for a rebuild (src/index.ts:83). Whether the host's own read filters, such as entries removed throughmemory-forget, also govern this direct table read depends on howmemory-coredeletes chunk rows at the plugin'sopenclaw2026.9.8 dev dependency; that was not read. Searches run at this pin withgit grep:-nEi "insert|update[[:space:]]|delete|writeFile|\.run\(|exec\("oversrc(one match, a comment);-nE "openOpenClawAgentDatabase|prepare\("(one read-only open, oneSELECT);-nEi "remember|forget|supersed|tombstone|retract|correct"oversrc(nothing);-nEi "arxiv|bibtex|@article|doi\.org|CITATION"over the tree (nothing). Screened before reading: no auto-run, build-time or cooldown finding, and one FLOAT onpackage.jsonwith a lockfile present; nothing was installed, built or run.- Comparing Retrieval-Augmentation and Parameter-Efficient
Fine-Tuning for Privacy-Preserving Personalization of Large Language
Models (arXiv:2409.09510)
was examined and has no report: its per-user adapters are written once
by a benchmark script, and nothing updates, versions or deletes
one. Salemi and Zamani, v1 14 September 2024. Version 2, of 26
June 2025, is the ICTIR '25 version of record (doi:10.1145/3731120.3744595).
The method trains one LoRA per user on that user's profile alone, and
the paper prices it at 55 MB for a rank-8 FlanT5-XXL adapter against 45
GB for a full copy. Its footnote points to
LaMP-Benchmark/LaMP, read at38c9d4d8…: CC BY-NC-SA 4.0, standard text, withPEFT/added on 18 February 2025 as 369 lines of Python in three files, and no test function anywhere in the repository.PEFT/train_peft.py:61-71trains an adapter for each user id into<output_dir>/adaptors/<user_id>/and skips any user whose directory is already non-empty (:63-64), so a rerun over a changed profile leaves an existing adapter as it was.PEFT/evaluate_llm.py:53-58globs that directory and loads the adapter under the user's id before predicting. That is the shape that brings Second Me into scope, a stored weight unit selected per user at inference. Here the user key is a directory name, a physical partition, and each profile is a static LaMP benchmark file rather than anything a session writes. Nothing has to answer "delete my data".git grepforrmtree,os.remove,unlinkanddelete_adapterfinds no hit underPEFT/; the repository-wide hits empty scratch directories during evaluation and dataset creation, or replace symlinks. The paper defines privacy as isolation between users, and its v2 text contains no match fordelet,unlearnorerasure. Screened before reading: no auto-run surface, no build-time execution point, three unpinned requirements files; nothing was installed or run. - On the Way to LLM Personalization: Learning to Remember User
Conversations (arXiv:2411.13405) was
examined and has no report: it releases no code, and its method discards
each conversation once trained. Magister, Metcalf, Zhang and
ter Hoeve of Cambridge and Apple, v1 20 November 2024. There is no later
arXiv version; the version of record is in the first L2M2 workshop
proceedings, pages 61–77 (2025.l2m2-1.5). PLUM
has the model write question-answer pairs about each conversation, then
fine-tunes a rank-16 LoRA on Llama 3 8B Instruct conversation by
conversation with a weighted cross-entropy loss. It reports 81.5%
accuracy over 100 single-turn conversations seeded from OpenAssistant.
Neither the arXiv PDF nor the ACL PDF contains a repository link, and
Apple's research page for the paper links only arXiv, with its
codefield null.gh search reposon the exact title returned one unrelated repository,jungyl/rabbithole, a self-study app; "Learning to Remember User Conversations", "PLUM personalization conversations" and "PLUM LoRA conversation" returned none. Theapple-aiml-researchandappleorg listings carry no repository named for PLUM, personalization or conversation memory. Neither does theCharlotteMagisteraccount, which holds GCExplainer, normaartjeth. Discarding is a design constraint: the introduction declines to store conversations as RAG does, and Section 3.2 drops each one once its samples are trained. A request to forget one conversation then names no record and leaves no corpus to retrain without. That is the limit weights as memory, at adapter granularity describes, adopted as a privacy measure, and with no code there is no artifact to pin either way. - Text-to-LoRA (arXiv:2506.06105) was
examined and has no report: its hypernetwork emits an adapter per task
description, and every adapter it writes is keyed by task or timestamp,
never by a user. Charakorn, Cetin, Tang and Lange of Sakana AI,
v1 6 June 2025. Version 2, of 9 June 2025, corrects the first author's
surname and carries the ICML 2025 footer (PMLR 267). The abstract links
SakanaAI/text-to-lora, read at8ba77493…: Apache-2.0, standard text, one commit titled "Initial release" on 8 June 2025, and 7,083 lines of Python in 31 files beside a vendoredsrc/fishfarm, with no test functions. The hypernetwork is trained on 479 Super-NaturalInstructions tasks, either to reconstruct their LoRAs or by supervised fine-tuning, and turns an embedded task description into a LoRA in one forward pass. Every generated adapter goes to disk. Evaluation writes them undergenerated_loras/<task>/<split>/lora_<i>(src/hyper_llm_modulator/utils/eval_hypermod.py:146-157,:208-234).scripts/generate_lora.py:93-96writes toextras/user_generated/<timestamp>_<random8>/with the description beside it intask_desc.txt, a pathgit grep user_generatedfinds nowhere else. The web demo writes to/tmp/gen_lora/, makes that the active LoRA for its chat and zips it for download (webui/app.py:350-362). The content is a task skill rather than a claim about anyone, and the onlyrmtreein the tree prunes training checkpoints (src/hyper_llm_modulator/sft_trainer.py:305-309). This is the architecture boundary at one remove: the weights are the product, and nothing outlives the call with an identity a correction could name. Screened before reading: no auto-run surface, one build-time execution point insetup.py, one unpinned manifest in the vendoredsrc/fishfarm, nothing inside the cooldown; nothing was installed or run. - Doc-to-LoRA (arXiv:2602.15902) was
examined and has no report: the adapter it generates from a document
lives in one process attribute until
reset(), and nothing writes it to disk. Charakorn, Cetin, Uesaka and Lange of Sakana AI and Minerva University, v1 13 February 2026 with no later version; the README cites it as an ICML 2026 paper. The abstract namesSakanaAI/doc-to-lora, read atbaa85db4…: MIT, three commits onmainbetween 27 February and 25 May 2026, and 14,018 lines of Python in 50 files, with no test functions. A Perceiver hypernetwork maps a context to per-layer LoRA deltas in one forward pass, and Table 9 puts the iterative update at 0.522 s against 41.912 s for context distillation on MultiFieldQA.ModulatedPretrainedModel.internalizeassigns the generated adapter toself.generated_loras, replacing whatever was there, andreset()sets it toNoneand restores the original forwards (src/ctx_to_lora/modeling/hypernet.py:784-813). The demo passes the context text into everygeneratecall. The paper calls the result "persistent, re-usable adaptations", yet the one adapter save on the context-distillation baseline,CtxDistillModel.save_lora(src/ctx_to_lora/modeling/context_distillation.py:251-269), has no caller bygit grep -w save_lora. Agit grepfortorch.save,save_fileandsave_pretrainedfinds only that method, a base-model config written intrain.pyand the vendored Text-to-LoRA baseline. Forgetting is all-or-nothing and in-process, with no record a correction could name. Personalized chat appears in the abstract's closing sentence and machine unlearning in the conclusion's future work, both as prospects, by a search of the PDF text forpersonaliandunlearn. Theiclr-cleanupbranch, whose history is unrelated tomainand whose last commit is dated 15 June 2026, was checked by file path only. Screened before reading: no auto-run surface, one build-time execution point insetup.py, nothing unpinned or inside the cooldown; nothing was installed or run. yukihamada/chathmdwas examined and has no report: no commit onmaincarries a LoRA generator, and thev1.0.0tag writes an all-zero adapter delta and keeps rated replies that no response reads. Neither commit has a LICENSE file. No licence grants reuse, but reading public code is in scope.mainwas read at621cfcd9…: 23 commits by one author, dated 18 to 20 June 2025 in +0900. It holds Cloudflare Pages functions that proxy chat to Groq, RunPod or a self-hosted backend, a SwiftUI client named WisbeeRAG, and character fine-tuning JSONL. Its LoRA mentions are product copy and canned demo replies (functions/api/chat.js:238-239). The client keeps messages in@Stateand lists ObjectBox as a package without importing it. The tag,27dd86ba…, is one parentless commit of 18 June 2025 whose historymaindoes not share. Itsscripts/generate_lora.py:38-68never calls the hypernetwork whose path it takes: it returns small random A matrices and all-zero B matrices, so a saved adapter changes no output, andsave_lora_adapterwrites it underloras/<name>/(:70-100). "Train LoRA Model" sleeps two seconds and sets a session flag (chatHMD_assistant.py:577-582), and the inference command that follows carries no--loraargument.chat_app.py:341-342passesloras/feedback_trained.ggufwhen it exists, and no code writes that file. What persists isLearningDataManager. Each rated reply becomeslearning_data/training_pairs/<id>.json, carrying up to six recent turns cut to 200 characters, plus a task-description file and amaster_index.jsonentry, all under one directory with no user key (learning_data_manager.py:23-78). Only an export and a statistics panel read it (:176-261).clean_old_dataunlinks pairs older than 30 days and leaves their index entries (:263-289). Searches at the tag withgit grep -n:-F -e "--lora"inchatHMD_assistant.py(nothing) and-E "get_training_dataset|export_for_text_to_lora"over*.py(the export path only); atmain,-iE "lora"over*.py,*.jsand*.swift(strings and paths only) and-E "import[[:space:]]+ObjectBox"(nothing). Screened before reading:maingave the screen nothing it parses, and the Swift and Wrangler manifests were read by hand; the tag gave one RUNS, allama.cppsubmodule left unfetched, and one FLOAT onrequirements.txt. Nothing was installed or run.seismael/llm-patchwas examined and has no report: it stores one Text-to-LoRA adapter per document, named by the document's path, and nothing selects or deletes one by user or project. Apache-2.0, standard text with a filled notice. It was read at1f0d5a32…: six commits by one author from 14 to 27 April 2026, a uv workspace of three packages with pytest suites.LocalSafetensorsRepositorywrites weights, PEFT config and a manifest to<output_dir>/<adapter_id>/, and lists, loads andrmtrees them (projects/llm-patch/src/llm_patch/storage/local_safetensors.py:39-119). The markdown source's id is the file path relative to the watched directory, minus its suffix (sources/markdown.py:35-38). A recompile overwrites that directory, so there are no versions. The watcher handles create and modify events only, so deleting a document leaves its adapter. The engine server attaches every stored adapter at startup whenLLM_PATCH_MODEL_IDis set (server/app.py:126-141,pipelines/use.py:53-54). The wiki-agent gateway routes each request by acontext_idoradapter_idthe caller puts in its metadata (projects/wiki-agent/src/llm_patch_wiki_agent/routing/metadata_router.py:27-43). Its MCP toolchat_with_adaptertakesadapter_idas a model argument, so the key is a routing label and any caller can name any adapter. The README's per-tenant adapters have no tenant field behind them. Detach removes an id from the controller's list without touching the model (runtime/controller.py:83-91), and/compilehands the request'sdocument_idtosaveunchecked. Memory in the ordinary sense was to be the LLM-wiki layer that the MCP server, both CLIs and the wiki tests import asllm_patch.wiki. It is in no commit:.gitignore:94readswiki/, whichgit check-ignore -v --no-indexshows matchingsrc/llm_patch/wiki/, andgit ls-tree -rlists no path under it at any of the six.ChatSessionkeeps history in a list. Searches at the pin withgit grep -nEunderprojects:"\(IAdapterRegistryClient\)"outside tests,-i "tenant|user_id|principal","on_deleted|on_moved", and"is_relative_to|\.resolve\("over storage and server, all nothing. Screened before reading: no auto-run surface, three build-time execution points (two Makefiles, a pytestconftest.py), two unpinnedpyproject.tomlfiles beside a rootuv.lock; nothing was installed or run.velantrian/Velantrim-Memory-Ruslanwas examined and has no report: it is a memory kept by convention, and no software in it stores, retrieves, scopes or corrects anything. It has no licence file and the API reports none, so nothing grants reuse. Read at862f1abe…through a shallow clone filtered to blobs under 2 MB, with only text files checked out. The memory is Markdown with fixed roles:START_HERE.mdgives any agent a reading order and five write rules,CURRENT.mdstacks dated checkpoints carryingAS_OFandLAST_VERIFIED,WORKBOARD.mdholds long-term orientation, andprojects/*.mdare per-project cards. A client reads through its own GitHub connector; a write is a diff shown to the owner, a draft pull request and a merge. The README calls the result "not a source of authority". The Python is four book-edition build scripts underprojects/religion-spirituality/, 481 lines that write Markdown, JSON and PDF into their own folders and name no memory file. Nothing enforces the write rules: the tree holds no dotfile, so no workflow or hook, and the API reportsmainunprotected. Labels such asNOT_VERIFIEDandPENDING_OWNER_DECISIONare prose no code parses, so nottrust_state; correction is an appended checkpoint plus git history, which the rubric excludes fromaudit_logby name.human_reviewfails the producer test. The owner's account opened and merged all 21 merged pull requests, so GitHub cannot tell the agent from the approver. Since the repository was created, 26 commits have reachedmainwith no pull request, among them a local merge of a branch whose last commit edits the merged card to record the owner's authorization. It shares an owner with Velantrim Crystal and is not its store: a research source register here links Crystal at the commit the atlas read, and neither tree names the other's files. Beside DiffMem, which ships the agent that explores its Markdown, and the Cline Memory Bank bullet in this list, this is memory as an editing surface with reader and writer both outside the repository. Screened before reading on the sparse checkout:NOTHING SCANNED, no manifest, hook or agent file; nothing was installed or run. Searches at the pin:git ls-tree -r --name-only HEAD | grep -E '(^|/)\.'and| grep -iE '(^|/)(licen[cs]e|copying)'(nothing);git grep -nE 'CURRENT\.md|WORKBOARD|START_HERE|AS_OF|LAST_VERIFIED' -- '*.py'(nothing); in Crystal at692e05e3…,git grep -nEi 'Velantrim-Memory|WORKBOARD\.md|START_HERE\.md'(nothing).fudan-generative-vision/Remorywas examined and has no report: its residual memory is a compaction checkpoint only its own session reads, and what crosses sessions is encoder weights. The paper is REMORY: Learning Residual Memory for Context Compaction (arXiv:2610.11287; Xia, Chen, Ge, Deng, Yang, Dong, Yuan and Zhu; submitted 8 October 2026, v2 11 October). Its network, 1.94B parameters for Qwen3.8-27B, appends up to 4,096 soft tokens after a/compactsummary for a frozen actor. Read at743fd1fc…: MIT with no rider, 42 commits from 7 to 20 October 2026 by one account, 7,646 lines of Python undersrc/. Each compaction writes one immutable row tomemory.sqlite, holding summary token ids, the residual tensor and a receipt naming the previous checkpoint (src/remory/store.py:33-35,src/remory/engine.py:123-134). Reads and deletes filter on the session id a client sends asX-Remory-Session(store.py:75,:87;server.py:39-44). That persistence is session resume, the shape SALT has.r-codex resumereopens one session, its provider refuses a checkpoint marker it did not write (src/remory/codex/provider.py:193-198), and no path reads another session's row. A summary can be wrong, but it is the session's own window read by its next window, the conversation-window side of the line. The delete route's only caller isexamples/quickstart.py:59. What crosses sessions is opt-in online training, added 18 October and absent from the paper. Accepted compaction frontiers, with the project text they carry, collect in one shared pool, a background worker distils them into new encoder checkpoints, and/remory loadpicks one per session; a new session starts on the released weights (src/remory/online/collect.py:43-60,control.py:72). That is weights as memory, at adapter granularity: a checkpoint is chosen or abandoned whole, nothing inside one names a fact, and captured samples stay on disk with no deletion path. The released GLM encoder is 1.24B against the paper's 1.502B, as the README says; the paper's archive tool is absent; and no result file is committed beyond the paper's figure, so no headline number can be recomputed. Screened before reading: no auto-run surface, one build-time point (tests/conftest.py), three dependency files inside the seven-day cooldown; nothing was installed or run. Searches at the pin:git grep -n -E '\.delete\(' -- src examples integrations(client, route, quickstart);git grep -n -E 'unlink|rmtree' -- src/remory/online training/context_compression/qwen38_online_objective.py(lock and temporary files);git grep -n -i -E 'archive' -- src integrations(the Codex tarball);git grep -n -E '43\.39|61\.03|76\.4'(nothing). In the paper,grep -n -i -E 'online|sqlite|session'finds one within-session count.DevLoops-ai/unified-brainwas examined and has no report: it is a code index of one repository's git history, written only by its ingester, and nothing a model concludes is kept for a later question. AGPL-3.0 with no rider, beside a commercial licence and a CLA, read at75461fec…: 25 commits from 24 October to 8 November 2026, 14,366 lines of Python, of which onlycodebase_qa_service.pychanged after the first examination at16e7efb. The README calls it "Persistent memory for System One coding agents"; the code is the same shape.next_claude.pyandingester.pywalk the history with tree-sitter and write every version of every symbol (the code calls them skills), call and reference edges, an FTS5 index and code vectors to<repo>/.unified-brain.db, with no model call. Correction is re-ingestion. The MCP server's one tool,retrieve(unified_brain_mcp.py:49), only reads.AskRequest.history(codebase_qa_service.py:2373) is never read. The one model-written state that persists is the timeline report — judge verdicts, findings, evidence and a ten-entry verdict history per probe underreport:<id>keys — and every read of it is in the report endpoints, so no later question sees one. That is the line drawn for Fullerenes and kivgraph in this list. Evaluation results are committed:evals/results/holds ten write-ups of the nine-question, 74-point xz set, andevals/runs/holds the Opus 5.5 and Fable 5.1 agents' per-question answers and a usage export. The README's cheap-profile figures recompute fromqa-xz-2026-11-06-pplx.md: the nine per-question scores sum to 68.75, and $17.55 for the Fable agent against $0.253 is 69 times. The grader is Claude Fable 5.1, the same model as the Fable contestant, as the file states; each profile is one run, and the README says replicability has not been measured. Screened at this pin: no auto-run or build-time surface, one floatingrequirements.txt, nothing inside the cooldown; nothing was installed or run. Searches at the pin:git grep -n -E 'req\.history|\.history' -- '*.py'(onlytemplates.py:1809, on the report page),git grep -n -E 'report:|reports_index' -- '*.py' ':!templates.py'(service lines 2972 to 5381 only, after the ask path at:2544-2790and before/api/retrieveat:5509), andgit grep -n -i -E 'watchdog|inotify|fsevents' -- '*.py'(nothing).- Can LLMs Improve Their Own Harness? A Controlled Study on
ARC-AGI-3 (arXiv:2610.30499) was
examined and has no report: its only durable artifact is a harness
source tree a coding model rewrites twice, and each game's writes are
sandboxed to its own output directory. Lehmann (TU Dresden;
Amazon, work done outside it) and Vahdati (Universität Hannover and
TIB), v1 21 October 2026, the only version listed. Each of 27 lineages
builds a harness through OpenCode, plays five development games and
revises from a feedback bundle, twice; every frozen snapshot is scored
on twenty held-out games. At gameplay the Seatbelt profile allows writes
only to a per-game output directory and a temporary directory, neither
of which may already exist
(
framework/control/runtime.sb:58-61;run_game.sh:61-65,:223-229,:461). The harnesses' own memories, such as T013's 1,200-characterGameMemory, live and die within one game. Across revisions the parent's tree is copied read-only and fingerprinted (system_snapshot.py:166-174),feedback/and.gitare excluded from every snapshot (:20-29), and each stage gets a fresh repository (:223-229). Revision 2 therefore sees its parent's evidence and no edit history. Qualification refuses a score cutoff (smoke_report.py:426-427), and the paper reports that no scored revision kept its parent unchanged. The only ancestral record is prose a model chose to keep: the Astra lineages carryREPAIR.md, and A001's second-revisionDEVELOPMENT.mdoverrides figures in its "inherited documentation". Code is the arXiv ancillary artifact, an anonymous review copy (CITATION.cffversionreview-2026-09-26) with no licence file under a CC BY 4.0 listing, pinned byMANIFEST.sha256(sha2563d49fd5763267b1519ec5ea6066a466d92f3713af5432b7ea5457f664dcb47cd): 11,861 lines of Python inframework/control/, 232 test functions, not run. Harness² keeps every adopted harness with a lesson for later tasks' editors; here there is one parent and one bundle. Harness-Zero distils an offlinememory.mdinto weights; here weights are fixed and nothing outlives the lineage. Themetauto-ai/HGMbar, a generation reading a durable record of what its ancestors tried, is met only by that unmanaged in-tree prose. Revision 2 raised mean held-out RHAE by 2.80 points (95% interval [−1.44, 7.35]) against 8.42 on development games. No GitHub repository turned up:gh search reposfor the exact title,harness adaptation gapandself-improving harness ARC-AGI-3;gh search codeforharness-adaptation-review-artifact,ARC_SCRATCH_SYSTEM_DIRand the qualification error string; accountsJensLehmannandS6savahd; orgsNIMI-research,TIBHannover,SmartDataAnalyticsandtu-dresden. The screen parsed nothing in this non-git tree; nothing was installed or run. fabio-rovai/open-ontologieswas examined and has no report: its triple store holds the ontology a user ships, which an agent edits like source code, and nothing in it records what an agent learned. MIT, about 97,000 lines of Rust undersrc/in a tree of 2,917 tracked files, read from a shallow clone atcefe5997…, a merge dated 30 October 2026. It is an MCP server and CLI that loads RDF/OWL into Oxigraph and puts a Terraform loop in front of changes to it.onto_plandiffs a proposed Turtle against the store with a blast radius, a risk score, locked-IRI violations and a conservativity check, andonto_applywrites the delta. The store is a working copy.src/config.rs:292-295makes"memory"the default, in which "every restart starts empty", and RocksDB persistence is opt-in. The production artefact is the fileonto_savewrites, and the README says "This is not an ontology editor": the tool runs on a change before it ships. The 23 SQLite tables the tree creates hold that loop's bookkeeping. They are plans, whole-store N-Quads snapshots foronto_versionandonto_rollback, IRI locks, monitor watchers, an operation log, embeddings, a redaction vault, and calibration from accepted or dismissed lint, enforce and alignment findings. The rest are specifications the agent may register for the ontology's own planner and gates: action schemas, default laws, invariants and ARGOS-style policy rules. None of them holds an observation, a preference or a decision about a user or a task. The nearest thing isonto_support_verdict, which stores a model-suppliedsupported,refutedorunrelatedper graph claim. Its only readers count verdicts and skip claims already judged (src/support.rs:261,src/support.rs:291), and nothing filters the graph on it. The governance is real, it sits entirely on the artefact side, and even there the agent holds every verb.onto_plan,onto_applywith aforcemode that skips the monitor gate,onto_rollbackandonto_lockshare one tool surface (src/server.rs:2548,src/server.rs:2612,src/server.rs:1051,src/server.rs:2635). The "Append-only audit trail of all lifecycle operations" thatdocs/lifecycle.mddescribes islineage_events, written at ten sites insrc/server.rs. It recordsapplywith its mode and no triples, andonto_version,onto_rollback,onto_loadandonto_ingestwrite no row. The Lean, Isabelle, Rocq, Dafny and Aeneas directories certify inferences and checker soundness, not any stored belief. The paper is arXiv:2605.09184 (9 May 2026), on LLM-driven ontology construction and stable-matching alignment over OAEI tracks, and its abstract describes no agent memory. Screened before reading: two auto-run surfaces, both harmless, since.mcp.jsonlaunches./target/release/open-ontologies serve, which does not exist without a build, and.claude-plugin/plugin.jsonis metadata. The screen also found three build-time execution points (Makefile,python/tests/conftest.py,studio/src-tauri/build.rs), 22 dependency files inside the cooldown with every file in the depth-1 clone dated to the tip, and 12 floating surfaces..gitattributescarries onlyeolrules, andCLAUDE.mdwas treated as data. The tree commits a 39 MB macOS binary atstudio/src-tauri/binaries/open-ontologies-aarch64-apple-darwinand a bundledstudio/src-tauri/sidecars/agent/dist/index.js, and neither was run. Nothing was installed or run. The searches behind the absence claims ran at the tree root. Tables:git grep -n -o -E 'CREATE TABLE IF NOT EXISTS [a-z_]+' -- src. Vocabulary:git grep -c -i -E 'remember|recall' -- src studio/src studio/src-tauri python, whose hits insrc/are retrieval-metric names, andgit grep -w -n -i -E 'memor(y|ies)' -- src, every hit being RAM, the storage mode or a WASM plugin's linear memory, apart from a design comment about the developers' own notes (src/align_fuzzy.rs:17) and a credit to synaptic-memory for the sync watermark pattern (src/sql_sync.rs:4). Lineage writers:git grep -n -E 'lineage\(\)\.record\(' -- src/server.rs. Verdict readers:git grep -n -E 'support_verdicts' -- src. Studio persistence:/usr/bin/grep -rn -E 'localStorage|sessionStorage|indexedDB' studio/src, which returns nothing.assafelovic/gpt-researcherwas examined and has no report: every store it writes is either a per-run index of scraped pages or an archive of finished reports, and no research run reads what an earlier one wrote. Apache-2.0 byLICENSE(pyproject.tomldeclares MIT), 3,211 commits at0957c301…, about 15,900 lines of Python in thegpt_researcherpackage and 2,400 inbackend/. The modules named for memory are not stores.gpt_researcher/memory/embeddings.pydefinesMemory, a factory that returns an embedding client for one of some twenty providers.VectorStoreWrapper(gpt_researcher/vector_store/vector_store.py) wraps a LangChain store that the caller constructs and passes in; when one is passed,skills/researcher.py:171,:181,:204,:256and:971chunk scraped or local documents into it, andreport_source="langchain_vectorstore"reads it back by similarity. That is the one path by which a later run could see an earlier run's material, and what crosses is raw source text tagged with its URL, not anything the agent concluded; the package never constructs a store itself, and the wrapper has no delete or update. Without a caller's store,select_context(context/select.py:53) filters each run's scraped pages in memory and discards them. The backend'sReportStore(backend/server/report_store.py) persistsdata/reports.json, one row perresearch_idwith question, answer, ordered log data andchatMessages, with upsert, a mergingPUTand aDELETE(backend/server/app.py:198-252);POST /api/reports/{id}/chat(app.py:263-328) reloads that report's answer and its prior chat turns into the next chat call and appends the reply. It is the Aider shape, scoped to one report: a transcript and the document it is about, with no unit smaller than the report, no status, and nothing that marks a turn wrong, and it never reaches a new research run — the frontend'sstartpayload (frontend/nextjs/hooks/useWebSocket.ts:80-89) carries the task, the report settings and the domain filters held inlocalStorage, and nothing from the history.ChatAgentWithMemory(backend/chat/chat.py:55) is named for that report-as-context; none of its three constructions inbackend/passes avector_store. The deep-agents variant gives each run a freshFilesystemBackendunder its own run directory (deep_agents/agent.py:88,deep_agents/main.py:68-74), and the LangGraphMemorySaverinmulti_agents/agents/orchestrator.py:5is commented out. Searched at the pin from the repository root, both empty:git grep -n -E "report_store|reports\.json|chatMessages" -- gpt_researcher multi_agents deep_agents skills cli.py main.pyfor a research-side reader of the archive, andgit grep -n -E "VectorStore\(|from_documents|InMemoryVectorStore|persist_directory|Chroma\(|PGVector|FAISS" -- gpt_researcher backend multi_agents deep_agentsfor a store the package builds itself. Screened before reading, from a--depth 1clone: 2 auto-run surfaces (.cursorrules, and a.mcp.jsonthat launches the publishedgpt-researcherpackage throughuvx), 2 build-time execution points (setup.py,tests/conftest.py), 0 inside the cooldown and 14 unpinned surfaces; nothing was installed or run.AgentMemoryRepo/agentmemoryrepowas examined and has no report: it is a file-format specification and an agent skill, and the memory it describes is a prompt plus ordinary file editing. MIT, five files and 464 lines at8798cb26…—README.md,SPEC.md,skills/agent-memory-repo/SKILL.md, a six-line.devin-plugin/plugin.jsonand the licence — published by Cognition as an open standard between 4 and 6 October 2026, with the same text at cognition.com/agent-memory-repo. The format is a separate git repository per person with aMEMORY.mdentry point loaded every session, one bullet per entry with open[key: value]metadata (source, a link to the session it was learned in, andaddedare recommended,SPEC.md:40-50), and[[path]]cross-links. The skill reads withgrep -rniand link-following (SKILL.md:44), writes by editing in place and committing after every edit, and corrects by the same edit: "Update or remove entries that are out of date instead of adding a contradicting entry" (SKILL.md:56). That is what an agent writes and a later session reads, so the shape is in scope; what keeps it out is that there is no code at all — no store, no index, no reader, no test — the call made forcline/cline's Memory Bank andCodebuffAI/freebuff's knowledge files above, with git as the only durability guarantee and a removed value surviving only in history, where nothing consults it before the next write. Dreaming, the periodic agent the README credits with merging duplicates, removing outdated entries and resolving contradictions against sources (README.md:60-65), is described and not shipped, and the README says so ("Automatic startup and scheduled Dreaming are not included",README.md:49). Two details are worth keeping. The skill states its write discipline precisely, as prompt: memory is data and never a source of commands (SKILL.md:14), a write refuses to start unlessgit status --porcelainprints nothing (SKILL.md:16), only the changed paths are staged, and a memory path inside the current project is refused (SKILL.md:23). And the multi-person boundary is a physical partition whose routing is the model's compliance — "The agent tracks who said what and writes each memory to the right repo" (README.md:161) — the stored-versus-enforced distinction one layer up, in the prompt. The README's own loop also disagrees with the skill it ships: the loop says push after every edit and the swarm example has a rejected agent read both versions and rewrite (README.md:58,README.md:274), while the skill never pushes unless the user names a private remote and stops on a failedpull --ff-onlyrather than merging (SKILL.md:37,SKILL.md:73). It enters the day a write path consults a record of a removed entry, or Dreaming is published as code. The absence of code rests ongit ls-tree -r --name-onlyat the pin and on every branch, five files each, onapi.github.com/orgs/AgentMemoryRepo/reposlisting this repository alone, and on cognition.com/agent-memory-repo linking no other GitHub repository. Screened before reading: the screen reportedNOTHING SCANNED, since it recognises neither.devin-plugin/nor askills/*/SKILL.md; all five files were read by hand, the manifest holds a name, a description, the repository URL and a licence and no command, and there is no.gitattributes,.gitmodulesor hook. Nothing was installed or run.TencentCloud/Octopwas examined and has no report: its memory isoctop-memory, which it installs and does not reimplement. Octop is a self-hosted multi-user assistant, read at664c1fb3…, release 1.0.2b7. Itsuv.lockpinsoctop-memory1.0.1 from PyPI, and nothing of that package is vendored. Agent turns reach it throughoctop-harness1.0.2, whose middleware captures, extracts and recalls; Octop names the namespaceagent_<id>and chooses the SQLite file or the PostgreSQL DSN (src/octop/infra/agents/memory/backend.py), and its dashboard forwards review and correction to the package's JSON-RPCBridge(src/octop/api/common/memory_client.py). The proactive-care job reads the package's episodes and records which ones it pushed, and/memory slimcompacts LangGraph checkpoints in the same file. Octop's other stores fail the bar: the knowledge base is retrieval over documents users upload, and the agent's only tool on it issearch_knowledge; conversation history is per-thread transcript storage, and no tool Octop registers searches across threads; theMEMORY.mdand daily-note files belong tooctop-harness, and Octop only serves and deletes them. How Octop wires the package, including one namespace shared by every user of a shared agent, and how deleting a conversation, a user or an agent reaches it, is in the octop-memory report, section 8. No source is vendored, sincegit ls-files | /usr/bin/grep -E '(^|/)octop_memory/'returns nothing, andgit grep -n -i -E 'search_history|history_search|conversation_search|recall_history|past_session|cross.session' -- srcoutside the bundled expert and subagent libraries returns nothing either. Screened before reading, from a full clone: 1 auto-run surface (.githooks/pre-commit, inert unlessmake install-hookssetscore.hooksPath), 10 build-time execution points (twoMakefiles, fourconftest.py, and four modules namedsetup.pythat are an API router and three setup helpers, not packaging scripts), 2 unpinned surfaces, andpyproject.tomlanduv.lockinside the cooldown;AGENTS.mdwas treated as data. Nothing was installed or run.- AIM (arXiv:2609.38445) was
examined and has no report: no code is released, and its lesson memory
starts empty on every run. AIM: Agentic Idea Management for
Automated Research (Choi et al., Google Cloud AI Research and
University of Wisconsin–Madison, v1 29 September 2026) searches over
explicit research ideas: an Agentic Surrogate clusters and ranks the
idea pool each iteration, an Agentic Acquisition step chooses explore or
exploit, and a Resource Planner spends a fixed branch budget. Its memory
is a lesson set grown by union,
M_{t+1} = M_t ∪ ΔM_{t+1}— effective implementation choices, open bottlenecks, and failures to avoid — which conditions every new idea. The part this atlas would read is the gate in front of that union. A Solution Auditor flags each resulttrivial,task_mismatch,idea_mismatchorreward_hacking; three of the four discard it from both the score history and lesson extraction, andidea_mismatchmakes the auditor rewrite the idea to describe what the code actually built, so lessons attach to the mechanism rather than the proposal. Nothing comes after the gate: the paper describes no path that retracts or supersedes a lesson, and Algorithm 1 initialisesM_1 ← ∅with the three runs per task independent, so nothing outlives a run — a second ground for exclusion that a release would not remove. The ablation is on one task, Flash Attention, where removing the auditor drops 90.5 to 87.6; that removal also takes out idea rewriting and the audit flags in the final score, so it bounds rather than isolates what unfiltered lessons cost. An unofficial reimplementation,hugoskn/agentic-idea-management-auto-researchat4120d5d5…, keeps the same per-run shape:research_loop.py:24builds a fresh state per run and nothing reads the saved state back. Searched on 2026-10-08: the PDF names GitHub once, as the project page, whose own repository holds only the site; the Hugging Face papers record has no repository; the first author's accountimhgchoihas no code repository pushed since February 2026; andimhgchoi/AIM,google-research/agentic-idea-managerand four other name variants return 404. - RankEvolve (arXiv:2609.39551) was
examined and has no report: no code is released, and its knowledge layer
is a correction design that can be read but not checked.
RankEvolve: A Reliable Multi-Agent Auto-Research Harness for
Evolving Ranking Models (Chen, Liu, Li and Yan, Meta, v1 30
September 2026) evolves the HSTU generative recommender under a compiled
protocol of phases and gates, with whole coding-agent products as nodes
that review and repair each other. Its knowledge layer (§2.3, Appendix
G) is an evidence store — per proposal, the hashes, prompt, patch, test
output, metrics and promotion decision, with negative outcomes kept as
leaderboard rows — and an experiential memory: append-only notes
committed into the folder each describes, a global wiki that cites them
and is declared the single source of truth, and an entity graph linking
every mention. Each protocol phase retrieves candidates by hybrid
search, graph walk and folder lookup, and a subagent picks which to
inject. The correction design is the part to keep. A reconciliation
agent finds conflicting notes through a shared graph node, writes a
condition-scoped conclusion into the wiki, favours the more recent and
better-evidenced note, demotes the other with a back-link so the reason
it was abandoned stays visible, and flags what the evidence cannot
settle for human review — resolve, don't just
detect, described rather than shown. The paper does not say what
demoted does on the read path, who clears a flagged conflict,
whether "no local note may contradict the wiki" is enforced at write
time or only by the reconciler's sweep, or whether a negative
leaderboard row is injected as context or refuses a near-duplicate
proposal. Because notes are committed to the repository they would
outlive a run, but the paper reports one twelve-iteration deployment,
says it ran no memory-on/off ablation, and notes a human operator also
steered that run at the gates. Not to be confused with
jmnian/RankEvolve, the code for a different paper. Searched on 2026-10-08: the PDF's four GitHub mentions are all references, and Appendix B says artefacts "will be released with the codebase" with no URL; there is no project page and no Hugging Face record; repository searches forRankEvolve,ExecML-HSTUand Executable Operating Protocol find nothing by these authors; andfacebookresearch/RankEvolve,meta-recsys/RankEvolveand five other variants return 404. ModalityDance/EngramEditwas examined and has no report: it edits a language model's conditional memory, which is model editing, not an agent memory system. EngramEdit: Decoupled Knowledge Updates in LLMs through Conditional Memory (Cai et al., arXiv:2610.10533, v1 7 October 2026), read atfb4089be…: MIT, five commits between 5 and 8 October 2026, 772 lines of Python inEngramEdit/beside ROME-style harnesses for CounterFact, ZsRE and MQuAKE. It changes what a LongCat-Flash-Lite model recalls about a subject by adding residuals to its n-gram embeddings with the backbone frozen. No agent writes to it, nothing is scoped to a user or project, and the boundary the families page draws around the model-editing line applies. What it adds to that boundary, a weight-side store addressed by exact keys and the reason the key is still not a fact, is in weights as memory, at adapter granularity. Screened before reading: no auto-run surface, no build-time execution point, and one requirements file inside the seven-day cooldown with two floating ranges, PyTorch installed separately; nothing was installed or run.FalkorDB/FalkorDBwas examined and has no report: it is the graph database several systems here keep their memory in, not a memory system itself. Source-available under the Server Side Public License or the Elastic License 2.0, read atec2448f3…, the head ofmasteron 9 October 2026: a Redis module of about 123,000 lines of Rust and C undergraph/that runs openCypher over GraphBLAS sparse matrices, with numeric, full-text and vector indexes. The README names agent memory as a use case, and nothing undergraph/orsrc/defines a memory unit, a write policy, a validity interval or an entity expiry:git grep -n -i -E '(^|[^[:alnum:]_])ttl([^[:alnum:]_]|$)|expire|valid_(from|to|at)|tenant' -- graph srcmatches only three Redis key-open flags ingraph/src/index/redisearch/redis.rs, and tenancy is one graph per Redis key, a physical partition. The memory semantics belong to the systems that use it — Graphiti, AutoMem, Janus-Graph, Memary and Potpie — and their reports carry them. One engine property reaches them: temporal values are deliberately kept out of the index, so an equality or range filter on a date or datetime property runs as a scan with a post-filter rather than an index lookup (graph/src/runtime/ops/edge_by_index_scan.rs:265-283,graph/src/index/falkordb/encode.rs:26-38), and a validity window stored as a datetime is filtered by scanning. Screened before reading from a shallow clone: 4 auto-run surfaces (a.claude/settings.jsonPostToolUse hook that runsrustfmt --checkon an edited Rust file,.devcontainer,.vscodesettings, and.gitmodulesnaming RediSearch, GraphBLAS and LAGraph, left uninitialised), 4 build-time execution points (threebuild.rsandtests/conftest.py) and 10 dependency files inside the cooldown, which the depth-1 clone inflates;CLAUDE.mdwas treated as data. Nothing was installed, built or run.- Two repositories
Perseus-Computing-LLCpublished from 8 October 2026 were examined and have no report yet, and the third, Kibisis, has a report at a later commit.harpe(context budgeting and priority eviction, at99fcd86d…) andargus(a hash-chained audit ledger, ataee3bd4e…) are MIT, seven commits each, each a dependency-free Rust crate beside a Python package of the same interfaces. The organisation's profile presents them and Kibisis as its product line and does not mention Perseus Vault, whose report stays pinned to the atlas's fork. Harpe decides what stays in a context window, which is outside this atlas's scope. Kibisis was examined beside them ate482b0ea…, its seventh commit, when its Python vault held an exact, un-normalised tombstone, stored content in plain text and had no agent surface; its report describes a later commit.perseus-benchmarks, at3520df98…, publishes LongMemEval-S recall figures that no code or committed artifact in it produces, and its Argus tamper-detection time of 46 µs, which the Argus README describes as a scan of 100,000 events, is the time of a loop that stops at the corrupted event 42 of a 10,000-event chain (perseus-benchmarks/src/main.rs:200-261). Screened before reading: no auto-run surface and no build-time execution point, every manifest inside the seven-day cooldown; nothing was installed or run. SakanaAI/masswas examined and has no report: what one MASS cycle learns reaches the next only as merged weights, and the workflow it searched for is removed from the training data on purpose. Recursive Self-Improvement through Multi-Agent Self-Supervision (Lee, Xu, Seely, Lee, Sojoudi, Zaharia and Tang, arXiv:2610.12176, v1 8 October 2026), read atfb403581…: no licence file, andNOTICE.mdsays no open-source licence has been assigned to the MASS-specific code; 14 commits between 29 September and 10 October 2026; 7,530 lines of Python in 43 non-test files, 2,535 of them inharness_improvement/iterate_multi_agent_prompt.py, and 12 test functions in three files, not run. A cycle searches, task by task, for a multi-agent workflow with the model frozen, has the same model judge each version pairwise against the previous one, the champion and a bare-task reference run, collects trajectories from the retained workflow, and trains a LoRA on them that is merged into the next generation's weights (mass/pipeline.py:96-131,:134-159,:277-289). Three things outlive a step, and none is memory in this atlas's sense. The per-taskcomparison_history.jsonlandchampion_history.jsonlare append-only judge verdicts that the optimizer's prompt summarises (harness_improvement/iterate_multi_agent_prompt.py:209-228,:855,:1580-1581,:2092); they record which run won, not a claim that could turn out false, and they sit under the cycle's ownrun_dir. The retained workflow is not carried forward either.workflow_promptreturns the hand-written file undertasks/initial/for version 0 in every cycle (mass/pipeline.py:90-93), andconfigs/cycle2.jsondiffers fromconfigs/paper.jsononly in generation, run directory, model paths and seeds, so cycle two searches again from the same starting workflows under a freshruns/L1. When the trajectories are rendered for training, the orchestrator's first message has the teacher prompt, workflow plus execution directive, replaced by the bare task (training/prepare_sft_data.py:161-169,:377-381;mass/pipeline.py:147,:233-234), so the student learns to produce the orchestration from the task alone. That is the inverse of RRSI, whose admitted harness is a commit the next run checks out. Here the one artifact a person could read, diff and correct is dissolved into the weights, and each adapter is merged before the next cycle trains, so cycle two's adapter is learned on top of cycle one's and the two cannot be separated. Weights as memory, at adapter granularity names that case: a merged adapter carries its contributions irreversibly. What remains is discarding a whole generation, andexportrefuses to overwrite one (mass/pipeline.py:281-284). Screened before reading: no auto-run surface, no build-time execution point, four requirements files inside the seven-day cooldown and one floating range; nothing was installed or run.- Harness-Zero (arXiv:2609.24974) was
examined and has no report: its memory is a file an offline evolution
agent writes, and the method's purpose is to remove that file at
deployment once the model has absorbed it. Harness-Zero:
Harness Distillation via Agent-as-Harness (Ye, Lu, Dong, Su and
Song, v1 21 September 2026), code at
metaevo-ai/harness-zero, read ata4a62232…: Apache-2.0, 15 commits between 20 September and 9 October 2026, 3,359 lines of Python insrc/harness_zero/beside a vendored copy of deepagents, and 88 test functions in nine files, not run. Each domain's evolved harness inharness_bank/carries amemory.mdthat thestudent-harness-evolveskill grows over three rounds of failed training tasks, as "accumulated checklist clauses (English, no source attribution, grouped by topic)" (.agents/skills/student-harness-evolve/SKILL.md:34,:85). At rollout it is copied into the trial's sandbox and primed into the system prompt through deepagents'MemoryMiddleware(src/harness_zero/student_harness.py:1-17,:28-30;src/harness_zero/student.py:244), and the only store the code writes is a per-trial, append-only directory of trajectories for fine-tuning (src/harness_zero/store.py:1-27). No agent writes memory at run time and nothing it learns in one task reaches the next, so the scope call is the one made forSakanaAI/massdirectly above, and the weight side is in weights as memory, at adapter granularity. Two things are worth keeping. Table 4 of the paper scores recovery of behaviours sourced from the memory file separately from skills, tools and middleware, after the harness is removed, which makes it the most direct measurement here of a memory document's content moving into weights. And the evolution rule strips the one field correction would need: a clause is merged into a topic section with no attribution to the failures that produced it, so a wrong clause cannot be traced to its evidence before distillation, and after distillation it is answered only by regenerating trajectories and retraining. Screened before reading: no auto-run surface, four build-time execution points (three in the vendored deepagents tree), nothing inside the cooldown and no unpinned surface; nothing was installed or run. mikekelly/nanowas examined and has no report: its memory is a specification the agent is told to build for itself, and the code it ships saves a conversation rather than anything learned. Read atbdaa98dc…: no licence file and none declared inmix.exsor the README; 160 commits between 6 and 11 October 2026; 8,186 lines of Elixir in 27 files underlib/and 8,307 lines of tests holding 283testblocks, not run. Nano starts an agent as a GenServer with two tools,evalandidle, running as root in a container, and leaves the agent to write the rest of its harness into the running node. What the shipped code persists is each agent's state map, transcript included, and its eval bindings, written to<name>.termand<name>.bindingson every change and read back at boot so the agent resumes where it stopped (lib/nano/state_store.ex:1-20,:123-150;lib/nano_agent.ex:1-14). That is one conversation outliving its process:git grep -n -i -E 'compact' -- libreturns nothing, the harness halts an agent before a call that might not fit its context (lib/nano_agent.ex:858-869), and nothing is extracted from the transcript, so the session is continued rather than remembered. Memory appears only in the growth docs. Item 7 ofseeding-docs/guidance.mdasks for goals and "what you have learned, on disk" (line 139),seedling-docs/bots.md:178-181asks for a memory per bot retrieved "in small, relevant amounts", and each doc closes by leaving the build to the agent. The boundary is the one drawn forfacebookresearch/HyperAgentsbelow: what an agent might write is not in the commit. Two things in the tree are worth taking. The binding saver leaves out the largest variables once their total passesmax_bindings_bytes, 16 MB by default, keeps them bound in the live process, and on restore names each one to the agent as not restored (lib/nano/state_store.ex:56-91,lib/nano_agent.ex:436-439,:496-497), so the gap between live and saved state is reported to the one reader who would act on it. And the experimental front-of-mind spec, a note of at most 1,000 characters re-shown whenever it sinks past a configurable depth of the context, requires the re-shown note to be marked as the agent's own with the time it was written, never readable as an instruction from the operators, and requires a switch to turn it off so its effect can be measured (seeding-docs/experimental/front-of-mind.md). That is the provenance rule this atlas asks of every injected memory, written down before the memory exists. Screened before reading: no auto-run surface or build-time execution point, oneAGENTS.mdread as data, andmix.lockis not a file the screen parses; nothing was installed or run.hydra-db/hydradbwas examined and has no report: it is the open graph database under a closed memory product, and the memory semantics live in the product. AGPL-3.0 with no additional terms, read at722f32c8…, the head ofmainon 14 October 2026: 54 commits by 13 authors since 11 August 2026, renamed from Turbolay in pull request 56, about 152,000 lines of Rust in 153 files with 1,007 test attributes, not run. It runs openCypher over SlateDB on S3-compatible storage, with GraphBLAS traversal, a Neo4j-compatible Bolt endpoint and an HTTPS query API; query nodes and indexers hold only disposable cache, and object-store leases pick one writer per cell. Nothing in it defines a memory unit, extracts, ranks for recall or embeds:git grep -n -i -E 'embedding|cosine|knn|hnsw' -- src crates ':!crates/cypher-parser-antlr/grammar'returns nothing, and the vector and full-textSEARCHclauses exist only in the vendored Cypher 25 grammar. The workload shows through anyway. The tests, and an importer from FalkorDB (examples/falkor_import.rs), writeEntitynodes joined byRELATESedges carryingrelationship_id,chunk_id,valid_from,superseded_byandvalid_to, scoped bytenant_idandsub_tenant_id(src/client/bolt/tests.rs:990-1001), and telemetry promotes both tenancy keys to every log line, with a mailbox folder as the example sub-tenant (crates/telemetry/src/layers.rs:310-311,:809-821). The engine property that reaches such a memory is a guarded bulk merge: a__hydradb_update_if_newer_bymarker applies an update only when its timestamp is strictly newer, and a__hydradb_create_only_prefix keeps a property such asvalid_fromfrom being overwritten after creation (src/query/opencypher.rs:22-40,:6340-6370;architecture.md:415-417), so a delayed replay cannot move a fact's validity start or its metadata backward. Supersession, validity and tenancy semantics belong to the caller. That caller is a closed product. The benchmark pages and the white paper describe HydraDB as a context engine from AGI Context, Inc., storing versioned edges with commit time and valid time, and link no source code, harness or per-question results. The white paper names the design choice the guarded merge serves: it rejects an LLM deciding to update or delete a similar record, because a false-positive delete purges history, and adopts a "Git-Style Append-Only Log" in which a changed fact is a new edge. No deletion of any kind is described, so a request to forget a fact has no mechanism on either page. Screened before reading, from a full clone: no auto-run surface, three build-time execution points (build.rsat the root and in two crates), nothing inside the cooldown and no unpinned surface, withAGENTS.mdandCLAUDE.mdread as data; nothing was installed, built or run.FreshHillyer/xiaoOwas examined and has no report: its long-term memory is an unpublished server behind an MCP client, and the memory crate in the tree has no caller. At3acadbb3…— a GitHub mirror, created 11 September 2026, of openEuler's AgentOS runtime hosted atgitcode.com/openeuler/xiaoO, carrying 1,055 commits of upstream history under the Mulan PSL v2 licence — the live path isapps/shared/src/gateway/memory_automation.rs: opt-in (enableddefaults to false), it callsmemory_searchbefore a turn and renders the hits as<untrusted_long_term_memory>system context, and after a completed turn it enqueues amemory_ingestcall into a durable JSONL queue with file locking, bounded capacity and retry with backoff — for every agent role unlessallowed_agent_rolesnarrows it, since an empty list admits all. The server both calls go to is RAM-A, which the docs configure only ashttp://127.0.0.1:18081/mcp; no link, source or package for it is in the tree, and a GitHub search for it finds nothing — so the store, the retrieval and the forgetting are all outside anything inspectable. The tree does carry a complete memory design of its own:crates/memory, 3,562 lines, with aDurableMemoryManagerover typedPreference/Constraint/Fact/Procedurerecords, filesystem and SQLite stores, recall packets and ahybrid_mergeof lexical and cosine scores. Nothing outside the crate uses any of it:rg -l '\b(DurableMemoryManager|DurableMemoryStore|SqliteDurableMemoryStore|RecallQuery|SemanticMemoryStore|SessionMemoryManager)\b' --type rust . | grep -v crates/memory/returns nothing, no manifest enables the crate'ssqlitefeature (rg -n '"memory/sqlite"' --glob Cargo.tomlfinds nothing), so the 691-line SQLite store is not compiled into any shipped binary, and ofMemoryManager's write methods onlysync_from_loop_statehas a caller —remember_fact,add_instruction,set_current_task,attach_session_memoryand all threebuild_recall*have none. What is wired is a per-sessionMemorySnapshotof messages saved for resume, which is conversation persistence rather than memory. The crate's own tests cover the chunker, the vector arithmetic and the no-op embedder, and nothing that stores. Screened before reading: no auto-running configuration, threebuild.rsfiles, thirty-one manifests inside the seven-day cooldown; nothing was built or run. The unwired crate is the design worth watching: if a later commit gives it a caller, it becomes a report.Abhishekax7/HYDRAwas examined and has no report: its "persistent memory" is a record of which sources belong to which project, and no stored finding is ever read back into a later run. At9b33d894…(MIT, nineteen commits by one author between 2 and 7 September 2026, 14,349 lines of Python in the backend against 13,499 of tests) it is a research platform — LangGraph orchestrating document, dataset and web agents over FAISS-and-BM25 retrieval with correction, citation-linked synthesis, and deterministic grounding and calibration evaluation. What its code calls memory isProjectMemory(backend/app/memory/models.py): a project's name, description, the ids of its documents, datasets and research threads, and a web-research flag. A research request checks that the project exists and attaches the finished run's thread id to it. Each result is saved, and read back only by API routes:rg -n '\.get_result\(|\.list_results\(' backend/appfinds an evaluation endpoint that scores a stored result and two routes that return results for display, and nothing on the research path. The other durable state is LangGraph's SQLite checkpointer, which lets a caller who supplies athread_idresume that thread's workflow state — continuity of one workflow, the same shape as session resume, not a store of claims that could later be scoped, corrected or forgotten. Uploaded documents are a retrieval corpus, not memory. Screened before reading: no auto-running configuration, no build-time execution path, three dependency manifests inside the seven-day cooldown and one unpinned surface; nothing was installed or run.n8group-oss/omarchy-session-memorywas examined and has no report: it restores the terminal, not what the agent knew. Atfe4f518a…(MIT, thirty-eight commits by one author since 24 August 2026, 20,634 lines of Rust with 38,855 of tests)osmcaptures tmux topology on every change through tmux hooks and a fallback daemon, records which coding-agent conversation was running in which pane, and after a reboot rebuilds the sessions, windows and panes and resumes each conversation in its own pane, on its own workspace and monitor. The agent state it keeps isagent_sessions(src/db.rs:271-289): an agent kind, the conversation's native id, its project directory and transcript path, and a one-line title whose schema comment says it is never a summary of what was said, with atitle_sourcecolumn so the agent's words and the user's first line are never confused. It stores pointers into each agent's own transcript store and reopens them; nothing is extracted, recalled into a later conversation, or open to correction — it is session and process restoration, on the far side of the line this atlas draws around conversation persistence. Worth noting for anyone building the same thing: the privacy discipline around titles is deliberate and written down, andagent_resume_debtrecords conversations that could not be resumed rather than dropping them. Screened before reading: no auto-running configuration, no build-time execution path, two manifests inside the seven-day cooldown; nothing was built or run.NodeDB-Lab/nodedbwas examined and has no report: it is a general multi-model database, and the agent memory it advertises is a page of SQL patterns for the application to run. At124cc53a…(Business Source License 1.1 converting to Apache-2.0 on 1 May 2030, with some crates Apache-2.0 already; 3,704 commits since 16 March 2026; about 1.18 million lines of Rust across 25 crates) it is a database server speaking the PostgreSQL wire protocol, with vector, graph, full-text, document, columnar, timeseries, array, spatial and key-value engines, Raft clustering, CRDT sync to an embedded edge edition, row-level security, tenants andAS OFbitemporal queries over system and valid time on the record engines. The crate namednodedb-memis a NUMA-aware allocation governor for engine budgets, not agent memory. What the tree offers agents isdocs/ai/agent-memory.md: example schemas for episodic, semantic and working memory and aCREATE SCHEDULEjob that selects old episodic rows, with the summarization, the insert of distilled facts and the deletion of the originals left to "your app".docs/ai/README.mddraws the same line — "we store, index, search, and fuse. You chunk, embed, rerank, and generate." The README names ma8e, a memory layer for coding agents built on embedded NodeDB, as the consumer; nothing of it is in this repository. The engine is substrate an atlas entry could build on, with bitemporal reads and RLS that many reports here lack, but there is no memory unit, write policy, correction or forgetting of its own to compare. Screened before reading, from a shallow clone: no auto-running configuration, eight build-time execution points, 28 manifests inside the seven-day cooldown and no unpinned surfaces across 36 scanned files; nothing was built or run.mnemoverse/mcp-memory-serverwas examined and has no report: it is the client of a hosted memory engine, and the store, the ranking and the consolidation all run behind the Mnemoverse API. At08781cba…(MIT, version 0.10.0, 87 commits since 10 April 2026, 4,558 lines of TypeScript against 8,197 lines of tests) it is an MCP server exposing nine tools —memory_write,memory_read,memory_list_recent,memory_feedback,memory_statsand four room tools — over a hosted service the README calls "hosted by design". Nothing durable is written locally:src/requests.tsbuilds request bodies,src/render.tsformats replies, and the outcome-driven re-ranking the README describes (a Rescorla-Wagner update on the prediction error) and the consolidation stage (HDBSCAN with Von Restorff protection, which the README says is designed in and currently switched off) are both properties of a service this repository does not contain. Two things in it are worth recording anyway.src/scope.tsexists because a read never covers rooms — a room is a separate org bucket and the search runs against the caller's own org — so rather than return a silent partial answer the client emits a scope disclosure naming which rooms went unsearched and how to read them, and treats silence as correct in exactly one case, when the caller has no rooms. Andsrc/requests.tscarries a dated postmortem of two scope bugs in one patch release: atrim()on the way out normalised past a deliberate 400-guard in core, so a padded room address "would have written into a shared room visible to other accounts", and the revert dropped a|| undefinedon the read path sodomain: ""becameWHERE domain = '', turning a search of every domain into a guaranteed miss. Sixty tests were green with the divergence in place because the guard test grepped the source for the absence of atrim(); the conclusion written into the file is the one this atlas asks for everywhere — "A denylist over source text is not a contract; a function whose output you can compare is." The paper it cites is arXiv:2603.08965. Screened before reading, from a shallow clone: five files, one auto-run surface, one build-time execution point, one unpinned surface and two dependency files inside the cooldown; nothing was installed and nothing was runnexi-lab/nexuswas examined and has no report: its memory brick was deleted upstream on 15 March 2026, and what remains at the pin is schema with no writer. At66e3b994…, 25 September 2026, Nexus is a distributed virtual filesystem for multi-agent systems — a Rust kernel, ReBAC permissions, IPC pipes, Raft federation and runtime-loadable Python "bricks", 344,403 lines of Python undersrc/outside tests — under Apache-2.0. Commit2dfc23d9…(15 March 2026, "strip LLM brick and all dependent bricks/services") removednexus.bricks.memory— 26 files, 10,117 lines, including the service, paging, enrichment, versioning and state modules — with its REST router, RPC handler, CLI command and the MCP toolsnexus_store_memoryandnexus_query_memory. The residue at the pin has no producer.MemoryModel(src/nexus/storage/models/memory.py:27-34) is still exported and still created byBase.metadata.create_all(src/nexus/storage/record_store.py:360), and no code path inserts a row: its one writer,migrate_identity_memory_v04.py, has no caller. The v2 request models insrc/nexus/server/api/v2/models/memories.pyhave no router underrouters/. Two readers wait on_memory_provider(src/nexus/factory/manifest_adapter.py:41,src/nexus/tools/langgraph/nexus_tools.py:679), and nothing assigns that attribute, so the LangGraph tool returns "Memory system not available". Three surfaces still advertise the deleted system:nexus mcpprints both removed tool names (src/nexus/cli/commands/mcp.py:884-885), the TUI calls eight/api/v2/memoriesroutes (packages/nexus-tui/src/stores/search-store.ts:256-644), and the example agents callnx.memory.store. The MCP integration test that exercises memory skips when the tool is absent (tests/e2e/self_contained/mcp/test_mcp_server_integration.py:298-299), so it passes against the deletion. The commit message says a canary asserts the removed modules raiseModuleNotFoundError;tests/unit/test_llm_removal_canary.py:12-21lists six LLM and ACE modules and no memory module. The last commit carrying the brick is999a9c2a…. Screened before reading: no auto-run surface, 43 build-time execution points, 30 dependency files inside the cooldown — every file in a depth-1 clone dates to the tip — and 15 unpinned surfaces; no agent-instruction file in the tree. Nothing was installed, built or run.aws/strands-dynamodb-storagewas examined and has no report: it is a byte backend beneath the memory layer, not a memory. Apache-2.0, at91a7bd00…, 66 commits from five contributors since 14 August 2026. It is a Python and a TypeScript implementation (826 and 863 lines) of the Strands SDK'sStoragecontract —write,read,delete,listandnamespace, plus an optional vectorsearchover DynamoDBSearchVectors— with S3 offload, gzip and TTL. No file underpython/src,typescript/srcor either test tree namesMemoryStoreorMemoryManager. The onlyMemoryStorein the repository is aDynamoDBMemoryStorebridge that two examples define as application code, withaddandsearchand no delete (examples/semantic-memory/semantic_memory.py:60-94). What would hold memories on this table is the SDK's ownFileMemoryStore, which the Strands Agents report covers. One seam between the two packages belongs on the record. At SDK release 1.55.0, the newest before the pin, the PythonFileMemoryStore.searchpasses its natural-language string straight tostorage.search(store.py:159), andDynamoDBStorage.searchreadsquery.pkon line 432, outside itstry, so a string raisesAttributeError.MemoryManagergathers store searches withreturn_exceptions=Trueand logs a warning (memory_manager.py:327-353), so extraction writes to DynamoDB and every search of that store returns nothing. The TypeScript package rejects a string with a testedStorageError, and the TypeScriptFileMemoryStorescans withlistandreadinstead, so the seam is Python-only. Read, not run.home-assistant/corewas examined and has no report: its assistant forgets every conversation after five idle minutes, and nothing in the tree stores anything the model learned. At087bf875…the Python underhomeassistant/runs to 1,547,500 lines over 1,525 integration directories, and the LLM surface is a small part of it. The chat history lives in ahass.datadict:ChatLogincomponents/conversation/chat_log.pyis keyed byconversation_id, and its cleanup callback at line 150 pops the entry. That callback runs whenhelpers/chat_session.py:102finds a session idle pastCONVERSATION_TIMEOUT = timedelta(minutes=5)(line 28). Every provider integration resends the whole log each turn. OpenAI'sstore_responsesoption (defaultFalse,openai_conversation/const.py:46) keeps responses on OpenAI's side, and no code reads them back;previous_response_idappears nowhere inhomeassistant/.WecoAI/SpecBenchwas examined and has no report: it is a benchmark that measures coding agents, and the only thing it calls memory is a summary of the current search tree that dies with the run. Apache-2.0, Python, at08607352…, a single commit by one contributor dated 21 May 2026: 5,231 lines of harness Python inaide/,experiments/andbenchmarks/outside the 31 task directories underbenchmarks/spec_bench/tasks/. It is the code for "SpecBench: Measuring Reward Hacking in Long-Horizon Coding Agents" (Zhao, Srikanth, Wu and Jiang, Weco AI; arXiv:2605.21384, v1 20 May 2026, v2 9 September 2026). The link is established from both ends rather than assumed. The paper names no URL — the v2 PDF says only "We release the benchmark and methodology", and every GitHub link in the v2 HTML is a third-party citation (OpenCode, Gemini CLI, autoresearch, MiniMax) — but the paper's affiliation and correspondence address are Weco AI, and the repository'sREADME.mdlinksarxiv.org/abs/2605.21384as its paper. Each task pairs a visible validation suite with a held-out suite, and the gap between the two pass rates is the reward-hacking measure; an AIDE, linear or autoresearch outer loop drives Claude Code, Codex or OpenCode. Nothing persists agent memory across sessions. The prompt's Memory section isgenerate_summary()over the in-process solution tree (aide/agent.py:251-260, used at:773), rebuilt at each step.dump_runwrites a per-run JSON for offline analysis (benchmarks/spec_bench/run_loop.py:537), and its counterpartload_run(aide/agent.py:1172) has no caller anywhere in the tree. Workspaces are per node, copied parent to child within one run (benchmarks/spec_bench/workspace.py:88-96), and a root workspace is deleted and recreated if present (:57-58). One thing bears on memory evaluation: that Memory section listsgood_nodes— any non-buggy node with a metric (aide/agent.py:235-236), and the metric is the visible pass rate — so a node that raised it by memorising tests is fed to later steps as a successful experiment, and the paper reports that severe reward-hacking cases "persist across the entire search trajectory". The hacking-critique retrospection path that could interrupt this ships disabled:retrospection_probdefaults to0.0and each metric trigger toFalse(aide/agent.py:304-313), andexperiments/only passes those defaults through. Searches run at the tree root:grep -rn -iE 'memor|remember|recall|persist|resume|session|journal|CLAUDE\.md|AGENTS\.md|history|summar|pickle|json\.dump|sqlite|embedding|vector'over the harness Python (hits are the prompt Memory section, the run dump and the per-node workspace manager);grep -rn 'load_run'(definition only);grep -rn -E '"--(resume|continue)|session_id|--session'over the agent adapters (none;start_new_session=Trueis a subprocess process-group flag). The screen found 0 RUNS, 54 EXEC (per-taskMakefiles andconftest.pys), 0 FRESH and 1 FLOAT (pyproject.tomlwith no lockfile), and nothing was installed, built or run.WecoAI/aidemlwas examined and has no report: its prompt section is literally named "Memory", and it is rebuilt from an empty journal at the start of every run. MIT, 3,432 lines of Python in 21 files underaide/plus 663 lines of tests, at60b3978d…, 3 September 2026, 94 commits since 3 April 2024. AIDE is an ML-engineering agent that searches a tree of candidate scripts. EachNodeholds a plan, code, a model-writtenanalysisand a metric, andJournal.generate_summary(aide/journal.py:229-239) joins plan, analysis and metric over every node not flaggedis_buggyinto the"Memory"key of the draft and improve prompts (aide/agent.py:284,aide/agent.py:317). The paper, arXiv:2502.13138 (18 February 2025), describes reuse inside one task's tree search and claims nothing across runs, so paper and code agree.facebookresearch/HyperAgentswas examined and has no report: the memory its paper describes is something an evolved agent wrote, and it is not in the committed program. Hyperagents (arXiv:2603.19461, submitted 19 March 2026; Zhang, Zhao, Yang, Foerster, Clune, Jiang, Devlin, Shavrina) extends the Darwin Gödel Machine so the meta agent that rewrites the task agent can also rewrite itself (DGM-H). At59a68f67…— CC BY-NC-SA 4.0, 26,398 lines of Python over 120 files, 9 commits from 19 March to 14 April 2026 — the durable state is the HGM shape:archive.jsonlappends generation ids (utils/gl_utils.py:160-176), each generation stores ametadata.json, amodel_patch.diffand its scores, andselect_parentsamples a parent by sigmoid-squashed score times a child-count penalty (utils/gl_utils.py:571-584, the CLI defaultscore_child_prop). That is a population of program versions and their measurements, read by the outer loop.ensemble.pyreads the archive per task, but only to return the cached prediction of the best-scoring generation for that question id. The paper's memory is emergent. Its §5.2 and Appendix E.3.7 show aMemoryToolover./memory.jsonholding timestamped, keyed entries — "gen65 changes over-corrected" is one — which the paper says later self-modification steps consulted. Those are claims that could be false, which HGM's tree never held, and this is the case the Gödel-machine note said would enter the atlas. It does not enter at this pin, because the code is not in the tree:MemoryTool,memory.json,PerformanceTrackerandperformance_historyreturn zero matches, and every Python use ofmemorymeans RAM. The evolved agents are published only as experiment logs on Google Drive, which were not read. The committed starting meta agent does not name the archive either:meta_agent.py:16builds the whole instruction as "Modify any part of the codebase at{repo_path}" and leaves theeval_pathanditerations_leftarguments unused, so the archive copied into its container bycopy_prev_eval_to_container(generate_loop.py:363-424) is there on disk and never mentioned in a prompt. The harness does carry a file across generations without being designed to.diff_versus_commitincludes untracked files in each child's patch (utils/git_utils.py:36-69) and descendants replay the lineage patches, so a note an agent writes inside the repository is inherited by its descendants as code. A note written under the git-ignoredoutputs/, where the paper'sPerformanceTrackerwrites by default, is not carried. Nothing in the paper's excerpt corrects an entry except overwriting it by key. The licence is non-commercial with no rider on analysis. Screen: 0 auto-run, 0 build-time exec, 0 inside cooldown, 1 unpinned surface (four git requirements, two without a commit); nothing installed, built or run.davidondrej/cloudroom-corewas examined and has no report: it saves every coding-agent session's history and hands none of it back to an agent. Apache-2.0, 18,056 lines of Rust in 44 files undersrc/plus 5,325 lines of tests, at17571eb7…, 26 September 2026, 11 commits since 17 September 2026. It is one Rust service per Linux VM that runs Codex, Claude Code, Pi and Cursor as unprivileged child processes behind a token-authenticated HTTP API. Its one durable table,cloudroom_records(docs/database/0001-session-records.sql:11-17), is keyed(store, session_id, sequence)and holds ordered receipts and native output. Its readers select bysession_idand serveGET /v1/sessions/{id}/eventsto clients (src/session/history.rs:127-129,src/session/mod.rs:456-476), and no statement insrc/deletes from it. Continuity across idle periods is the harness's own native resume (src/session/sleep.rs:193-198), and compaction is forwarded to the harness (src/session/mod.rs:1049). The sync roots insrc/sync/mod.rs:148-182copy skills, Cursor rules, settings files and MCP server entries from a Mac to the VM, which is configuration, not learned state. The dependencies areaxum,tokio,serde,serde_json,sqlxandtokio-stream, so no memory engine sits behind it. What earns the entry is the upload upsert, which keeps the first stored record on a key collision and returns whether the retransmitted text matched (src/session/history.rs:57-61), so a retry after a lost commit reply is idempotent and a different record under the same sequence is detected rather than overwritten.mcn92/pikeletwas examined and has no report: its records can now be retired and replaced by id, but only by whoever compiles the corpus, and nothing an agent learns can reach them. Apache-2.0 (Matthew Noonan), 74,482 lines of JavaScript, Rust and Python over 270 files atd00f50ac…(the 0.9.2 release, 1 October 2026), created 20 April 2026. It compiles a corpus into a single self-contained.pikeletfile — source text, semantic and keyword indexes, query encoder, integrity commitments, retrieval calibration and evaluation fixtures — served over HTTP Range reads from static storage and mounted for an agent over MCP. The artifact rule is unchanged (spec/SEARCH_ARTIFACT_CONTRACT.md:106-110: an artifact "is immutable after publication", and a superseding one has a new identity). What releases 0.9.0 to 0.9.2 add is the layered profile,LAYERED_PROFILE.md, which keeps every file immutable and makes the corpus mutable by chaining files.pikelet appendwrites a small layer over a parent: new records chunked from--sourcedocuments, a cumulative tombstone bitset over global record ids from--remove, and(oldId, newId)supersession edges from--supersede <oldId>=<sourcePath>.compactfolds a chain back into one base whose lineage segment translates old citations forward, andrebasereplays only the deletions a layer itself introduced onto another head. The read side is careful. The mask is applied before candidate selection, and a tombstoned record stays hydratable by id "because an agent may have cited it" (decision 4,LAYERED_PROFILE.md:142-152). MCPget_recordreturns it withtombstoned: trueand itscurrentSuccessor, fields the result whitelist inprovenanced()(packages/pikelet/src/mcp.mjs:145-168) had been dropping, which, per the comment there, turned a tombstoned record into a live one on its way to the model;test/mcp_conformance.mjsdoes not mention the field. Two things keep it outside. The first is who writes. The MCP server dispatches four tools,search,list_packs,verify_packandget_record(packages/pikelet/src/mcp.mjs:872-875), and none of them writes.appendLayer,compactChainandrebaseLayerare called frompackages/pikelet/src/cli.mjs:27-39and the tests and nowhere else, and the profile's non-goals open with "Readers never write" (LAYERED_PROFILE.md:1617). A layer's input is a document path run through the base's declared chunker, so--supersedeswaps a corpus chunk for a re-ingested file: a publisher shipping a corrected manual, not an agent revising a conclusion. The second is what a correction is. A tombstone is a bit on a row id, un-deletion is a non-goal, and decision 9 (LAYERED_PROFILE.md:184-187) gives records "identity within a history, not content identity", so appending bytes equal to a removed record creates a new live id that nothing suppresses. That is the hide-a-row correction, chosen deliberately for a corpus in which re-publishing a document is meant to bring it back. A versioned document index with an honest update path is still the document-index case. The profile's status line (LAYERED_PROFILE.md:6) still reads "not implemented" while the CLI ships it andtest/layered_profile.mjsis in thenpm testchain; its section 13 records BEIR measurements of what layering costs, with the result files underbenchmarks/beir/results/. Recorded rather than dropped for two findings that still hold at this pin. The ablation experiment is the shape this atlas asks for and rarely finds: a pack was rebuilt byte-for-byte identical except for the record carrying one fact, the retrieval result moved frommatchQuality: strongat confidence 0.915 tononeat 0.136, and a third pack changed the same record's value and the grounded answer followed it (docs/veyra-ablation.md). The write-up separates what is reproducible from what is not —examples/one-file-search/web/public/reproduce-ablation.mjsre-derives the retrieval-side numbers, while the paired model sessions are marked "a described observation rather than a reproducible result" — and it refuses the overclaim the experiment invites, stating that this "does not mean Pikelet can prevent an LLM from hallucinating." The limit on citing it is that the script prints rather than asserts, and the packs it reads are release assets fetched bynpm run demo:veyra, so nothing fails in CI when the numbers move. The part that does run is the committed abstention fixture:test/fixtures/encoder-conformance/abstention-golden.jsonholds ten labelled queries, five of them labellednone, andtest/complete_profile.mjs:848-855requires all ten to reproduce their label and a query labellednoneto return zero results, inside thenpm testchain (package.json:23). That is the store-level must-not-retrieve assertion this atlas looks for, built for a search index. It holds for the library call, whose default withholds results undernone; the MCPsearchtool ships them by default (showAbstained,packages/pikelet/src/mcp.mjs:202), so what an agent sees is the verdict, not an empty list. Searches run at this pin:git grep -nE "appendLayer|compactChain|rebaseLayer"(the CLI, the three definitions andtest/layered_profile.mjs);grep -n "toolName ===" packages/pikelet/src/mcp.mjs(four read tools);git grep -nE "request\.method|method === 'POST'" -- packages(the two Worker templates, whose only POST routes are/searchand/reset_cache). The admin-gated/addand/deleteroutes inexamples/legacy/reference-worker/worker.jsare an HNSW index service already present at the first examination,9f81ad79…, and no MCP tool reaches them.veersaraf/forgetting-benchwas examined and has no report, because it measures the thing rather than being it — and its measurements are worth carrying anyway. MIT, Python, 3,304 lines over 34 files at12596f7d…, dated 4 September 2026. It is "[a] benchmark for whether agent memory forgets — not just whether it recalls", built on the observation that the mainstream libraries "are built and benchmarked around recall" while "the under-measured half of long-horizon memory is whether an agent forgets stale facts, resolves contradictions, and stays bounded over thousands of turns". A reference memory core ships with it, but it exists to be measured, which is what puts this here rather than in a report. Four things in it are worth a reader's time. The first is the design decision that keeps the contradiction metric from being a tautology: the memory core does not receive clean slot keys, it extracts(entity, attribute)from raw text with a trained tagger, and 40% of updates are deliberately phrased to defeat it — implicit or numeric updates like "Alice relocated to Denver" that never restate the attribute — while the metric is scored against ground truth the memory never sees. A benchmark whose contradiction rate reached zero "would be measuring its own plumbing, not memory quality". The second is the resulting floor: across keep-everything, last-write-wins, Ebbinghaus decay and a learned policy, the stale-fact contradiction rate bottoms out near 0.33 and no policy beats it, because extraction misses set it. The third is what decay actually buys over per-slot dedup, which is the mem0-style bar: not contradictions and not recall, which match within noise (0.319 against 0.330, and 0.668 against 0.670), but bounded memory — about 40% fewer entries and 42% fewer tokens, with the gap widening over the horizon, because last-write-wins "never forgets what it can't slot" and distractor noise therefore accumulates forever. The fourth is that forgetting is a frontier rather than a setting: sweeping the decay constant moves between 0.10 contradictions at 0.50 recall and 0.67 recall at the 0.33 floor, and per-slot dedup is one fixed point on that curve. What earns the entry, beyond the numbers, is the reporting. The one result that flatters the worst policy is kept and explained rather than dropped — keep-everything "wins" precision and recall because "retaining every past value means old entries whose value coincidentally equals the current one get counted as correct hits", which is "hoarding, not skill", and is the same hoarding that gives it by far the worst contradiction rate. And the live adapters for the commercial libraries are marked "probed, not scored", with the scope of the claim stated plainly: "No claim here is a mem0 or Letta win."cp-lab-uts/Knowledge-State-Governancewas examined and has no report: it is a paper artifact with no memory system in it, and its central table is the clearest measurement of this atlas's own thesis that the corpus has. No licence file, Python, at706c7e82…, dated 7 September 2026 — code and frozen results for "Relevant but Inadmissible: Budgeted Knowledge-State Governance for Persistent Large Language Model Agents" (Zhu, Zhu, Ye, He, Zuo and Wang). The title is the argument. A record can be exactly what a query asks for and still be one the agent must not be given, because something superseded it, because it belongs to a branch that was closed, or because a record it depended on is no longer valid.derive_statusescomputes those three classes from supersession links,closes_branch_idand dependency edges stored on the episode, and a budgeted packer then fills a token budget from the admissible set only. The measured result, over 60 episodes at 4,096 and 8,192 tokens with 2,000 bootstrap samples, is inexperiments/results/table_a_stateshift_admission.csv, and three rows carry it. Hybrid retrieval and recency both score a current-evidence rate of 1.0 — and a superseded-admission rate, a branch-leak rate and a dependency-invalid admission rate of 1.0 as well, at both budgets: perfect relevance, and every inadmissible record admitted along with it. The governance policy holds the same current-evidence rate of 1.0 with all three at 0.0. The third row is the one to carry: an LLM judge asked to decide admissibility scores 0.70 current-evidence recall while still admitting 0.27 of superseded records, 0.17 of dependency-invalid ones and 0.06 off-branch — worse on both axes than a deterministic rule over links the store already holds. Whenever this atlas withholds a review mark because the adjudicator is a model rather than a person or a rule, that row is the measurement behind the judgement. The repository also carriesuse_branchanduse_dependencyablation switches so each component's contribution is separable, human-audit utilities with a disagreements file beside the summary, and frozen aggregates chosen so the manuscript's numbers can be checked without rerunning a hosted model. It is reviewed without a licence file, which for a paper artifact bounds reuse rather than reading.Brain0-ai/brain0was examined and has no report: what it durably holds is what happened, not what is true — and one mechanism in it answers a question this atlas asks of every system. Apache-2.0, Rust with a TypeScript GUI, 16,675 lines across 52 Rust files at68edafc0…, dated 9 September 2026. It is "[t]he black box for AI-written code": "gittells you what changed. brain0 tells you why: which prompt wrote it, what the agent read to write it, and whether you can trust it." It passively builds a decision graph linking every commit to the agent intents behind it, down to the function, with a DLP audit of what agents read and a risk score, reading "git and the transcripts your agents already write to disk" with "[n]o hooks, no agent cooperation, no code changes". Everything it stores is a historical event — this prompt was issued, this file was read, these lines changed — and a later reading cannot contradict any of it, only find it recorded wrongly. That is the scope line this atlas draws for an audit log or a task queue, and it is why there is no report rather than a criticism. What earns the entry isbrain0-reconcile, which refuses to take an agent's word for its own work. "A coding agent declares what it changed (via MCP). The observer records what actually changed." The crate compares them and does two things with the comparison: gap-filling, so "everything that actually changed is linked to the agent's task even if the agent never mentioned it, so the graph is complete", and drift detection, so "when declared and done diverge (e.g. 'I only touched X' but 12 files changed), the discrepancy is recorded as a first-classDriftsignal on the task and feeds the a-priori risk." This atlas withholds a review mark whenever the only evidence of an actor is a string that actor supplied; brain0 applies the same instinct to an agent's account of its own changes, treats the self-report as a claim rather than as the record, and stores the gap between claim and observation as data. Any system that asks an agent to summarise what it did has the same exposure and, usually, no observer to check it against.zhengkid/Dream-RSIwas examined and has no report: no code is released yet, and what it stores is a record of what happened rather than a claim that could turn out false — but its bound on replay is the thing to take. Dream-RSI: Recursive Self-Improvement through Evolving Worlds, Zheng, Wu, Zhang, He, Zhang, Coleman, Wei, Bai, Liu, Liu, Wang, Zhuan, Kang, Xiang, Huang, Cheng and Guo (Google, Google DeepMind, University of Maryland, University of Virginia), © 2026 Google, at4149ea91…, dated 16 September 2026. The search is written down because the absence is the first finding: the repository holdsREADME.md,CITATION.cff, a PDF underpapers/and anassets/directory, and nothing else — zero files matching*.py,*.rs,*.ts,*.js,*.goor*.ipynb, and no licence file. The README's own release table says it: paper "✅ Available", full codebase "⏳ Being prepared". The idea is that a completed discovery run is already a simulator. Each node of a discovery tree "preserves this inherited history and records the outcome of the new generation–evaluation attempt, including the resulting filesystem snapshot, generated artifact, evaluation diagnostics, and score", so "[s]ince all node outcomes are pre-stored, a single costly online run enables thousands of rapid, zero-execution-cost off-policy evaluations" — alternative exploration policies are scored by walking the recorded tree instead of re-running the agent. That is durable agent history put to a use this atlas does not otherwise track: not recall, but counterfactual evaluation. It is out of scope for the same reasonBrain0-ai/brain0above is — the trees record attempts and their realized outcomes, and a later reading cannot contradict "this attempt scored 0.71", only find it written down wrong. What earns the entry is where the exactness stops, because the paper puts the bound in the formalism rather than in prose. Replay reveals only what was recorded: "each branch is traversed in its recorded parent–child order, and no outcomes beyondT_iare generated", and the child set is empty "when no recorded continuation remains", so the simulator runs out rather than extrapolating. The improvement guarantee is scoped the same way — because the candidate set includes the incumbent, the selected policy "is no worse than the current policy … in average replay score on the fixed history", which is a claim about the replay score on a frozen history and deliberately not one about the world. Any memory that answers "what would have happened" from stored history owes a reader exactly those two sentences: where its coverage ends, and which quantity its guarantee is over.- arXiv:2609.11060 was
analysed and has no report: the mechanism is two prompt blocks and a
tool grant inside a curator nobody outside the authors can run.
Grounding Agent Memory: Environment-Probing Curation for Enterprise
Agents (Susheel Suresh, Hazel Mak, Sahil Bhatnagar, Chhaya Methani
and Alejandro Gutierrez Munoz, Microsoft Corporation, submitted 10
September 2026, cs.AI and cs.SE, no venue named) describes a store whose
only mutator is an asynchronous post-task curator agent; the task agent
holds
memory_readand no write tool at all. A record iscategory: pattern | rule | trap | schema | policy | interaction,confidence: high | medium | low,applies_to: a short retrieval scopeandlemma: one concise, actionable claim, with "provenance, utility, and usage metadata" named once in §3.2 and never specified, shown or used. The intervention is small and stated as such: the same curator, schema, retriever, distiller and CRUD policy, plus a read-only subset of the task's own environment tools and two inserted prompt blocks telling it to "verify candidate and existing memories before Create or Update whenever correctness, scope, freshness, or actionability is uncertain" — propose, probe, commit. The claim an atlas report would test is drift repair: CLBench migrates its schema silently after question 20, and the trajectory-only curator carries "Useattrs_g3" forward while the probing curator rewrites it to "Useproduct_attributes_g3". That repair is opportunistic, not a mechanism — it fires when a later task in that area closes, nothing watches the environment, and a contradicted record is removed withmemory_deleterather than kept as a rejected value, so the store has no trace that a lemma was once believed and no valid-time axis on which to ask what it believed last week. The headline 39% to 73% pass rate is memory against no memory; the paper's own contribution moves 70±16 to 73±5 pass and 20.00±6.52 to 22.60±2.07 reward over five paired runs, which §5.3 concedes ("[b]ecause uncertainty intervals overlap, we treat this as a mechanism interpretation rather than a resolved subgroup effect") and the abstract does not. The separation that survives is in variance rather than means, and the cross-model no-drift table is cleaner on Sonnet 4.6 (+0.421 against +0.351) than on Opus 4.7 (+0.263 against +0.252). "Task-agent cost from $3.38 to $1.68" is the synchronous half only: §4 says "task-agent cost excludes the separately tracked curation phase", the per-world table adds that "costs exclude distillation/curation", and no curation figure is reported anywhere, while probing adds curator tool calls by construction and the distiller and curator run the samegpt-5.4at xhigh effort as the task agent. Retrieval is never under test — a transcript in Appendix E.3 readsmemory_read: showing 11/21 matched entries (query asked for top-25; index holds 21 total), so at fifteen to twenty-one records a world the reader returns most of the store and the result measures what got written. The question the deployment section raises and never answers is whose grants a probe runs under: §A.2 assigns the curator "a least-privilege, read-only subset of connectors or MCP tools already registered for the responding agent" and asserts that "existing authentication, authorization, and audit boundaries remain in force", but the word tenant does not appear in the paper,applies_tois a retrieval string the curator writes rather than a key any read path enforces, and a lemma validated against one user's view of an enterprise corpus is committed to an index later task agents read — the scope-predicate shape this atlas finds in running code again and again. "Auditable" appears once, in the abstract, with no probe log or lemma-to-probe link behind it. The grounding search: 14,488 words extracted from the v1 HTML, onegithub.comURL in the whole text and it isgithub/copilot-sdk, no code- or data-availability statement, and the adapted APEX split — six worlds and 90 tasks grouped by(domain, world_id)out of the 480-task original — is not released either, so the benchmark variant is no more reproducible than the system. The only code trace is downstream and is a request rather than an artifact: issue 107914 onNousResearch/hermes-agent, opened 11 September 2026, proposes the same loop for that project'sagent/background_review.py, whose staged writes Hermes Agent already records with anoriginofforegroundorbackground_review. If code appears, the first things to read are the probe-tool binding — which credential a probe uses and whether the probe result is stored beside the lemma it validated — and then whetherconfidenceandapplies_toever reach the read path or stop at the write. augustoolucas/yacaowas examined and has no report: the only thing its workflow durably writes is a plan for the job in hand, and the only thing its code durably writes is a version pin in your config. MIT, 927 lines across 14 files at12079c75…, v0.4.3, 107 commits since 22 July 2026. Yet Another Coding Agent Orchestrator is a plugin for OpenCode whose whole content is two agent definitions and three skills: an orchestrator that clarifies, plans and reviews, and a builder subagent that implements one self-contained task contract at a time and answers in a fixed four-field format —STATUSovercomplete/partial/blocked/escalate,CHANGES,VERIFIED("exact command(s) run and their real output (not 'should pass')") andGAPS. It is workflow, and it says so. The vocabulary settles the scope question rather than the README: across every.js,.mdand.jsonin the tree,memor,recall,remember,forget,persist,belief,retriev,embedding,sqlite,vectorandknowledgereturn three incidental hits — memorize in the README's prose, a comment about persisting an update-check timestamp, and "[r]egisters the agents in memory" meaning in-process. The planning skill does write durable files,.opencode/plans/plan-<slug>/plan.mdand one task contract per task, and nothing in the three skills or the two prompts reads an earlier plan back: they are a work ledger for the current job, which is the line this atlas already draws forbeadsandoh-my-openagent. What earns the entry is the other durable write. WithautoUpdateon, the plugin fetches the latest release tag from the GitHub API and rewrites the user'sopencode.jsoncin place to pin the plugin spec forward, preserving jsonc comments and quote style by rewriting raw text rather than reparsing, andupdateScope: "all"extends that to the project's own config. It defaults to off and the write is temp-file-then-rename with the original mode copied — careful work. It is still a plugin that edits the file that decides which plugins you load, which is worth knowing before the screen in this repository's own screening skill is pointed at the next thing that does it less carefully.- arXiv:2601.12538 was
examined and has no report: it is a survey, and its companion repository
is a reading list. A Survey of Agentic Reasoning for Large
Language Models: Towards Recursively Self-Improving and Collective
Agents (Tianxin Wei, Ting-Wei Li, Zhining Liu and 26 co-authors;
University of Illinois Urbana-Champaign with Meta, Amazon, Google
DeepMind, UCSD and Yale; v1 18 January 2026, v2 20 September 2026;
accepted by TMLR) is 135 pages organised along three layers —
foundational, self-evolving, collective — and memory is one subsection
of the second. Section 4.2 sorts thirty systems in its Table 6 on three
axes: setting (in-context or post-training), format
(text, semantic, workflow, trajectory, graph, multimodal, implicit) and
type (factual or experience). Its claim is a direction of
travel, from memory as "a passive buffer" to memory as "a
policy target", where an RL-trained agent decides what to add,
update or delete; Memory-R1, Memory-as-Action, Mem-α and MemAgent are
the instances. Section 5.3.2 adds four dimensions for multi-agent memory
— architecture, topology, content, management — and names
Summarize-and-Forget and Filter-and-Verify as
management strategies. Nine of Table 6's thirty have reports here: LangMem, LlamaIndex, MemGPT as Letta, MemoryBank, A-Mem, MemOS, LightMem, Mem0 and Zep.
MemAgent, which the survey files under post-training memory control, is
conversation-window management by this atlas's scope bar. What the
taxonomy does not carry is the axis this atlas grades on: none of its
axes asks whether an entry can be corrected, scoped, or kept deleted,
and in the 63,064 words
pdftotextextracts from the v2 PDF, tombstone, unlearn, stale, poison and valid time occur zero times and forget six. So the RL memory managers are described by the operations they learn, and not by whether a deleted value can be learned back. The project link isweitianxin/Awesome-Agentic-Reasoning, MIT, 91 commits, at6c3d3c6d…(21 September 2026). It holds a 1,438-line README with 594 distinct arXiv links, a LICENSE, thirteen figures and a talk PDF, and no code, so the screen had nothing to parse. Searches:grep -n -i githubover the extracted text finds five lines — the project link, a Copilot footnote and three bibliography entries;git ls-filesover the list's checkout finds no source file. The record is for a reader who meets the survey's Table 6 and wants the implementations: the nine linked above are the place to start, and none of the post-training systems in its third block has a report here. - xmemory (arXiv:2604.27906) was
examined and has no report: the engine is a proprietary hosted service,
and every public repository is a client, an integration or benchmark
data. From Unstructured Recall to Schema-Grounded Memory:
Reliable AI Memory via Iterative, Schema-Aware Extraction (Alex
Petrov, Alexander Gusak, Denis Mukha and Dima Korolev, all of xmemory;
v1 30 April 2026, v3 13 August 2026, cs.AI, 33 pages) describes memory
as a system of record whose schema states "which values must never
be inferred". Writes are decomposed into object detection, field
detection and field-value extraction, with validation gates, local
retries and an LLM judge in the loop; a value that fails validation
becomes a retry, a clarification or an explicit unknown rather than a
commit. Three contexts split the work: a request context per write, a
session context that assembles partial objects across turns, and a main
context described as "the durable, versioned store" holding
current values, their history and provenance links to the sessions they
came from. Schema changes are versioned migrations that mark
irrecoverable values as unknown. The end-to-end benchmark drives field
updates, clears, relation deletion, an entity rename and a cascading
entity delete, re-asking state questions after each; xmemory reports
97.10 % F1 against 80.16–87.24 % for Cognee, Mem0, Supermemory and Zep, and 95.2 % on a generated
expense-splitting task. Its own limitations section says the benchmarks
are deliberately structured and that incorrect facts pass if they pass
the validators. The atlas has not checked these numbers. The
organisation
xmemory-aipublishes twelve repositories, one of them a fork ofhermes-agent.xmemory_client_pyat2cead52f…is 9,365 lines whosewrite,review_suggestions,decide_suggestionsandapply_pending_decisionsare each onePOSTto/instances/{id}/…onhttps://api.xmemory.ai; its schema-evolution module says its models "mirror the server-side wire formats". Its LICENSE grants MIT for the client only and states that the backend, "its memory engine, schemas, extraction and reader models" are proprietary.claude-code-pluginat5fa4330a…andxmemory-skillare all-rights-reserved and reach the service through thexmemclicommand; the TypeScript client, the n8n node, two Temporal plugins, an example agent and an MCP catalogue listing are the same boundary in other runtimes.datasetsat372866e8…holds the three benchmarks' YAML and CSV data and six Python files, all of them the expense-task generator; the harness that ran the five baselines is not in it. Searches:pdftotextextracts 13,619 words, in whichgithuboccurs eight times — four links intodatasets, three in bibliography entries for Cognee and LoCoMo, and one in prose about LongMemEval — and source code never; the twelve trees were listed through the API and only the client was cloned. If the engine were published, the first thing to read would be what the main context does with a value it replaces: whether the earlier value stays queryable and marked replaced, and whether a cascading delete leaves anything that stops re-extraction from writing the deleted record back. YoKONCy/TriviumDBwas examined and has no report: it is an embedded vector, graph and document database, and every memory semantic in it is one a caller builds on top. Apache-2.0, at7edf8cea…, a commit of 30 October 2026; about 70,700 lines of Rust insrc/, inline test modules included, with PyO3 and napi-rs bindings, a CLI and a nightly HTTP server. A node is a caller-supplied vector, a JSON payload, optional sparse text and labelled weighted edges under oneNodeId. Writes go through a WAL;deleteclears the vector slot, the property and text index entries and both edge directions (src/database/mod.rs:1860-1873,src/storage/memtable.rs:2962). Reads are TQL,search_hybrid, and SA-PPR spreading activation with FISTA residual recall and DPP diversification. Nothing in the engine calls a model, assigns a status, records why a value changed, or retires anything on its own. The documented agent pattern is a caller-written payload of typememorywith a date, and the node checklist recommends acreated_atfield so the caller can filter by time and clean up (docs/best-practices.md:204-270). Scope is the same:payload_filteris documented as multi-agent isolation byagent_id(src/database/config.rs:154-155), an arbitrary predicate the caller must pass on every query, beside one database file per agent under a sharedResourceRuntime. The one stateful recall policy is real and is deliberately not memory. Withenable_refractory_fatigue, the top 15 nodes of a diffusion are marked in aHashMap<NodeId, u8>, and the next query that reaches one scales its energy by 0.15 and clears the mark (src/graph/traversal.rs:87-95,274-285;src/storage/memtable.rs:619,1652-1693). The map starts empty at every open and no storage file writes it; the engine refuses it in batch search and on read-only handles, whose error calls it process-local (src/database/mod.rs:556,990). It is a diversity heuristic over one process's query sequence, and nothing it holds could turn out to be false. The README's paper, arXiv:2605.02171 (QuIVer: Rethinking ANN Graph Topology via Training-Free Binary Quantization, Wenxuan Xiao, Zhiyou Wang and Chengcheng Li, v1 4 May 2026, cs.DB), is about the ANN index and does not mention memory. Screened before reading: no auto-run surface, three build-time execution points (build.rs,src/index/quiver/corrected_sm/build.rs, an npmprepublishOnly), seven dependency surfaces inside the cooldown and one floating range;AGENTS.mdwas treated as data, and nothing was installed, built or run. Searches:git grep -n -i -E 'decay|ttl|expire|forget|consolidat|supersed|contradict' -- src crates/triviumdb-server/src crates/triviumdb-cli pythonmatchessettled,little-endianand aTimeDecayHookfixture inside the#[cfg(test)]module that opens atsrc/hook.rs:687;git grep -n -i -w -E 'mcp|llm|openai|anthropic|chat' -- src crates python ':!crates/triviumdb-server/web'returns nothing, and the same pattern matchesREADME_QUIVER.md;git grep -n -i fatigue -- src/storagehitsmemtable.rsalone. A layer that put lifecycle, provenance or a correction path on these nodes would be the report, with this engine in itsstoragerow.- Memorilla (arXiv:2610.21375) was
examined and has no report: it is a learned reader for a document
collection, and the collection belongs to the caller.
Memorilla: Latent Semantic Memory for LLMs (Adibvafa
Fallahpour, Parsa Idehpour, Vignesh Kothapalli, Nikita Mounier, Shirley
Wu, Shayan Pardis and Jure Leskovec; Stanford, Toronto, Pennsylvania,
MIT and the Vector Institute; v1 15 October 2026, v3 3 November 2026,
cs.LG and cs.AI, no venue named) embeds each document once with a frozen
Qwen3-Embedding-4B into what §2.1 calls "the query-independent
document store". For each query, 16 learned slots are conditioned
on the question embedding, cross-attend over every document embedding,
and are projected into a frozen Qwen3-8B's input space as soft tokens.
The paper reports the best average across eight personalization,
long-document and knowledge-intensive benchmarks against baselines that
include Mem0 and MemoRAG. On FactKG it
scores 84.33% against 80.43% for full context, with 108× fewer document
tokens. On TextWorld, success rises from 18.6% for full-history
in-context learning to 24.2%. Table 13 shows where the gain comes from.
Query-independent pooling at matched parameters reaches 31.10 on PMv2
short answer against Memorilla's 44.04, and a Q-Former that also sees
the question reaches 43.34. Replacing every document embedding with
Gaussian noise moves the documents-only variant by +0.04 and Memorilla
by −5.93. The code is
snap-stanford/memorilla, Apache-2.0, atd3e3f8f1…(13 November 2026): 26 commits and 8,783 lines of Python in 38 files. Inference keeps a tensor the caller holds.MemoryVLLM.answer(question, documents)embeds[*documents, question]on every call (memorilla/vllm.py:345).MemoryVLLM.write(documents)embeds a list once and returns aCollection(:28,:298-313): the embeddings on the GPU or, withmemory_cache=True, the keys and values of the two cross-attention layers computed once (memorilla/memory.py:322-362). The README times a question over one million documents at 8.1 ms with the cache against 74 ms without. TheCollectionis a return value. The library does not name it, keep it, save it or change it; no function adds, changes or removes a document, andwriteon a longer list embeds every document again. The persistent store the paper describes is, in this tree, a benchmark cache. It isEmbeddingStore(memorilla/embeddings.py:72), whose docstring reads "Read-only, memory-mapped access to one split's document and question embeddings".build_embeddingswrites a whole split from its parquet files (:387-431), and the only invalidation is an error message telling you to remove the directory and recompute (:561). §2.1's "only added or changed documents must be re-encoded" has no code path. Neither does §7's claim that each user's store "can be kept on device or deleted on request". It is a privacy claim with nothing behind it in the release except deleting a split directory, and the project site makes it under Future directions as something an assistant "could" do. The agent's document store lives for one game. It isTrajectoryMemoryin the authors' SkyRL fork at0ce9767c…: a Python list capped atmax_documents(skyrl-gym/skyrl_gym/envs/textworld/memory.py:62-96) and recreated at every episode reset (base.py:111). What carries from one game to the next is the memory module's GRPO-trained weights, a policy learned over many games rather than anything one game revealed. No memory token has an identity. Each is recomputed per query, so no key, claim or value could be corrected. This is the boundary aimee's prepared attention state sits on, one level further: aimee's tensors derive from a governed store in its own tree, and Memorilla has no store. The screen found no auto-run surface. It flagged one build-time execution point (tests/conftest.py), one dependency surface inside the cooldown (pyproject.toml, changed in the pinned commit) and no lockfile. Nothing was installed or run. Searches:pdftotextextracts 15,032 words from v3, in whichgithuboccurs zero times, since the repository is linked from the project site rather than the paper;git grep -n -E 'def (add|append|delete|remove|update|upsert|forget)' -- '*.py'matches onlyEmbeddingWriter.add(memorilla/embeddings.py:259), whose callers arebuild_embeddingsand the tests;git grep -n -i -w -E 'sqlite3?|faiss|chromadb|qdrant|lancedb|pgvector'matches.gitignorealone. A release that kept a per-user store would be the report. The first things to read in it are whether removing a document leaves anything that still answers from it, since the soft tokens are rebuilt per query and only the store could keep a deleted document, and whether the personalization checkpoints were trained on the users they serve. The cache settles part of the first by construction: it is refused unless the module has no document self-attention (memorilla/memory.py:293-295), so each document is one independent column of keys and values and removing it would be exact. No call removes one.pv4andpmv2are trained on synthetic users here; a deployment fine-tuned on real conversations moves deletion into the weights, which is the case that brings Second Me into scope. enriqxxx/53on-harnesswas examined and has no report: it is the desktop shell of a memory product whose engine is downloaded from 53on.com at run time, and no memory code is in the tree. MIT for the code, with a NOTICE that reserves the 53ON name and logo, read at7005c3f5…, the head ofmainon 9 November 2026, six commits by one author from 8 to 9 November 2026. It is an Electron app for Windows, 5,843 lines of JavaScript, HTML and CSS undersrc/andrenderer/with no test files, and its README says the memory engine and the store run as a service on 53on.com. Two paths touch memory.src/membio.js:8-70installs an engine of exactly four files,memory.core.js,memory.node.jsand two language files, fromhttps://53on.com/xsite/packages/<package>/Assets/engine/<version>-<n>/: it checks a manifest's signature against a key built into the shell and each file's SHA-256, runs the complement's self-test on the result, and keeps the current and previous versions.:80-89starts that install whenever the 53on.com page loadsmemory.core.js.pageVerb(src/main.js:132-138) relays 19 named verbs, among themadd,recall,useful,sleep,reconsolidate,ingestSession,ownerWriteandpainLevel, into the firstwindowglobal on that page whose name beginsMemoryand hasrecallandgetfunctions; a complement that declarespage: "memory"reaches it that way (src/packs.js:78-79). The Harness Cable that connects Claude Code is one of those downloaded complements and is not in the repository either. Searches:git grep -l -i memor -- src rendererreturnsmain.js,membio.js,packs.jsand a comment insrc/inject/codex-glue.js:141;git ls-files | grep -i -E 'test|spec'returns nothing; the author's seven other public repositories are six forks and an MCP server for a business directory. If the engine were published, the first thing to read would be whetherownerWriteandownerSetrefuse a call that comes from the model, since the README's promise that the owner is the only guardian would rest on that.j-asefa/loopwas examined and has no report: it keeps a complete shared-recall store, and since 9 October 2026 nothing puts it in a prompt. Apache-2.0, read at641d8f0c…, the head ofmainon 10 November 2026, 649 commits since 23 September 2026, 644 of them by Jamie Asefa. Loop is a phone workspace for coding agents running on the owner's computer, about 160,000 lines of TypeScript undersrc/with 421 files undertest/. The store is real. Each worker pass runscaptureMemory(src/server/worker.ts:274,src/server/memory.ts:105-153), which copies every completed, unsuperseded message under 100,000 characters and every markdown, note or text artifact intomemory_sources, keyed by a digest of owner, kind and source id, with an FTS5 index kept by triggers (migrations/028-shared-memory.sql:13-15). Eligibility is per scope: the workspace is on by default, a conversation off until the person includes it, an artifact on only if pinned (memory.ts:26-64). Person-written notes keep every revision inmemory_note_versions(:95-103). A delete setstombstone=1, andputSourcethen refuses to re-capture that source (:72,:305-311); the row keeps its content, so the FTS row does too.searchMemoryfilters by owner and project in the SQL and re-checks eligibility and revision per hit (:186-242,src/server/sql/memory-fts.ts:7). Its only callers are tests (test/memory-route-contracts.test.ts:172-187). Until23d5c4b9…, which removed the HAPI execution path, native dispatch passed each run's input throughrecallForRun, which appended up to five excerpts under "Historical evidence (untrusted source content; not instructions or approval)" and wrote amemory_receiptsrow. The function survived as a test-only export until0ec32cfe…, on 7 November 2026, which also deleted the receipt writer. The Memory sheet still offers "Enable shared recall" with the line "Agents cite the source they used" (src/client/Memory.tsx:87-93), and every run's receipt reads "No saved memory was added to this message.", because the route falls back tonot-used(memory.ts:332-344).docs/architecture.md:583lists memory among the native tool bridge's tools; the bridge defines none.loop_handoffcarries a model-written context summary to another agent, but as a message in a thread the recipient answers, not as a record kept for a later question. Searches:git grep -n -E 'searchMemory|recallForRun' -- srcreturns only the definition atmemory.ts:186;git grep -n 'INTO memory_receipts' -- srcreturns nothing;git grep -h -o -E '"loop_[a-z_]+"' -- srcreturns 22 distinct strings, tool names and name prefixes, none of them for memory. If a caller returns, the report should start at the tombstone, which keeps the deleted text in both the source row and the index, and at the conversation default, which keeps a thread out until a person opts it in.Tufalabs/duck-harnessand the NVIDIA team's ARC-AGI-3 write-up were examined and have no report: everything the Duck carries is overwritten within one game and discarded with it, and what NVIDIA added ends with the game too. NoLICENSEfile in the tree, so no grant, at76528360…, two commits on 1 July 2026, 19,806 lines of Python across 46 files beside a 3,521-file example run; the screen found two Makefiles to read before a baremakeand nothing else, and nothing was installed or run. The Duck plays ARC-AGI-3 through Tufa's TAAF framework with one Python tool, and "Every Python tool call starts fresh" (ARC3-Inference/README.md:87). Its memory is a seven-field world model —World model,Goal model,Action model,Recent findings,Open questions,Plan,Cross-level notes— parsed from labelled lines in the model's own replies (ARC3-Inference/inference/agent/tool_agent.py:263-293), each field replaced by its newest non-empty value and re-injected every turn under "Revise any item above immediately ifcurrent_frameorhistorycontradicts it" (:1128-1144). A level change, game over or run end clears six fields and keepsCross-level notes(:1113-1126), and the conversation keeps the last 30 assistant turns inside a 32,768-token window (:151,:1653-1670). Both are attributes of the agent object, emptied whenever the run directory changes (:975-984):git grep -n -e _summarized_knowledge -e _history_messages -- ARC3-Inferencefinds no write to disk, and the one state file,tool_runtime_state.json, holds observed frames rather than claims. A field that is replaced stops being current rather than turning out false, which puts this on the context-engineering side of the line. The bundled run, 25 games at 20 passes for a TAAF final score of 1.60, shows how little crosses even a level: the carried block reaches 174 of 500 prompt logs, andgrep -rl -e '- Cross-level notes: ' example-run/promptsreturns none. ARC-AGI-3: NVIDIA team solution, third place in ARC Prize 2026 ARC-AGI-3, published on 12 November 2026 by Darragh, Ivan, Gal Kaplun, Elad Sarafian, CPMP, Yeyin Zhu and Giba, takes the Duck's loop through Daniel Franzen's public Milestone-2 harness and adds a Python interpreter that persists for the game, level-completion summaries and history-trim summaries, so that "Level lessons survive resets and trimming" — within one game. Level notes were "the only prompt change that gave a clear gain", the summaries took about 4% of calls, and the persistent interpreter cut missing-variable errors from 54 to 2 per run. The two selected submissions scored 56.26 and 60.95 on the public leaderboard and the final version 73.3 on the team's 110-game local test, and most of the reported gain is serving: a pruned, quantization-aware-distilled Qwen3.8-Flash-Next and a sparse-attention KV cache offloaded to CPU memory to play 96 games at once, which is out of scope here as well. Its code is in datasets attached to the selected Kaggle notebooks and a zip on the write-up page, not a repository at a commit. A harness that writes its notes to disk and reads them back in a later pass or game is what would be read first.matiasbattocchia/open-bsp-apiwas examined and has no report: it is a messaging platform whose agent reads a window of the conversation, and its one memory field has had no writer since the code was first committed. Unlicense, read atf2e8b024…, 395 commits from 21 August 2025 to 3 November 2026, 392 of them by Matías Battocchia, 30,526 lines of TypeScript across 87 files and 18,887 of SQL; the screen found a format-and-lint hook, a plugin session-start hook that prints a setup notice, and the plugin's MCP server started withdeno run, and nothing was installed or run. OpenBSP is a multi-tenant WhatsApp, Instagram, TikTok and Slack business platform on Supabase: Postgres tables behind PostgREST and row-level security, Deno edge functions per channel, and a Claude Code plugin that reads and answers the inbox. Itsagent-clientfunction answers an inbound message by selecting that conversation's rows frommessagesnewer than seven days, newest first, capped at 50 (supabase/functions/agent-client/index.ts:71-72,:300-308), and each protocol handler cuts the list again to the agent'smax_messages(protocols/chat-completions.ts:355-361). A contact's/newdrops everything before it. That is a window over a transcript, on the context-engineering side of the line: the rows record what was said, and nothing derives a claim from them. The conversation row does declare a memory,ConversationExtra.memory, a nested string map (_shared/types/extra_types.ts:7-9,:141). Its only reader is the/newbranch, which empties it when it is non-empty (agent-client/index.ts:363-372); the block that would persist aconversation.extrareturned by the model sits inside a comment (:1060-1073), as it did ina0a25acd…, the commit that added the code on 21 August 2025, and no handler puts the map in a prompt. The agent's tools are a calculator, code execution, HTTP, MCP, attachments and parameterised SQL against a database the operator names, so anything an agent keeps there belongs to the operator's schema. The tree holds no test file. Searches:git grep -n -w memory -- supabase pluginreturns six lines, the type, the three-line reset and two uses of the word in prose;git grep -n -i -E 'embedding|pgvector|tsvector' -- supabasereturns nothing, andsupabase/schemas/00_extensions.sqlcreates eight extensions, none of them a vector one. A writer forextra.memoryand a handler that serialises it are what would be read first.- LongCapHarness (arXiv:2611.10463) was
examined and has no report: the paper describes no memory, and no code
is released. LongCapHarness: Capability-Guided
Auto-Harnessing for Long-Context Reasoning (Tao Zhang and Yuhang
He, Microsoft Research Asia, v1 7 November 2026, no venue named) has a
strong model, GPT-5.6-Sol, study a development set of questions with
reference answers and write a harness per capability: primitives
implemented as code or as a bounded model call, control logic that
sequences them, and a capability state that says how a question
is prepared and which intermediate outputs are kept. The harness is
revised by comparing its answers with the references, and then, in
§3.2's words, it "is frozen and saved to the capability
library". At test time a small model picks a harness by matching
each one's text description against the question and runs it inside an
8K or 32K window. Nothing is written after development.
Per-input state is created for one run and dropped; the library gains no
entry, loses none and records no outcome, and the word memory
does not occur in the paper. What it has is the write half of skills as procedural
memory with the feedback loop closed before deployment: a library of
procedures selected by description, authored offline against labelled
data, with no path by which a failing harness is noticed or retired in
use. The development split is drawn from the evaluated benchmarks
themselves, 2,242 development and 59,826 held-out examples with no
overlap, chosen so that harness development sees "each evaluated
task type" (§4.1); the result is therefore reuse on new inputs of
known task types, not on new tasks. Reported averages on HELMET are
79.32 for Llama3-8B at 8K against 70.15 for the post-trained NExtLong
model at 128K, and 78.73 for Qwen2.5-3B against 64.10 for PolicyLong; on
LongBench-v2's Long subset the harness trails PolicyLong, 27.85 to
31.50. Development cost is estimated at $541.47 of API charges against
$3,696.00 and $1,858.82 of training. §6 states the dependency:
performance drops sharply when the small models write their own
harnesses. No repository is linked from the abstract page or the HTML
full text, the text contains no code-availability statement, and on 14
November 2026 a GitHub repository search and a code search for
LongCapHarnessreturned two reading lists and no implementation. Read from the arXiv HTML of v1; no experiment was reproduced. - arXiv:2510.26493 was
examined and has no report: it is a position paper with definitions and
no system, and the two repositories it links hold no code.
Context Engineering 2.0: The Context of Context Engineering
(Qishuo Hua, Lyumanshan Ye, Dayuan Fu and six co-authors, ending with
Pengfei Liu; SJTU, SII and GAIR; v1 30 October 2025) argues that context
engineering predates agents by more than twenty years and sorts it into
four eras by machine intelligence: 1.0 for context-aware computing, 2.0
for agents, and 3.0 and 4.0 for human-level and superhuman systems, the
last labelled Speculative in its own heading. It frames the
whole activity as entropy reduction and defines it formally
(Definition 4) as a function from raw context and a task to a
composition of processing operations. Memory is §5.3.1 and §5.4.
Short-term memory is the subset of context whose temporal-relevance
weight exceeds a threshold, long-term memory the abstracted subset whose
importance exceeds another, and memory transfer a function from
the first to the second (Definitions 5.1 to 5.3). None of the weights,
thresholds or functions is given a form, so the definitions name the
slots of promotion
between tiers without filling any. §5.4 coins self-baking
for an agent digesting its own context into persistent structures and
lists four designs: natural-language summaries, fixed-schema fact
extraction, progressive vector compression, and a hierarchy over them.
The paper reports no experiment, benchmark or measurement; its
applications section describes Gemini CLI, deep-research agents and
brain-computer interfaces from their documentation. The passage most
useful to this atlas is §6.5, which lists what lifelong memory lacks, in
its words: "Systems rarely include features to check for
contradictions, undo wrong updates, or trace the reasoning steps that
led to a conclusion." That is the gap the rejected-value
tombstone and the append-only memory
audit address, stated as an open problem and not as a design. Code
search, 15 November 2026: the paper's HTML links
GAIR-NLP/Context-Engineering-2.0, which is a README and five figures, and citesGAIR-NLP/SII-CLI, which is a README and three images with no source; a GitHub repository search for the title found one other same-named repository, also a README and figures. The hosted product the README links was not examined. DigitalDreams-Lab/OpenVorldwas examined and has no report: it is a workspace that runs a crew of agents over a project folder, and the only thing a member carries between turns is the chat it is in. MIT, read at881c48b0…, the head ofmainon 16 November 2026, 49 commits by one author from 15 to 16 November 2026, version 0.11.0: 3,660 lines of JavaScript underengine/server, a React and Phaser client, and 41 test files of 3,211 lines; the screen found a committed pre-commit hook that is inert untilcore.hooksPathnames it and apackage.jsonand lockfile changed inside the cooldown, and nothing was installed or run. OpenVorld gives each agent a name, a role, a workbench folder and a model driver (Claude Code, Codex, Antigravity, opencode or an OpenAI-compatible API), and lets the person grant access one writ at a time. Each conversation is a thread: an index entry and an append-only JSONL event file (engine/server/threads.mjs:49-54). A turn sees that thread and nothing else. An API driver is handed the thread's last 30 founder and agent messages (threads.mjs:61-64,engine/server/agents/runner.mjs:208-213). A CLI driver resumes its own session by id, and when that session is gone it is given the same messages as text, newest kept, cut at 12,000 characters (runner.mjs:103-119,:194-198,:217-220). A party room replays the latest 40 room messages, each cut at 2,500 characters (engine/server/parties.mjs:82,:102-112); the project's architecture note says of it "the transcript is the memory" (docs/ARCHITECTURE.md:56). That is a window over a transcript, on the context-engineering side of the line: the rows record what was said, nothing derives a claim from them, and nothing carries from one thread to another. Three other things reach a prompt and none is written by an agent: the member's prompt template, the person's own name and about-me text fromprofile.json(engine/server/profile.mjs:32-38), and the list of writs the member holds (runner.mjs:57-60). The ten engine tools are file, command, fetch, world-info and game-command tools (engine/server/agents/tools.mjs:67-85), beside five browser tools andsecret_ask; none stores or recalls a note. The durable records an agent does cause are about access and not belief:grants.yaml, and anaudit.logline per tool call and per grant decision (engine/server/gate.mjs:21,tools.mjs:45). Searches over the tree:git grep -n -i -E 'memor' -- . ':!package-lock.json'returns seven lines, the architecture sentence above, four comments about process memory and a test'sMap;git grep -n -i -E 'embedding|vector|sqlite|recall|knowledge' -- engine packs docs ':!engine/client/demo'returns nothing; and no route under/api/vorlds/:id/threadsis aDELETE, so a thread can be neither removed nor edited through the API. The piece worth knowing is beside memory: a member's vault values are redacted from every event before it reaches the transcript (runner.mjs:156-157,:222), so the one store that is replayed is filtered at the write.huggingface/pybotwas examined and has no report: its memory store is the state of one conversation in a Python dict, and nothing in it is written to disk. Apache-2.0, read at7d63c7fb…, the head ofmainon 16 November 2026, 21 commits from 12 to 16 November 2026: 636,409 lines of Python in 528 files underbot/, of whichbot/memory/is 109,319 lines in 117 files, and a 197-line command line with one test file; the screen found apyproject.tomlwith no lockfile, changed inside the cooldown, and nothing that auto-runs, and nothing was installed or run. PyBot is a rule-based chatbot with no model: regular expressions, branches and lookup tables, which its README says a swarm of more than 1,000 agents wrote across over 5,000 evaluated versions. Each turn callsturn(text, memory)(bot/runtime.py:82-116). The command line createsmemory = {}when a chat starts and replaces it on/reset(pybot.py:125,:140-141), and the dict ends with the process. So the README's Memory store row describes dialogue state:observehooks pull a name, a job, a city, pets and plans out of each line intomemory["user"]with an ordered log of when each was said (bot/memory/__init__.py:307-340), and the store module answers questions about the conversation itself (bot/modules/memory_store.py:2-11). It is still a careful piece of in-conversation state.forgettakes a value back out when the person retracts it and leaves the log entry, because "a fact that was true ten turns ago is still part of the conversation" (bot/memory/__init__.py:533-539). And the runtime gives every responding module its own deep copy of the dict and adopts only the chosen module's copy, so "a reply that is not chosen leaves no trace" (bot/runtime.py:6-11,:56-61,:89-104): a write made while drafting a reply is committed only if that reply is the one sent, which is a cheap answer to speculative writes that the persistent stores in this atlas rarely give. That is all inside one session, on the conversation-window side of the line. Search:git grep -n -I -E '(^|[^_a-z.])open\(|write_text|json\.dump|import (os|pickle|sqlite3|shelve|json|pathlib|tempfile|socket|urllib)|from (os|pathlib|urllib)' -- botreturns four lines: three are the wordopeninside regular expressions about valves and messages, and the fourth is an unusedimport os, sysinside a function atbot/knowledge/lookup.py:3220. No file underbot/opens, writes or loads anything. The README's 550,000 lines of agent-written tests are not in the repository, and its SmolTalkBench win rate of 26% is the project's own figure; neither was checked here.ewiger/hqlwas examined and has no report: it is a typed query language whose "knowledge vault" is a directory of Markdown a person writes, read into an in-process snapshot on every invocation; no verb writes a card, and the tree holds no agent, model or tool surface. MIT (LICENSE, HQL Contributors;Cargo.tomlagrees), 75,808 lines of Rust undersrc/and 3,722 lines of HQL underlib/, 917#[test]functions acrosssrc/andtests/, 423 commits by one author between 15 September and 16 November 2026, read at8137545f…. A vault is the nearest directory holding.hmd/(src/vault.rs:112-120);assemblereads every Markdown file under it, resolves[[links]]through thehypermarkdowncrate, and buildsCardvalues and link and relation edges in memory (src/vault.rs:138-226,src/knowledge.rs:14-114). Nothing is persisted from that pass. The two search arms rank that snapshot:lexicalis a 256-dimension hashed bag of words compared by cosine (src/extensions/lexical.rs:21-26,:108), andsemanticopens an SQLite index withSQLITE_OPEN_READ_ONLY(src/extensions/semantic.rs:348) that a separate tool,hmd-semantics build, produced; the binary carries no embedding model, so a query whose vector is not already in the index'squerytable is refused with the command that would add it (src/extensions/semantic.rs:455-475). The write verbs are data-integration ones.insert,update … setanddeleteeach compile to one statement against a configured SQLite, PostgreSQL or Spark table (src/mutation.rs:136-270), transactions wrap those tables (src/transaction.rs:35-48), andtarget/sinkwrite files, channels and queues (src/io.rs:2019-2023,:2072-2078); their invoker is whoever wrote the.hqlprogram, the vault is not an endpoint kind, and all of them are refused while a document is rendered (src/mutation.rs:146-151,src/extensions/io.rs:2208-2212). The README's "AI-native" lines (README.md:40,:49,:615) describe what a program could express, and a warning atREADME.md:617-620marks agents, prompts and runs as values as "Design only", absent from the release and specified in the project's book;src/context.rsis the execution context of an invocation — project, vault and configuration discovery — and no code undersrc/orlib/calls a model, registers a tool or serves a protocol. That is the document-index case. The part that transfers is how retrieval refuses to be silently wrong. EveryHitcarries aRetrievalnaming the query, index, model, model revision, metric and whether the search was approximate (src/search.rs:14-44); a card whose text digest differs from the one stored at index time still ranks and raises aStaleIndexwarning instead of vanishing, a card absent from the index is left out and counted in a warning instead of scored zero (src/extensions/semantic.rs:121-157), andrankdrops zero-score values (src/search.rs:82-105), with a committed test for the stale case (tests/semantics.rs:209). A graph built by retrieving and then expanding labels each nodeMember,Retrieved(score)orExpanded { seed, depth }(src/graph.rs:41-63), so an expanded neighbour is never presented as a match. Searches run at this pin withgit grep:-nEi "mcp|model context protocol" -- src lib tests Cargo.toml(nothing);-nEi "remember|forget|recall|tombstone|supersed|retract" -- src lib(five hits: a REPL:resethelp line, a Kafka null-value comment,std::mem::forget, a type-lattice reset comment and a README table row);-nEiw "agent|agents" -- src lib(six hits, allureq::Agent);-nEi "openai|anthropic|ollama|llm|chat_completion|prompt" -- src lib Cargo.toml(two hits, a config fixture in asemantic.rstest);-nE "target\(.*\.(hmd|md)" -- examples doc/public lib tests(nothing);-nEi "arxiv|bibtex|@article|@misc|doi\.org|CITATION"(no paper; the hits are prose about doc-string citations); control:-nE "OpenFlags"returnssrc/extensions/semantic.rs:25and:348. Screened before reading: no auto-run surface; twobuild.rsfiles run at build time,Cargo.toml,Cargo.lockandtests/packages/hello/Cargo.tomlchanged inside the seven-day cooldown, andAGENTS.mdandCLAUDE.mdwere treated as data; nothing was installed, built or run.- MemoryLake (
memorylake-ai) was examined and has no report: the CLI and the agent harness are open, and storage, extraction, ranking and forgetting all run on the hosted service behind them. Both repositories are MIT, with identicalLICENSEfiles and matching manifests.memorylake-ai/memorylake-cli, read at7c5f8155…(80 commits since 20 July 2026, four authors, 65,785 lines of Rust with 1,338#[test]functions), is a typed HTTP client whose default base ishttps://app.memorylake.ai/openapi/memorylake(crates/core/src/config.rs:14). Its core crate depends onreqwest,serde,ringandtomland on no storage, index or embedding crate (crates/core/Cargo.toml). Search is onePOST …/memories/search(crates/core/src/api/search/memories.rs:12-17,:66-72), fact creation onePOSTto a scope-rootedfactspath (crates/core/src/api/facts/add.rs:36-43), and forgetting onePOST …/facts/{id}/forget(crates/core/src/api/facts/forget.rs:32-46).memorylake-ai/memorylake-harness, read atf184d5dd…(53 commits since 7 August 2026, two authors, 14,972 lines of shell, Python and TypeScript with 195 test cases), holds plugins for Claude Code, Codex, DeepSeek Harness, opencode, QwenPaw, QwenWork and WorkBuddy, and every one of them shells out to that CLI. What the harness keeps under~/.memorylake/harness/(claude-plugin/scripts/lib/common.sh:401-403) is bookkeeping: config, a content hash and remote id per synced file (claude-plugin/scripts/sync-on-write.sh:146-159), a project-id list cached for 600 seconds (common.sh:184-222), per-turn gate markers, and QwenPaw's outbox of turns not yet appended (qwenpaw-plugin/memorylake_backend/sync.py:304-365). No reader turns any of it into recalled content: every recall path ismemorylake search(claude-plugin/bin/ml-recall:89-97,qwenpaw-plugin/memorylake_backend/manager.py:435-452), and extraction is a server stage the CLI calls cook (crates/core/src/api/conversations/cook_status.rs:1-22). None of the organisation's other own repositories holds the server.memorylake-hermesat2d0b8e2c…is a Python client of thev1andv2endpoints (src/memorylake_hermes/client.py:55-65).memorylake-locomo-benchmarkat4ede2a6a…holds ten result files, five charts and a plotting script, without the harness behind its 94.03 % overall F1, which was not checked here. The rest are skills, a model-provider plugin, evaluation scripts, demos and a benchmark agent, and the docs offer hosted and bring-your-own-key modes but no self-hosting, so the bar's "closed-source behind an open wrapper" exclusion applies. Recorded for what a reader can take. Comments in both clients date server behaviour measured against the live API. Batch forget is not atomic — it stops at the first unknown id and names only that one — so the CLI forgets per id and reports each outcome (forget.rs:16-27, loop incrates/cli/src/commands/fact.rs:216-231). Facts are stored verbatim and not deduplicated (add.rs:33-35). Omittingproject_idssearches no documents rather than all of them (memories.rs:21-25). An overwritten library file keeps its id and is never re-indexed, so an update is delete plus re-import (sync-on-write.sh:20-28). The trace contract is a provenance shape worth copying:ADD,UPDATEandFORGETevents, each withsource_kindCOOKorMANUALand, when extracted, the conversation and message ids, and a forgotten fact still answers its trace as expired (crates/core/src/api/facts/trace.rs:12-77). Conflicts carry category-specific strategies the server enforces (crates/core/src/api/facts/conflicts/resolve.rs:22-51), resolve, not just detect as a published contract.ml-recallmakes a failed search print UNAVAILABLE and exit 1 so it cannot read as an empty one, and uses scores for ordering only (claude-plugin/bin/ml-recall:17-21,:42-49). WorkBuddy's recall gate denies the first non-search tool call of a turn exactly once, through an atomicmkdirmarker (workbuddy-plugin/scripts/recall-gate.sh:50-91). Three things sit against it. In the Claude Code plugin auserorfeedbackmemory whose description changes is stored as a new fact and the previousfact_idis overwritten in local state without being forgotten (sync-on-write.sh:181-195); the superseded preference stays in the cloud unless the server's conflict detection catches it, and no harness path calls the conflict API. The Claude Code and Codex hooks fire onWrite|Editonly (claude-plugin/hooks/hooks.json:29) and neither plugin callsfact delete, so a memory deleted locally stays recallable from every other device, as the README says: "memories already uploaded stay until deleted server-side". And recall passes every visible project id (ml-recall:92-94), so scope is the workspace, by design. Searches, each with a positive control:git grep -n -i -E 'sqlite|lancedb|chroma|faiss|embedding|vector|bm25|cosine'over the harness (no match;searchunder the same flags hits); the same terms over bothCargo.tomlfiles;git grep -n -E 'fact (delete|remove|update)|forget|memory_forget'(hitsdsh-plugin,opencode-plugin,qwenpaw-pluginand connector skills, none inclaude-pluginorcodex-plugin);git grep -n -i conflictwithout--on-conflict(prose only);arxiv|bibtex|@article|@misc|doi.org|CITATIONin both trees (no match, so no paper). The organisation was listed withgh api orgs/memorylake-ai/reposand each non-fork tree read throughgit/trees/HEAD?recursive=1; only the CLI and the harness were cloned. Screened before reading, from full clones: inmemorylake-clithe screen found Cursor rules addressed to an agent, twobuild.rsfiles, andCargo.tomlandCargo.lockchanged inside the seven-day cooldown; inmemorylake-harness, a Claude Code marketplace manifest and plugin hook registrations (SessionStart, PreToolUse, PostToolUse, Stop), committed git hooks, two npmpreparescripts, a pytestconftest.py, and apyproject.tomlwith no lockfile; nothing was installed or run. If the engine were published, the first thing to read would be whether aFORGETevent stops a later cook of the same conversation from writing the fact back. arXiv:2611.22299was examined and has no report: it releases no code, and the one thing its method keeps across tasks is the evolved harness, accepted a module at a time through a gate that compares against the seed. Harnesses That Improve Themselves: A Unifying Framework for Self-Improving Agent Harnesses (Deep Shah and Nehal Kathrotia, Google; v1 17 November 2026, cs.AI, no venue or comments line) is mostly a survey. It splits a harness into four editable components — context and state, agent control, action interfaces, verification and recovery — and the improvement loop into four stages: diagnose, propose a patch, validate, deploy. Memory appears twice, and neither time as a mechanism the paper builds. §III lists "Cross-turn environment and memory persistence" as the fourth family of mechanisms optimisers discover, citing other work for the split between working and experiential memory. Table III's third safeguard, Securing Persistent Memory, asks that saved memories and learned rules be treated "as untrusted inputs with tracked origins", which is evidence before belief stated as advice. In memory terms the durable state of the paper's own method is harness code: an accepted module edit is a claim that the patch helps, and it can turn out false. Eq. 1 admits a harnesshwhen its expected runtime tokens per task stay under a budget and the Stage 3 gateG_val(h, h0)passes, defined as runtime execution of the modified code paths and non-regression on a held-out validation split. The baseline ish0, the starting harness, not the incumbent, so as written each accepted edit can lose ground on the one before it while staying above the seed. The experiment is 60 SWE-bench Lite issues (sympy: development 12, validation 8, held-out 20; django: held-out 20 as out-of-distribution) from a 142-line seed, with Gemini 3.8 Flash as the frozen task model and Gemini 4 Carbon as the optimiser, the names as the paper gives them. Table IV, combined held-out: seed 5.0% (2/40), Prompt-Only Reflection 2.5% (1/40), Unconstrained Full-Harness Rewrite 42.5% (17/40) at 451.6k tokens per task, Modular Gated Evolution 40.0% (16/40) at 46.7k. Transferred zero-shot to Gemini 4 Argon, the four read 10.0%, 15.0%, 30.0% and 37.5%. Two readings sit against the abstract's "gated modular evolution outperforms prompt reflection and full-harness rewrites across models and repositories". On the first model the ungated rewrite solves one task more and leads on django, 10 of 20 to 8; the gated arm wins on tokens and on transfer, by three tasks of 40. And the arms had different search budgets: 100 rollouts for the gated arm against 24 for the rewrite and for the reflection (footnote ‡). The reflection arm is the result that bears on memory. ItsRULES.mdopens with a rule forbidding a finish on an empty or untested diff, is appended to and never pruned, and the arm doubled unverified out-of-distribution exits from 15.0% to 30.0%; the gated arm'sverify.pyblocks the same exit in code and records none. A learned text rule that nothing enforces is advice to the model, not a mechanism. The narrated module sequence stands in for an ablation:context_mgr.pycompaction andaction_aci.pywindowed views accepted,control.pyraising the turn limit from 12 to 18 rejected on validation accuracy and the token cap,verify.pyaccepted. Search, 20 November 2026: of 10,639 words of extracted text,githuboccurs once, in the title of reference [1], andgitlab,huggingfaceandzenodonot at all; the paper has no code or data availability statement, and the abstract page links no project page.gh search reposfor the exact title returns four repositories for a different paper sharing the phrase, Self-Harness: Harnesses That Improve Themselves (arXiv:2606.09498, Hangfan Zhang and co-authors, 8 June 2026); a code search for the id finds feed mirrors and reading lists; a GitHub user search finds no account for the second author and 107 for the first author's name, none attributable. With a release, two things would be read first: what Stage 3 keeps of a rejected edit — whether thecontrol.pypatch is recorded, keyed on what it changed, so the optimiser cannot propose it again next round, which is the rejected-value tombstone applied to harness code — and whether the gate's baseline ish0in the code as it is in the equation. Harness² is the reviewed system that keeps each adopted harness for later tasks.- Five published claims about BitterBot Desktop were wrong at
cf9332b1…, the pin they were made at, and are corrected. Three credited the system with more than its code did. The report awardedbitemporalon the relationship interval, and every writer at that pin stampedvalid_fromwith the insert time andvalid_untilwith the supersession time, so the interval was belief time; the mark is withdrawn. It said the retrieval query excluded forgotten and expired chunks, citingmanager-embedding-ops.ts:1119-1120, which is the embedding backfill; the vector and keyword queries inmanager-search.tsread neither lifecycle column. It said a conflict resolver superseded chunks by similarity before storing, andresolveFactConflictandsupersedeChunkhad no caller, so no reachable path wrotevalid_time_end. Two described failures that could not occur. A secondLifecycleStateinmemcube.tswas said to make migration v1's CASE reclassify a writer-markedconsolidatedchunk asgenerated;memcube.tswas imported by nothing, and v1 runs once per database before any writer ofconsolidatedexists. And the skill resolver's NULL exclusion was attributed to a column "added by migration", which SQLite filled with itsDEFAULT 'active'; no inserter wrote NULL. Each claim was a positive one, and each fell to a search for its producer, caller or importer that the reading did not run. - Three published claims about Prime Agent were wrong at
66abc2a6…, the pin they were made at, and are corrected. The report said every durable write went throughapplyRefinementProposal, with no tool that edits an entry directly; the system prompt at that pin advertisedrlm.harness.create_memory,update_memory,delete_memoryand their twins (packages/coding-agent/src/core/prompts/rlm.ts:47), implemented inprime-agent-runtime/src/rlm/harness.py, which writes the same state file with no snapshot or record. It said the harness had no search and that nothing ranked which entries reached the prompt;harness.pydefined a rankedsearch(:861), and the digest was sorted by term overlap with the goal and recent messages (agent-session.ts:9050,refinement.ts:590-610). And it said a local refinement naming a global entry would update it;_applyRefineloaded only the target scope's file before applying (agent-session.ts:9442,:9461), so that edit was refused asentry not found. All three sit outsidesrc/core/refinement/, the directory the reading treated as the whole mechanism; the first was in a sibling Python package, and the third needed the caller rather than the callee. - Four published claims about OmniMemory were wrong at
59874e5b…, the pin they were made at, and are corrected. The report named the no-op returned bycreate_lifecycle_dispatch_handleras the Kafka handler forexpire-memoryandarchive-memory; that factory had no caller outside tests, andcreate_memory_dispatch_engineregistered_create_lifecycle_bridge_handler(src/omnimemory/runtime/dispatch_handlers.py:1005), which read acommandkey the expire command lacks and calledhandle_shutdown()for a literal"expire-memory". It called the retrieval stubs a default set byOMNIMEMORY_USE_STUB_HANDLERS;HandlerMemoryRetrieval.initialize()raisedNotImplementedErrorfor every non-stub configuration (handler_memory_retrieval.py:169), so the stubs were the only path. It counted sixtest_checker_*controls in the gate file; there were five. And it quoted a README sentence about "15 runnable" nodes moving toomnimarketand citeddocs/migrations/MARKET_MIGRATION_BOUNDARY.md; both were removed on 1 September 2026 by545cc0cc…. The first three were wrong at every pin since5dacb73c…; the first rested on a function's name and docstring rather than its callers. - Three published claims about memex were wrong at
80411705…, the pin they were made at, and are corrected. The report said no write path could update a memory and that the tool a model calls could not;memex_importwas one of the eight registered MCP tools (src/memex/mcp_server.py:281), took nodes carrying slugs and wrote them through the update branch ofWikiStore.write(src/memex/infrastructure/import_export.py:63-69), so a model could update a page by slug through the import tool, though not throughmemex_write. It said per-turn injection hooks covered pi, Claude Code, Codex and Copilot; only pi and Claude Code had an injection point, Codex had transcript capture through itsnotifywrapper, and Copilot a CI workflow (marketplace/README.md:21-24). And it said the only test touchingvalid_fromasserted a round trip;test_write_input_validationalso asserted that a malformedvalid_fromis rejected (tests/unit/test_guardrails.py:58). The first rested on the write tool's contract rather than on the whole tool registry. - Three published claims about yantrik-mind were wrong at
97935b1e…, the pin they were made at, and are corrected. The report described a receipt for every read, the operator's included;messages_since(crates/mind-memory/src/lib.rs:4234-4256at that pin) read the transcript with no scope and no receipt, andcompact_conversation(crates/mind-conversation/src/briefing.rs:297-379) folded every member's lines into the rolling summary the primary's prompt carries. It said scope was stored on the belief; it was a side table keyed by proposition text whose writer upserted on every scoped assertion (lib.rs:3252-3265,:5461-5477), so saying the same words moved a belief between scopes, private to shared included. And its stack fields readdelegatedwith a graph arm; the layer opened YantrikDB on one SQLite file beside its own tables, and belief recall scored every node by embedding or keyword with no traversal (lib.rs:2694-2716). The first took the receipts module's header for its callers; the second read the type and not its writer. - Five published claims about Leteo were wrong at
f49917e4…, the pin they were made at, and are corrected. The report withheldnegative_evalon the ground that the exclusion tests were count comparisons rather than assertions that a named memory does not come back;the_full_text_triggers_follow_every_write(src/store/tests/search.rs:104-155) asserted that a search for a replaced title returned nothing while the new title was found and that a hard-deleted memory was not found, anda_project_whose_name_the_tokenizer_splits_still_finds_its_memories(:992-1039) stored one memory in three projects and asserted a narrowed search returned exactly the one in its own project, so the mark was earned. It withheldaudit_logon the localsync_mutationsoutbox alone; the cloud server kept every pushed upsert and delete incloud_mutations, written byinsert_mutations_tx(src/cloud/cloudstore/mod.rs:665-685) and updated or deleted by no production statement, so that mark was earned too. And it said a caller who passes nothing gets no project clause, and that the suite's PostgreSQL tests needed a database the repository did not provide;mem_searchandmem_contextfilled the project from the working directory (src/mcp/tools.rs:328-338), dropping it only underall_projectsor an ambiguous directory, and the CI workflow ran the ignored tests against a PostgreSQL service container. It also counted thirteen ignored tests where the tree carried eleven#[ignore]attributes; the other two hits were doc comments insrc/cloud/auth.rsandsrc/cloud/cloudstore/tests.rs. The first rested on the suite's test names rather than its assertions, the second on the local store rather than the whole tree, and the third on the store API rather than its callers. - Three published claims about HOLO-Invariant were wrong at
2d36396a…, the pin they were made at, and are corrected. The report said there was no store with a read path, no record of mutations and nothing that retrieves;HoloChain(holosim/core.py:23) was an append-only, hash-chained JSONL store whosecorrectandrevalidateappended records naming their target (:309-341,:473-516), read back throughget_effective_state(:343-363) andReplayEngine.search(holosim/replay.py:73), soaudit_logwas earned and is awarded. It said a plain latest-value store was run against the benchmark fixture, and groundednegative_evalon that comparison; both scored conditions were written by hand —benchmarks/examples/passing-condition.jsonand a dict literal attests/test_latest_value_continuity_baseline.py:51-65— and the mark rests instead onholosim/tests/test_core.py:53-72, which asserted at that pin that a corrected value does not come back as current. And it described every correction as bound to an authorized baseline transition candidate;correcttook no authorization, and the bound candidate belongs to the separate baseline-promotion path inverified_claim_correction_transition.py. - Three published claims about LEVH were wrong at
9bdcb25f…, the pin they were made at, and are corrected. The report awardedhuman_reviewon the ground that the producing agent could reach neither held-queue decision, and grounded that onserver/mcp_stdio.pycontaining neitheradmitnorheld. The tools are registered fromserver/tools/, andadmit_memorythere (server/tools/admission.py:38-73) tookforce: bool, which stored a review-verdict candidate without writing a held row (server/core/engine/ingest.py:95). The tool was tieredadmin(server/tools/profiles.py:100) and the stdio server advertised every tier whenLEVH_MCP_PROFILEwas unset (server/mcp_stdio.py:140), so the producer could skip its own review and the mark is withdrawn. Its census of 26,342 lines of Python and 896 test functions described the first-reading pin,6802ac81…, where both figures reproduce; at9bdcb25f…they were 27,113 and 999. And it placed the console's held count in the admission-gate settings panel; that panel carried descriptive text, and the count was on the connector-sync panel (frontend/src/app/settings/_sections/connectors.tsx:142). The first searched the transport file rather than the registry it imports. - Three published claims about mushroomdb were wrong at
4896a895…, the pin they were made at, and are corrected. The report quoted deleting a rule as one that "answers by retracting every edge it owns"; that sentence (crates/core-rules/src/engine.rs:150-154) describes a via-hop rule misreading an empty overlay after a snapshot and wrongly retracting its edges, while rule deletion is documented as "[r]emove the rule and exactly its owned edges" (:3539). The behaviour was right and the quotation was not. It read the diff-apply comment as protecting edges "still supported" by some other source; the comment scopes the diff to one source's outgoing triples so that triples where the node is "a dst for some other source" are left alone (:1043-1045). And its matrix said no model call happens "unless embeddings are enabled", taken from the README; nothing in the tree calls a model,reqwestwas a dev-dependency only, and every integration takes caller-supplied vectors. The first rested on a phrase's words rather than its paragraph, and the third on the README rather than the dependency graph. - Four published claims about NouGenShards were wrong at
73078c05…, the pin they were made at, and are corrected. The report tied the event-time axis to the brain-scan import and said imported traces were stamped at their true era.run_importcalledcapturewithoutoriginal_timestamp(src/nougen_shards/brain_scan/importer.py:84-90), so every scanned trace carried its import time; the producers of a real event time were the tube importer,/sync/push, and the MCP and HTTP capture callers. It said there was no mutation record.history.db'sshard_events(src/nougen_shards/history.py:43-66) took a CREATED row on every capture and a UTILITY_CHANGE row with both scores on everymark_shard(src/nougen_shards/core.py:1225,:2946), and no statement updated or deleted one, soaudit_logwas earned. It did not creditnegative_eval, thoughtests/test_distill.py:103-118asserted that anas_ofbefore the learning date returned nothing, bracketed by a wider bound that returned the shard. And it describedvalid_untilandlast_verifiedas set bymark_verified, which no product path called (src/nougen_shards/core.py:1285-1298). The first rested on a docstring rather than the importer's call, the second on a search that never openedhistory.py. - Seven published claims about Osiris were wrong at
561d5697…, the pin they were made at, and are corrected. The report said there was no isolation boundary and no partition predicate, and withheldnegative_eval; reflections were house-scoped on search, the provenance lens and select (src/orchestrator/compositions.py:313-345,:439,:536at that pin), andtest_reflections_are_house_scoped_in_search(tests/test_reflection_acl.py:37-52) asserted that another house and an anonymous caller got no Reflection hit where a housemate did, sonegative_evalwas earned. It said the evidence classes rank and never withhold; the open-thread wall thatorientrenders moved threads with no self-declared assertion into a counted echo pile (compositions.py:3434). It said assertion rows were never mutated;assert_propertymoved a repeated observation'sobserved_atin place and flipped the prior row'sis_current(src/actions/core.py:267,:295). It described an audit row per mutation and left out the daily heartbeat, on by default, that deleted audit rows older than 90 days (src/workers/arq_worker.py:1203-1262). It gave retrieval as lexical and graph;_fn_searchalso fused a local-embedding route (src/orchestrator/semantics.py). It called the 112-line evidence module eighty lines long. And itstrust_staterecord citedsrc/mcp_server.py:3062,:4204andsrc/cli.py:4852, none of which held a status predicate; the thread read was atsrc/mcp_server.py:3091. The first rested on the shared graph rather than on the read lenses, and the second and third on module docstrings rather than their code. - Six published claims about Chump were wrong at
631fcaa7…, the pin they were made at, and are corrected. The report described the ablated memory as the FTS fact table;CHUMP_BYPASS_SPAWN_LESSONSemptiesload_spawn_lessons, which readschump_improvement_targets(src/reflection_db.rs:503-627), and the fact table is not touched by it. It described retrieval as FTS5 and a graph;recall_for_context(src/memory_tool.rs:525-755) also scores by embedding cosine and fuses the three arms. It presented EVAL-056's null as credible under the project's controls; the write-up attributes its first run's failures to API connectivity under an exit-code scorer that rule 6 ofdocs/process/RESEARCH_INTEGRITY.mdprohibits, and the re-score's A/A delta was +0.200 against the ±0.03 rule 5 requires before citing. It called the 5% mechanism threshold preregistered;docs/eval/preregistered/RESEARCH-022.md:20-27states 10%. It said four public write-ups survived among 83 documents; the directory held 78 markdown files and 39 were public, and the publicREMOVAL-003-design.mdanswered its open question aboutbelief_state. And it withheldnegative_eval, thoughscope_hint_filters_unrelated_lessons_in_assembled_block(src/reflection_db.rs:3283-3340) asserted that an off-domain lesson stays out of the assembled block while two others from the same store appear. The first and last came from reading one store as the whole memory. - Five published claims about Project Athena were wrong at
f82e8f69…, the pin they were made at, and are corrected. The report awardedaudit_logtocore/flight_recorder.pyand the auditors;record_actionhad no caller outside the module's own__main__self-test, the auditors printed their reports, andaudit_runner.pyoverwroteaudit_state.jsonandaudit_score.json, so no record of memory mutations existed. It said theepistemic_status:frontmatter key appeared nowhere but in its own definition;examples/protocols/reasoning/RSN-504-problem-framing.mdandexamples/protocols/decision/DEC-500-gto-problem-solver.mdcarried it at line 5. It said no benchmark result was committed;docs/BENCHMARKS.md:52reported MRR@5 0.769 and Hit@5 0.892 on a 65-query gold set. It counted thirteen labelled documents wheregit grepfinds fourteen, and gave roughly 60,000 lines of Python where the tree held 72,502. The first rested on a module's docstring rather than its callers, and the third on the README rather than the documents it linked. - Three claims about Daimon
on the capabilities and comparison pages were wrong at
fb1ccd03…, the pin its report was read at, and are corrected. Both pages said Daimon suppresses a forgotten value on the read path rather than refusing the write;write_checkpointpassed the forgotten content keys toadmit_checkpointbefore a byte landed (plugin/daimon_briefing/store.py:1374). The capabilities page said the key is a hash of the exact text; it is a canonical form, NFKC-folded, casefolded, whitespace-collapsed and confusables-translated. And both said no test re-asserts a forgotten value;plugin/tests/test_forget_reassertion_e2e.pyforgets a value, re-extracts the same sentence and asserts it stays gone beside a positive control. The report was right on all three; the cross-page prose predated the readings that established them. - Twenty-seven line anchors in the ripwire report were wrong at
e54b688e…, the pin they were published against, and are corrected. They were resolved at the previous pin,f8e6087c…, and the re-pin moved the frontmatter without moving them; between the two,src/quality.hgrew from 7,142 lines to 7,365.findSuppressingAck, the ratchet the report is built around, sat atsrc/quality.h:6021-6025, not 5798-5802, and the zero-magnitude guard at:4815-4817, not 4592-4594. Every anchor was re-resolved by matching its text at the old pin against the new one; the rest ofquality.h,cli.h,mcpverbs.h,verbs_quality.h,serialize.handmain.cppmoved by offsets, and the evidence record's test anchors were unchanged. The same summary also kept the count of two marks afterhuman_reviewwas withdrawn on 2026-09-19. - Four published claims about Tideline were wrong at
76490fe2…, the pin they were made at, and are corrected. The report said the five fixtures contained four assertions, all a path check, and that breaking every cooldown rule would leave them exiting zero; they recorded 77 named checks through acheck()helper and exited 1 on any failure (tests/fixture_phase13_cooldown.py:236), the fourassertstatements being setup guards. It said narratives and snapshots were kept outside the context window and not injected; the provider's session-start block injected the latest snapshot and up to three recent high-weight narratives (plugins/tideline_provider.py:298-320), and per-turn prefetch injected more. It describedcontextandthreadsas one live row per key; both were append tables with no key constraint (server.py:110,:119). And it said there was no append-only record and no status column;amendmentswas an append-only revision layer over narratives whose semantic fields were never updated (server.py:182-187), andthreadscarried astatuscolumn. No mark moved on these; the first rested on countingassertrather than reading what the scripts did with their results, and the last two on reading the schema's history tables without the rest of it. - Five published claims about a-memory were wrong at
32edbb91…, the pin they were made at, and are corrected. The report withheldnegative_eval, thoughtests/test_lifecycle/test_c8_tails.py:73-90and:133-149asserted that private and hidden facts were absent fromsearchin a store holding a matching pinned or visible fact. It saidfeatures/inject.py:222filtered visibility in Python;CoreEntry(core/memory.py:34-44) had novisibilityfield, so the check always passed. The unfiltered builders were six — bothinject.pyblocks,recall.py:62,smart_context.py:51,ops.py:93andops.py:240, theCONTEXT.mdwriter — andcore/__init__.py:106was an uncalled helper. It said the key lookup carried the predicate;:450was the superseded-pair query insidesearch, andget(:258-263) had none. It said the agent could hide a key and not unhide it; the MCP tool forwarded an explicitvisibility(mcp_server/tools/memory.py:78), which overrode the stored flag. And it said every delete appended a ledger row; the 15-minute forgetting loop's archive deletes (lifecycle/forgetting.py:224) anddelete_older_thanwrotecore_memorywith none. Separately, the recall cache key omitted the layer (core/__init__.py:81), and the agent-layer multi-source retriever answered with user-layer rows untild8ec04fe…. Most rested on the comment or docstring beside the code rather than on the object or caller it described. - Five published claims about Muninn were wrong at
b95d5044…, the pin they were made at, and are corrected. The report said nothing in the tree could remove a memory;cascadeDeleteThread(src/db/threads.ts:349-363) deleted every memory of a deleted topic, reached from/deltopicon Telegram and Slack and the threadDELETEroutes, and had since March 2026. It said asharedrow was retrievable by every user of the bot;sharedMemoryReadsAllowed(src/auth/policy.ts:114) narrowed both search functions to the reader's own rows on an authenticating instance. It said the dashboard only displayed memories;POST /api/wiki/remember(src/dashboard/routes/wiki-routes.ts:2771) saved them. Thenegative_evalrecord said its cited test could not pass on an empty result;searchMemories filters by userId for personal scope(src/db/memories.test.ts:71) asserts withevery, which an empty array satisfies, whileacceptance 11(:120-171) held the paired cases on one seed. And it said the review gate's actor was whoever reached the port; underMUNINN_AUTH=entrathe default-deny zones insrc/auth/zones.tsrequired an admin role. The first three rested on searches scoped tosrc/db/memories.ts, and the cascade lives in the threads module. - Five published claims about Cortana were wrong at
9609d2ab…, the pin they were made at, and are corrected. The report awardedbitemporalon separateobserved_at,valid_fromandvalid_untilcolumns gated by "a moment the query is given". The only writer boundvalid_from,observed_atandcreated_atto onenow(crates/core/src/store.rs:1893),valid_untilwas documented as an "expiry for short-lived working context" (crates/core/src/memory.rs:267), and the search bound the wall clock (store.rs:2067); the mark is withdrawn. It did not creditnegative_eval, thoughnative_memory_is_idempotent_acl_scoped_and_redactable(store.rs:8681) asserted an empty recall for a second principal beside a one-row recall for the first, andtests/evaluation.rsran three absence cases throughcortana eval --memory. It said a rejected candidate'sdedupe_keywas not consulted, and the candidate writer refused a re-offer under the same key from the same creator (store.rs:2206-2228). It said approval took an approving principal; it was anexplicit_approvalboolean on the agent's own MCP tool (crates/mcp/src/mcp.rs:222). And its architecture table namedsrc/api.rsand four other paths that had moved undercrates/. The first rested on column names rather than on the insert's bindings, and the third on a field's storage rather than its reader. - Four published claims about Animus were wrong at
6d0e14fb…, the pin they were made at, and are corrected. The report said search scores were normalised so that a lower BM25 became a higher relevance.ScoreFromBm25clamped every negativebm25()value to zero, so every SQLite match scored 1.0, andScoreFromTsRankranked the best PostgreSQL match lowest (src/kernel/memory/MemorySearch.cpp:26-35). It said ordinary conversation could not mutate episodic memory.ToolExecutionService::Executeresolved any registered handler by name (src/kernel/chain/ToolExecutionService.cpp:169), andConsolidationToolapplied no action whitelist to a session key carrying none of its three prefixes (src/kernel/tools/ConsolidationTool.cpp:113-115). Itsaudit_logrecord placed mutation producers on every reachable ontology write.UpdateEntity,DeleteEntityandDeletePropertyhad no caller, andSyncPropertyStatesFromObservations, called at every boot (src/kernel/AgentKernel.cpp:344), rewrote property states with no log row (src/kernel/ontology/OntologyStore.cpp:656-705). And the census in its summary, v0.3.10 with 405 commits and sixteen test binaries over 8,364 lines, described the first pin; this one was v0.4.0 plus six commits, with 526 commits and 22 CTest registrations over 10,630 lines. The first rested on the formula rather than the sign of its input, and the second on the tool schema a session is offered rather than on the dispatcher. - Five published claims about pi-memory were wrong at
0f09c6b4…, the pin they were made at, and are corrected. The report did not creditnegative_eval, saying nothing in the tree asserted a record stays out of a retrieval;tests/engine.test.ts:35-46asserted a superseded fact returned nothing at the defaultasOf, andtests/isolation.test.ts:16-38and:51-69asserted one project's facts stayed out of another's search. It said retrieval returned contradicted facts labelled rather than withholding them; a terminal resolution closedinvalid_atat the event time (src/storage/projection.ts:385-398),factIsValidAtthen dropped the fact (src/retrieval/hybrid.ts:167-169), and the prompt hook selected only supported and needs_review facts. It withheldscope_enforcedbecausescope_idwas a parameter rather than a property of the handle; the agent-reachable search injected the engine's own scope (src/engine.ts:400-402), dropped documents of any other scope, and gave the model no scope argument. It quoted the capture gate's header as "Not a copy of prjct fail-open excess.", a line commit77e5bd3e…removed before the pin. And its census of 15,920 lines and 41 test files reproduces under no method tried;srcheld 12,755 lines andtests48*.test.tsfiles. The first three rested on the storage query and the field's signature rather than on the read path and the test suite. - Six published claims about yacmemo were wrong at
4a12be94…, the pin they were made at, and are corrected. Thehuman_reviewrecord said a person's dismissal silenced a collision's warning on every later search._index_notedeleted every collision row involving the note, dismissed ones included, and re-detected the pair asopenunder a new id on the next write or edit of either note, andreindexcleared them all (yacmemo/store.py:1271,:1199); the mark holds, because no agent path could set the status. It said the memory subsystem contained no generative model; the curator posted to a configuredchat/completionsendpoint (yacmemo/curator.py:61). It said nothing in the system approved a curator proposal;POST /api/{user}/proposal/actionrecorded a person's adopt or dismiss per item (yacmemo/webui/app.py:302,yacmemo/store.py:1117). Its summary and verdict said console saves and deletes left nocall_logrow and no before-image;yacmemo/webui/app.py:179-192logged both with abefore_hash, as the report's own section 9 said. It said the store locked every public method;_MUTATINGnamed seven, leavingsaveanddelete_note, the console's write paths, unlocked (yacmemo/store.py:96). And section 4 and the file index cited an earlier pin's lines, such asstore.py:151-198for a guard at:182-222. The first rested on the reader of the status rather than on what the re-index did to the row. - Five published claims about Loreweave were wrong at
8fe4c5a2…, the pin they were made at, and are corrected. The report said there were no committed must-not-retrieve cases.tests/facts.test.ts:166-174asserted an invalidated fact absent from the default query and:332-343a late-recorded fact absent fromasKnownAt, each beside anasOfcontrol on the same store, andtests/note-gate.test.ts:164and:269-274asserted out-of-vault content absent from search, sonegative_evalwas earned. It said a fact's valid time came from frontmatterdate,event_date,createdorvalid_from, citingsrc/temporal/dates.ts:205-206; that function dates blocks for search windows (src/store/db.ts:445-447), and facts readvalid_from,dateandcreatedonly (src/facts/extract.ts:177). It saidsource_typewas used in a single timeline heuristic;src/facts/journal.ts:369and:404also closed every slot holding astatedrow to extraction. It said every table was derivable from the vault; the access log and the per-block usage history were not. And it said backdating was handled in the as-known-at clause. That held for a backdated assertion, while every close rewrote the onevalid_untilcolumn in place (src/facts/journal.ts:181-217,src/facts/model.ts:263-268), soasOfcombined with an earlierasKnownAtanswered from a close learned afterwards. - Four published claims about CogZ were wrong at
6d664c86…, the pin they were made at, and are corrected. The report saidtransition_statushad one caller and that a hand-edited frontmatter status reached an upsert that never consulted the lattice, so a file edit could move an entity from active to pruned or out of the terminal state.sync_parsed_filesent every update of an existing row throughupdate_entity_preserving_status, which returnedIllegalTransition(src/files/sync_ops.rs:59-76), andsrc/consolidate/merge.rs:280andsrc/index/stale_flagging.rs:159called the lattice too; all three were present at3b8486d8…, the first reading's commit. It awardedaudit_logto an append-only event table whiledelete_entity_cascaderewrote mutation rows withUPDATE events SET entity_id = NULL(src/storage/crud_batch.rs:158,:203), and edit payloads carried no id, so a rewritten row no longer said which entity had changed; the mark is withdrawn. Itstrust_staterecord citedcrud_batch.rs:33and:80as a batch fetch filtering on status; both were batch stale-markingUPDATEs. And the census — version 0.1.5, 31,088 lines in 145 files, thirteen MCP tools — described the first reading's commit; this one was 0.2.1, with 33,082 lines in 152 files and seventeen tools, and the first History entry named this pin for a reading made at the other. The first rested on the one caller ofupdate_statusrather than on every caller oftransition_status, and the last on a re-pin that moved the frontmatter without recounting. - Six published claims about kannaka-memory were wrong at
2b35b46d…, the pin they were made at, and are corrected. The report said the!m.hallucinated && m.amplitude > 0.01filters atsrc/consolidation.rs:1673and:1812keep a flagged memory out of belief formation. They chose which memories a new dream is compared against in a quality gate, andbelief_core_snapshot(src/medium/chiral.rs:1565) read every right-hemisphere wavefront, dreams included;trust_stateheld on remember's duplicate match, which excluded flagged rows (src/openclaw.rs:645). It said there was no validity interval.effective_at,observed_atandexpires_atsat onHyperMemory(src/memory.rs:181-187), written bykannaka remember --effective/--observed/--expires(src/bin/kannaka.rs:1870-1879) and read byswarm brief(:4296), sobitemporalwas earned. It said merge records leave behind who a consolidation merged with; thecollective::mergefunctions that write them had no caller outside tests, andsrc/hrm_store.rs:655and:690rebuilt every memory with an empty list. It said a consumer of recall output could check the flag;RecallResultcarried no such field. It listed an MCP surface, deleted on 22 March 2026 in19cbd73b…. And it gave version 0.16.5 whereCargo.tomlread 0.16.6. Two counts were also off: the gate's tests assert the flag five times rather than four, and one of threeevals/directories has no Dockerfile, instruction or probes. The first rested on a filter's predicate rather than on what the filtered list was for, and the third on a field's declaration rather than its writers. - Six published claims about LongtermMemory-MCP were wrong
at
5955730d…, the pin they were made at, and are corrected. The report said decay and reinforcement were persisted only when the change crossed half a point, so that a dozen reads did not produce a dozen writes. The threshold guarded only theimportancecolumn:applyDecayAndReinforcementwrote the accumulator intometadata, wrotelast_accessedand calledpersist()on every unprotected access (src/memory-store.ts:438-456), andsearchran it for every candidate above the similarity threshold (:209-212). It praised the versioned schema as a migration path for a file that would outlive releases;initializeSchemadropped thememoriestable on a missing or mismatched version (:67-95), and the migration test asserted the wipe. It called the backup manual;savetriggered one automatically (:162-163,src/backup.ts:77-84). It said importance weighted nothing at retrieval;searchByTypeandsearchByTagsordered by it (:298,:320). It counted 109 tests; there were 101 vitest cases and 29 benchmarks. And it withheldnegative_eval, thoughtests/integration/mcp-server.test.ts:222-240asserted that a populated preference stays out of afactlisting beside a positive control. The first two rested on the threshold function and the version table rather than on their callers. - Four published claims about Verimem were wrong at
068baf45…, the pin they were made at, and are corrected. The report withheldbitemporal, sayingsearch_factstook a singleas_ofover record time. The clause wasCOALESCE(asserted_at, created_at) <= ?(verimem/semantic.py:5444), the schema documentedasserted_atas the event time distinct fromcreated_at(:764-773), andrecall_as_of(verimem/temporal_context.py:254) composed it with supersession, so the mark was earned. It said no committed must-not-retrieve case existed;tests/test_recall_include_orphaned_coldpath.py:28-41stored a visible and a quarantined fact and asserted only the visible one came back, then thatinclude_orphaned=Truereturned the other. It said the scope helpers were imported byverimem/cli.py; the MCP fact tools imported them too (verimem/mcp_server.py:13011,:14446), with the scope taken from optional tool arguments. And its anchors for recall and the restore (verimem/semantic.py:4016-4026,:5695-5701) and its 130,388-line count came from the first reading's commit; at this pin those functions sat at:4040and:5719-5725, and the package held 126,812 lines. The first rested on the parameter name rather than the clause, the second on a search that stopped at the negative-bundle suites. - Five published claims about chitta-field were wrong at
c5e0ff0e…, the pin they were published at, and are corrected. The report awardedaudit_logon the op log.compact_waldeleted every segment a committed snapshot covered (src/store/maintenance.rs:1397-1430,src/store.rs:434-494), exported to the daemon ascf_compact_walandcf_maybe_compact_wal(src/ffi.rs:2903,:2922), and no path read past ops except replay; the mark is withdrawn. It did not creditnegative_eval, thoughtest_recall_excludes_invalidated_statuses(src/store/tests.rs:1596) asserted three excluded statuses absent from semantic recall beside an active memory that had to return. Its diagram had the contradiction detector setContradicted. The detector returned candidates to the FFI caller, resolution returned ops for that caller to apply, the only setter wascf_set_memory_status(src/ffi.rs:2852), and the reconcile pass the report credited used a six-word prefix heuristic (src/organ/reconciler.rs:76). It gave the scope as a project cleared by its own op;ClearProjectremoved code-file and symbol entries (src/field.rs:1719), and memories were scoped by an optional realm. And its census — 57,134 lines, 287 test functions,src/store.rsat 12,206 lines — describedf3176e58…; at the pinsrc/store.rswas 3,728 lines. - Six published claims about AideMemo were wrong at
58b803cc…, the pin they were made at, and are corrected. The report read the server profile and described it as the whole system, so the default local store went unread. It said the only times were creation, update and a revision and did not describeFactRecord.observed_at(crates/aidememo-core/src/types.rs:463-468), an observation time read bysinceanduntil(crates/aidememo-core/src/search.rs:171-189). It said nothing marked a stored fact superseded and did not describesuperseded_at, withheld by default on search, list, query and every context assembler (crates/aidememo-cli/src/cmd/mcp_tools.rs:354-361). It did not creditnegative_eval, thoughfact_list_defaults_current_only_trueandscoped_read_tools_do_not_expose_neighbouring_source_content(crates/aidememo-cli/src/cmd/mcp_tools.rs:6190-6229,:5179-5300) asserted superseded and foreign-namespace facts absent beside positive controls. It did not describe the Hermes pending queue for auto-captured facts, which no retrieval reads and no agent tool drains (crates/aidememo-cli/src/cmd/pending/mod.rs:280-297). And it placed the embedded local store behind the storage-neutral command trait and gave the server's credential-bound scope as the system's scoping; the CLI, stdio MCP and bindings useaidememo-core, which is not behind the trait and takessource_idfrom the call (crates/aidememo-cli/src/cmd/mcp_tools.rs:791-810). - Four published claims about RE-call were wrong at
1157360f…, the pin they were made at, and are corrected. The report counted 162 dated preregistrations running from 15 August to 15 September 2026; that was the count at the first-reading pin, and at this onedocs/preregistrations/held 188, the last dated 16 September. Its tests section gave 494 test files, the first pin's figure, where this pin had 518 entries undertests/. The inspected-repositories entry named the licence Apache-2.0;LICENSEat this pin was the PolyForm Noncommercial License 1.0.0, introduced by3e1adc25…, as the report's own summary said. And thescope_enforcedrecord said no query path reached the rows without the tenant GUC set. The write-time hook queriedrecall_chunks_v1with an explicit predicate and no GUC (recall_hooks/write_time.py:222-229), andrecall/pool.py:38-52stated that a superuser orBYPASSRLSrole ignores the policy, which the MCP server allowed for single-tenant serving with a warning. The mark holds, because every statement carries the tenant predicate. - Five published claims about Slowave were wrong at
00b5a1d7…, the pin they were made at, and are corrected. The report said every timestamp was a record time;slowave_remembertook an optionaloccurred_at, an RFC 3339 source-event time kept apart from the write clock (slowave/mcp/tools.py:1309), and episode ranking read it against an anchor estimated from the query (slowave/latent/retrieval.py:338).bitemporalstays withheld, on the absence of a validity interval rather than of a second clock. It said the derived layers could always be discarded and rebuilt fromraw_events;remember()wrote its schema directly (slowave/core/engine.py:713), and consolidation, the rebuild's only schema writer, skipped any prototype whose episodes were all remember events (slowave/core/consolidation.py:180), so a remembered schema was not re-formed. And itsnegative_evalrecord said three cases paired a required with a forbidden content; seven did (tests/acceptance/test_memory_lifecycle.py:119,:225,:348,:748,:782,:806,:853). The first two rested on the column names and the rebuild's own description rather than on the write path's arguments and the consolidation loop. Two more were wrong at the same pin. The report said a schema matched by its primary prototype was reactivated whatever its status;reinforce_schemaraised salience and confidence and left the status alone (slowave/symbolic/schema_store.py:656-663), so a stale schema stayed stale. And it called the client-setup module install-time execution; the build backend had no install hook, and only the in-tree Homebrew formula ranslowave setupfrompost_install. The first followed a code comment rather than the update it described. - Five published claims about memtomem were wrong at
95baf628…, the pin they were made at, and are corrected. The report said the scope fragment was composed into every chunk query.mem_consolidatebuilt its groups fromget_source_files_with_countsandlist_chunks_by_source, which took no boundary, and returned previews of every project's chunks (packages/memtomem/src/memtomem/server/tools/consolidation.py:48,:66,:75);scope_enforcedholds on the retrieval paths. It said the registry test meant a future read surface could not skip the gate. The test guarded the vocabulary gate rather than the boundary, and its docstring said a green run did not mean no unvalidated read surface could exist (packages/memtomem/tests/test_scope_vocabulary_architectural_guard.py:50-62). It withheldhuman_reviewon the consent flag alone and said correction lived only in files. A candidate queue with pending, approved and rejected states sat in the tree, cleared bymem_candidate_reviewon the agent's tool surface withreviewerdefaulting to"user"(packages/memtomem/src/memtomem/server/tools/formation.py:221-224). Itsbitemporalrecord citedtest_search_scope_filter.py, which held no validity case;test_temporal_validity.pydid. And it dated the first commit 28 March 2026; the first commit is dated 10 April 2026. The second followed the test's name rather than its docstring. - Six published claims about OpenMasq were wrong at
a8d9a9ee…, the pin they were made at, and are corrected. The report said memory extraction sent not one new byte of real data, repeating the comment atpackages/ui/src/memory/extract.ts:26-30.runMemoryExtractionread every user turn past the watermark whether or not its redaction had completed (packages/ui/src/state/memory/memoryExtractionRun.ts:103-106) and replayed it throughapplyVaultalone (packages/ui/src/memory/extract.ts:185-186), so a turn refused before its values reached the vault went to the extractor as typed. It said an organisation could close the feature remotely; closing access hid the screen while injection, search and extraction continued (packages/ui/src/state/billing/featureAccess.ts:21-32). It called the store one per install; settings, and the memory with them, were keyed per signed-in account (packages/ui/src/state/storePersistence.ts:40-41). It said merging two devices' card lists was left toautoCleanMemory; the sync merged per card id three ways, propagated deletion as an id-keyed tombstone, and carried neitherfactsLognorreviewedAt(packages/sync/src/userdata.ts:77-86,:166-243). Itsnegative_evalrecord said a greeting injected neither card's text; the case asserted only the first card's fact absent (packages/ui/src/evals/memoryFlow.test.ts:64-72). And its census of 197 commits and version 0.9.0 was the first reading's; this pin held 268 commits and version 0.11.1. The first rested on a code comment rather than the replay it described. - Four published claims about OmniClaude's injection path were wrong
at
6f062cd5…, the pin they were made at, and are corrected. The report said provisional patterns are admitted at half score rather than excluded;include_provisionaldefaults toFalse(src/omniclaude/hooks/injection_limits.py:455) and the selector drops them at:774. It presented a composite score with an evidence multiplier as the ranking; the mapper setsusage_count=0on every cache and API record (src/omniclaude/hooks/handler_context_injection.py:733), so every score is zero, and the single production call (:556) passes no evidence resolver, so the order is confidence, then pattern id. It said abudget.cap.hitevent fires when the token cap bites; that call passes norun_id, which the emit condition requires (injection_limits.py:939). And it said the model cannot save or search memory; the internal plugin'srecallanddecision_storeskills, present since March and April 2026, tell it to do both against stores in other services. Smaller errors at the same pin: thenegative_evalevidence said one helper made a single case run the parse, the filter and the caps together, which no case does; the injection record was described as lost when the API is unreachable, while it goes to a local emit daemon; the file index treated the inventory'sdisabled_hooksas the count of dark hooks, while the two injector scripts were dark and declared in neither half; and the inspected-list line called the framework dependencies private whenomnibase-core0.47 releases were on PyPI from 29 August 2026. Each rested on a docstring, a default left unread, or a field's declaration rather than its writer. - Two published claims about memhtml were wrong at
a219190e…, the pin they were made at, and are corrected. The report awardedhuman_reviewon the ground that a sleep run's memories stayed invisible to search until a person merged.runrestoredHEADonly after a failed phase (packages/sleep/src/run.ts:249), every write door committed toHEADand re-indexed it (apps/cli/src/operations.ts:267-271,:341), and the runbook's cron re-indexed every ten minutes (RUNBOOK.md:93), so unmerged curation reached the agent's searches and its writes landed on the sleep branch; the mark is withdrawn. It also said the merge gate meant a run that degraded retrieval could not land; the gate built its own fixture corpus in an in-memory database (packages/eval/src/harness.ts:34-37,:146) and did not read the branch. - Five published claims about GitMem were wrong at
d47a625f…, the pin they were made at, and are corrected. The report said the scar-search fallback had answered PGRST202 "on every call, on every deployment, since it was written" and that the deployed functions werematch_<table>andmatch_<table>_weighted.schema/setup.sql:322definedgitmem_scar_searchand no file in the tree defined amatch_function, so the rename the report credited as the fix (06c26eb8…, 8 August 2026) is what made the fallback fail on every store built fromsetup.sql, and the committed test asserted the regressed name. It said no read path applied a stored project key; threads went throughbuildScopedThreadQueryinsrc/services/thread-scope.ts, and session history, the session-start decision panel andlog(src/tools/log.ts:125) filtered by project. It described thePreToolUsegate as holding until every surfaced scar was answered;hooks/scripts/recall-check.sh:150blocked only while the session's confirmation count was zero. It did not creditnegative_eval, thoughtests/unit/services/local-file-storage.test.ts:206-221asserted that an archived learning stays out of a populated active-only list beside two positive controls. And it said the schema recorded repeat mistakes and thatexecution_successfulclosed the loop to the outcome;repeat_mistakehad no writer in the tree, andexecution_successfulwas derived from the agent's own confirmation or reflection. The first rested on a code comment over the schema file in the same tree, and the last on the column's declaration rather than its writers. - Nine published claims about Hestia were wrong at
51ebf7b0…, the pin they were made at, and are corrected. The report said recalled memory reached the prompt with no data fence;brain/hestia.py:230wrapped it withcontext_budget.evidence, a JSON object labelledtrust: data_onlyand clipped at 3,000 bytes, beside a system-prompt rule that memory is data (brain/prompt.py:37). It saidconfidencewas shown in the context block and broke ties;context_blockrendered id, source and last_seen (brain/memory_store.py:130-131) and the sort key was(score, pinned)(:119). It counted ten tools and a 48-word stop list; the registry held eleven (brain/tools/__init__.py:24-36) and the list 34 words (brain/memory_store.py:90). It said no committed result reported a score;benchmarks/RESULTS.mdandbenchmarks/heldout_2026-07-06*.txtdid, all for tool calling and none for memory. It said no deployment variable could bypass the review gate;HESTIA_INBOX_DIRset to the memory directory put proposals where_all()globbed (brain/config.py:38,brain/memory_store.py:49). The verdict, the family paragraph and the homepage card said the autowrite bypass existed and defaulted off; no code readHESTIA_NOTETAKER_AUTOWRITE, and only a test set it. A pattern page saidreview_notes.pycould edit a proposal; it listed, promoted and discarded (brain/review_notes.py:98-108). And the body anchored the inbox route atbrain/hestia.py:346, where it sat at:773. - Three published claims about Theurian were wrong at
6c64a6ba…, the pin they were made at, and are corrected. The report said every MCP tool was read-only and thatsystem.capabilitiesreportedwriteTools: false. At that pin it reportedTrue(packages/theurian-core/src/theurian/mcp/tools.py:3324) beside three registered proposal tools,knowledge.proposeChangefirst (:3335), whose drafts carriedstatus: approved(packages/theurian-core/src/theurian/application/proposal_service.py:4365). TheFalsereading was true of the first pin,e5f3abe1…. It said each revision recorded itssource_commit; the engine's only construction of a revision passed none (packages/theurian-core/src/theurian/application/migration_engine.py:612-636), so the column was always null. And its census of 313,168 lines and 4,209 test functions at version 0.0.0 was measured at the first pin and read the workspace root's placeholder version, while the package was 0.4.0. The first was a reading of the first pin carried through a re-pin without re-reading the tool registry; the second rested on the column's declaration rather than its writers. - Four published claims about Demarkus were wrong at
dd22c38a…, the pin they were made at, and are corrected. The report awardedaudit_logon a history it said kept every version. Any write carrying the metadata keyretentiondeleted the oldest versions (protocol/store/store.go:1405-1406), the agent'smark_publishoffered it (client/cmd/demarkus-mcp/main.go:459), andVerifyChaincompared links from its second element (protocol/store/store.go:1679), so a pruned history verified, astestRetentionasserted (server/internal/storetest/conformance.go:536-538). It said a document had no status; an archive state withheld it from FETCH and LOOKUP (server/internal/handler/handler.go:329-332,server/internal/filestore/filestore.go:111-112), sotrust_statewas earned. It did not creditnegative_eval, thoughTestHandleLookupReadAuthFiltering(server/internal/handler/handler_lookup_test.go:180) kept a protected document out of a populated LOOKUP beside a public control. And it said the server did not rank; LOOKUP ordered by matched terms and importance (server/internal/catalog/catalog.go:303-312). That last rested on the README rather than the handler. - Four published claims about RainBox were wrong at
e09dd4f6…, the pin they were made at, and are corrected. It awardedscope_enforcedon the main retrieval's filter, but the uuid arm of the samememory_querytool (source/agents/assistant.py:1268-1305) applied no room or agent predicate, andmemory_forgetby text (:2277-2287) matched claims in every room and listed their uuids on an ambiguous match, so the assistant could read another room's claim in two calls on its own surface. It did not creditnegative_eval, thoughtest_hard_filters_exclude_secret_expired_out_of_scope(source/memory/test_hybrid_retrieval.py:77-94, byte-identical at both pins) asserted that a secret, an expired and another room's claim were absent from a populated store beside a public claim that had to be returned. It described chat commands —remember that,forget,correct that OLD -> NEW,what do you remember?— as a live write path and as the producer of theexplicit_human_commandactor;parse_memory_commandandhandle_memory_command(source/memory/ops.py:51,:326) had no caller outside tests after1bdbdf48…retired the query agents on 1 September 2026, and it presented five actors as a structural trust model when two had a producer. And itstrust_staterecord cited the write-time conflict query (source/db/memory.py:644) as the read path; retrieval's status filter ishard_filtered_claims(source/memory/retrieval.py:217), and the mark holds on it. The scope mark rested on the query arm alone, the commands on their handlers and direct tests rather than a caller. - Eight published claims about AgentWorkingMemory were
wrong at
6b04ba62…, the pin they were made at, and are corrected. The report awardedscope_enforcedon the agent-scoped default;memory_recalltook an optionalworkspaceargument from the model (src/mcp.ts:419,:435) that widened recall to every agent registered under the name supplied, with no membership check (src/engine/activation.ts:208-209,src/storage/sqlite.ts:673-677), so the mark is withdrawn. It described a third retraction regime, a cross-domain bridge whose weight is reduced while the far side is spared; that regime is a docstring, and the propagation applies one multiplier computed at the source and writes no edge weight (src/engine/retraction.ts:33-34,:319-363). It saidretracted_bywas a caller-supplied string the engine left null; the engine overwrites it with the correction engram's id (:104), and no tool or route accepts it. It said composing the predicates into SQL made aLIMITmean the same thing to every caller; on the default SQLite backend both BM25 queries take their FTS window beforeagent_idandretractedapply (src/storage/sqlite.ts:648-658,:856-866). It quoted'excludes retracted by default in search'as testing the default; the case passesretracted: falseexplicitly (tests/integration/memory-lifecycle.test.ts:352). It countedstaging_eventsamong the event tables;logStagingEvent, its only writer, had no caller. It said there was no LoCoMo or LongMemEval harness and no committed result; both harnesses were undertests/, anddocs/benchmarks.mdcarried results. And it gave 16 MCP tools and 49 test files where the tree registered 19 tools and held 68 test files. - Five published claims about Temvera were wrong at
75243a3d…, the pin they were made at, and are corrected. The report awardedtrust_stateon the authority enum, which is fixed at ingest and read only by action gates whose callers are the bypass probes and the threat fixture (src/temvera/governance.py:69-97,src/temvera/security.py:26-41). It awardedscope_enforcedon a tenant that exists only on an unpersisted evidence envelope; no store, query, retriever or packet takes one, and the record itself said the check governed authorization rather than retrieval. It said ingest was gated before it landed by six checks; those were the action gate's, and no append called either policy method (src/temvera/store.py:24-35). It said every query took both instants; the hybrid retriever applied valid time only on request and the packet builder took neither (src/temvera/hybrid.py:47-52,src/temvera/retrieval.py:28-36). And it described the plain ledger's redaction as leaving the record intact;redact_payloadsrewrote ingest lines withos.replace(src/temvera/store.py:169). The two marks rested on what the gate checked rather than on which path called it. - Ten published claims about agents-memory were wrong at
a60babbb…, the pin they were made at, and are corrected. The report awardedscope_enforcedon the slug filter initer_project_memory_files; the MCPsearch_memorydefaultedprojectto empty, which read every registered repository's store (src/agents_memory/store.py:2041) with no project predicate on the ranked fill (src/agents_memory/index.py:259-260), andread_memory_file,get_project_memoriesandget_relatedtook no scope, so the model chose the boundary per call and the mark is withdrawn. It awardednegative_evalontests/test_extract_filters.py, which keeps material out of extractor output; no committed case at that pin asserted that anything stays out of a search. It said there was no index and no ranking;search_memoryfilled from an FTS5 BM25 index (store.py:2088,index.py:224). It said there was no deduplication, no secret scan at write time and no atomic writer;_already_has_factskipped an exact repeat (store.py:2341),add_memoryranscrub(:2404), and_writewrote a temp file andos.replaced it (:230-237). It said nothing assembled a context block;always_on_body(:1518) wroteUSER.mdandPROJECTS.mdinto every host's always-on files. It creditedpromote_bulletwith a receipt the model could read; the tool had left the MCP surface and its one caller discarded the flag (:2776). It saidtests/test_distill_benchmark.pymeasured throughput; it asserted quality thresholds against a classifier defined in the test file (:140). And its census — 6,450 lines at version 1.0.0 on one commit,add_memoryat:1872in astore.pyof about two thousand lines — described the first pin, while this one was 1.1.0 on 103 commits withadd_memoryat:2393in 3,302 lines. The index, secret-scan, atomic-write, receipt and census claims were true of the first pin and were carried through a re-pin unchecked; the scope mark rested on the slug branch rather than on the default that bypassed it. - Eight published claims about mnemora were wrong at
509f4e73…, the pin they were made at, and are corrected. The report withheldscope_enforced, though every recall stage set the store filter's tenant fromctx.tenantId(packages/core/src/recall-runtime.ts:564,:631,:1129) and the conformance kit asserted a cross-tenantgetnull beside a same-tenant control (packages/testkit/src/memory-store-conformance.ts:284-300); the mark was earned. It said nothing recorded a mutation beyond the status itself, or who made it;memory_eventsheld a row per transition with a caller-declared actor and a digest snapshot (packages/postgres/migrations/0001_init.sql:145-158). It called the transitions to archived and forgotten unconditional, repeating a doc comment;forgetcompare-and-set the observed status (packages/core/src/runtime.ts:3234-3238) and the archive sweep locked only active rows (packages/postgres/src/memory-store.ts:1935-1940). It described a recall footprint recording what a recall touched;recall-footprint.tsis a pure function estimating whether mnemora beats sending the whole conversation (packages/core/src/recall-footprint.ts:14-15). It drew the validity gate as active only whenvalidAtwas supplied; it defaulted to now (packages/core/src/recall-runtime.ts:305-306). It said a memory whose provenance was never established could not be built; an inferred memory'smodeldefaulted tounknown(packages/core/src/runtime.ts:128,:2113). It gave the version as 0.1.1 frompackage.json; the pin is release tagv0.5.0, and the project's ADR 0070 makes the tag the version. Two anchors,memory-store-conformance.ts:4238-4262andmemory-store.ts:999-1030, were lines at the first pin,3676311e…. - Seven published claims about Veracium were wrong at
1d33f019…, the pin they were made at, and are corrected. The report awardedtombstoneon source revocation, saying its key was the content's identity;identity_digestwas SHA-256 over a framed(origin, source_id)(src/veracium/source_identity.py,src/veracium/ingest.py:336), which names a source, not a value. It awardedbitemporalonvalid_frombesideobserved_at; ingest set both from the caller's event date, which its own docstring calls "when a statement was made, not what it is about" (src/veracium/ingest.py:84,:767-774), so valid time was an observation time. It gaveassertablethree conditions wheresrc/veracium/schema.py:810-812had four,valid_nowamong them. It said third-party claims were bornQUARANTINEDby their channel; the channel setUSE_ONLY, andQUARANTINEDcame from the extractor'sthird_party_claimrelation (src/veracium/ingest.py:182-201). It described a principal-scope test inside one user as a cross-user one (tests/test_0020_read_surfaces.py:271-302), counted fifteen schema versions whereSCHEMA_VERSIONwas 14, and carried a size census from an earlier pin. The first two rested on a field's name and a docstring rather than on the digest's constructor and the field's writers. - Four published claims about Flair were wrong at
6fadb74f…, the pin they were made at, and are corrected. The report awardedscope_enforcedon a resolver it said every cross-agent read path imported, with no caller argument reaching it.FeedMemories.connectsubscribed to the raw table with noallowRead(resources/MemoryFeed.ts:179-189), so Harper's default admitted the super user, and only the Fabric branch offlair initprovisioned the least-privilege user a verified agent otherwise falls back from (src/commands/init.ts:285,:325,resources/auth-middleware.ts:393). On a local instance every verified agent therefore received every memory event, private rows included. AndmakeByIdReadGatedecided on the value the caller's target shaped (resources/record-type-kit.ts:285,:297), so a property read of another agent's private row returned its content past a middleware check that looked up the raw path segment (resources/auth-middleware.ts:629-631). The mark holds at the new pin, where both paths apply the rule. It said there was no supersession; a successor'ssupersedesclosed the predecessor'svalidToand default search dropped it (resources/Memory.ts:461-465,resources/semantic-retrieval-core.ts:228,:599). It citedtest/data-scoping.test.tsas the predicate's test; the file defines its own copy and imports nothing fromresources/. And its first History entry linked this commit, dated 18 September 2026, for a reading made on 16 September at02512aae…. The scope claim rested on the module header's list of paths rather than on every reader of the table. - Five published claims about LLM Memory were wrong at
63084315…, the pin they were made at, and are corrected. The report withheldscope_enforcedbecause the permission service had no test, which the rubric does not require; the mark stays withheld becausehasNoteAccessand the search filter match every share pattern as a LIKE prefix (node/api/src/services/note-permissions.js:130,node/api/src/services/memory.js:276). It said the database-constrained outcome meant an unresolved discussion could not be recorded as agreement;computeOutcomereturnedconsensuswhen no general vote had closed (node/api/src/services/discussion.js:173-175). It named the rootschema.sqlas the model; that file dated from 8 April 2026 and lackednote_permissions. It counted fifteen test files where there were twenty-three, missing eight script tests undernode/api/scripts. And it said deletion kept no record of the deleted value; deletion was a restorable soft delete, beside a daily decay soft-delete and retention rows emptied but kept (node/api/src/services/documents.js:481-565,node/api/src/services/cleanup.js:114-331). - Six published claims about mnemos were wrong at
6e7b14f4…, the pin they were made at, and are corrected. The report awardedscope_enforcedond.collection = ?(internal/search/bm25.go:103). The collection was an optional argument onmnemos.search(internal/mcp/tools_search.go:19) that searched every collection when omitted, andmnemos.readtook a uri or chunk id with no collection (internal/mcp/tools_read.go:16-17), so the model chose the boundary per call and the mark is withdrawn. It withheldnegative_eval, thoughTestSearchHidesDeniedCollection(internal/memory/visibility_test.go:47-59) asserted that a deny-listed collection never surfaced from a populated two-collection store while the visible one ranked first, withTestEmptyDenyShowsEverything(:93-103) as the control. It said ingested content passed theSecretScannerbefore it was written; the ingest pipeline had no scanner, and onlyrememberandokfyscreened (internal/memory/write.go:86,internal/ingest/okfy.go:89) until6ef270d9…. It gave re-ingest as the update path with the files as the source; a directory ingest was additive, and only the watcher,forgetandmoveevicted a document whose file was gone (internal/ingest/watcher.go:230,:348) until0252f607…. It said there was no status field; a taskstatusenum (internal/okfschema/okfschema.go:45) was read by the list filter (internal/storage/documents.go:220), though no epistemic one existed. And its census, twenty packages with 19,800 lines and 84 test files in one section and 28,764 lines with 115 test files in another, described the first pin and the commit four before 6e7b14f; 6e7b14f held 24 packages and 29,443 lines of Go in 118 test files. The scope mark rested on the filter's presence rather than on who supplies it, and the ingest claim on the security package's docstring rather than on the pipeline's callers. - One published claim about MemContinuum was wrong at
16293db8…, the pin it was published against, and is corrected. The report, its homepage card, its verdict and its families paragraph said the pre-edit hook hands the governing chain to the model before it edits the file. The hook runs onPreToolUsebefore the edit reaches disk, and its header said at that pin that the context arrives with the edit's result and governs the next move, not the edit that triggered it (hooks/pre-edit-chain.sh:6-14). - Six published claims about MemContinuum were wrong at
e21bfa06…, the pin they were published against, and are corrected. The report, its verdict and its families paragraph said the store's append-only check ran again in CI where--no-verifycould not reach it.hooks/install-hooks.md:222-225recommended that for a shared store, and no workflow, template or script in the tree ran--against-ref; that was true at the first pin as well. Section 9 kept a paragraph awardinghuman_reviewafter the mark was withdrawn on 2026-09-19. Section 10 said there was no benchmark and nothing was measured, whilebench/held a public retrieval harness of 57 queries, three runners, a scorer and a negative control, added in05f0fe69…. The census and threememidx.pyanchors were carried from161f555d…: 1,792 test functions rather than 1,605,invariant_enforcement_classat:3955rather than 3918,cmd_driftat:4084rather than 4047, and the hook wiring atscripts/repo-init.sh:1615rather than 1643. The "64 read queries" carrying the project predicate included 11 updates and deletes. And the recorded search fordeclinedin the hooks returned two hits from unrelated vocabulary rather than none; the claim it grounds holds. - Eight published claims about Klypix MCP were wrong at
43e7c5cf…, the pin they were made at, and are corrected. The report awardedhuman_reviewonbrain_garden's approval code. The agent's ownbrain_notearchived any card through aCORRECTIONcue (src/klypix-format.mjs:5863),brain_reconcile'sconfirmarray stamped and archived cards by id (bin/klypix-worker.mjs:648), and no proposal was stored to wait for anyone, so the code guarded one bulk path. It awardedaudit_logon the graveyard and restore points;purgeGraveyarddeleted the entry outright (src/brain-graveyard.mjs:162-163),pruneBrainHistoryran after every snapshot (src/brain-history.mjs:195), and the capture ledger kept the newest 1000 lines. It said no MCP tool computed evidence freshness;opBrainTaskContextandopBrainAskcalledinspectCardEvidence(src/klypix-core.mjs:503,:683). It said only the Claude Code hook wrote the cross-project registry;brain_synccalledregisterProjectBrain(bin/klypix-worker.mjs:889) under a comment reading "Claude's lifecycle hook is no longer the sole registry writer". It presented the retired "15% to 40%" ranker figure as a published result. And it counted 21 tools beside a README sentence of "Exactly 19", 57 test files with 53 chained, four hooks and asmithery.yaml, where the tree held 22 tools, a README saying "Exactly 22", 103 test files with 97 chained, five hooks and no Smithery manifest; itshuman_reviewrecord citedtest/brain-garden.mjs, which never existed. The first rested on the gate's own comment rather than on the other verbs that reach the same state, and the second on the record's name rather than on its deleters. - Three published claims about Velantrim Crystal
were wrong at
3ed3a53e…, the pin they were made at, and are corrected. Thehuman_reviewrecord said that on the Python and HTTP pathsactorwas a caller-supplied string. On HTTP and the CLI the actor was derived from a configured principal, a supplied actor had to match it, and force approval needed the ADMIN role (core/curator_runtime.py:101-128,core/curator_auth.py:128-152). The record missed the limit that did hold:/ingestand/review/approveaccepted the same bearer token (core/api.py:79-106). The mark stands on the read-only MCP server. Thenegative_evalrecord said a graph walk excluded a stale terminal hit and its neighbour while returning the rest;test_graph_walk_excludes_stale_terminal_vector_hit_and_its_neighbor(tests/test_pipeline.py:801-820) asserted only the two absences. Cases with a returned control existed at that pin (tests/test_pipeline.py:593-613,:684-707), and the mark stands on them. And the census of 750 commits to 30 August described the first pin; that pin held 762 commits to 13 September. - Five published claims about Stella were wrong at
e5faf774…, the pin they were made at, and are corrected. The report awardedscope_enforcedon the domain exclusion in recall; its one production caller built the session scope from every domain in the workspace taxonomy (crates/stella-cli/src/contextgraph.rs:160), so the filter excluded only nodes tagged with a domain since removed from it, and the mark is withdrawn. It awardedbitemporalon the edge intervals; the only productionFactAssertionleftvalid_fromandvalid_toempty (crates/stella-cli/src/memory.rs:1164), anchors were written with both empty, andvalid_towas set to the anchor scan's own clock (crates/stella-cli/src/memory/anchor_scan.rs:175,:239), an observation time. It withheldtombstone, saying nothing was keyed on a rejected value; a declined proposal was aRejectedevent on a lineage hashed from its wording, and both halves of induction skipped it (crates/stella-cli/src/memory/learning.rs:1121,:1176), pinned bya_declined_proposal_is_not_re_promoted. It said no benchmark results were committed;bench/evidence/tb21-hh10-20260731/held a scored Terminal-Bench 2.1 head-to-head. And it said there was no paper, wheredocs/papers/held four project-written analyses, none of them about memory. The first two rested on what the filter and the columns could do rather than on what their callers passed, and the third on a search for the word the codebase uses. - Seven published claims about vir were wrong at
d6347c69…, the pin they were last published against, and are corrected. The description, summary, verdict and homepage card quoted "243 transcripts, about 20 mine" and "354 sessions". The README had replaced both on 2026-09-04 with 1,386 transcripts, 562 agent-internal runs skipped, 410 notes and 396 sessions, so the 92% figure the report drew had no source at the pin. The report withheldnegative_eval, thoughsrc/search/retriever.test.ts:390-425asserted on a vault holding a live, a rejected and an archived note that only the live one entered the TF-IDF index; the case existed at every pin read. Thetrust_staterecord said a rejection withheld a note from every read.listDistilledcarried no rejection gate (src/state/db.ts:769-779), sovir_recent_notes, the CLAUDE.md candidates, summaries and dedupe kept serving it, and the mark rested on the two search paths. The tombstone paragraph said nothing on the write path read.rejected/;src/pipeline/writer.ts:109-113left a rejected session's note in place on re-distillation, keyed on the session, so the withholding stands. Section 10 said nothing evaluated distillation quality, thougheval/distill/held a blind, human-graded A/B of the distill prompt from 2026-09-15 with its results kept out of the tree. Section 3 counted 46 test files against 93, and section 5 said notes carried no status field while section 9 credited one. - Six published claims about Sonder Runtime were wrong at
1a41a88d…, the pin they were made at, and are corrected. The report awardedscope_enforcedon the project and account filters of the prompt-assembly reads.memory_search(server.py:15630), an MCP tool on the agent's project-bound tool list (:18527) routed by_agent_dispatch(:17549), read facts, preferences, sessions and interactions with no project or scope predicate, so the mark is withdrawn. It awardedaudit_logonrefinement_history.apply_preference_refinementandrollback_preference_refinement(refinement_transactions.py:226,:290) had no caller outside tests, preferences changed throughupsert_preferenceandset_preference_enabledwithout a journal row, and the authoritative fact source that writesmemory_replication_logwas constructed only in tests. It said tasks and preferences carriedaccount_scope; preferences carried ascopecolumn defaulting to'global'(sonder_runtime/adapters/memory_store.py:219-232). It said the quarantine math weighted caller-sourced outcomes over machine ones; only heuristicallyattributedevidence was excluded, andtest_directly_graded_machine_evidence_still_drives_the_gate(tests/test_outcome_source.py:281) asserted that machine evidence counts. It said nothing outsidetests/constructed anOutcomeService;MemoryFacade.recorddid (sonder_runtime/application/memory/facade.py:63), itself without a caller. And it placedis_tombstoned_duplicateingrounded_extraction.pyrather thanreflection.py:165, and named a rootrecall.py,mmr_rerank.pyandeval_history.py, none of which existed; severalmemory_store.pyline anchors were off by up to nineteen lines. The first two rested on the filter and the triggers rather than on every reader and every writer. - Six published claims about Yantrik OS were wrong at
ec2e424f…, the pin they were made at, and are corrected. The report said the OS layer had no retrieval of its own; the companion'ssmart_recall(crates/yantrik-companion/src/memory_evolution.rs:190) ran up to three engine recalls and dropped audit and system domains, andrecall_identity_facts(crates/yantrik-companion/src/companion.rs:3607) read the engine's table by raw SQL. It said nothing superseded or retired a claim and that no mutation record existed;forget_topicsetconsolidation_status = 'tombstoned'(crates/yantrik-companion/src/tools/memory.rs:655), LLM consolidation recorded update and merge decisions, andconsolidation_logtook inserts from three paths (crates/yantrik-companion-tools/src/memory_hygiene.rs:355). It counted 753 test functions; the tree held 809#[test]attributes. It listedyantrik-mcpas an MCP surface; the crate was not a workspace member and nothing built it. It put an SSH-key pattern table in the output sanitizer; the table belonged todetect_harmful_command(crates/yantrik-companion-core/src/sanitize.rs:343). And it classified the storage as delegated to the adopter, where the companion embedded the engine's SQLite file. An open question it left, whether the companion read the engine's lifecycle states, had an answer at the pin: it filtered on them in four files. The first two came from reading the brain and cortex crates as the whole memory layer. - Six published claims about inspeximus were wrong at
d9efe84a…, the pin they were made at, and are corrected. The report withheldbitemporal;remember(valid_from=...)stamped a declared event time apart fromtsandas_of(key, when, as_recorded=)filtered on both (inspeximus/core.py:2860,:10731-10782), withtests/test_bitemporal.pycommitted. It withheldaudit_log;_emit_write_receiptand_declare_retiredappended a hash-chained receipt for every write and retirement (inspeximus/core.py:3335,:3442) and no path removed one. It awardedscope_enforcedon the tenant and agent view, but the shipped MCP server held an operator handle with no tenant:recallandgetread every record,recall_asbound a model-supplied agent name andall_projects=Truedropped the project scope (inspeximus/mcp_server.py:584-629,:770,:2151-2160,:2216-2239). Its census of version 2.35.0, 129,806 lines, 294 test files and a 15,891-linecore.pydescribed3df65354…, two days earlier; the pin was 2.44.0 with 306 test files and a 16,187-linecore.py. Its opening quote, "Your agent's most expensive failure is not forgetting", was in the README at that commit and nowhere in the tree at the pin. And its tombstone and scope records citedcore.py:2105-2121,:5924-5962,:7940-7958and:8377-8394, line numbers of the same older commit; at the pin the guard comment was:2226-2264, the guards:6210-6257and_acl_visible:8670. The two withheld marks rested on the absence of prose about the mechanism rather than a search for its writers, the scope mark on the library path rather than the surface the agent reaches, and the last three on a census taken before the pin was set. - Seven published claims about OmniNode Knowledge Base
were wrong at
cb724907…, the pin they were last published against, and are corrected. The body described the tree of the first pin. It saidvalidate.pyran five checks and that nothing checked that an ADR id identified one record. The validator ran eight, includingcheck_adr_id_uniquenesswith one exact-path exemption for ADR-0010 (scripts/validate.py:456-520). It said the scripts had no tests;tests/held 92 pytest functions in five files, and.github/workflows/ci.yml:40ran them. It listeddeep-diveandevidenceartifact types and quotedevidence/README.md; both types and directories were removed on 26 August 2026. It counted 37 accepted ADRs and 7 accepted pivots, where there were 32 and 5. It quoted theCLAUDE.mdreconciliation stamp as the 2026-06-21 refresh; the file read 2026-08-19. The matrix said asupersededstatus was used once, where three artifacts carried it. The verdict entry and the families paragraph kept the first pin's counts, a five-check validator and an Apache-2.0 licence. No mark changes. - Four published claims about mnemonic were wrong at
5fc9a5f5…, the pin they were made at, and are corrected. The report said supersession shortened a note's decay half-life so that it kept returning "ranked lower, until it fades".computeDecayInfohad two callers,project_memory_summaryand consolidation evidence (src/tools/project-memory-summary.ts:112,src/tools/consolidate-helpers.ts:679), and none on the recall path, so a superseded note ranked as before. Writing the edge also set itsupdatedAtto the current time (src/tools/relate.ts:423,src/tools/consolidate-helpers.ts:323-327). It said confidence was derived from git history signals and drew it feeding the ranker;computeSignalStrengthread frontmatter role, lifecycle,updatedAtand relationship count (src/provenance.ts:153-173), git supplied only a five-dayrecentlyChangedflag, and both were computed for results already selected (src/tools/recall.ts:817-852). Its update and delete description named no deletion, thoughforgetandconsolidatewithprune-supersededboth deleted notes, which also answered its open question of whether a superseded note is ever excluded. And it counted 1,686 test cases; the tree held 1,496itandtestcalls in 88 files. The first two rested on the constants' names and the README's framing rather than on the callers of each function. - Five published claims about gaius were wrong at
b720bdb6…, the pin they were made at, and are corrected. The report withheldnegative_eval, thoughtests/test_inject_credential_filter.py:70-87asserted a credential-bearing fact absent from inject output beside a clean fact that had to appear; the mark was earned. Itstrust_staterecord said a read filteredreview_state != 'rejected'atgaius/facts.py:443. That line is the write-time contradiction check; retrieval excludedoutcome = 'rejected'(gaius/landscape.py:1119,gaius/mcp_server.py:134), which the reject verb writes alongside, so the mark stands on the other column. It called the review state three-valued;auto,pending,confirmed,rejected,deferredandagent-reviewedwere all written (gaius/maturity.py:87-93,gaius/review.py:669,:706). It said the hard gates exit 2 on force-push, unconfirmed live-trade and prod-delete; no code in the tree did, anddocs/hard-gates.md:172said the plugin's hooks block no tool call. And it said most reads carriedWHERE domain = ?with one path making it optional; the injector andgaius_searchapplied the domain only when supplied (gaius/landscape.py:1120-1123), the session hook supplied none, and the domain was a topic label that deduplication ignored (gaius/facts.py:474-476). - Six published claims about Fidelis Memory were wrong at
318a5cbb…, the pin they were last published against, and are corrected. The report withheldnegative_eval;tests/test_user_id_namespace_isolation.pywas committed there, and asserts that a server bound to oneuser_iddoes not return another namespace's record from a shared Chroma collection, beside an unfiltered control that returns both. It said every store reader passed the scope key;recall_sessions.query_sessions, a documented public function, read session rows withwhere={"mem_type": "session"}and no key, though nothing in the tree called it. It said the README placed Mem0, Zep and Supermemory figures beside the 73.0%; that paragraph was in the README at804e521f…and gone at the pin. It said the README headed its benchmark with 470 questions and left the graded-subset caveat toSUMMARY.json; at the pin both the headline and the table gave the graded count, 317/434. Its census of 312 test functions, 31 test files, 39,279 lines and a 368-test README badge did not describe the pin, which held 427 test functions in 43 files, 43,905 lines of Python and no badge. And it citedserver.py:182and:222for the scope filters and README:8,:122-136,:138-150and:225-240; at the pin those wereserver.py:390and:435and README:7,:276-291,:293-306and:446-458. The withheld mark rested on a summary of the suite rather than a search of it, and the rest on text carried forward from the first reading without being read against the pin. - Four published claims about NeuralMind were wrong at
38c74096…, the pin they were made at, and are corrected. The report praised audit rotation for seeding the new file from the archived file's final hash. The backward scan inrotatestopped on the archive's trailing newline and read nothing, so the continuation marker chained to zeros, and the marker's hash covered its ownprev_sha256, whichverifyexcluded; a rotated log failedverifyat line 1 (neuralmind/audit.py:272-303,:183-202), androtatehad no production caller. It saidverifytreated an unparseable entry as a legacy line and updated the running hash from its content, as the comment at:187says.read_eventsdropped unparseable lines beforeverifysaw them, one invalid UTF-8 byte made it return no records andverifyreportok(:163-171), and a record without a hash reset the running hash to zeros (:188). It said the core had no delete or forget path;neuralmind memory resetcleared a synapse namespace throughclear_namespace(neuralmind/cli.py:2506,neuralmind/synapses.py:2255), and the decay run at session start deleted edges below a threshold (neuralmind/synapses.py:926,neuralmind/hooks.py:328). And it counted 150 test files where the tree held 145 namedtest_*.py. The first two rested on a docstring and a comment rather than the code beneath them. - One published claim about Context OS was wrong at
15b5acac…, the pin it was made at, and is corrected. The report calledstate/decisions.mda table only ever appended to and never rewritten, and groundedaudit_logon it and onstate/current-log.md. The setup workflow could write any path understate/(SETUP_ROOTS,contextos/kernel.py:140), andrender_setupreplaced a populated file whole once the payload listed it inreplace_populated(contextos/kernel.py:1534-1563,:4155-4157), so a production path rewrote both. The mark held on a record the report did not cite: the create-only receipt each apply publishes (contextos/kernel.py:4198,:4384). The claim rested on the writer the session loop uses rather than on every writer the path policy admits. - Seven published claims about Areev were wrong at
5b6b29f3…, the pin they were made at, and are corrected. The report awardedhuman_reviewon a self-approval block; that block records a trigger only for model and external findings (crates/areev-loop/src/engine.rs:437), so the MCPareev_recommendationstool approved and applied builtin findings asagent:mcp, ascrates/areev-cli/tests/mcp_smoke.rs:717asserted. The MCPareev_caltool also ranAPPROVEas the session principal,user:localon a default server, recorded as a human. It said noUPDATE oplogexisted;crates/areev-store/src/lib.rs:2272andpg.rs:151backfilled thenscolumn. It said the conformance kit ran against the reference substrate; itsBackendhad two implementations, the embedded store and Postgres, and fifteen case modules, not eleven. It saidverify_run.pyandtests/golden/reproducibility.txtwere gone; both were incrates/areev-bench/. It said CAL, the MCP tools and the store applied a-0.3penalty; the penalty is applied only insideareev-context. It called the loop's Observation audit grains append-only;forgetrefused only Tier-2 authz records. And its store line anchors were from an earlier pin. The first rested on the MCP handler's literal actor rather than on who records the trigger. - Five published claims about HUQAN were wrong at
844be596…, the pin they were last published against, and are corrected. Thehuman_reviewandaudit_logrecords rested oncreateHumanOversightApprovalRuntime, which only tests constructed; the MCP server passedoptions.humanOversightApprovalRuntime || nullandrunStdiocalledcreateServer()with no options (mcpServer.js:81,:108). Both marks stood on other code: the approve verb filtered out oftools/listbehind an operator capability (lib/mcp/tool-surface.js:11), andaudit_logtriggers refusing update and delete (graph.js:245-254). The report said a quarantined write was held with its own receipt. The learn path wrote nothing on any outcome butallowand recorded aREVIEWaudit event (lib/learn-use-case.js:79-95), so thetrust_staterecord cited a returned outcome rather than a stored status. It withheldnegative_eval, thoughtest/memory-tombstone-supersede-downstream-exclusion.test.jsasserted that list and query reads excluded a tombstoned record beside a surviving one. And its census, 287,058 lines over 1,563 files, was the first pin's; that tree held 299,410 lines in 1,652 JavaScript files. - Ten published claims about AgentDatabase were wrong at
85149238…, the pin they were last published against, and are corrected. The report called the admission matrix proof that a model's inference could never persist; the source type, actor type and authorization mode are envelope fields the writing agent supplies, matched as strings (OpenAIDatabase/scripts/memory_mutation.py:243-256), with references checked for form only (:69-76). It said the abstention reason priority lived in policy rather than code order;retrieval_decisionbranches in code (OpenAIDatabase/scripts/memory_forgetting.py:256-271) andvalidate_policyonly compares the policy list with a literal (:96-110). It read the gold benchmark's 1.0 as a test of the store's pipeline; the scored ranker ispredictinsidescripts/evaluate_memory_gold_benchmark.py:226-292, which never callsquery_records. It saidnegative_triggerswere rendered into the agent's context; the boot viewAGENT_MEMORY.mdomits them (scripts/memory.py:394-447). It said there was no index beyond the active view;agent-memory.jsoncarries a lexical routing index and every keyword query builds one in process (scripts/memory.py:502-506,:1272). It said the boot index mixed scopes; all six entries areglobal:owner. It calleddata/memory/active/a rendered active view; it is the 278-record legacy store the cutover read. It put the tree at 15,000-odd files where there were 23,937, and its recorded licence search at four vendored files where 58 licence-named files exist, one outsideCodexSkills/, none granting this repository. And section 9 listedhuman_reviewas awarded after its withdrawal on 2026-09-19. The marks were unaffected:negative_evalholds ontests/test_memory_forgetting.py:195-260, which runs the shipped query path. - Four published claims about NEOTH were wrong at
6a375573…, the pin they were made at, and are corrected. The report withheldnegative_eval, thoughquery_three_lanes_excludes_unverified_facts_and_resolved_contradictions(SRC/neothd/src/cli/recall.rs:3130) asserted a candidate fact absent from the canonical recall lane beside verified facts that had to appear. It withheldtombstone, thoughforget_by_topicwrote a_tombstone.<topic>sentinel in its erasure transaction and profile extraction rejected any later claim naming the topic (SRC/neothd/src/memory/forget.rs:369-383,SRC/neothd/src/profile/claim_guard.rs:466-485). It said ground-truth promotion was only explicit;insertpromoted a candidate to verified at two distinct sources and a confidence of 0.85, and the opt-in consolidation sweep wrote mature episodic clusters into the table (SRC/neothd/src/memory/groundtruth.rs:451-459,SRC/neothd/src/memory/consolidation_sweep.rs:358). And it said contradiction demoted the lower-credibility side of every detected pair; only a polarity flip did, and a value divergence was recorded for the operator with both facts left verified (SRC/neothd/src/memory/contradiction.rs:422-427). - Four published claims about SageOx
CLI were wrong at
02f4f406…, the pin they were made at, and are corrected. The report putMEMORY.mdandmemory/in the ledger besidesessions/anddata/, one ledger per team; they were in the team-context checkout (cmd/ox/agent_prime.go:2215readsteamDir/MEMORY.md,cmd/ox/memory_put.go:116writes observations undertc.Path), and the ledger was per project repository (internal/ledger/ledger.go:86). Its headline said a memory conflict falls to the LLM tier; the resolver was wired only to the ledger pull (internal/daemon/sync.go:1361) and the ledger push hook (cmd/ox/session_upload.go:533), only whenOX_LLM_MERGE_BINnamed a binary, the team-context pull (internal/daemon/sync_team.go:507) passed none, andMEMORY.mdandmemory/were hard-denied (internal/manifest/auto_resolve.go:45-46). It said there was no retrieval and nothing ranked;handlePrompt(cmd/ox/agent_hook.go:479) injected up to four hits fromledgersearch.Search, a term-frequency ranking, andox conversation topichid atoms with avalid_to(internal/conversation/read/topic.go:99). And it said CI was disabled, quoting a README comment;.github/workflows/ci.ymlran on push and pull request beside a leftoverci.yml.disabled. It also gave the marker check asstrings.Contains, which was only a fast path before a line-prefix scan (internal/ledger/automerge/automerge.go:251-261). The first two followed the word "ledger" across two repositories, the third read the priming path and not the prompt hook, and the fourth took a comment as evidence. - Four published claims about memini were wrong at
452ff229…, the pin they were made at, and are corrected. The report awardedscope_enforcedand said working and episodic memories never cross a namespace boundary on a read;memory_list,memory_getandmemory_historytook a model-suppliednamespacethattools.ns(internal/api/mcp/mcp.go:639-648) accepted for any valid name, at every tier, andscope="everywhere"read the subtree at the full tier filter. It awardedtombstoneto a supersession pointer, a record-keyed mechanism the rubric excludes, and the exact-dedup lookupGetByFingerprintrequiredsuperseded_by IS NULL, so a superseded value written again was stored live. It awardedaudit_logto an event table thatPruneEventsdeleted from hourly, by default after720hand beyond100000rows (internal/config/config.go:618-622at that pin). And it cited the controlled cross-namespace case astestCrossNamespaceUpsert; the case atinternal/store/storetest/conformance.go:73-145wastestIDsByPrefix. The first rested on the store's namespace parameter rather than on who supplies it, the second on the pointer's doc comment, and the third on the event writers rather than the deleter. - Seven published claims about CodeWiki-Plus were wrong at
4b826918…, the pin they were made at, and are corrected. The report awardedtombstoneon the task-memory supersession marker, which is keyed on an entry. The write check compared only live entries (codewiki/mcp/tools/task_manager.py:756) and distillation's three duplicate searches skipped deprecated notes (codewiki/mcp/tools/distill_conversation.py:419,:532,:692,:743), so a rejected claim extracted again landed as a new draft. It awardedscope_enforcedon atask_idfilter applied only when the caller passed one, and not on thecheckorby_filepaths (codewiki/mcp/tools/note_query.py:848,:876-887,:1137-1140). It awardedaudit_logon telemetry that recorded use rather than mutation, andrecord_hitrewrote the file (codewiki/mcp/tools/telemetry.py:148-196). It said a confidence level only adjusted ranking; shadow notes were dropped unlessinclude_shadowwas passed (codewiki/mcp/tools/note_query.py:1149,:1164). It said notes reachedstablethroughconfirm_note;ingest_noteacceptedstatus: stable(codewiki/mcp/registry.py:1033,codewiki/mcp/tools/note_ingest.py:278). It read the import of_trust_tierinknowledge_loop.pyas an unused consumer; that module is a compat re-export facade (codewiki/mcp/tools/knowledge_loop.py:1-14). And it said no paper was cited; the README cited the upstream CodeWiki paper with a BibTeX entry (README.md:875-885). - Ten published claims about Vibe Cognition were wrong at
208e7d2e…, the pin they were last published against, and are corrected. The report said there was no scope key on the read path; that commit added personal constraints, which every storage read and search filtered by the recorded owner's email (src/vibe_cognition/cognition/scope.py:33,src/vibe_cognition/cognition/storage.py:1135-1146). It withheldnegative_eval, thoughtests/test_personal_constraints.py:61-93asserted that a teammate's search, get and neighbour reads excluded a personal constraint beside a project one that had to appear. It said a removed node was never un-embedded and that nothing reconciled ChromaDB with the graph, quoting the docstring of_reconcile_orphan_embeddings, the startup sweep that deletes those vectors (src/vibe_cognition/server.py:347-377); the local delete also purged them (src/vibe_cognition/cognition/operations.py:80-81). It said both replay bookkeeping sets were never drained; each search drained_replayed_node_ids(src/vibe_cognition/tools/cognition_tools.py:989), and a re-add discarded from_removed_node_ids(storage.py:1635). Its audit record said no case asserted that a mutation without a journal line fails;tests/test_wp_core_tail.py:48-59did. It said there was no benchmark or evaluation of any kind;scripts/bench_wave1.py,scripts/bench_wave3.pyandscripts/eval_conflict_lens.py, with a labelled fixture, were committed. It said multi-process correctness relied on replay rather than a lock; appends took an exclusive lock (src/vibe_cognition/cognition/journal_io.py). It described one sharedjournal.jsonl, attribution from git config, and person nodes edited in place; writes went to per-person shards under.cognition/journal/behind a confirmed identity, and people were profile files. Its 58 test files were the first pin's count and its 900-linestorage.pymatched neither pin; at this one there were 80 test files and 1,735 lines. And its storage anchors,_append_journalat:942among them, came from an earlier commit; at the pin it was:1235, with its six calls at:502-618. The embedding and bookkeeping claims rested on comments read as descriptions of the code beneath them, and the rest on the first reading's text carried forward across two re-pins. - Two published claims about EGC
were wrong at
f24f53c2…, the pin they were made at, and are corrected. The report withheldnegative_eval, saying no test asserted that one project's material stayed out of another's recall. The caselist is scoped to project_path(tests/lib/working-memory.test.js:158-174) wrote one key under two projects and asserted each list returned only its own value, beside an expiry case and an overwritten-decision case intests/scripts/egc-memory-search.test.js:156-171; neither file changed between that pin anda46dd1b2…. And it saidcompress_observationssummarised raw observations without deleting them; on theobservations.jsonlpathreplaceObservationoverwrote the raw line with the summary (mcp/servers/egc-memory/src/compress.ts:311-329at that pin). The first rested on searching decisions and lessons for a cross-project case and not the third memory tier. - Six published claims about PLUR1BUS were wrong at
c381fd57…, the pin they were last published against, and are corrected. The report said injection was capped per feature with no global budget;applyGlobalInjectBudgettrimmed the auto-recall prompt torecall.globalInjectMaxChars, default 17,000 characters (index.js:13134). Theaudit_logrecord calledreconsolidation-events.jsonlappend-only by construction;appendJsonlcapped it at its newest 5,000 lines (lib/neo-arch.js:2265-2285) and the daily consolidation rewrote it throughpruneAll, and the mark rests ondestructive-ops.jsonlinstead. It said no test asserted that bulk background writers consult the tombstone;tests/tombstone-bulk-writers.test.jsasserted it for four writers throughassertCardWriteAllowed. The verdict said the code records that derived records carry no scope field; that comment was gone and the records were stamped with avisibility. An Avoid entry warned against patching the host atpostinstall, a patch removed in 7.5.0. It said the tree held no arXiv reference;README.md:1126cites the jina-reranker-v3 paper. Two enumerations were short:confirmedhad two readers, both pending-list builders, and two snapshot scripts also namedmerge-proposals.jsonl. - Five published claims about Otis were wrong at
879397c8…, the pin they were last published against, and are corrected. The report said thecompactedevent carries the messages it replaced; itsmessagesfield held the kept suffix,result.keptMessages(src/app/conversation.ts:215-219,src/core/compaction.ts:62), and the replaced turns survived as earlier events the log never rewrites, plus an in-turnturnsegment. It said the dependency manifest had no lockfile;bun.lockhad been committed since the repository's first commit on 16 July 2026. It said the hashed session directory recorded no mapping back to its workspace;registerWorkspacePathwrote the absolute path toworkspace.json(src/storage/workspace-registry.ts:15), and the desktop's global history listed those sessions. It said every skill file was 0600; the manager set 0700 on its own directories and 0600 on its manifest and lock, and cloned files kept the modes git wrote. And its figures of 23,700 lines at v0.1.36 and 419 lines insession-events.tswere the previous pin's, where this one measured 30,661 lines at v0.1.48 and 613. The first rested on the field's name rather than its caller, the third on a reading that predated the registry, and the last on figures carried across a re-pin. - Three published claims about MemoryIndustry were wrong at
2f45dcb7…, the pin they were made at, and are corrected. The report awardedscope_enforced, but every search arm read$3::uuid IS NULL OR o.project_id = $3 OR o.project_id IS NULL(rust/src/search/bm25.rs:24,rust/src/handlers/faro.rs:302). The project was bound only by the agent's owncuba_jornada start project=orcuba_proyecto switch(rust/src/handlers/jornada.rs:25,rust/src/handlers/proyecto.rs:100-115), or in the HTTP daemon alone from the client's root (rust/src/http.rs:449), so an unbound stdio session read every project. It said the audit log had no writer on any memory path;set_trustappendedmemory.promoteandmemory.quarantinethrougharchivo::handle(rust/src/handlers/eco.rs:145-149), a call the recorded search, which grepped for theINSERT, could not see. And it said quarantine withheld a row from every search branch; the twocuba_faroerror arms carried no trust predicate (rust/src/search/bm25.rs:88-97,rust/src/handlers/faro.rs:1375-1384), andcuba_contexto's importance layer (rust/src/handlers/contexto.rs:124-128) andcuba_alma action=get(rust/src/handlers/alma.rs:165-168) served quarantined observations. The first rested on the predicate's presence rather than on what its empty value did, the second on a search for the insert rather than for its callers. - Seven published claims about Polyphony ARC were wrong at
9bb384c2…, the pin they were made at, and are corrected. The report said the harness stores whatever summary comes back, with no truncation, length check or validation;_run_layer3refuses a reply that is tool-call markup and truncates past 20,000 tokens (arc_hs/hs_compaction.py:329-361), under a 16,384-token generation cap (arc_hs/coding_session.py:74). It said the successor gets the summary beside a directory listing; it also gets a notice, a code-written state pointer listing five fixed file names, an assistant turn the harness wrote and up to 20,000 tokens of its newest turns, and loses the main prompt (hs_compaction.py:227-256,:303-316). It quoted two comments as two failures; both describe per-turn trimming, and the other recorded failure, a token meter that under-counted grid frames, went unreported (:8-23). It said eleven games score below 5; ten do. It dated the scorecard 7 July 2026, the leaderboard's date; the scorecard was published on 2 July, before the commit. It said no record survives of what a compaction dropped;agent.logkeeps a truncated line for every assistant turn and bash call (coding_session.py:323-324,:427-430). And it gavearc_hs/6,542 lines, the count forarc_hs/andcompat/together;arc_hs/holds 5,599. The first two rested on the prompt string rather than on the function that receives the reply, and the fourth on a hand count of the scorecard table. - Five published claims about ai-memory were wrong at
74d2d31e…, the pin they were made at, and are corrected. The report called a handoff addressed from one harness to another by typedfrom_agentandto_agent; every production writer setto_agenttoNone(crates/ai-memory-hooks/src/router.rs:3123,crates/ai-memory-mcp/src/server.rs:3563), only a CLI listing read it, and a manual handoff'sfrom_agentwasOther. It said an unclaimed handoff decays out on a schedule; the four writers ofexpired(crates/ai-memory-store/src/ops.rs:2623,:2959,:3015,:3074) were supersession, a cancel and an operator bulk expiry, none of them on a clock. It said no retrieval-quality benchmark was found, whiledocs/benchmarks/held three LongMemEval-S reports dated 1 September 2026. It awardedscope_enforcedalthoughmemory_query'sglobalargument searched every project with no project or viewer predicate (server.rs:1930-1951). And it withheldnegative_evalalthoughnamed_proxy_operators_stay_isolated(crates/ai-memory-mcp/tests/suite/handoff_identity.rs:264-285) asserted that another operator's baton is not delivered, beside the owner's successful claim. The first two rested on the type definition and its doc comment rather than on the writers of the fields. - One published claim about MuscleMemory was wrong at
4c7b01b4…, the pin it was made at, and is corrected. The report said a passing session that touches an existing skill's files and matches its action shapes counts as a check rather than a new skill. At that pinauto_learncounted only successful tool calls (packages/musclememory/service.py:1170,:1214), whileevaluatecompared the count with every tool event in the trace (:786-789). Any session containing a failed command therefore raisedmetrics_conflict, was skipped at:1240, and was compiled as a duplicate skill. The claim rested on the matching rule rather than on the metrics the caller sent. - Two published claims about ThoughtDAG were wrong at
850b89d1…, the pin they were made at, and are corrected. The report awardedaudit_logon the canvas event log and called it append-only in code and in contract.logEventkept the newest 9,000 entries once the array passed 10,000 (src/store/slices/events.ts:16,:24), a production delete of mutation records present at every pin the report was read at; the report listed the cap as a limit and kept the mark. It also said the README's one arXiv link was an example query; the README carried none at that pin, and the example lived indocs/guides/why-layer.md. The first rested on the log's contract comment rather than on what its one writer does past the cap. - One mark and two claims about Daimon were wrong at
f05d6340…, the pin they were made at, and are corrected.scope_enforcedwas credited on the per-project read path while the shipped MCP server tookslugandall_projectsfrom the model ondaimon_recall, andslugondaimon_brief, refusing them only underDAIMON_TENANT_SCOPED, which is off by default (plugin/daimon_briefing/mcp_server.py:44-53,plugin/daimon_briefing/mcp_tools.py:65-87, identical at both pins); the evidence record listed the caller-chosen slug among its own limits. The report took the corroboration docstring's "append-only and never rewritten" (plugin/daimon_briefing/capture.py:299) at its word and said the event log held nothing for a deletion to miss, while resolve and reopen rows carryitem_textthatscrub_event_fieldsredacts in place. And the whole-tree validity-interval search left out a research benchmark underresearch/memory-backend/benchmark/state/that drives Graphiti's bi-temporal edges; it touches no product path. - Four published claims about Wenlan were wrong at
47971618…, the pin they were made at, and are corrected. The report awardedscope_enforcedon the claim that the resolver refuses a caller who names no Space.resolve_read_scopereturnsReadScope::Globalfor an absent or blank name (crates/wenlan-core/src/read_scope.rs:34-40, identical at both pins), and without aWENLAN_SPACEpin the MCP layer passes the model'sspacethrough, so a standard-profilerecallthat omits it searches every Space. The mark is withdrawn. It led itsnegative_evalrecord with an MCP round trip said to seed two spaces; that test runs against a wiremock that stores nothing and returns only the alpha row (crates/wenlan-mcp/tests/space_roundtrip_e2e.rs), so the mark rests on the core tests against a real database, which it also cited. It said there was no validity axis;event_dateandevent_endwere onmemoriesand filtered by the temporal channel, an event-time axis that does not earnbitemporal. And its model showed identity and preference supersedes held for a person; the Protected tier gates merges the daemon proposes, while an agent's ownsupersedesis gated only by its trust level, which defaults to full (crates/wenlan-server/src/memory_routes.rs). The scope claim rested on the resolver's two error branches, not on the branch an empty argument takes. - Three published claims about Mandalore were wrong at
33329382…, the pin they were made at, and are corrected. The report withheldscope_enforcedon the ground thatExactScopewas a caller-selected widening; every production caller passedExactScope: true(internal/memory/service.go:193,internal/sync/remote.go:237) andrecallHeadsmatched the stored scope by equality, so the mark was earned. It did not creditnegative_eval, thoughTestRetrievalQualityMatrix(internal/memory/evaluation_test.go:55-62) asserted exact result sets from which superseded, future-effective and other-scope revisions had to be absent in a populated store. And it said authorship recorded the model, so that "written by which model" was answerable;Authorship.ModelandSessionIDhad no producer, andinternal/binding/binding.go:226set device, actor and harness only. The first rested on the field's comment rather than its callers, and the third on the field's declaration rather than its writers. - Seven published claims about Portable Handoff were wrong at
ec5f203b…, the pin they were made at, and are corrected. The report said the model cannot write the commit, branch, dirty flag or a file hash, and the families page thatfinalizetakes the snapshot from local git alone;finalizereads the snapshot back from a preflight JSON file with a key-set check and runs no git (src/portable_handoff/preflight.py:69-74), and the shipped host commands write that file to a fixed path inside the repository, so the facts were protected from the draft and not from the agent. The report and its verdict entry presented the briefing's publication state as checked at read time and said the recorded file hashes are compared with the tree;head_publishedis the write-time value and is never recomputed, and only draft-named files are re-hashed, never the changed-file hashes (src/portable_handoff/load.py:82-154). The report saidsanitize.pyscans every string; strings under eleven structural keys are skipped, one of them the free-textevidence_refs(src/portable_handoff/sanitize.py:126). The report and its verdict entry saidfinalizerecords the scan as any of four statuses; it writespassed, and nothing writesfailedorunknown(src/portable_handoff/finalize.py:204). Those four overstated the system. The report said the budget drops items in rotation and cited an uncalled helper for its truncation; each list is emptied before the next, and truncation runs only above the 12,000-token hard cap (src/portable_handoff/budgeting.py:73-114). It saidverifiedis refused beside a conversational provenance, where a draft's claim is downgraded toclaimed. And it said the null-id guard keeps the capsule's commit honest; it guards worktree entries, whileproject.commitcomes fromgit rev-parse HEAD, which fails on an unborn branch (src/portable_handoff/gitfacts.py:183,:257-259).
Weights as memory, at adapter granularity
Low-rank adapters are commodity rather than exploratory, published and exchanged as artifacts, so the question of whether this atlas's capabilities have a referent in a fine-tuned model is not hypothetical. The answer is that the unit of identity is the adapter, never the record inside it, and that single fact decides which capabilities survive the move into weights and which do not.
Four of the seven survive at adapter granularity,
and the corpus already proves it. Scope is enforceable by routing —
which adapter loads for which user or project — and MemOS carries the
scope_enforced mark on exactly that basis while mounting a
parametric module. A training manifest can record which corpus and which
base-model version produced an adapter, which is a real audit trail over
training mutations. Adapter v2 superseding v1 at
deployment is real supersession, and discarding an adapter is a real
deletion. Validity intervals over adapter versions are ordinary
bi-temporality.
What fails is anything that needs record identity, and that is the atlas's admission test rather than a side issue. A delta is opaque: no read path reports what it learned from a given document, so "why does the system believe this" has no answer at the level the question is asked. Nothing can be superseded inside an adapter — only the whole adapter. Nothing can be deleted from one; a deletion request that names a record is answered by retraining without it, which requires still holding the corpus the request asked you to destroy. And a merged adapter carries its contributions irreversibly, while a withdrawn one reaches neither the copies already taken nor the merges downstream of them.
So the honest statement is not that weights cannot carry these mechanisms. It is that weights carry them at a granularity coarser than the thing a correction names, and that no implementation reviewed here closes the gap. None of this rests on how many adapters exist or how popular any host is — it rests on the shape of the artifact and on what the reviewed systems actually do, which are the only things worth resting on.
Below the adapter there is a coarser case, and it removes all
four. mini-AGI has no
adapter and no artifact boundary at all: one model, one weights
directory, and a gradient step taken on every 2,048 characters of
whatever it reads — a book, a directory somebody pointed it at, or the
exchange a person just had with it. There is no v2 to supersede
v1, no manifest recording which corpus produced which delta,
and no discarding of a unit, because the unit is the whole thing. Scope
is not enforceable by routing either, since routing here is a paging
decision made from the text being read rather than from who is asking.
So the four capabilities that survive at adapter granularity survive
because the adapter is a discrete, versioned, detachable
artifact — and none of them is a property of weights as such. Its one
deletion, prune(), removes an expert file that the router
has not chosen inside a survival window; the docstring states the trade
plainly — "an expert which is genuinely rare rather than dead is
deleted, and deletion is permanent" — and nothing about it can be
aimed at a fact. That is the boundary condition worth carrying: the
finer the weight artifact, the more of this list you keep, and at zero
granularity you keep none of it.
At the finest weight-side granularity yet, the key is an
n-gram and still not a fact. EngramEdit (arXiv:2610.10533, code at ModalityDance/EngramEdit)
edits a DeepSeek-Engram-style conditional memory with the transformer
frozen, and its implementation keeps the edits as a sidecar:
EngramEditEmbedding maps an exact token n-gram of length 2,
3 or 4 to a residual vector, adds it to the base embedding whenever that
n-gram is active, and saves the map as engramedit_state.pt
apart from the weights (EngramEdit/memory.py:12-102,
:138-142). That is a key a correction could name, and it
belongs to the subject's tokens rather than to the fact. Each batch of
edits is solved jointly and summed into whatever a key already holds
(engramedit_main.py:410-419,
memory.py:91-102), and the snapshot records which request
ids were applied but not what each added
(memory.py:104-111). So the file can be discarded whole and
a key cleared with every fact that touched it, but no single edit can be
withdrawn, and
git grep -n -i -E 'remove|delete|undo|revert|rollback|pop\(' -- EngramEdit
finds no verb that tries. The paper treats each embedding "as one
logical vector, abstracting the finite hashed tables" the
architecture uses, and the code does exactly that, so its 5,000-edit
results say nothing about the collisions a write into a real hashed
table would meet.
The distributional escape does not work either. It is tempting to hold that an adapter trained for shape — schema, vocabulary, house style — stores nothing correctable and so escapes all of this. Style adapters demonstrably encode the sources they were trained on; that is why withdrawal requests are made about them at all. Distribution and content are a spectrum, not a boundary, and a system that treats the distinction as a safety argument has made an unmeasured assumption. The build-side consequence is in what I would build, and the two should be read together.