m2m-vector-search 1.0.7

Machine-to-Memory Edge-Optimized Vector Search Database with Vulkan Compute API

M2M Vector Search Engine

Machine-to-Memory (M2M) Engine & Gaussian Splat Vector Store

A vector database with hierarchical retrieval for local-first applications. Now available in two explicit flavors: The minimal SQLite-style for Edge, and the Advanced Agent-style for intelligence.

---

📋 Table of Contents

• Overview
• Common Use Cases
• Two Modes of Operation
  • SimpleVectorDB (Edge / "SQLite" approach)
  • AdvancedVectorDB (Agentic approach)
• Architecture & 3-Tier Memory
• Comparison
• Benchmarks
• Installation
• Troubleshooting
• License

---

🎯 Overview

M2M Vector Search is a vector database built on Gaussian Splats with hierarchical retrieval (HRM2). Designed originally for generative exploration and Self-Organized Criticality (SOC), it has been refined to offer production-ready profiles for both sheer speed (Edge computing) and complex reasoning (Agents).

Core Engine Features

Feature	Description
Hierarchical Retrieval (HRM2)	Two-level clustering (Level 1 Coarse, Level 2 Fine) for sub-millisecond searches.
Gaussian Splats	Full latent representation (μ, α, κ).
Local-First	No cloud dependencies, pure local Python/NumPy logic.
GPU Acceleration	Optional true Vulkan compute shader acceleration for MoE routers.

---

🌟 Common Use Cases

• Edge AI Devices: Run fast vector searches on resource-constrained devices without internet access.
• Autonomous Agents: Use AdvancedVectorDB for agents that need to dynamically cluster and forget information over time.
• Local RAG Pipelines: Integrate with LangChain/LlamaIndex for private document Q&A without sending data to APIs.

---

🌐 Omnimodal & Multimodal Ready

M2M does not care about the source of your vectors; it seamlessly stores and routes high-dimensional embeddings from any modality. By pairing M2M with state-of-the-art embedding models, you can achieve true omnimodal retrieval.

Supported Data Formats & Best Practices

Modality	Recommended Embedding Model	Format / Best Practice
Text	OpenAI text-embedding-3, BGE, all-MiniLM	Chunks of Markdown, raw string text, JSON blobs. Normalize text before embedding.
Images	OpenAI CLIP, SigLIP	.png, .jpg, .webp. Normalize vectors to S^D space to perfectly fit M2M's spherical mapping.
Audio	ImageBind, Whisper-based encoders	.wav, .mp3. Embed 5-second acoustic slices to match natural HRM2 clustering.
Video	VideoMAE, ImageBind	Frame aggregations or temporal tokens. Group frames as "splat clusters".
Spatial/3D	PointNet++, 3D Gaussian Splatting	Pass raw splat features (μ, α, κ) directly for 3D routing applications.
Telemetry	Time2Vec	Server logs, IoT sensory data encoded to hyperspheres.

---

🌓 Two Modes of Operation

We realized that applications need completely different things. Standard RAG needs a blazing fast, "dumb" vector store. Autonomous agents need exploratory latent spaces. Thus, M2M provides two compatible, interchangeable interfaces:

1. SimpleVectorDB

"The SQLite of Vector DBs"

Designed for raw edge computing and pure embedding retrieval. It strips away all advanced mechanics (generative sampling, memory tiering, entropy tracking) to maximize throughput and minimize RAM/VRAM footprint.

Best for: RAG workflows, embedding lookup, static local vector caches.

import numpy as np
from m2m import SimpleVectorDB

# Zero-configuration initialization
db = SimpleVectorDB(device='cpu')

# Add embeddings dynamically
db.add(np.random.randn(10000, 640).astype(np.float32))

# Blazing fast hierarchical search
results = db.search(np.random.randn(1, 640).astype(np.float32), k=10)

# Save/Load your index instantly
# db.load("vector_cache.bin")

2. AdvancedVectorDB

"The Cognitive Latent Space"

Designed for Autonomous Agents. Enables the 3-Tier Memory Manager (VRAM -> RAM -> SSD), Langevin Dynamics for generative vector exploration, and Self-Organized Criticality (SOC) to passively consolidate redundant memory.

Best for: Long-running Agents, dynamic memory systems, associative reasoning.

import numpy as np
from m2m import AdvancedVectorDB

# Initialize Full Cognitive Suite
agent_db = AdvancedVectorDB(device='vulkan')
agent_db.add(np.random.randn(50000, 640).astype(np.float32))

# 1. Standard Search
nearest = agent_db.search(np.random.randn(1, 640).astype(np.float32), k=10)

# 2. Generative Latent Exploration
# Uses Underdamped Langevin Dynamics to explicitly walk the energy manifold
creative_samples = agent_db.generate(query=np.random.randn(1, 640).astype(np.float32), n_steps=20)

# 3. Consolidate Memory via Self-Organized Criticality
# Automatically removes near-duplicate or useless splats based on access frequency
removed_count = agent_db.consolidate(threshold=0.85)

Note: Both systems utilize the same underlying SplatStore and HRM2Engine. An index built and persisted in SimpleVectorDB can be loaded natively into AdvancedVectorDB, and vice-versa!

---

🔗 Integrations

M2M natively supports the industry-standard frameworks for building RAG applications and Agentic workflows.

LangChain Integration

from langchain.vectorstores import M2MVectorStore
from langchain.embeddings import HuggingFaceEmbeddings

embeddings = HuggingFaceEmbeddings(model_name="sentence-transformers/all-MiniLM-L6-v2")

vectorstore = M2MVectorStore(
    embedding_function=embeddings.embed_query,
    splat_capacity=100000,
    enable_vulkan=True
)

vectorstore.add_texts(["Document 1", "Document 2"])
results = vectorstore.similarity_search("Query", k=5)

LlamaIndex Integration

from llamaindex import VectorStoreIndex, SimpleDirectoryReader
from m2m.integrations.llamaindex import M2MVectorStore

documents = SimpleDirectoryReader("./docs").load_data()

vectorstore = M2MVectorStore(latent_dim=640, max_splats=100000, enable_vulkan=True)
index = VectorStoreIndex.from_documents(documents, vector_store=vectorstore)

query_engine = index.as_query_engine()
response = query_engine.query("Your search query")

---

🏗 Architecture

The 3-Tier Memory Hierarchy (Advanced Mode)

Tier	Storage	Latency	Use Case
Hot	VRAM	~0.1ms	Active queries, highly recurrent context.
Warm	RAM	~0.5ms	Cached HRM2 embeddings, mid-term context.
Cold	SSD	~10ms	Long-term persisted cold storage.

Component Breakdown

• M2MEngine: The main router and orchestrator.
• SplatStore: splats.py handles the physical tensors and GPU tracking.
• HRM2Engine: hrm2_engine.py builds the two-level K-Means lookup tree.

---

⚖️ Comparison with other Vector DBs

Feature	M2M Vector Search	FAISS	Pinecone	Chroma
Deployment	Local / Edge	Local	Cloud / Managed	Local / Server
Engine Focus	Gaussian Splats, SOC	IVF, HNSW	Proprietary ANN	SQLite / HNSW
GPU Support	Vulkan (Cross-platform)	CUDA (NVIDIA only)	N/A	N/A (CPU mostly)
Agentic Features	Yes (Memory Tiering, SOC)	No	No	No

---

📊 Benchmarks

Test Configuration

Parameter	Value
CPU	Dual Core Local Edge Device
RAM	2GB Available
Vectors	10,000 (sklearn fallback)
Dimensions	640D

Results

System	Avg Latency	Throughput	Speedup
Linear Scan	30.06ms	33.26 QPS	1.0x (baseline)
M2M CPU	89.24ms	11.20 QPS	0.3x
M2M Vulkan	51.88ms	19.28 QPS	0.6x

(Reproduce local benchmarks via python benchmarks/run_benchmark.py --dataset sklearn --n-splats 10000 --n-queries 100 --k 10)

---

🚀 Installation

System Requirements

Component	Minimum	Recommended
OS	Windows 10, Linux, macOS	Linux / Windows
CPU	2 Cores	4+ Cores
RAM	2 GB	8+ GB
GPU	Optional (Any Vulkan 1.0+ compatible device)	Dedicated GPU (NVIDIA/AMD) with Vulkan support

Note on Homogeneous Distributions vs Latency: If vectors are perfectly homogeneous (a highly dense cluster without clear boundaries), the internal K-Means index struggles to separate them into distinct semantic paths. Consequently, the HRM2 engine must probe multiple overlapping clusters, forcing the latency closer to O(N) linear time as opposed to the ideal O(sqrt(N)) logarithmic speedup seen in normally distributed or distinctly grouped datasets.

Prerequisites

• Python 3.8+
• NumPy 1.24+
• scikit-learn 1.2+

From Source

git clone https://github.com/schwabauerbriantomas-gif/m2m-vector-search.git
cd m2m-vector-search
pip install -r requirements.txt

Verify your installation:

python scripts/validate_project.py

---

🛠️ Troubleshooting

Having issues? Check out our Troubleshooting Guide for solutions to common problems.

---

📄 License & References

Licensed under the AGPLv3.

• Methodology Conclusions: METHODOLOGY_CONCLUSIONS.md
• Config Guide: CONFIG_RAG.md

---

M2M: Machine-to-Memory