Mapped to a shared offline runtime family and usable with a recording or compatible ESP32 CSI stream.
Intended capability
Pilot this intended outcome through the shared Intrusion event family, then validate it against site-specific ground truth: Detects unexplained, gait-free motion in a zone or window where the estate declares the fleet parked, idle, or absent — the robot that moves at 02:00 in a hall the fleet manager swears is asleep, or traffic in a lane outside every declared route envelope. Remote actuation of exposed robot middleware is demonstrated practice, and the machine's own telemetry is precisely what an attacker or a fault would corrupt; this row's verdict is physical and owes nothing to the fleet API. The finding is a divergence between declared state and observed physics — a security-grade lead framed by the movement-space confinement requirements EU 2023/1230 places on the machinery — never an intrusion verdict and never an accusation.
This describes the intended outcome. Readiness is shared-family mapped, evidence is class B, 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
Baseline-subtracted motion energy with gait-band absence and a smooth envelope betrays powered motion regardless of what any API declares — no micro-Doppler is claimed, and no constant-period claim is made for a driving robot; machine-regularity language is reserved for cyclic sources. The verdict runs on the CSI field alone; the declared-idle window comes from the read-only estate feed and is needed only to make the contradiction, not the observation. Perpetually cyclic furniture — conveyors, fans, HVAC — is baselined per zone at commissioning, so the detector fires on new unexplained motion energy, not the building's own rhythm.
02 Shared processing path
Per-zone baseline-subtracted motion-energy detection with gait-band-absence and envelope-smoothness tests on CSI -> commissioned baseline subtraction of perpetual mechanical rhythm -> new-motion event with zone and interval -> host-side contradiction join against declared fleet state and route envelopes (read-only) -> divergence finding with confidence; event-bounded camera person-confirm at instrumented entries adds whether a human was also present.
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: scripted unauthorized-motion runs during declared-idle windows against a commissioned zone baseline, plus confounder nights — HVAC cycling, cleaning crews with carts; score detection latency, false-fire rate against building rhythm, and the cart-pusher confusion rate. Any Annex III confinement or supervisory clause number is verified against EUR-Lex before it appears in print.
04 Commercial hypothesis
'Declared Idle, Observed Moving' — for the security owner of an automated estate: an independent physical check that machinery stayed inside its declared movement space and schedule, from sensors the fleet software cannot rewrite — evidence toward the confinement and cybersecurity requirements EU 2023/1230 places on the machinery, inherited by the operator through procurement, and toward the operator-side frames of 2009/104/EC and IEC 62443.