RecursiveIntell Rust Libraries

Overview

The Rust Libraries workspace is the substrate for Recall, Gloss, AiDENs, and the broader RecursiveIntell evidence-runtime architecture. The current source basis separates canonical crates from satellite utilities and research-linked crates so support claims stay honest.

Core Rust Stack

The high-confidence canonical lane includes:

• semantic-memory: projection plane and durable queryable memory substrate.
• semantic-memory-forge: evidence/export authority for truth bundles, envelopes, and verification substrate.
• forge-memory-bridge: deterministic bridge from Forge/export truth to semantic-memory import/projection.
• knowledge-runtime: planning, routing, merge, scoped retrieval, temporal/scope interpretation, and view disclosure.
• stack-ids: shared identifiers, scopes, digests, trace primitives, and replay links.
• verification-control, verification-policy, verification-calibration, and verification-adjudication: governed verification/control decisions.
• contract-schema-gen: schema generation and contract governance.

Promising Or Early Kernel Work

• llm-tool-runtime: provider-agnostic tool contracts, dispatch, receipts, route/error taxonomy, and execution provenance.
• recursive-kernel-core: recursive inference schemas and operator contracts.
• constraint-compiler, kernel-execution, kernel-oracles, and kernel-conformance: compiler, execution, oracle, and harness surfaces for recursive kernel behavior.

Satellite And Utility Crates

The satellite lane includes agent-graph, job-queue, AI-Batch-Queue, Tauri-Queue, LLM-Pipeline, llm-output-parser, Ollama-Vision-RS, ComfyUI-RS, parser support, turbo-quant, turbo-semantic, and fib-quant.

These crates can carry execution lineage into products, but they should not silently become canonical truth authority.

Research-Linked Quantization

turbo-quant implements TurboQuant, PolarQuant, and QJL-style vector quantization experiments. fib-quant is an alpha Rust implementation of the paper-core radial-angular vector quantization path from the FibQuant paper. Both are explicitly gated: no default-on compression, no production KV-cache readiness claim, and no benchmark claim without local receipts.

Boundary Rule

The main failure mode for this workspace is boundary drift. Every crate needs a clear owner plane, write authority, emitted artifact set, and receipt/conformance story.