Independent use will determine whether Zero-mem provides practical external-memory retrieval for Pi agents without consuming model context for the retrieval process.
state: expiredheat: lowuncertainty: highknownscott: lowagent-memory memory-retrieval llm-toolingskorotkiewicz
What is this?
Zero-Mem is presented as an external-memory framework for LLM agents that preserves original interaction traces and retrieves evidence through an entity-context graph and temporal hierarchy rather than LLM-generated summaries or abstractions. The supplied paper snippet claims no LLM calls or token consumption for memory operations outside final question answering, with 57.6% lower latency than its fastest baseline under an equivalent context budget. The evidence titles attribute a Pi-oriented release to skorotkiewicz, but the snippets do not establish that person’s role, clearly connect the Pi release to the paper, or provide independent real-world validation; practical utility therefore remains unproven here.
Why it matters to Scott
The claimed architecture is already held in Scott’s “Wiki-Graph” position and implemented territory around “dev-wiki — governed multi-territory knowledge engine”: external, graph-routed, source-preserving memory that avoids spending model context on broad reconstruction. Zero-Mem is currently only another unvalidated implementation example; independent Pi usage could eventually inform Scott’s retrieval design, but the supplied evidence does not yet establish performance or practical utility.
ip:concept.wiki-graphdev:project.dev-wikidev:concept.read-only-archive-discovery-ladderradar:concept.agent-memoryradar:person.pi
queries asked of Scott's wikis
- non-generative agent memory retrieval
- agent memory outside the context window
- provenance-preserving memory evidence
- entity graphs and temporal memory hierarchies
- token and latency economics of memory retrieval
- Pi agent persistent project memory
Measured heat
no measured readings yet — the hourly heat pass fills this in
How the heat travelled
no chain yet — the hourly chain pass fills this in
Evidence (2) — ⭐ canonical anchor
Interpretation history
2026-08-10T02:28:23Z
No independent use, benchmark, or implementation evidence emerged within the observation window; the release remains an unvalidated instance of an architecture already familiar to Scott.
2026-08-08T02:26:03Z
Re-evaluation adds no independent usage, benchmark, or implementation evidence; Zero-mem remains an unvalidated example of an architecture already familiar to Scott.
2026-08-08T02:25:10Z
grounded: known/low — The claimed architecture is already held in Scott’s “Wiki-Graph” position and implemented territory around “dev-wiki — governed multi-territory knowledge engine
2026-08-08T02:22:32Z
case created — The linked first-party repository is a concrete agent-memory artifact, but it has no independent usage evidence yet.
Decision trace
- 08-10 12:28expireNo independent use, benchmark, or implementation evidence emerged within the observation window; the release remains an unvalidated instance of an architecture already familiar to Scott.
- 08-10 12:28alert_silentThe only delta is elapsed time without validation, which creates no consequential update for Scott and does not justify further attention.
- 08-10 12:28alert_routeThe only delta is elapsed time without validation, which creates no consequential update for Scott and does not justify further attention.
- 08-08 12:26repriceRe-evaluation adds no independent usage, benchmark, or implementation evidence; Zero-mem remains an unvalidated example of an architecture already familiar to Scott.
- 08-08 12:26alert_silentNothing consequential changed beyond re-observing the original low-attention release, so independent usage or credible practical benchmarks can wait for routine review.
- 08-08 12:26alert_routeNothing consequential changed beyond re-observing the original low-attention release, so independent usage or credible practical benchmarks can wait for routine review.
- 08-08 12:25alert_silentA small implementation release appears to have occurred, but the supplied evidence establishes neither practical retrieval performance nor a meaningful architectural delta from Scott’s existing extern
- 08-08 12:25alert_routeA small implementation release appears to have occurred, but the supplied evidence establishes neither practical retrieval performance nor a meaningful architectural delta from Scott’s existing extern
- 08-08 12:25groundThe claimed architecture is already held in Scott’s “Wiki-Graph” position and implemented territory around “dev-wiki — governed multi-territory knowledge engine”: external, graph-routed, source-preser
- 08-08 12:22createThe linked first-party repository is a concrete agent-memory artifact, but it has no independent usage evidence yet.