echo-mem 0.1.0__tar.gz

echo_mem-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

echo_mem-0.1.0/PKG-INFO

@@ -0,0 +1,140 @@
+Metadata-Version: 2.4
+Name: echo-mem
+Version: 0.1.0
+Summary: A long-horizon memory architecture for AI agents
+License-Expression: Apache-2.0
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: psycopg[binary]<4,>=3.2
+Requires-Dist: psycopg-pool<4,>=3.2
+Requires-Dist: pgvector<1,>=0.3
+Requires-Dist: alembic<2,>=1.13
+Requires-Dist: sqlalchemy<3,>=2
+Requires-Dist: mcp<3,>=2.0
+Requires-Dist: sentence-transformers<4,>=3
+Provides-Extra: dev
+Requires-Dist: pytest<9,>=8; extra == "dev"
+Requires-Dist: ruff<1,>=0.6; extra == "dev"
+Requires-Dist: build<2,>=1; extra == "dev"
+Requires-Dist: twine<7,>=5; extra == "dev"
+Dynamic: license-file
+
+# Echo Memory
+
+A long-horizon memory architecture for AI agents. Echo Memory is built to remember
+everything an agent has ever learned, in the best possible way, and to keep fetching and
+writing that memory efficiently no matter how much history accumulates, for coding
+tools, chatbots, DevOps agents, or any other agentic system, local or deployed.
+
+## Why
+
+Every AI agent starts from zero unless something remembers what happened last time, and
+remembers it well enough and fast enough to still be useful after months or years of
+accumulated history. Most memory tools solve short-term recall with plain vector search
+over stored facts. That degrades as history grows: more candidates, more noise, slower
+retrieval. Echo Memory is built around the read/write algorithm and the data structure
+that keeps working at long horizons, not just at day one:
+
+- **A temporal, self-consolidating memory graph.** Facts are edges between entities, not
+  flat vector rows. Old, rarely-accessed memory doesn't just accumulate: it gets
+  consolidated into higher-level summaries over time (never deleted, always traceable
+  back to the original), so retrieval cost stays bounded by what's *currently relevant*,
+  not by everything that's *ever* been written. See
+  [`docs/designs/echo-memory-design.md`](docs/designs/echo-memory-design.md#long-horizon-memory-architecture)
+  for the actual mechanism.
+- **Real graph structure, not just similarity.** Multi-hop queries like "how did we end
+  up here?", answerable because facts are connected, not just individually embedded.
+- **Causal typing, not just similarity.** Edges can be tagged `caused_by`, `led_to`,
+  `blocked_by`, `contradicts`, set by the agent's own read of the conversation, not
+  inferred statistically. Honest about what's tractable today and what isn't.
+- **Auditable by design.** Every change to memory is logged, with a plain-language reason
+  you can read back (`echo-memory why <fact_id>`). Memory that consolidates and edits
+  itself is only trustworthy if you can see why.
+- **A write path that costs nothing to run.** Extraction happens in the calling agent,
+  never on the server, so recording a memory makes zero LLM calls. Measured locally with
+  `echo-memory benchmark`: **write 15ms median, query 8ms, digest 1ms, $0.00 inference
+  cost per episode.** The tradeoff is explicit and worth stating: the agent must arrive
+  with entities and facts already extracted, which is more work for the caller and the
+  reason the [MCP tool contract](docs/DEVELOPMENT.md) spells the shape out. The
+  comparison that makes this matter is Zep/Graphiti, the closest architectural match
+  (bi-temporal edges, fact invalidation, episode provenance): its own published
+  description of ingestion is that "every episode triggers multiple LLM calls for
+  extraction, entity resolution, and invalidation" and that "write cost scales with
+  volume". Here it doesn't.
+- **One storage engine, every scale.** Postgres + pgvector + Apache AGE, from a single
+  local agent up to an organization-wide shared graph spanning every agent a business
+  runs. No forced migration later. (The novel work is the memory structure and algorithm
+  running on top of Postgres, not a new database engine; see the design doc for why.)
+- **Any agent, not one vendor's.** The interface is [MCP](https://modelcontextprotocol.io):
+  any MCP-compatible agent can read and write the same memory graph, whether that's a
+  coding assistant, a chatbot, an ops agent, or something built in-house.
+
+## Who this is for
+
+- **A developer running local agents** who wants Claude Code, Cursor, or anything else to
+  stop losing context between sessions and tools.
+- **A team or organization running agentic systems in production** (support bots, DevOps
+  agents, internal tooling) that needs a shared memory layer instead of N disconnected
+  ones, with the tenancy model (below) to keep it scoped correctly per agent, per team, or
+  org-wide.
+
+## Status
+
+Early and staged. See [`docs/designs/`](docs/designs/) for the full architecture and the
+v1a → v1b build plan. **The validated wedge driving v1a is specifically cross-tool coding
+agent memory** (the founder's own daily pain, real and tested). The broader vision above
+is the target this architecture is built toward, not yet something v1a itself proves. v1a
+proves basic recall works before v1b adds causal typing and multi-hop graph retrieval, and
+before v1.1 adds the org-wide tenancy the broader vision depends on.
+
+## Getting started
+
+The core recall loop is built and running: `write_episode`, `query_memory`,
+`get_audit_log`, an MCP server wiring them together, and an `echo-memory` CLI (`why`,
+`export`). Full setup is in [`docs/DEVELOPMENT.md`](docs/DEVELOPMENT.md); short version:
+
+```bash
+git clone git@github.com:ayushcodes10/echo-mem.git && cd echo-mem
+docker compose up -d                       # Postgres + pgvector + Apache AGE
+python -m venv .venv && source .venv/bin/activate && pip install -e ".[dev]"
+alembic upgrade head
+
+claude mcp add --scope user echo-memory \
+  -e ECHO_MEMORY_USER_ID=your-user-id \
+  -e ECHO_MEMORY_AGENT_ID=claude-code \
+  -e ECHO_MEMORY_DATABASE_URL="postgresql://postgres:postgres@localhost:5433/echo_memory" \
+  -- "$(pwd)/.venv/bin/python" -m echo_memory.server
+```
+
+Start a new Claude Code session and `write_episode`/`query_memory`/`get_audit_log` are
+available across every project, not just this repo.
+
+Prefer it scoped to one project - a single Claude project, a Cursor workspace, a repo
+whose memory shouldn't mingle with the rest? `echo-memory install [path] --for
+claude|cursor|both` writes a project-scoped MCP config plus a skill (or, for Cursor, an
+always-applied rule) telling the agent when to record and when to recall. See
+[`docs/DEVELOPMENT.md`](docs/DEVELOPMENT.md) for Cursor/per-repo setup, the
+`echo-memory` CLI, and running tests; see
+[`docs/INTEGRATIONS.md`](docs/INTEGRATIONS.md) for using Echo Memory from an agent
+that doesn't speak MCP (a chatbot, a DevOps agent, a booking agent, or any custom
+tool-calling loop); and see
+[`docs/designs/echo-memory-design.md`](docs/designs/echo-memory-design.md) for the
+current build plan and progress.
+
+## Architecture
+
+- **Storage:** PostgreSQL with the `pgvector` and Apache AGE extensions
+- **Retrieval:** hybrid vector + full-text search (v1a), with Personalized PageRank via
+  `networkx` added in v1b for multi-hop associative retrieval
+- **Interface:** [Model Context Protocol](https://modelcontextprotocol.io) server:
+  `write_episode`, `query_memory`, `get_audit_log`
+
+## Contributing
+
+See [`CONTRIBUTING.md`](CONTRIBUTING.md). Issues and PRs welcome; please read the design
+docs first so proposals fit the staged build plan.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE).

echo_mem-0.1.0/README.md

@@ -0,0 +1,118 @@
+# Echo Memory
+
+A long-horizon memory architecture for AI agents. Echo Memory is built to remember
+everything an agent has ever learned, in the best possible way, and to keep fetching and
+writing that memory efficiently no matter how much history accumulates, for coding
+tools, chatbots, DevOps agents, or any other agentic system, local or deployed.
+
+## Why
+
+Every AI agent starts from zero unless something remembers what happened last time, and
+remembers it well enough and fast enough to still be useful after months or years of
+accumulated history. Most memory tools solve short-term recall with plain vector search
+over stored facts. That degrades as history grows: more candidates, more noise, slower
+retrieval. Echo Memory is built around the read/write algorithm and the data structure
+that keeps working at long horizons, not just at day one:
+
+- **A temporal, self-consolidating memory graph.** Facts are edges between entities, not
+  flat vector rows. Old, rarely-accessed memory doesn't just accumulate: it gets
+  consolidated into higher-level summaries over time (never deleted, always traceable
+  back to the original), so retrieval cost stays bounded by what's *currently relevant*,
+  not by everything that's *ever* been written. See
+  [`docs/designs/echo-memory-design.md`](docs/designs/echo-memory-design.md#long-horizon-memory-architecture)
+  for the actual mechanism.
+- **Real graph structure, not just similarity.** Multi-hop queries like "how did we end
+  up here?", answerable because facts are connected, not just individually embedded.
+- **Causal typing, not just similarity.** Edges can be tagged `caused_by`, `led_to`,
+  `blocked_by`, `contradicts`, set by the agent's own read of the conversation, not
+  inferred statistically. Honest about what's tractable today and what isn't.
+- **Auditable by design.** Every change to memory is logged, with a plain-language reason
+  you can read back (`echo-memory why <fact_id>`). Memory that consolidates and edits
+  itself is only trustworthy if you can see why.
+- **A write path that costs nothing to run.** Extraction happens in the calling agent,
+  never on the server, so recording a memory makes zero LLM calls. Measured locally with
+  `echo-memory benchmark`: **write 15ms median, query 8ms, digest 1ms, $0.00 inference
+  cost per episode.** The tradeoff is explicit and worth stating: the agent must arrive
+  with entities and facts already extracted, which is more work for the caller and the
+  reason the [MCP tool contract](docs/DEVELOPMENT.md) spells the shape out. The
+  comparison that makes this matter is Zep/Graphiti, the closest architectural match
+  (bi-temporal edges, fact invalidation, episode provenance): its own published
+  description of ingestion is that "every episode triggers multiple LLM calls for
+  extraction, entity resolution, and invalidation" and that "write cost scales with
+  volume". Here it doesn't.
+- **One storage engine, every scale.** Postgres + pgvector + Apache AGE, from a single
+  local agent up to an organization-wide shared graph spanning every agent a business
+  runs. No forced migration later. (The novel work is the memory structure and algorithm
+  running on top of Postgres, not a new database engine; see the design doc for why.)
+- **Any agent, not one vendor's.** The interface is [MCP](https://modelcontextprotocol.io):
+  any MCP-compatible agent can read and write the same memory graph, whether that's a
+  coding assistant, a chatbot, an ops agent, or something built in-house.
+
+## Who this is for
+
+- **A developer running local agents** who wants Claude Code, Cursor, or anything else to
+  stop losing context between sessions and tools.
+- **A team or organization running agentic systems in production** (support bots, DevOps
+  agents, internal tooling) that needs a shared memory layer instead of N disconnected
+  ones, with the tenancy model (below) to keep it scoped correctly per agent, per team, or
+  org-wide.
+
+## Status
+
+Early and staged. See [`docs/designs/`](docs/designs/) for the full architecture and the
+v1a → v1b build plan. **The validated wedge driving v1a is specifically cross-tool coding
+agent memory** (the founder's own daily pain, real and tested). The broader vision above
+is the target this architecture is built toward, not yet something v1a itself proves. v1a
+proves basic recall works before v1b adds causal typing and multi-hop graph retrieval, and
+before v1.1 adds the org-wide tenancy the broader vision depends on.
+
+## Getting started
+
+The core recall loop is built and running: `write_episode`, `query_memory`,
+`get_audit_log`, an MCP server wiring them together, and an `echo-memory` CLI (`why`,
+`export`). Full setup is in [`docs/DEVELOPMENT.md`](docs/DEVELOPMENT.md); short version:
+
+```bash
+git clone git@github.com:ayushcodes10/echo-mem.git && cd echo-mem
+docker compose up -d                       # Postgres + pgvector + Apache AGE
+python -m venv .venv && source .venv/bin/activate && pip install -e ".[dev]"
+alembic upgrade head
+
+claude mcp add --scope user echo-memory \
+  -e ECHO_MEMORY_USER_ID=your-user-id \
+  -e ECHO_MEMORY_AGENT_ID=claude-code \
+  -e ECHO_MEMORY_DATABASE_URL="postgresql://postgres:postgres@localhost:5433/echo_memory" \
+  -- "$(pwd)/.venv/bin/python" -m echo_memory.server
+```
+
+Start a new Claude Code session and `write_episode`/`query_memory`/`get_audit_log` are
+available across every project, not just this repo.
+
+Prefer it scoped to one project - a single Claude project, a Cursor workspace, a repo
+whose memory shouldn't mingle with the rest? `echo-memory install [path] --for
+claude|cursor|both` writes a project-scoped MCP config plus a skill (or, for Cursor, an
+always-applied rule) telling the agent when to record and when to recall. See
+[`docs/DEVELOPMENT.md`](docs/DEVELOPMENT.md) for Cursor/per-repo setup, the
+`echo-memory` CLI, and running tests; see
+[`docs/INTEGRATIONS.md`](docs/INTEGRATIONS.md) for using Echo Memory from an agent
+that doesn't speak MCP (a chatbot, a DevOps agent, a booking agent, or any custom
+tool-calling loop); and see
+[`docs/designs/echo-memory-design.md`](docs/designs/echo-memory-design.md) for the
+current build plan and progress.
+
+## Architecture
+
+- **Storage:** PostgreSQL with the `pgvector` and Apache AGE extensions
+- **Retrieval:** hybrid vector + full-text search (v1a), with Personalized PageRank via
+  `networkx` added in v1b for multi-hop associative retrieval
+- **Interface:** [Model Context Protocol](https://modelcontextprotocol.io) server:
+  `write_episode`, `query_memory`, `get_audit_log`
+
+## Contributing
+
+See [`CONTRIBUTING.md`](CONTRIBUTING.md). Issues and PRs welcome; please read the design
+docs first so proposals fit the staged build plan.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE).

echo_mem-0.1.0/pyproject.toml

@@ -0,0 +1,53 @@
+[project]
+# The distribution is "echo-mem", not "echo-memory": that name is already taken
+# on PyPI by an unrelated hosted product in this same category (Textstone Labs,
+# published 2026-03-29), so `pip install echo-memory` installs theirs. The
+# import package stays `echo_memory` - the CLI, the MCP registration command
+# (`-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.1.0"
+description = "A long-horizon memory architecture for AI agents"
+readme = "README.md"
+license = "Apache-2.0"
+requires-python = ">=3.11"
+dependencies = [
+    "psycopg[binary]>=3.2,<4",
+    "psycopg-pool>=3.2,<4",
+    "pgvector>=0.3,<1",
+    "alembic>=1.13,<2",
+    "sqlalchemy>=2,<3",
+    "mcp>=2.0,<3",
+    "sentence-transformers>=3,<4",
+]
+
+[project.scripts]
+echo-memory = "echo_memory.cli.main:main"
+
+[project.optional-dependencies]
+dev = [
+    "pytest>=8,<9",
+    "ruff>=0.6,<1",
+    "build>=1,<2",
+    "twine>=5,<7",
+]
+
+[build-system]
+requires = ["setuptools>=68"]
+build-backend = "setuptools.build_meta"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+"echo_memory.skill" = ["SKILL.md"]
+
+[tool.pytest.ini_options]
+markers = [
+    "eval: retrieval-quality evals against real data (reserved, not in use yet)",
+]
+testpaths = ["tests"]
+
+[tool.ruff]
+line-length = 100
+target-version = "py311"

echo_mem-0.1.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

echo_mem-0.1.0/src/echo_mem.egg-info/PKG-INFO

@@ -0,0 +1,140 @@
+Metadata-Version: 2.4
+Name: echo-mem
+Version: 0.1.0
+Summary: A long-horizon memory architecture for AI agents
+License-Expression: Apache-2.0
+Requires-Python: >=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: psycopg[binary]<4,>=3.2
+Requires-Dist: psycopg-pool<4,>=3.2
+Requires-Dist: pgvector<1,>=0.3
+Requires-Dist: alembic<2,>=1.13
+Requires-Dist: sqlalchemy<3,>=2
+Requires-Dist: mcp<3,>=2.0
+Requires-Dist: sentence-transformers<4,>=3
+Provides-Extra: dev
+Requires-Dist: pytest<9,>=8; extra == "dev"
+Requires-Dist: ruff<1,>=0.6; extra == "dev"
+Requires-Dist: build<2,>=1; extra == "dev"
+Requires-Dist: twine<7,>=5; extra == "dev"
+Dynamic: license-file
+
+# Echo Memory
+
+A long-horizon memory architecture for AI agents. Echo Memory is built to remember
+everything an agent has ever learned, in the best possible way, and to keep fetching and
+writing that memory efficiently no matter how much history accumulates, for coding
+tools, chatbots, DevOps agents, or any other agentic system, local or deployed.
+
+## Why
+
+Every AI agent starts from zero unless something remembers what happened last time, and
+remembers it well enough and fast enough to still be useful after months or years of
+accumulated history. Most memory tools solve short-term recall with plain vector search
+over stored facts. That degrades as history grows: more candidates, more noise, slower
+retrieval. Echo Memory is built around the read/write algorithm and the data structure
+that keeps working at long horizons, not just at day one:
+
+- **A temporal, self-consolidating memory graph.** Facts are edges between entities, not
+  flat vector rows. Old, rarely-accessed memory doesn't just accumulate: it gets
+  consolidated into higher-level summaries over time (never deleted, always traceable
+  back to the original), so retrieval cost stays bounded by what's *currently relevant*,
+  not by everything that's *ever* been written. See
+  [`docs/designs/echo-memory-design.md`](docs/designs/echo-memory-design.md#long-horizon-memory-architecture)
+  for the actual mechanism.
+- **Real graph structure, not just similarity.** Multi-hop queries like "how did we end
+  up here?", answerable because facts are connected, not just individually embedded.
+- **Causal typing, not just similarity.** Edges can be tagged `caused_by`, `led_to`,
+  `blocked_by`, `contradicts`, set by the agent's own read of the conversation, not
+  inferred statistically. Honest about what's tractable today and what isn't.
+- **Auditable by design.** Every change to memory is logged, with a plain-language reason
+  you can read back (`echo-memory why <fact_id>`). Memory that consolidates and edits
+  itself is only trustworthy if you can see why.
+- **A write path that costs nothing to run.** Extraction happens in the calling agent,
+  never on the server, so recording a memory makes zero LLM calls. Measured locally with
+  `echo-memory benchmark`: **write 15ms median, query 8ms, digest 1ms, $0.00 inference
+  cost per episode.** The tradeoff is explicit and worth stating: the agent must arrive
+  with entities and facts already extracted, which is more work for the caller and the
+  reason the [MCP tool contract](docs/DEVELOPMENT.md) spells the shape out. The
+  comparison that makes this matter is Zep/Graphiti, the closest architectural match
+  (bi-temporal edges, fact invalidation, episode provenance): its own published
+  description of ingestion is that "every episode triggers multiple LLM calls for
+  extraction, entity resolution, and invalidation" and that "write cost scales with
+  volume". Here it doesn't.
+- **One storage engine, every scale.** Postgres + pgvector + Apache AGE, from a single
+  local agent up to an organization-wide shared graph spanning every agent a business
+  runs. No forced migration later. (The novel work is the memory structure and algorithm
+  running on top of Postgres, not a new database engine; see the design doc for why.)
+- **Any agent, not one vendor's.** The interface is [MCP](https://modelcontextprotocol.io):
+  any MCP-compatible agent can read and write the same memory graph, whether that's a
+  coding assistant, a chatbot, an ops agent, or something built in-house.
+
+## Who this is for
+
+- **A developer running local agents** who wants Claude Code, Cursor, or anything else to
+  stop losing context between sessions and tools.
+- **A team or organization running agentic systems in production** (support bots, DevOps
+  agents, internal tooling) that needs a shared memory layer instead of N disconnected
+  ones, with the tenancy model (below) to keep it scoped correctly per agent, per team, or
+  org-wide.
+
+## Status
+
+Early and staged. See [`docs/designs/`](docs/designs/) for the full architecture and the
+v1a → v1b build plan. **The validated wedge driving v1a is specifically cross-tool coding
+agent memory** (the founder's own daily pain, real and tested). The broader vision above
+is the target this architecture is built toward, not yet something v1a itself proves. v1a
+proves basic recall works before v1b adds causal typing and multi-hop graph retrieval, and
+before v1.1 adds the org-wide tenancy the broader vision depends on.
+
+## Getting started
+
+The core recall loop is built and running: `write_episode`, `query_memory`,
+`get_audit_log`, an MCP server wiring them together, and an `echo-memory` CLI (`why`,
+`export`). Full setup is in [`docs/DEVELOPMENT.md`](docs/DEVELOPMENT.md); short version:
+
+```bash
+git clone git@github.com:ayushcodes10/echo-mem.git && cd echo-mem
+docker compose up -d                       # Postgres + pgvector + Apache AGE
+python -m venv .venv && source .venv/bin/activate && pip install -e ".[dev]"
+alembic upgrade head
+
+claude mcp add --scope user echo-memory \
+  -e ECHO_MEMORY_USER_ID=your-user-id \
+  -e ECHO_MEMORY_AGENT_ID=claude-code \
+  -e ECHO_MEMORY_DATABASE_URL="postgresql://postgres:postgres@localhost:5433/echo_memory" \
+  -- "$(pwd)/.venv/bin/python" -m echo_memory.server
+```
+
+Start a new Claude Code session and `write_episode`/`query_memory`/`get_audit_log` are
+available across every project, not just this repo.
+
+Prefer it scoped to one project - a single Claude project, a Cursor workspace, a repo
+whose memory shouldn't mingle with the rest? `echo-memory install [path] --for
+claude|cursor|both` writes a project-scoped MCP config plus a skill (or, for Cursor, an
+always-applied rule) telling the agent when to record and when to recall. See
+[`docs/DEVELOPMENT.md`](docs/DEVELOPMENT.md) for Cursor/per-repo setup, the
+`echo-memory` CLI, and running tests; see
+[`docs/INTEGRATIONS.md`](docs/INTEGRATIONS.md) for using Echo Memory from an agent
+that doesn't speak MCP (a chatbot, a DevOps agent, a booking agent, or any custom
+tool-calling loop); and see
+[`docs/designs/echo-memory-design.md`](docs/designs/echo-memory-design.md) for the
+current build plan and progress.
+
+## Architecture
+
+- **Storage:** PostgreSQL with the `pgvector` and Apache AGE extensions
+- **Retrieval:** hybrid vector + full-text search (v1a), with Personalized PageRank via
+  `networkx` added in v1b for multi-hop associative retrieval
+- **Interface:** [Model Context Protocol](https://modelcontextprotocol.io) server:
+  `write_episode`, `query_memory`, `get_audit_log`
+
+## Contributing
+
+See [`CONTRIBUTING.md`](CONTRIBUTING.md). Issues and PRs welcome; please read the design
+docs first so proposals fit the staged build plan.
+
+## License
+
+Apache License 2.0. See [`LICENSE`](LICENSE).