RuView: Safety Critical Fixes and Protocol Improvements
Seven merged pull requests addressed critical safety, security, and reliability issues in RuView, including a life-safety fix in medical triage logic and resolution of a firmware protocol collision that was causing silent data loss.
Duration: PT2M13S
Transcript
Good morning. This is RuView for June 4th, 2026.
The team resolved several critical issues this cycle, led by safety fixes and protocol improvements that address both life-critical functionality and silent data corruption.
The most important change is a safety fix in the Mass Casualty Assessment tool. PR 926 corrected triage logic that was incorrectly classifying survivors with detectable heartbeats as deceased when they showed no breathing or movement. This was happening in both triage calculation paths - survivors with pulses but no visible breathing or movement, indicating respiratory arrest, were being deprioritized instead of marked as immediate priority. The fix ensures any detectable heartbeat overrides a deceased classification.
Protocol reliability saw major improvements with PR 931 resolving a firmware magic number collision. Two different packet types were both using the identifier 0xC511_0004 - fused vitals from mmWave sensors and WASM output packets. The sensing server only knew how to parse the WASM format, so 48-byte fused vitals packets were being silently misparsed as malformed WASM events, causing complete loss of mmWave vital sign data. The fix reassigns WASM output to a new identifier and adds proper parsing for both packet types.
Several workflow and security improvements round out the cycle. PR 920 fixed the export RVF flag to stop silently producing placeholder models instead of trained ones when combined with training commands. PR 929 made bearer token authentication case-insensitive per RFC standards, reducing setup friction. And CSI processing improvements in PR 940 address occupancy detection issues by filtering out structureless null frames that were causing bimodal presence signals.
These fixes particularly matter for deployments using the C6 plus mmWave configuration and any medical assessment workflows. The protocol changes require coordinated firmware updates to maintain WASM event streams.
That's your RuView update. Back tomorrow.