Retry-Storm CSI Harvest: Attacker-Triggered Sampling Burst
Trying harder to send during an attack was supposed to gather more evidence — it gathers less.
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.
Retained for transparency, but blocked from execution because the catalog physics review rejected it.
An early research proposal with no capability-specific product validation yet.
No browser runtime is assigned to this capability yet.
Retry-storm CSI density inverts under jamming. CSI is captured only on frames that were successfully received; a retry is the symptom of a frame that did not arrive, so the jamming that triggers the retry storm destroys the very samples this claims to harvest. Two further independent kills: a single-antenna ESP32-S3 cannot aim sampling at a camera's field of view — that needs a phased array this hardware does not have — and own-link CSI carries no attacker-device telemetry whatsoever, no MAC, no chipset, no emissions signature. The salvageable sliver, escalating from ~6.6 Hz ambient to the dedicated ESP-NOW 76–146 Hz carrier at the first sign of link degradation, is a burst mode of link-denial-tripwire, not a capability, and it loses outright to any fast-onset jammer. The correct responses to a jammer are link-denial-tripwire and same-band-ble-alert-egress.
Intended capability
This describes the intended outcome. Readiness is physics limit, evidence is class C, 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.
CSI is estimated from the preamble of a frame that was successfully received. A retry is the symptom of a frame that was not received, so under active jamming the retry count rises while the count of frames carrying usable CSI falls. Two further independent kills: CSI is a property of a transmitter-receiver link, not a beam, so a single-antenna node cannot concentrate sampling on a camera's field of view; and the channel response of one's own link encodes the propagation environment, not the emitter that ruined it.
Retired — no pipeline is proposed. The salvageable fragment is an escalation from ~6.6 Hz ambient CSI to the dedicated ESP-NOW 76-146 Hz carrier at first sign of link degradation, which is a burst mode inside the jam_detect family, not a capability of its own.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Not scheduled. The falsifying experiment is trivially cheap and was run in reasoning rather than on the bench: increase retry rate under a co-channel jammer and count frames yielding a CSI estimate — the count falls, which is the whole result.
Retired before it was offered. The correct responses to a jammer are link-denial-tripwire for the verdict and same-band-ble-alert-egress for getting that verdict out of the building.
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.