CASE STUDY · PUBLIC
tdg-rust
A cognitive memory engine in pure Rust: each memory a (Content, Embedding, Telos) node, traversed as a graph and served over MCP. Legacy by operator ruling, green at its pinned gate.
Status ruling legacy but working
Problem
Vector stores flatten memory into similarity search and lose the telos: what a memory is for. The engine modelled memory as a developmental graph instead.
Build
- Memory nodes carry content, embedding and telos, so retrieval can rank by purpose as well as by similarity.
- MCP exposure of the graph: insert, traverse, and query as tool calls, with the e2e paths inside the test suite.
Outcome
- 626 tests passing with zero failures at commit 44e7f9b, every binary summed: 449 in the lib slice, plus MCP e2e, plugin, integration and the smaller binaries.
- The status label is part of the claim: older code, no current maintenance, gate green at the pinned commit. Green is not the same as maintained, and a client inheriting the repository deserves to know it is legacy.
Provenance
| Gate, executed | 626 passed, 0 failed, 1 ignored | cargo test --workspace --no-fail-fast at 44e7f9b, 2026-10-20 |
|---|
Reproduce
Clone the repository, check out 44e7f9b, and run `cargo test --workspace --no-fail-fast`. The lib slice alone reads 449; cite the total with the breakdown, not one slice as the whole.
From the documentation
The current-state document is published with the honest version: v0.5.0 post-optimization, 499 tests, and a plain statement of what the engine is and is not.
CURRENT-STATE.md, repository docs (not published: guard-excluded)
A teleological developmental graph described as a metabolism rather than a database is a deliberate design position, and the document states it in those words so nobody reads it as a storage engine.
CURRENT-STATE.md, repository docs (not published: guard-excluded)
The suite figure carries its ignored test as an ignored test (626 passed, 1 ignored) rather than dropping it, the same class-labelling rule the register uses.
register row, 44e7f9b