All capabilities
Camera Shield & Cage Watch Shared-family mapped

Cabinet Witness

Unattended Cabinet Presence Witness: Someone Is at That Rack

Records that somebody was standing at a particular rack, outside the hours they should have been.

Contested Space · Contested capability

What this capability does not do.

Does not act.

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.

Does not identify.

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.

Does not survive everything.

This witnesses a person at the cabinet, never the cabinet opening. Presence is CSI variance; it does not see a door. The door event belongs to rack-tamper-geometry-door-panel-blanking.

Across Camera Shield Jam the mesh and the wake never fires. Two people moving together read as one disturbance. Re-rack a row and the fade map is wrong until you recalibrate.

Observable
Per-link CSI amplitude variance across subcarriers, sampled at the mesh frame rate (about 6–9 Hz on ESP32-S3). No phase, no waveform, no audio.
Retention
A presence score and its state transitions. Raw CSI is consumed on the node and in your browser; it is never written to disk and never exported.
Node minimum
1 node
Export policy
Conditional — Exportable into a signed release, subject to the deployment’s own preflight.
Chain of custody

Node identity

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.

Reading provenance

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.

Install attestation

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 works

Properties you can map to your own controls

  • No optical sensor is present in this capability’s node set.
  • Raw CSI does not leave the node. Only derived event rows are stored or exported.
  • No stored identifier resolves to a person. Where access events are correlated, that correlation happens in your systems, against your logs.
  • The runtime executes on the node and in your browser. This capability has no cloud inference path.

These are properties, not certifications. Latent does not assert compliance with any framework on your behalf.

A capability description, not an incident record.
Readiness Shared-family mapped

Mapped to a shared offline runtime family and usable with a recording or compatible ESP32 CSI stream.

Evidence Strong theory Supported hypothesis

Published physics or adjacent results support the hypothesis; capability-specific product and site validation are still required.

Runtime family Presence

Calibrated motion and presence score from CSI variance and change statistics.

When no ESP32 is connected

No compatible ESP32 stream is connected. Use the bundled Camera Shield recording; it demonstrates the shared Presence runtime, not independent proof of this capability.

Intended capability

Pilot this intended outcome through the shared Presence family, then validate it against site-specific ground truth: Witnesses a person standing at a named cabinet outside a change window, and logs the interval with the cabinet's zone. The radar's static hold carries the nominally-still person at the rack face — a deliberately quiet body is exactly its target — while CSI attributes the zone: which links are perturbed says which cabinet. It witnesses a person at the cabinet, never the cabinet opening: neither sensor sees a door. The sibling that owns the door event is rack-tamper-geometry-door-panel-blanking, which detects the panel's geometry step directly — the two are designed to be read together, and neither substitutes for the other. Absence of presence is missing data, not evidence that nobody was there.

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

See the environment before installing it.

This exact kit is one of 191 first-class designs. It includes geometry, objects, nodes, wording, scenarios, installation, limitations, and catalog-bound readiness.

Shared-family mapped

No rendered revision is available yet.

Bundled recording

A related Camera Shield scene

This is one recorded vertical scenario. It is not separate validation of every capability in the catalog.

01 The physics

A person standing at a rack face is the mmWave radar's design case: a static target whose torso and limb micro-motion keeps returning 24 GHz energy in the aisle-aimed cone for as long as they stand there, however still they hold. The same body occupies the Fresnel volume of the CSI links that cross that aisle position, producing amplitude variance whose link pattern says which cabinet — the radar carries the hold and the mesh carries the address. The claim stays bounded to 'a body at this rack position', which is exactly what the two observables jointly support.

02 Shared processing path

Radar static-target energy on the aisle-aimed cone (the hold) + per-link CSI amplitude variance and low-velocity Doppler on aisle-crossing links (the address) -> adaptive PCA baseline against the cabinet zone's own quiet window with a mechanical-rhythm term -> presence verdict with dwell hysteresis, sustained by the radar through motionless intervals -> zone attribution to the named cabinet object in the layout -> interval row joined against the change calendar on a host.

This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.

03 Validation plan

Presence detection is class A in open rooms; the new claim is per-cabinet zone attribution in a metal-dense aisle. Own-hardware: eight nodes on one rack row, a person standing at each of 12 cabinets for 90 s in rotation, report per-cabinet attribution accuracy and confusion with adjacent cabinets; 14 nights of empty baseline with plant cycling for the false-presence rate.

04 Commercial hypothesis

'Cabinet Witness' — a change-window cross-check for the colo security lead, sold as an attendance record at named cabinets and explicitly not as a door sensor, which is the neighbouring entry's job. Plus tier: the aisle carries an aimed mmWave radar, because the person this entry exists to witness is the one holding still.

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.