1 - Runtime loop
Capture and active use
Hermes lifecycle hooks, bounded injection, explicit identity, completed-turn sync, pre-compression, correction tools, and failure-soft behavior.
The supplied list contains 25 links representing 24 unique systems, plus a pinned Memory-OS rulebook. We will measure whether an agent captures, retrieves, recognizes, uses, revises, links, and explains memory during real work.
A good database cannot pass with weak agent use, and a good injection rule is not mistaken for a complete memory system.
Hermes lifecycle hooks, bounded injection, explicit identity, completed-turn sync, pre-compression, correction tools, and failure-soft behavior.
Facts and episodes, provenance, temporal correction, isolation, portability, inspectability, local-first operation, and predictable latency.
Discover relationships, combine evidence, propose higher-order memories, supersede stale claims, and leave human-readable receipts.
This preserves what made the fabric approach reliable without hard-coding one provider's block names forever.
The agent identifies the canonical envelope and memory IDs it used before acting.
A trace proves recall materially changed a decision; retrieving text alone fails.
Updates carry provenance, scope, evidence type, and reason - never an opaque transcript dump.
New facts supersede or qualify old ones while retaining temporal history.
Derived memories cite their sources and remain reviewable.
A dashboard, open notes, or evidence browser shows what exists and why it was recalled.
Personal, Nagato, game, and candidate namespaces cannot bleed through search or maintenance.
Adapters, export, backup, delete, and replay tests prevent irreversible lock-in.
Disposition is test priority, not a verdict. Older findings are dated 29 June; six newcomers were checked against their current repository documentation on 25 July.
| System | Shape / value | Disposition |
|---|---|---|
| Mnemosyne | Hermes providerSQLitedashboard Known-good lifecycle baseline. | Run first - control |
| Engraphis | local enginegraph Inspectable recall, temporal history, proactive packets, consolidation, and code links. | Run first |
| SMRITI (vn-envy) | SQLitetemporal Episodes plus facts, supersession, multi-channel retrieval, offline tests. | Run first |
| mind | one-filedream cycle Deterministic graph, provenance, aging, consolidation receipts. | Run first |
| Open Second Brain | Hermes provideropen notes Human-readable control with a heavier Bun/Node surface. | Run first |
| Honcho | servicereasoning Direct reference for the desired theory-of-mind direction. | Run first |
| ctx | MCPDream Mode Autonomous cross-referencing, stale detection, temporal gravity, tenant scopes. | Architecture challenger |
| Cognee | platformknowledge graph Serious reasoning platform with a heavier envelope. | Architecture challenger |
| Hindsight | service Strong retain/recall concepts; infrastructure cost is part of the test. | Architecture challenger |
| Ariadne | Hermes provider Promising native shape; packaging/path defects need recheck. | Integration challenger |
| engRAM | Hermesencryptedoffline Bundled embeddings and encrypted RAM-indexed vault. | Privacy challenger |
| HyAtlas Memory | Hermes providergraph/vector Broad capability, heavier dependencies. | Second screen |
| SuperLocalMemory | Hermes provider License, dependency, and documentation risks. | Risk screen |
| Memory-OS | runtime modrulebook Mandatory pre-action protocol is design evidence. | Pattern donor |
| agent-memory-skill | skillgovernance Authority and provenance patterns. | Pattern donor |
| hermes-memlock | companion Lifecycle and safety ideas rather than a store. | Adapter donor |
| Rhizome | knowledge vault Project knowledge rather than full conversational memory. | Artifact screen |
| Unforgit | repo memory Useful coding context; narrower than Nagato's needs. | Artifact screen |
| Context MCP | project context Context utility, not a full learning loop. | Artifact screen |
| smriti (thelonewolf) | young MCP Distinct from vn-envy's project. | Quick screen |
| Noshy | MCP utility Small surface; unlikely to cover the lifecycle alone. | Quick screen |
| remember | tool/library Simple surface; earlier license ambiguity. | Risk screen |
| dyadcore | component Building block, not a complete provider. | Component donor |
| edgeless-memory | library Basic component with little active-use evidence. | Quick screen |
The first wave contains different architectures so we can discover which shape works.
Canonical envelopes, lifecycle adapter, rubric, privacy fixtures, corrections, negative-relevance cases, and trace receipts.
License, Windows, offline posture, isolation, export/delete, activity, weight, integration, and failure behavior.
Mnemosyne, Engraphis, vn-SMRITI, mind, Open Second Brain, and Honcho. ctx or Cognee can displace a lane on evidence.
Game and development scenarios test changed decisions, corrections, synthesis, irrelevant recall, restart, and restore.
The winner runs behind the provider boundary with isolated candidate state and no live memory import.
These notes remain requirements even when their originating system is eliminated.
Research and disposable tests do not require downtime. Live changes remain behind explicit approval.
I will return after the executable first wave if the evidence exposes a real product tradeoff. A maintenance window is needed only after disposable Nagato integration passes and a concrete cutover plus rollback package exists. Personal Hermes, Nagato Hermes, GTC, and the bridge will not be restarted or repointed before that checkpoint.