Rogue Emitter Grid: Zone Containment by Multi-Node RSSI
Finds roughly where an unexpected transmitter is sitting, by which nodes hear it loudest.
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.
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.
The evidence is proven or strong, but this capability still needs a capability-specific ESP32 or Rust runtime adapter.
Published physics or adjacent results support the hypothesis; capability-specific product and site validation are still required.
No browser runtime is assigned to this capability yet.
No capability-specific offline runtime is mapped yet. Keep the feature visible, explain the required edge adapter, and never fabricate a live result.
Intended capability
This describes the intended outcome. Readiness is needs edge adapter, 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.
In promiscuous mode an ESP32-S3 reports per-frame RSSI for 802.11 traffic on its tuned channel, and BLE scanning yields advertiser RSSI from the same die. Path loss makes received strength fall monotonically with distance, so the ranking of nodes that hear an emitter loudest is a real spatial constraint — degraded but not destroyed by multipath, which is why the honest output is a zone rather than a position.
Promiscuous per-frame RSSI capture + BLE advertiser scan slices -> per-emitter strength vector across nodes -> MVE zone attribution over the node-rank vector against the layout's named zones -> persistence gate (transient bursts are held, not paged) -> containment zone with a corroborating node count.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Blocked on the same link-stats host import that gates promiscuous frame metadata at the edge module boundary. Own-hardware plan: six nodes across a server room, a rogue AP and a BLE beacon walked to 20 surveyed positions, report zone-attribution accuracy and 90th-percentile position error against floor markings; measure how MAC randomization fragments unassociated-device tracks over an eight-hour office day.
'Emitter Grid' — zone containment for the physical-security engineer who has been handed a spectrum analyzer and told to sweep the floor by hand, sold with several-metre honesty and a printed list of the radios it cannot hear.
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.