Copper Failover Uplink: The Alert Path a Jammer Cannot Reach
Cabled nodes keep a wire to shout down when the radio is 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.
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.
Conducted signalling on a differential copper pair shares no medium with the 2.4 GHz airspace, so radio-frequency denial has no mechanism to reach it. The ESP32-S3's native USB serial already carries the enrollment and flashing path, which is why the transport exists today at short range; the distance limit is USB's own electrical budget, not a radio one.
Transport resilience, not a sensing kernel — no detection pipeline is claimed. Local jam or link-loss verdict -> wired serial framing to the local host -> host relay to the SOC -> per-node uplink-health ledger that pages on the silence of any node, cabled or not.
This is a capability design path. Components may be shared with other catalog entries; it is not presented as a unique algorithm.
Own-hardware: three cabled nodes plus one deliberately uncabled node on a powered hub to one host, exercised under a broadband emitter; report wired alert delivery latency during total radio blackout and verify that the uncabled node's silence pages within the configured heartbeat window. The RS-485 variant cannot be validated until a hardware profile carrying a transceiver exists in both the firmware profile catalog and the deployment registry.
'Copper Last Mile' — an out-of-band alert path for the rows that matter most, sold to the facility security director with the topology stated on the box: a 5 m star per host today, RS-485 multi-drop on the roadmap, and coverage that ends exactly where the cable ends.
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.