Analysis updated 2026-05-18
Build a RAG system where retrieved context is organized into named categories so the AI has structured, explainable memory.
Add semantic search to a documentation tool where users query with an approximate category path and get relevant results.
Store and retrieve domain-specific knowledge in an AI assistant using a hierarchical category tree instead of a flat vector store.
| grecinto/tensortree | ashutosh-swain-git/dahmer | audriusbutkevicius/gohashcompare | |
|---|---|---|---|
| Stars | 1 | 1 | 1 |
| Language | Go | Go | Go |
| Last pushed | — | — | 2016-07-09 |
| Maintenance | — | — | Dormant |
| Setup difficulty | moderate | easy | moderate |
| Complexity | 3/5 | 1/5 | 2/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
No license stated, run the included demo with `go run ./src/examples/cli_kb_demo` to verify setup.
Most vector databases let you store chunks of text as numerical representations and then search for similar chunks by meaning. TensorTree is a Go library that adds a layer of structure on top of that: rather than storing everything in a flat pile of vectors, you organize knowledge into named categories, nest those categories into a tree hierarchy, and then retrieve content through either the category path or semantic similarity. The practical effect is that a query for something like "Root/Knowledge" can resolve to the more specific stored category "Root/Engineering" because the system compares the meaning of the path components rather than requiring an exact match. This means you do not have to know the precise category names your data was filed under in order to find it. The core technical approach stores items in a tree-indexed structure that the description says provides search speeds proportional to the logarithm of the number of items, meaning searches scale well as the database grows without requiring manual tuning or index rebuilds. Adding new content involves a single vectorization step that converts text to an embedding on demand, there is no separate indexing pipeline to manage. TensorTree is part of a larger system called SOP, and the repository includes a snapshot of the SOP memory subsystem, an architecture document, a conceptual article, and one working command-line demo you can run with a single Go command. The demo creates a small category hierarchy, inserts content, and shows the semantic path matching in action. The project is aimed at use cases where an AI application needs structured memory that is browsable and explainable: RAG pipelines, copilot tools, documentation search, and internal knowledge tools where the category structure itself carries meaning. The README does not state a license.
A Go library that adds hierarchical category structure to semantic vector search, letting you organize knowledge into named trees and retrieve content by either path or meaning without a separate indexing pipeline.
Mainly Go. The stack also includes Go.
Setup difficulty is rated moderate, with roughly 30min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.