Injection-Zone Presence Confirm
When an attack is running, checks whether a body is actually standing in the zone the attack seems to come from.
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.
RSSI attribution is 3–8 m zone-grade and the radar covers one cone: an attacker in an uncovered or mis-attributed zone reads as “planted/remote”, so “no body seen” must never close the incident. The camera adds nothing in darkness without illumination.
Across Airspace A jammer already running when you took the baseline is invisible. The baseline must be captured in a verified-quiet window, and a baseline of unknown provenance is worth nothing.
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.
Calibrated motion and presence score from CSI variance and change statistics.
No compatible ESP32 stream is connected. Use the bundled Airspace recording; it demonstrates the shared Presence 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.
Management-frame counting and RSSI zone ranking are this vertical's proven observables; the LD2410C confirms a human-scale moving or static target in the attributed zone's cone at ms latency on a band the attack cannot touch. Capture and TFLite person detection run locally and cloud-free; no streaming representation exists.
deauth-storm/jam verdict + RSSI zone rank -> LD2410 occupancy check of the attributed zone -> on-site vs planted/remote classification -> camera wake, bounded snapshot, local store -> journal event carrying all three verdicts
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Red-team exercises: scripted deauth from in-zone, adjacent-zone and planted-device positions; classification accuracy and snapshot hit rate measured; storage audit proving zero captures without a live attack verdict.
'Is the attacker in the building?' — for security operations turning an RF verdict into a physical-response decision.
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.