Cage Calibration Drift Audit: Is the Baseline Still Worth Anything
Watches whether the room still matches the picture it was taught, and says when a zone is no longer trustworthy.
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.
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.
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.
A room's static multipath is a slowly varying quantity: racks, cable trays and doors set the fade structure, and each physical change writes a permanent step into it. Separating a step (something moved and stayed moved) from a transient (someone walked past) is a timescale discrimination — steps persist across the quiet windows that transients do not survive — which is what makes staleness measurable rather than guessed.
Per-zone static-geometry snapshot from CIR sparse recovery + per-link amplitude fade structure -> step-change detection against the stored commissioning baseline across quiet windows -> compartment CUSUM accumulating per-zone drift -> staleness score with a hard threshold that marks the zone untrustworthy and names the links responsible.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Own-hardware: eight nodes in a live cage row, commission a baseline, then apply 20 scripted room changes over six weeks — re-rack a row, move a crash cart, prop a door, add blanking plates — and report which changes cross the staleness threshold, at what magnitude, and how many days of ordinary operations pass before a false staleness flag appears. No runtime kernel computes the headline; the audit consumes geometry snapshots on a host, following the taught-axes-compliance-recorder precedent.
'Baseline Provenance' — the audit an assessor asks for when told a fade map is doing security work, sold to the compliance officer as the reason the other entries in this vertical are allowed to make claims at all.
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.