Airspace Emitter Census: Day-Over-Day Inventory Delta
Takes a nightly roll call of everything transmitting in the building and tells you what is new.
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.
Protocol-visible emitters announce themselves: Wi-Fi BSSIDs and station frames carry stable addresses in the clear, and a subset of BLE advertisers use stable or resolvable identities. Differencing the set heard across a scan schedule against an enrolled set is a set operation on real, repeatably observable identifiers, which is why it survives multipath that would ruin a position estimate.
Scheduled scan slices (Wi-Fi channel walk + BLE advertiser sweep) -> stable-identifier extraction with a quarantine-then-expire lane for randomized addresses -> set difference against the enrolled inventory -> persistence scoring across consecutive census windows -> MVE zone attribution for confirmed new identities -> nightly delta 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 the link-stats host import. Own-hardware plan: 14 nights in a working office plus a server room, enrol the known estate, introduce three unauthorized emitters on unannounced nights, report catch rate, nights-to-confirm, and the daily false-delta count driven by visitor phones under MAC randomization.
'Nightly Census' — the inventory question a CISO already asks of the network, asked of the air instead, sold to the security engineering lead who accepts that it bounds what was heard and never what is present.
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.