All capabilities
Cobot Cell Witness Physics limit

TouchProof

Contact-Force Limit Verification via RF

People wish the radio field could verify that a collaborative robot never pressed too hard on a person. It cannot — and this entry exists so nobody re-sells the idea.

Readiness Physics limit

Retained for transparency, but blocked from execution because the catalog physics review rejected it.

Evidence Frontier Unvalidated concept

An early research proposal with no capability-specific product validation yet.

Runtime family Not mapped

No browser runtime is assigned to this capability yet.

Why live sensing is unavailable

The inverting mechanism is dynamics-from-kinematics: force equals effective mass times deceleration, so the pitch reads deceleration from the CSI motion envelope and multiplies by a mass model. Two independent kills. First, path-length modulation carries no force information — a 30 N brush and a 150 N clamp can produce identical motion envelopes because effective mass, contact stiffness, and pose are unknowns RF cannot observe, so the inversion is underdetermined at any sampling rate; this is the band's rule 3 stated as physics rather than policy. Second, the contact transient occupies milliseconds and structural bands far above the 3.3 Hz ambient CSI Nyquist (0.41 Hz on the decimated WASM path), so the deceleration the model needs is never sampled — this kill holds even granting a perfect mass model, which makes the two kills independent. A third bar is structural rather than physical: verifying force limits is a performance claim against the certified stack's own protective function, barred by R-A1 regardless of what the physics could do, and injury-severity inference is barred with it. The salvageable sliver: the PDM mic honestly detects an impact as a broadband level transient — 'a contact event occurred at T' can enter the session ledger and the cell certificate as an event marker with no severity attached, and that sliver already ships inside the cycle-conformance and phantom-actuation rows, where its claim stays within one sensor's physics.

Intended capability

Document why this proposed outcome is blocked by the reviewed physics: The tempting row: independently verify that a power-and-force-limited cobot's contacts stayed under the declared force and pressure limits — reading contact severity out of the arm's motion envelope at the moment of touch, an auditor's dream for collaborative cells. Rejected: force is not an RF observable, and the row is written down so nobody re-pitches it.

This describes the intended outcome. Readiness is physics limit, evidence is class C, 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.

Physics limit

No rendered revision is available yet.

Bundled recording

A related Cobot scene

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

01 The physics

The pitch inverts kinematics into dynamics: contact deceleration, read from the CSI envelope, times an assumed effective mass, would yield force. Both factors fail. Effective mass and contact stiffness are pose-, payload-, and tissue-dependent unknowns RF cannot supply; and the contact transient itself lives at millisecond timescales and structural-vibration frequencies far above the 3.3 Hz ambient Nyquist — the envelope never even sees the event it would need to differentiate.

02 Shared processing path

CSI envelope deceleration estimate -> assumed effective-mass model -> force estimate — dead at both stages: stage one is unsampleable at ambient rates, the second is unknowable from RF.

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

None — rejected at physics review; the impact-event sliver is validated inside cobot-cycle-conformance-drift and cobot-phantom-actuation, where it honestly lives.

04 Commercial hypothesis

The row that would have sold itself: 'independent proof your cobot never exceeded its declared contact limits' — which is exactly why it is written down as dead.