[Announcement / RFC] RuView Rust QCS1 simulator and QCA9300 interoperability track

[ruvnet]

Announcement

RuView and Cognitum.one have published a simulator-first Qualcomm Atheros CSI beta and would like to align its first physical-data adapter with the established PicoScenes QCA9300 ecosystem.

• Release: https://github.com/ruvnet/RuView/releases/tag/v0.9.2-qualcomm-beta.1
• Merged implementation: feat: add Qualcomm CSI simulator and vendor integration program ruvnet/RuView#1359
• Platform ADR: https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-268-qualcomm-atheros-csi-platform.md
• QCS1 protocol ADR: https://github.com/ruvnet/RuView/blob/main/docs/adr/ADR-269-qualcomm-csi-wire-protocol.md

This is a collaboration announcement/RFC, not a claim that public ath11k/ath12k firmware exports raw CSI.

Available now

• Rust QCS1 codec with bounded dimensions, CRC32, finite-value checks, chipset bandwidth/chain limits, and strict datagram validation
• Deterministic profiles for QCA9300, QCN9074, and QCN9274
• UDP/replay simulator and RuView sensing-server ingestion
• Bounded REST/WebSocket summaries with mandatory qualcomm:simulated provenance
• Reproducible fixtures and SHA-256 manifests
• QCA9300 capped at 3x3 and 20/40 MHz; modern profiles are explicitly experimental pending a lawful firmware export path

Interoperability questions

1. Is there a stable documented PicoScenes frame/container subset recommended for translating QCA9300 CSI into another application envelope?
2. Which QCA9300 metadata should be treated as authoritative for chain order, scaling, subcarrier indices, center frequency and timestamps?
3. Are small redistributable capture fixtures available, or is there a preferred procedure for publishing newly captured conformance fixtures?
4. Would a standalone Rust parser/translator for the documented PicoScenes container be useful upstream, provided it does not redistribute proprietary components?
5. Are there known public QCN9074/QCN9274 CSI paths we should track, or should those profiles remain simulator-only?

Our intended next gate is exact-hardware QCA9300 capture, translated-vs-source comparison, calibration/repeatability tests, and published firmware/tool provenance. We would welcome corrections to the ADR and fixture design before hardware validation begins.

[ruvnet]

Combined project update covering the Realtek, MediaTek, Qualcomm betas and the repeatable vendor-integration ADR: https://gist.github.com/ruvnet/5ca5a27f2e607dcfcf0e3655fdec2d62