A frontier proposal with a validation plan, not an implemented detector.
Intended capability
Research whether the field could support this proposed outcome: Logs the estate's 2.4 GHz noise-floor, packet-error, and CSI-SNR trends per zone as a standing annotation stream, and flags floor shifts with no declared cause — a drive-noise rise in a hall declared powered down, a floor step coincident with nothing on the maintenance calendar. This is deliberately the humblest row in the band: the ISM floor is the most confounded spectrum in a building, so an EMI finding is a cue to consult the other sensors and an annotation on their findings — never certificate evidence on its own, and the row's output says so about itself.
This describes the intended outcome. Readiness is research concept, evidence is class C, and a catalog mapping or recording is not proof of this outcome at a real site.
Solution blueprint
See the environment before installing it.
This exact kit is one of 191 first-class designs. It includes geometry, objects, nodes, wording, scenarios, installation, limitations, and catalog-bound readiness.
No rendered revision is available yet.
Bundled recording
A related Fleet scene
This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.
01 The physics
Motor and servo drives shift the local RF noise floor when energized, and the mesh measures that floor continuously as a by-product of being a mesh: noise-floor estimates, per-link PER, CSI SNR. But most VFD and servo emission rolls off far below 2.4 GHz, and microwave ovens, co-channel WiFi and Bluetooth, and battery chargers move the same floor with no way to tell them apart from below. The channel is real and free; its evidentiary weight is corroboration, stated plainly in every record it produces.
02 Shared processing path
Per-zone noise-floor + PER + CSI-SNR aggregation -> diurnal and operational baseline per zone -> CUSUM step and trend detection on floor level -> host-side join against declared power and maintenance state (read-only) -> unexplained-shift annotation attached to concurrent findings from other rows, tagged corroboration-only.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
03 Validation plan
Own-hardware protocol: controlled drive energization trials at ranged distances from nodes, interleaved with oven, charger, and co-channel confounders; measure whether drive state is even separable from the confounder floor per zone class before any claim hardens beyond annotation.
04 Commercial hypothesis
'Floor Ledger' — for the estate operator, free with the mesh: the ambient RF weather report that annotates the real findings, and occasionally asks the useful question — what was energized in Hall C at 02:00, when you had declared it dark?