-
Notifications
You must be signed in to change notification settings - Fork 1
How to enable semantic search
Hybrid retrieval (lexical + dense + graph, weights 0.45/0.45/0.10 in in_memory_repository.py:695) over the same store. Measured 2026-08-31: file-level recall@8 = 1.0 on all 16 hand-labeled questions across requests + urllib3 (raw artifacts in docs/).
Embeddings are optional and off by default. The env fallback enables only when BOTH are set:
export CIE_EMBED_DSN="https://integrate.api.nvidia.com/v1" # explicit opt-in
export CIE_EMBED_API_KEY="nvapi-..." # or NVIDIA_API_KEYA bare provider key (NVIDIA_API_KEY alone) never turns network on —
pinned by tests. No key? Everything still works; semantic_search
and the dense leg of hybrid_search degrade to the lexical+graph
signals, and supports_embeddings() reports false.
host core.llm › registered override (register_embed_functions) ›
env-gated fallback › raise. Vectors are computed at index time and
persisted — queries don't re-embed the corpus.
- Model used in the benchmark:
nvidia/nemotron-3-embed-1b(dim 2048) - recall@8 = 1.0 on 16/16 questions; hybrid MRR 0.854 (requests) / 0.781 (urllib3); semantic alone 0.754/0.823 — neither retriever dominates; hybrid's floor is higher
- Index overhead ≈ free at this scale (+0.03s @ 665 nodes)
- Misses are published in the benchmarks doc, not hidden
If code and this wiki disagree, the code wins — then this wiki gets a PR. Evidence lives in the repo, not here.
Start
How-tos
- Install & serve to your MCP client
- Choose your storage backend
- Run the Neo4j team mode
- Index & keep it fresh
- Ask impact questions
- Task & QA layer
- Semantic search
- Snapshot or serve HTTP
- Policies & the write boundary
- Troubleshoot
Reference
- Extraction pipeline
- Data model
- Tool reference
- Benchmarks
- Security & determinism
- Two tiers · Project layout · Docs index
Contribute