Today RuView and Cognitum.one moved two vendor integrations from research into reproducible, simulator-first Rust betas. Both integrations label synthetic data explicitly and stop short of claiming physical-hardware validation before the boards and vendor SDKs arrive.
- Merged RuView PR #1356.
- Published v0.9.0-realtek-beta.1.
- Added a deterministic RTL8720F radar simulator, parser/validation boundary, sensing-server integration, tests, documentation, and ADRs.
- Opened the upstream Ameba RTOS announcement and collaboration thread: Ameba-AIoT/ameba-rtos#1338.
- Physical RTL8720F validation remains scheduled for when the hardware and vendor SDK arrive.
- Merged RuView PR #1358.
- Published v0.9.1-mediatek-beta.1.
- Added deterministic profiles for MT7981+MT7976, MT7986+MT7975, and MT7988+MT7996.
- Defined the versioned
MTC1application envelope for complex I/Q, MIMO dimensions, RSSI, bandwidth, PPDU metadata, provenance, sequence/timestamp, and CRC32. - Added strict Rust validation, UDP ingestion, latest-frame REST output, bounded WebSocket summaries, replay generation, and explicit
mediatek:simulatedprovenance. - Published Windows binaries, three deterministic replay captures, and SHA-256 manifests.
- Opened the upstream mt76 announcement/RFC: openwrt/mt76#1106, cross-referencing the existing MT7916 HE160 investigation in mt76#1087.
- Hardware crate: 183 tests passed; one timing-sensitive test remains intentionally ignored.
- Sensing server: 177 tests passed.
- Targeted MediaTek codec/summary tests: 9 passed.
- Clippy completed for hardware and sensing-server targets with only pre-existing warnings.
- Optimized Windows release builds completed.
- Live UDP simulator-to-server checks passed for all three profiles.
- Replay determinism was confirmed; the MT7986 fixture SHA-256 is
3f93b0d71afec8c9e78da85fc6667ac3fa87b10e1ea92727951d0a60afb3f223. - Invalid oversized 4x4x1024 frames were rejected as designed.
- All required GitHub checks passed before merge.
Once boards and SDKs arrive, we will replace simulator-only confidence with captured-vs-simulated fixtures, verify vendor metadata and scaling, exercise loss/rate behavior on the physical transport, and document firmware/SDK provenance. For MediaTek, the upstream question is especially important: public firmware support for CSI export varies, so RuView?s adapter will follow a confirmed mt76/firmware boundary rather than assume private interfaces.
- Merged RuView PR #1359.
- Published v0.9.2-qualcomm-beta.1.
- Added the bounded Rust
QCS1codec, deterministic QCA9300/QCN9074/QCN9274 simulator profiles, UDP/REST/WebSocket integration, replay fixtures, and SHA-256 manifests. - QCA9300 is the first physical baseline; QCN9074/QCN9274 remain explicitly simulator-only until a public firmware export path is confirmed.
- Published the PicoScenes interoperability RFC: wifisensing/PicoScenes-Issue-Tracker#77.
ADR-270 now classifies RF Solutions, Origin AI, Plume, Linksys, Electric Imp, Mist/Juniper, Luma, Google Nest, NETGEAR, and Wifigarden by actual capability: complex CSI, derived sensing, RF telemetry, network-only, or unsupported. Every provider must pass the same research, contract, simulator, Rust validation, physical-hardware, provenance, and publication gates. A simulator can validate software behavior but never proves CSI availability or RF accuracy.