All capabilities
Datacenter Security Needs edge adapter

TouchLog

Taught-Axes Compliance Recorder

Every auditable action — open a panel, lift a tile — becomes a named, logged event.

Readiness Needs edge adapter

The evidence is proven or strong, but this capability still needs a capability-specific ESP32 or Rust runtime adapter.

Evidence Strong theory Supported hypothesis

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

Runtime family Not mapped

No browser runtime is assigned to this capability yet.

Why live sensing is unavailable

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

Validate this target only after a capability-specific adapter and ground-truth study exist: During commissioning, a technician deliberately performs every auditable physical action (open PDU panel, unlock cage, lift floor tile, open fire-riser cabinet) while the system watches — after which each action becomes a named, logged, timestamped RF event forever, forming a tamper-evident physical audit trail.

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

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.

Needs edge adapter

No rendered revision is available yet.

Bundled recording

A related Datacenter scene

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

01 The physics

Each discrete mechanical action produces a reproducible joint signature: a transient micro-Doppler burst (the motion) plus a persistent CIR geometry step (the new position of a metal panel/tile) — a two-factor physical fingerprint unique per action and location.

02 Shared processing path

Axis discovery (poke-and-observe supervised perturbations) builds a labeled axis per action -> CIR sparse recovery + Doppler features projected onto taught axes at runtime -> anomaly manifold catches physical events matching NO taught axis (the scariest category) -> compartment log per zone.

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

Own-hardware: teach 15-20 distinct actions in a server room, hold-out test 200 replays plus 50 untaught actions, measure per-axis classification accuracy and untaught-event catch rate; WiMANS for multi-activity separability priors.

04 Commercial hypothesis

A physical-world audit log to match your syslog — every panel, tile, and door event named and timestamped, and 'unknown physical event' as its own alarm class — sold to compliance-driven colo operators (SOC2, FedRAMP facilities).