Blackout Occupancy Ledger
Keeps writing down whether anyone was in the room, even while the radios are being drowned out.
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.
Cone-scoped: an intruder outside the radar cone during blackout yields an honestly-empty ledger that must never be read as “nobody was on site”. Physical destruction or power cut of the node ends the record — and that truncation is itself the finding.
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.
The LD2410C's 24 GHz FMCW chain is fully independent of the jammed 2.4 GHz band, and its per-gate moving/static energies arrive over UART regardless of link state; flash logging needs no radio at all. The node cannot egress during broadband jam — it senses and records, and the journal's silence-is-an-alarm doctrine covers the live gap.
Jam/silence verdict from link-denial-tripwire -> switch LD2410 stream to local flash ring -> timestamped presence/range ledger through the blackout -> journal back-fill + gap annotation on link recovery
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Chamber tests: full 2.4 GHz denial with scripted occupancy in the cone; ledger completeness and clock integrity across the blackout; faithful journal back-fill; power-loss-during-blackout recovery test.
'The blackout has a transcript' — for security teams who need to know whether anyone was in the room while the RF was down.
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.