ingraph 0.1.0

A declaration-driven indexing framework: records and nodes are written as Rust types, and the storage rows, the dataflow between them and the GraphQL query surface are emitted from the declaration.
Documentation
//! The LIVE walks: a real Tantivy index beside a real SQLite store for the full-text flavour, and
//! the in-tree vector face against the same store for its mirror.
//!
//! # Why these RUN rather than assert on a rendered statement
//!
//! Every stage of this pipeline is invisible in text. A floor that filters instead of terminating
//! renders nothing at all; a dedup that keeps the wrong sighting renders nothing; a gather that
//! pruned mid-page and never asked again renders one perfectly good statement. So each stage's own
//! mutation pin lives beside the stage — see `keys/tests.rs` and `gather/tests.rs` — and what is
//! here is the claim those cannot make: a query text goes into a real engine, a real store answers
//! the composed gather, and whole entities come back ranked in the engine's order.
//!
//! # Both flavours share ONE system of record, which is what makes the second a MIRROR
//!
//! `corpus` is the upstream: a transcript segment, its stored row, and a filter over a product
//! dimension. The two flavours differ in the index they ask and in nothing else, which is exactly
//! the claim the shared core makes.
//!
//! It is also what lets the third walk exist. `fusion` asks BOTH indexes the same question and joins
//! their two rankings at the media root — a claim neither flavour's own file can make, and one that
//! needs the two of them over one system of record to be about anything.
//!
//! # And a fourth walk, over the same corpus, at a grain none of those has
//!
//! `set` asks a SET election: the entity holds several embeddings, the engine answers at the ELEMENT
//! grain, and several of its hits name one entity. That is the one thing the mirror cannot exercise
//! — its engine answers one hit per entity — so the collapse, the fold and *`k` counts entities* get
//! their own live walk, hydrating out of the same store.

#![cfg(feature = "sqlite")]

mod corpus;
#[cfg(feature = "tantivy")]
mod fulltext;
/// The FUSED walk, which needs both flavours at once — so it inherits the full-text half's engine
/// gate on top of the module's own store gate.
#[cfg(feature = "tantivy")]
mod fusion;
mod set;
mod vector;