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.

rvcsi-mcp (an MCP tool server), rvcsi-daemon (live radio capture + WebSocket), rvcsi-adapter-esp32 (a live ESP32 serial/UDP source), and the legacy nexmon packed-float CSI export are tracked as follow-ups on top of these crates.

# the CLI
cargo install rvcsi-cli      # installs the `rvcsi` binary

# or a library, in Cargo.toml
[dependencies]
rvcsi-core    = "0.3"
rvcsi-dsp     = "0.3"
rvcsi-events  = "0.3"
rvcsi-runtime = "0.3"        # the composition layer most apps want

npm install @ruv/rvcsi

import { inspectCaptureFile, eventsFromCaptureFile, RvcsiRuntime } from "@ruv/rvcsi";

console.log(inspectCaptureFile("session.rvcsi"));        // frame count, channels, quality, ...
for (const ev of eventsFromCaptureFile("session.rvcsi")) // presence/motion/anomaly/...
  console.log(ev.kind, ev.confidence, ev.timestampNs);

const rt = RvcsiRuntime.openCaptureFile("session.rvcsi");
let f; while ((f = rt.nextCleanFrameJson()) !== null) { /* validated + DSP-cleaned */ }

# Capture real nexmon_csi on a Raspberry Pi:
tcpdump -i wlan0 dst port 5500 -w csi.pcap

# Transcode to a validated .rvcsi capture (Pi 5 / BCM43455c0 profile):
rvcsi record --source nexmon-pcap --in csi.pcap --out session.rvcsi --chip pi5

# Inspect it:
rvcsi inspect session.rvcsi
#   frames : 12048   channels : [36]   subcarriers : [256]   mean quality : 0.91
#   validation : accepted=12001 degraded=47 rejected=0 ...

# Run the DSP + event pipeline:
rvcsi events session.rvcsi
#   1700000000000000000 ns  presence_started   conf=0.94  evidence=[7]
#   1700000003000000000 ns  motion_detected    conf=0.81  evidence=[10]
#   1700000061000000000 ns  baseline_changed   conf=0.62  evidence=[31]

# Learn a v0 baseline, decode a chanspec, list known Nexmon chips:
rvcsi calibrate --in session.rvcsi --out baseline.json
rvcsi decode-chanspec 0xe024
rvcsi nexmon-chips

There is no ESP32 adapter crate yet — until rvcsi-adapter-esp32 lands, an ESP32 .csi.jsonl recording can be transcoded into .rvcsi with the bridge script in scripts/, then run through the same inspect / events / calibrate toolchain.

This repo ships a Claude Code plugin marketplace (.claude-plugin/marketplace.json) with an rvcsi plugin: slash commands for capturing/inspecting/replaying CSI and running the event pipeline, plus an agent that knows the schema, the validation rules, and the adapter contract.

/plugin marketplace add ruvnet/rvcsi
/plugin install rvcsi@rvcsi

Then: /rvcsi-inspect <file.rvcsi>, /rvcsi-events <file.rvcsi>, /rvcsi-record …, /rvcsi-nexmon …. See plugins/rvcsi/README.md.

cargo build --workspace
cargo test  --workspace          # 170 tests, 0 failures
cargo clippy --workspace         # clippy-clean

#![forbid(unsafe_code)] in every crate except rvcsi-adapter-nexmon, where unsafe is confined to one ffi module wrapping the C shim — every block carries a // SAFETY: comment. The C shim is allocation-free, bounds-checked, ABI-versioned, and never panics.

rvcsi-node is a workspace member (a napi cdylib links fine with Node symbols left undefined on Linux/macOS), so cargo build/cargo test work without a Node toolchain — only napi build (the npm prebuild) needs Node.

rvCSI was extracted from the RuView / WiFi-DensePose project (ADR-095, ADR-096) where it was incubated; RuView consumes it back as a vendor/rvcsi submodule.

Licensed under either of Apache License, Version 2.0 or MIT license at your option. Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.