spacedb-vector 0.7.3

SpaceDB Layer 4 — the private-RAG substrate: an on-node vector index where a query embedding goes in and only top-k results come out (ids + scores), so the corpus never leaves the home. Retrieval is gated by an mID capability. Phase 1 SpaceDB Mission, M6.
Documentation
#![forbid(unsafe_code)]
//! # spacedb-vector — SpaceDB Layer 4 (the private-RAG substrate)
//!
//! A native, on-node vector index co-located with the data: a query embedding
//! goes in, and **only the top-k results come out** — the corpus never leaves the
//! home. An authorized AI agent's retrieval runs here, **gated by an mID
//! capability** ([`retrieve`]), which is the concrete mechanism behind
//! "inaccessible by default, accessible by mID-gated consent": semantic access to
//! *results*, not bulk data.
//!
//! Open-core (MIT): depends only on `spacedb-access` (for the capability gate).
//! S3 ships an exact flat k-NN [`VectorIndex`]; sub-linear ANN (HNSW / IVF) is a
//! future optimization behind the same surface.

mod error;
pub use error::{VectorError, VectorResult};

mod index;
pub use index::{Match, Metric, VectorIndex};

mod retrieve;
pub use retrieve::retrieve;

/// Compiles the README's examples as doctests, so the documented API can never
/// drift from the real one. Not part of the public API, and not rendered into
/// the crate docs — it exists only under `cargo test --doc`.
#[cfg(doctest)]
#[doc = include_str!("../README.md")]
pub struct ReadmeDoctests;