Noise-Floor Tripwire: Every-Node Interference Watch
Logs how loud the radio background is in every room, and pages when several rooms get loud together.
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.
Every ESP32-S3 receiver maintains a noise-floor estimate for the 20 MHz channel it is tuned to, used internally for clear-channel assessment. A broad-spectrum emitter raises that estimate on every node inside its coverage simultaneously, so the spatial pattern of the rise — which nodes, how much, how fast — is a genuine physical observable at $6 per point, with no additional radio hardware.
Per-node noise-floor register sampling -> adaptive PCA baseline per node over its own diurnal history (rooms have rhythms) -> CUSUM on floor departure with a minimum simultaneity window across nodes -> corroboration gate -> argmax-node room attribution -> bounded event row.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Blocked on a host import that exposes the receiver's noise-floor register to the edge module — a signed-firmware ABI change, not a code change, so this entry ships pilot-only until that release lands. Own-hardware plan: eight nodes across four rooms, baselined a week to capture the building's own duty cycles, then a swept co-channel emitter walked room to room; report room-attribution accuracy and the false-page rate against microwave ovens, USB3 radiators and a saturated legitimate AP.
'Floor Rise' — a $6-per-room log source for the surface most SOCs cover with a rack unit per floor, or not at all, sold to the netsec lead who accepts room-granular attribution and nothing finer.
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.