echo-mem 0.5.2__tar.gz → 0.5.3__tar.gz

{echo_mem-0.5.2/src/echo_mem.egg-info → echo_mem-0.5.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: echo-mem
-Version: 0.5.2
+Version: 0.5.3
 Summary: A long-horizon memory architecture for AI agents
 License-Expression: BUSL-1.1
 Requires-Python: >=3.11
@@ -94,6 +94,8 @@ echo-memory export                 # everything, as JSON
 echo-memory install --for cursor   # wire one client, project scoped
 echo-memory adopt                  # wire every MCP client on the machine, each with its own id
 
+echo-memory infer-causal-hints     # type the facts whose own sentence states a cause (dry run)
+
 echo-memory eval                   # retrieval quality against your own store
 echo-memory eval --context         # what a recall costs against injecting everything
 echo-memory eval --context --sweep # the same, as a curve across corpus size
@@ -138,13 +140,30 @@ this happen" is an ordered chain and similarity cannot produce one. "A led_to B"
 caused_by A" are one claim written from opposite ends, and both assemble into the same
 chain.
 
-A fact with no hint is associative, which is the default and usually correct. Facts
-written before 0.5.0 have no hint and are not a gap to fix. An empty answer from
-`trace_cause` says which kind of empty it is: nobody recorded a cause here is a
-different fact about a store than there are no chains.
+A fact with no hint is associative, which is the default and usually correct. An empty
+answer from `trace_cause` says which kind of empty it is: nobody recorded a cause here is
+a different fact about a store than there are no chains.
+
+**Filling it in, for a store that predates it.** Facts written before 0.5.0 carry no
+hint, so on an existing store `trace_cause` has nothing to walk.
+`echo-memory infer-causal-hints` re-reads the fact text already stored with your own
+model (`ECHO_MEMORY_LLM_API_KEY`, `ECHO_MEMORY_LLM_MODEL`) and types the edges whose own
+sentence states the relation. Dry run by default; `--write` applies what it printed and
+`--clear --write` takes it back.
+
+This is extraction done late, not causal discovery, and the difference is enforced rather
+than promised. A sentence with no causal connective is never sent to a model, so
+co-occurrence is refused before it costs anything. Every proposal has to quote the words
+that state the relation, and a quote that is not literally in the fact is dropped, so a
+model reasoning from the world instead of reading the sentence gets nothing stored. Each
+hint written is audited and marked as extracted late, which is what makes `--clear`
+able to remove exactly these and never one you wrote at write time.
 
 **No inference on the write path.** Extraction happens in the calling agent, so storing
-a memory invokes no model on the server. The cost moved rather than vanished: the agent
+a memory invokes no model on the server. `infer-causal-hints` above is not an exception
+to that and is worth being precise about: it is a command a person types against facts
+already stored, it never runs as part of a write, a migration or a hook, and a store that
+never runs it never causes a model call. The cost moved rather than vanished: the agent
 has to arrive with entities and facts already extracted, which is what the
 [tool contract](docs/DEVELOPMENT.md) spells out. The comparison that makes this matter is
 Zep/Graphiti, the closest architectural match, whose own description of ingestion is that
@@ -169,8 +188,8 @@ difference nobody sized is not a result.
 |---|---|---|
 | Context per recall vs injecting everything | **96.7% less**, hit@10 0.872 over 1,190 questions | `echo-memory eval --context` |
 | The same saving across 8x of corpus growth | 75.5% at 32 facts rising to **96.4% at 261**, hit@10 0.900 to 0.946 | `echo-memory eval --context --sweep` |
-| LoCoMo retrieval, 1,982 questions, 5,882 turns | recall@10 **0.601**, hit@10 0.658, MRR 0.460 | `scripts/locomo-bench.py` |
-| LongMemEval retrieval, 90 questions, 15 per type | session@10 **0.940**, turn@10 0.727 | `scripts/longmemeval-bench.py --per-type 15` |
+| LoCoMo retrieval, 1,982 questions, 5,882 turns | recall@10 **0.601**, hit@10 0.658, MRR 0.460, session@10 0.850 | `echo-memory eval-external locomo` |
+| LongMemEval retrieval, 90 questions, 15 per type | session@10 **0.937**, recall@10 0.727, MRR 0.428 | `echo-memory eval-external longmemeval --per-type 15` |
 | Server side model calls per write | **0** | `echo-memory benchmark` |
 | Write, query, digest latency (median) | 15ms, 8ms, 1ms | `echo-memory benchmark` |
 | Entity resolution AUC | 0.666, 95% CI [0.421, 0.881] | `echo-memory calibrate` |

{echo_mem-0.5.2 → echo_mem-0.5.3}/README.md

@@ -71,6 +71,8 @@ echo-memory export                 # everything, as JSON
 echo-memory install --for cursor   # wire one client, project scoped
 echo-memory adopt                  # wire every MCP client on the machine, each with its own id
 
+echo-memory infer-causal-hints     # type the facts whose own sentence states a cause (dry run)
+
 echo-memory eval                   # retrieval quality against your own store
 echo-memory eval --context         # what a recall costs against injecting everything
 echo-memory eval --context --sweep # the same, as a curve across corpus size
@@ -115,13 +117,30 @@ this happen" is an ordered chain and similarity cannot produce one. "A led_to B"
 caused_by A" are one claim written from opposite ends, and both assemble into the same
 chain.
 
-A fact with no hint is associative, which is the default and usually correct. Facts
-written before 0.5.0 have no hint and are not a gap to fix. An empty answer from
-`trace_cause` says which kind of empty it is: nobody recorded a cause here is a
-different fact about a store than there are no chains.
+A fact with no hint is associative, which is the default and usually correct. An empty
+answer from `trace_cause` says which kind of empty it is: nobody recorded a cause here is
+a different fact about a store than there are no chains.
+
+**Filling it in, for a store that predates it.** Facts written before 0.5.0 carry no
+hint, so on an existing store `trace_cause` has nothing to walk.
+`echo-memory infer-causal-hints` re-reads the fact text already stored with your own
+model (`ECHO_MEMORY_LLM_API_KEY`, `ECHO_MEMORY_LLM_MODEL`) and types the edges whose own
+sentence states the relation. Dry run by default; `--write` applies what it printed and
+`--clear --write` takes it back.
+
+This is extraction done late, not causal discovery, and the difference is enforced rather
+than promised. A sentence with no causal connective is never sent to a model, so
+co-occurrence is refused before it costs anything. Every proposal has to quote the words
+that state the relation, and a quote that is not literally in the fact is dropped, so a
+model reasoning from the world instead of reading the sentence gets nothing stored. Each
+hint written is audited and marked as extracted late, which is what makes `--clear`
+able to remove exactly these and never one you wrote at write time.
 
 **No inference on the write path.** Extraction happens in the calling agent, so storing
-a memory invokes no model on the server. The cost moved rather than vanished: the agent
+a memory invokes no model on the server. `infer-causal-hints` above is not an exception
+to that and is worth being precise about: it is a command a person types against facts
+already stored, it never runs as part of a write, a migration or a hook, and a store that
+never runs it never causes a model call. The cost moved rather than vanished: the agent
 has to arrive with entities and facts already extracted, which is what the
 [tool contract](docs/DEVELOPMENT.md) spells out. The comparison that makes this matter is
 Zep/Graphiti, the closest architectural match, whose own description of ingestion is that
@@ -146,8 +165,8 @@ difference nobody sized is not a result.
 |---|---|---|
 | Context per recall vs injecting everything | **96.7% less**, hit@10 0.872 over 1,190 questions | `echo-memory eval --context` |
 | The same saving across 8x of corpus growth | 75.5% at 32 facts rising to **96.4% at 261**, hit@10 0.900 to 0.946 | `echo-memory eval --context --sweep` |
-| LoCoMo retrieval, 1,982 questions, 5,882 turns | recall@10 **0.601**, hit@10 0.658, MRR 0.460 | `scripts/locomo-bench.py` |
-| LongMemEval retrieval, 90 questions, 15 per type | session@10 **0.940**, turn@10 0.727 | `scripts/longmemeval-bench.py --per-type 15` |
+| LoCoMo retrieval, 1,982 questions, 5,882 turns | recall@10 **0.601**, hit@10 0.658, MRR 0.460, session@10 0.850 | `echo-memory eval-external locomo` |
+| LongMemEval retrieval, 90 questions, 15 per type | session@10 **0.937**, recall@10 0.727, MRR 0.428 | `echo-memory eval-external longmemeval --per-type 15` |
 | Server side model calls per write | **0** | `echo-memory benchmark` |
 | Write, query, digest latency (median) | 15ms, 8ms, 1ms | `echo-memory benchmark` |
 | Entity resolution AUC | 0.666, 95% CI [0.421, 0.881] | `echo-memory calibrate` |

{echo_mem-0.5.2 → echo_mem-0.5.3}/pyproject.toml

@@ -6,7 +6,7 @@
 # (`-m echo_memory.server`) and every existing install reference it, and
 # renaming the module would break live configuration to fix a cosmetic mismatch.
 name = "echo-mem"
-version = "0.5.2"
+version = "0.5.3"
 description = "A long-horizon memory architecture for AI agents"
 readme = "README.md"
 # BUSL-1.1 is the SPDX identifier for the Business Source License 1.1, so

{echo_mem-0.5.2 → echo_mem-0.5.3/src/echo_mem.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: echo-mem
-Version: 0.5.2
+Version: 0.5.3
 Summary: A long-horizon memory architecture for AI agents
 License-Expression: BUSL-1.1
 Requires-Python: >=3.11
@@ -94,6 +94,8 @@ echo-memory export                 # everything, as JSON
 echo-memory install --for cursor   # wire one client, project scoped
 echo-memory adopt                  # wire every MCP client on the machine, each with its own id
 
+echo-memory infer-causal-hints     # type the facts whose own sentence states a cause (dry run)
+
 echo-memory eval                   # retrieval quality against your own store
 echo-memory eval --context         # what a recall costs against injecting everything
 echo-memory eval --context --sweep # the same, as a curve across corpus size
@@ -138,13 +140,30 @@ this happen" is an ordered chain and similarity cannot produce one. "A led_to B"
 caused_by A" are one claim written from opposite ends, and both assemble into the same
 chain.
 
-A fact with no hint is associative, which is the default and usually correct. Facts
-written before 0.5.0 have no hint and are not a gap to fix. An empty answer from
-`trace_cause` says which kind of empty it is: nobody recorded a cause here is a
-different fact about a store than there are no chains.
+A fact with no hint is associative, which is the default and usually correct. An empty
+answer from `trace_cause` says which kind of empty it is: nobody recorded a cause here is
+a different fact about a store than there are no chains.
+
+**Filling it in, for a store that predates it.** Facts written before 0.5.0 carry no
+hint, so on an existing store `trace_cause` has nothing to walk.
+`echo-memory infer-causal-hints` re-reads the fact text already stored with your own
+model (`ECHO_MEMORY_LLM_API_KEY`, `ECHO_MEMORY_LLM_MODEL`) and types the edges whose own
+sentence states the relation. Dry run by default; `--write` applies what it printed and
+`--clear --write` takes it back.
+
+This is extraction done late, not causal discovery, and the difference is enforced rather
+than promised. A sentence with no causal connective is never sent to a model, so
+co-occurrence is refused before it costs anything. Every proposal has to quote the words
+that state the relation, and a quote that is not literally in the fact is dropped, so a
+model reasoning from the world instead of reading the sentence gets nothing stored. Each
+hint written is audited and marked as extracted late, which is what makes `--clear`
+able to remove exactly these and never one you wrote at write time.
 
 **No inference on the write path.** Extraction happens in the calling agent, so storing
-a memory invokes no model on the server. The cost moved rather than vanished: the agent
+a memory invokes no model on the server. `infer-causal-hints` above is not an exception
+to that and is worth being precise about: it is a command a person types against facts
+already stored, it never runs as part of a write, a migration or a hook, and a store that
+never runs it never causes a model call. The cost moved rather than vanished: the agent
 has to arrive with entities and facts already extracted, which is what the
 [tool contract](docs/DEVELOPMENT.md) spells out. The comparison that makes this matter is
 Zep/Graphiti, the closest architectural match, whose own description of ingestion is that
@@ -169,8 +188,8 @@ difference nobody sized is not a result.
 |---|---|---|
 | Context per recall vs injecting everything | **96.7% less**, hit@10 0.872 over 1,190 questions | `echo-memory eval --context` |
 | The same saving across 8x of corpus growth | 75.5% at 32 facts rising to **96.4% at 261**, hit@10 0.900 to 0.946 | `echo-memory eval --context --sweep` |
-| LoCoMo retrieval, 1,982 questions, 5,882 turns | recall@10 **0.601**, hit@10 0.658, MRR 0.460 | `scripts/locomo-bench.py` |
-| LongMemEval retrieval, 90 questions, 15 per type | session@10 **0.940**, turn@10 0.727 | `scripts/longmemeval-bench.py --per-type 15` |
+| LoCoMo retrieval, 1,982 questions, 5,882 turns | recall@10 **0.601**, hit@10 0.658, MRR 0.460, session@10 0.850 | `echo-memory eval-external locomo` |
+| LongMemEval retrieval, 90 questions, 15 per type | session@10 **0.937**, recall@10 0.727, MRR 0.428 | `echo-memory eval-external longmemeval --per-type 15` |
 | Server side model calls per write | **0** | `echo-memory benchmark` |
 | Write, query, digest latency (median) | 15ms, 8ms, 1ms | `echo-memory benchmark` |
 | Entity resolution AUC | 0.666, 95% CI [0.421, 0.881] | `echo-memory calibrate` |

{echo_mem-0.5.2 → echo_mem-0.5.3}/src/echo_mem.egg-info/SOURCES.txt

@@ -25,9 +25,11 @@ src/echo_memory/cli/export.py
 src/echo_memory/cli/graph.py
 src/echo_memory/cli/health.py
 src/echo_memory/cli/hooks.py
+src/echo_memory/cli/infer_causal.py
 src/echo_memory/cli/initdb.py
 src/echo_memory/cli/install.py
 src/echo_memory/cli/judge.py
+src/echo_memory/cli/llm.py
 src/echo_memory/cli/main.py
 src/echo_memory/cli/merge.py
 src/echo_memory/cli/queue.py
@@ -45,6 +47,7 @@ src/echo_memory/cli/trial.py
 src/echo_memory/cli/unmerge.py
 src/echo_memory/cli/why.py
 src/echo_memory/eval/__init__.py
+src/echo_memory/eval/external.py
 src/echo_memory/eval/independent.py
 src/echo_memory/eval/retrieval.py
 src/echo_memory/eval/sweep.py
@@ -89,10 +92,15 @@ src/echo_memory/migrations/versions/0021_delivery_evidence.py
 src/echo_memory/migrations/versions/0022_independent_evaluation.py
 src/echo_memory/migrations/versions/0023_second_judge.py
 src/echo_memory/migrations/versions/0024_node_by_id.py
+src/echo_memory/migrations/versions/0025_lexical_statistics.py
+src/echo_memory/migrations/versions/0026_late_causal_extraction.py
+src/echo_memory/migrations/versions/0027_lexical_staleness_without_a_scan.py
 src/echo_memory/retrieval/__init__.py
+src/echo_memory/retrieval/bm25.py
 src/echo_memory/retrieval/causality.py
 src/echo_memory/retrieval/fusion.py
 src/echo_memory/retrieval/query_memory.py
+src/echo_memory/retrieval/salience.py
 src/echo_memory/skill/SKILL.md
 src/echo_memory/trial/__init__.py
 src/echo_memory/trial/check.py