📡 rvCSI — edge RF sensing runtime
Turn WiFi Channel State Information into validated, typed, confidence-scored RF events — in Rust, from TypeScript, from the CLI.
rvCSI is the stable, hardware-abstracted runtime layer that real CSI pipelines are missing. Today, WiFi sensing is shell scripts, patched firmware, kernel modules, Python notebooks, PCAP dumps and ad-hoc DSP — formats differ per chip, drivers are unstable, malformed packets are common, device assumptions leak everywhere. rvCSI fixes that:
- Ingests CSI from many sources behind one trait (
CsiSource) — Nexmon (BCM43455c0 / Raspberry Pi 4 & 5, 4358, 4366c0), ESP32, Intel, Atheros, .rvcsi capture files, deterministic replay.
- Validates every packet in Rust before it can touch application code — length/finiteness/profile checks, plausibility bounds, structured errors, never panics, never raw pointers across a language boundary.
- Normalizes everything into one schema —
CsiFrame → CsiWindow → CsiEvent.
- Processes with reusable DSP — Hampel/MAD outlier filter, phase unwrap, smoothing, sliding variance, DC removal, baseline subtraction, motion energy, presence, heuristic breathing-band estimate.
- Emits typed events with confidence + evidence — presence started/ended, motion detected/settled, baseline drift, anomaly, signal-quality drop, calibration-required, breathing candidate.
- Bridges to RuVector as RF memory — deterministic window/event embeddings, similarity search, drift detection.
- Exposes a Rust API, a TypeScript SDK (
@ruv/rvcsi, napi-rs), and a CLI (rvcsi).
rvCSI is structural sensing: excellent at detecting change, presence, motion, drift, and learned patterns — deliberately silent on exact identity, exact pose, and medical-grade certainty. Detection ≠ decision — rvCSI emits evidence; agents and applications decide what to do.
The architecture is set by ADR-095 (the 15 platform decisions: Rust core, C-only-at-the-hardware-boundary, TS SDK via napi-rs, normalized schema, validate-before-FFI, CSI-as-temporal-delta, RuVector as RF memory, replayability, detection≠decision, local-first, read-first/write-gated MCP, mandatory quality scoring, versioned calibration, plugin adapters) and ADR-096 (the crate topology, the napi-c shim contract, the napi-rs surface). See the PRD for requirements and the domain model for the 7 bounded contexts.
Crates
