|
| 1 | +# Vectorize Agent Memory Benchmark PR |
| 2 | + |
| 3 | +## Target |
| 4 | + |
| 5 | +- Repository: `https://github.com/vectorize-io/agent-memory-benchmark` |
| 6 | +- PR: `https://github.com/vectorize-io/agent-memory-benchmark/pull/25` |
| 7 | +- Fork: `https://github.com/TerminallyLazy/agent-memory-benchmark` |
| 8 | +- Branch: `add-tree-ring-provider` |
| 9 | +- Commit: `00408ae3acd63127cef87189f353f86932a6e2fd` |
| 10 | +- Evidence comment: |
| 11 | + `https://github.com/TerminallyLazy/Tree-Ring-Memory/issues/26#issuecomment-4916501736` |
| 12 | + |
| 13 | +## Placement |
| 14 | + |
| 15 | +- Added `src/memory_bench/memory/tree_ring.py`. |
| 16 | +- Registered `tree-ring` in `src/memory_bench/memory/__init__.py`. |
| 17 | +- Added the static `catalog.json` provider entry. |
| 18 | +- Added the README setup note for `TREE_RING_BIN`. |
| 19 | + |
| 20 | +## Copy |
| 21 | + |
| 22 | +The PR positions Tree Ring Memory as a runnable local provider for AMB rather |
| 23 | +than a directory listing. It deliberately avoids claiming any benchmark score. |
| 24 | + |
| 25 | +## Validation |
| 26 | + |
| 27 | +- Checked upstream PRs and issues for existing Tree Ring Memory references. |
| 28 | +- Built the local Tree Ring CLI with `cargo build -p tree-ring-memory-cli`. |
| 29 | +- Ran `python3 -m compileall src/memory_bench/memory/tree_ring.py |
| 30 | + src/memory_bench/memory/__init__.py`. |
| 31 | +- Ran `uv run omb providers` and verified `tree-ring` appears. |
| 32 | +- Generated the AMB catalog and verified the `tree-ring` provider entry. |
| 33 | +- Ran a local ingest and scoped recall smoke with |
| 34 | + `TREE_RING_BIN=/Users/lazy/Projects/Tree_Ring_Memory/target/debug/tree-ring`. |
| 35 | +- Ran `git diff --check`. |
| 36 | +- Verified PR state: open, ready, mergeable. |
| 37 | +- Check status: no checks reported. |
| 38 | + |
| 39 | +## Notes |
| 40 | + |
| 41 | +This is a stronger outreach surface than another awesome-list entry because it |
| 42 | +puts Tree Ring Memory into an apples-to-apples agent-memory benchmark harness. |
| 43 | +The adapter uses JSONL import for benchmark documents, maps AMB `user_id` to |
| 44 | +Tree Ring `project`, and uses `tree-ring recall --include-sensitive` for |
| 45 | +personal-context benchmarks while leaving Tree Ring's secret-like import block |
| 46 | +intact. |
0 commit comments