Jam-Time Sentinel
Even while the radios are being drowned out, a wired node keeps saying whether a body is in the aisle, and about how far along.
Contested Space · Contested capability
Latent emits a reading. It does not switch cameras, unlock cages, cut power or open a ticket. Your VMS, PoE switch or access controller does that, on your side of the boundary. A Latent blueprint contains no executable code, no remote URLs and no device secrets — by schema, not by policy.
No face, no plate, no MAC, no device identity, no payload. A movement signature is a shape moving through a room, not a person. Nothing stored here resolves to an individual.
Cuts to copper or host power end the feed — silence on the wired path is its own top-severity alarm. Cones cover declared aisles only; a 24 GHz interferer (another FMCW radar) can degrade it and must be alarmed as radar-band interference, never ignored.
Across Camera Shield Jam the mesh and the wake never fires. Two people moving together read as one disturbance. Re-rack a row and the fade map is wrong until you recalibrate.
Each node mints its own key over USB, in your hand. Physical possession is the root authority: a device that cannot prove physical presence is refused enrollment outright. A cloud pairing PIN is a weaker ownership claim and is never treated as liveness.
Every reading is attributable to a device id, profile id, hardware id and firmware version recorded at install and verified by mutual HMAC-SHA256 proof over an LFW1 nonce exchange. A node whose proof did not verify is marked untrusted, not merely offline.
Completing an installation is a high-risk action. It requires your explicit browser approval, an approval snapshot that still matches, an idempotency key, and heartbeats less than three minutes old. There is no silent commissioning.
How enrollment worksProperties you can map to your own controls
These are properties, not certifications. Latent does not assert compliance with any framework on your behalf.
Mapped to a shared offline runtime family and usable with a recording or compatible ESP32 CSI stream.
Published physics or adjacent results support the hypothesis; capability-specific product and site validation are still required.
Collapse of the node’s own CSI stream and received power against a learned baseline. This is evidence that one link on one 20 MHz channel went deaf — never attacker identification, and never a claim about any other band.
No compatible ESP32 stream is connected. Use the bundled Camera Shield recording; it demonstrates the shared Link denial runtime, not independent proof of this capability.
Intended capability
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
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
This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.
24 GHz FMCW shares no propagation medium or protocol with 2.4 GHz WiFi, so RF denial of the mesh has no mechanism against it; the LD2410C's UART verdicts reach the host over the existing copper-failover path the jammer also cannot touch. Coverage is one in-room cone per radar, stated on the box.
Estate jam/silence verdict -> cabled node promotes LD2410 stream to primary -> presence + range-gate verdicts over copper failover -> live 'jammed but sensing' state to the operator with per-gate position
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Estate-scale drill: sustained denial of the mesh while movers traverse covered aisles; verdict latency and range attribution verified end-to-end over copper; graceful degradation confirmed when the copper host is down.
'Jammed is not blind' — for datacenter security owners whose response plan needs live position during the exact attack that kills their cameras.
A quiet reading is not an all-clear. If nodes are stale, degraded or jammed, this runtime says so explicitly. It never infers safety from missing data.