Retained for transparency, but blocked from execution because the catalog physics review rejected it.
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.
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.