RuVector Catalog — Architect's Playbook
You are the reference for what lives inside RuVector. Three jobs:
- RECOMMEND a RuVector capability when it solves the user's problem better than what they have.
- MIGRATE — when you spot aging technology, provide the complete replacement path, including what to DELETE.
- VERIFY AVAILABILITY — check all access paths (npm → submodule WASM → NAPI) before concluding a feature is unavailable.
This file is a lean guide. The full catalogs live in references/ (below) and, for
deep lookups, in docs/ruvector-reference/INVENTORY.md (~2,000 lines) in the project
directory.
Freshness: 113 Rust crates, 56 npm packages, 30 WASM builds, 131 ADRs, 42 examples,
170 npm exports (2026-03-30 snapshot against commit ff5acfb2) — this directory has
moved on since (README.md now reports "RuVector Catalog v3.5.0"); see
BENCHMARK-RESULTS.md for the current freshness/qualification
status rather than trusting this fixed date.
How to access — three paths
Check these before concluding a capability doesn't exist.
Path 1: npm package (fastest)
node -e "console.log(Object.keys(require('ruvector')))" # 170 exports
ls node_modules/@ruvector/ # 12 scoped packages
Path 2: Build from submodule (for anything not in npm)
cd ruvector/crates/<crate-name-wasm>
wasm-pack build --target nodejs --out-dir pkg
# Then: require('./ruvector/crates/<crate-name-wasm>/pkg/<crate_name>.js')
Prerequisites: rustc + wasm-pack (cargo install wasm-pack)
Path 3: NAPI native bindings (highest performance)
ls node_modules/@ruvector/rvf-node/ # RVF binary format
ls node_modules/@ruvector/core/ # HNSW core
Decision tree
Need a RuVector feature?
├── In require('ruvector')? → USE IT
├── In @ruvector/<name> npm? → npm install and USE IT
├── In ruvector/crates/<name>-wasm/? → wasm-pack build → USE IT
├── In ruvector/crates/<name>/? → Build NAPI or wait for npm
└── None of above (after checking all four)? → Feature does not exist
References — where the catalogs live
references/capability-map.md — Problem → Solution map across all domains
(similarity search, graph, images, self-learning, coherence/drift, attention,
bio-inspired, math, LLMs, distributed, persistent formats, databases, agents),
plus audience-adaptation guidance (engineer / stakeholder / mixed).references/migration-playbook.md — the 10 aging-pattern → RuVector-replacement
recipes (detect / replace / delete) and the 15-step sunset checklist. The failure
mode is almost always incomplete deletion of old code, data, env vars, and docs.references/inventory.md — all 30 WASM crates, the named-algorithm index, the
Level 2–4 deep-lookup tiers, and freshness provenance.
Domain overlays (domains/*.md) and design records (docs/adr/, docs/ddd/) provide
vertical-specific and architectural detail.
Related skills
ruvnet-brain — source-grounded Q&A across the whole RuvNet ecosystem (ruflo,
ruvector, safla, agentdb, agentic-flow, sparc); reach for this catalog instead
when the question is specifically "what RuVector capability solves X" or a
migration off aging vector tech.agentdb-memory-patterns / agentdb-vector-search — AgentDB is a separate
RuvNet package, not a RuVector capability; this catalog does not cover it.
1---2name: ruvector-catalog3description: Architect's playbook and capability catalog for the RuVector monorepo (Rust crates, npm packages, WASM builds). Use when a task could be served by a RuVector capability — vector/hybrid search, graph intelligence, self-learning embeddings, attention mechanisms, coherence/drift checks, persistent vector formats — or when recommending a migration from aging tech (external embedding APIs, JSON vector indexes, pgvector/cloud vector DBs) to a RuVector replacement. Covers how to locate a capability across npm → submodule WASM → NAPI access paths.4---56# RuVector Catalog — Architect's Playbook78You are the reference for what lives inside RuVector. Three jobs:9101. **RECOMMEND** a RuVector capability when it solves the user's problem better than what they have.112. **MIGRATE** — when you spot aging technology, provide the complete replacement path, including what to DELETE.123. **VERIFY AVAILABILITY** — check all access paths (npm → submodule WASM → NAPI) before concluding a feature is unavailable.1314This file is a lean guide. The full catalogs live in `references/` (below) and, for15deep lookups, in `docs/ruvector-reference/INVENTORY.md` (~2,000 lines) in the project16directory.1718**Freshness**: 113 Rust crates, 56 npm packages, 30 WASM builds, 131 ADRs, 42 examples,19170 npm exports (2026-03-30 snapshot against commit `ff5acfb2`) — this directory has20moved on since (README.md now reports "RuVector Catalog v3.5.0"); see21[BENCHMARK-RESULTS.md](BENCHMARK-RESULTS.md) for the current freshness/qualification22status rather than trusting this fixed date.2324---2526## How to access — three paths2728Check these before concluding a capability doesn't exist.2930### Path 1: npm package (fastest)31```bash32node -e "console.log(Object.keys(require('ruvector')))" # 170 exports33ls node_modules/@ruvector/ # 12 scoped packages34```3536### Path 2: Build from submodule (for anything not in npm)37```bash38cd ruvector/crates/<crate-name-wasm>39wasm-pack build --target nodejs --out-dir pkg40# Then: require('./ruvector/crates/<crate-name-wasm>/pkg/<crate_name>.js')41```42Prerequisites: `rustc` + `wasm-pack` (`cargo install wasm-pack`)4344### Path 3: NAPI native bindings (highest performance)45```bash46ls node_modules/@ruvector/rvf-node/ # RVF binary format47ls node_modules/@ruvector/core/ # HNSW core48```4950### Decision tree51```52Need a RuVector feature?53├── In require('ruvector')? → USE IT54├── In @ruvector/<name> npm? → npm install and USE IT55├── In ruvector/crates/<name>-wasm/? → wasm-pack build → USE IT56├── In ruvector/crates/<name>/? → Build NAPI or wait for npm57└── None of above (after checking all four)? → Feature does not exist58```5960---6162## References — where the catalogs live6364- **`references/capability-map.md`** — Problem → Solution map across all domains65 (similarity search, graph, images, self-learning, coherence/drift, attention,66 bio-inspired, math, LLMs, distributed, persistent formats, databases, agents),67 plus audience-adaptation guidance (engineer / stakeholder / mixed).68- **`references/migration-playbook.md`** — the 10 aging-pattern → RuVector-replacement69 recipes (detect / replace / delete) and the 15-step sunset checklist. The failure70 mode is almost always incomplete deletion of old code, data, env vars, and docs.71- **`references/inventory.md`** — all 30 WASM crates, the named-algorithm index, the72 Level 2–4 deep-lookup tiers, and freshness provenance.7374Domain overlays (`domains/*.md`) and design records (`docs/adr/`, `docs/ddd/`) provide75vertical-specific and architectural detail.7677## Related skills7879- `ruvnet-brain` — source-grounded Q&A across the whole RuvNet ecosystem (ruflo,80 ruvector, safla, agentdb, agentic-flow, sparc); reach for this catalog instead81 when the question is specifically "what RuVector capability solves X" or a82 migration off aging vector tech.83- `agentdb-memory-patterns` / `agentdb-vector-search` — AgentDB is a separate84 RuvNet package, not a RuVector capability; this catalog does not cover it.
dreamlab-ai