All capabilities
Cobot Cell Witness Shared-family mapped

Shared-Space Witness

Shared-Space Witness: Co-Motion Intervals on the Record

Writes down every stretch of time a person and the moving robot arm truly shared the workspace.

Readiness Shared-family mapped

Mapped to a shared offline runtime family and usable with a recording or compatible ESP32 CSI stream.

Evidence Strong theory Supported hypothesis

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

Runtime family Zone dwell

Time-in-zone estimate from calibrated presence transitions.

When no ESP32 is connected

No compatible ESP32 stream is connected. Use the bundled Cobot recording; it demonstrates the shared Zone dwell runtime, not independent proof of this capability.

Intended capability

Pilot this intended outcome through the shared Zone dwell family, then validate it against site-specific ground truth: Records every interval a human occupied the collaborative workspace while the arm was in motion — the month-deep independent record of when and for how long shared-space operation occurred under speed-and-separation collaboration (ISO/TS 15066 lineage, now carried in ISO 10218:2025). The certified safety stack owns separation live; nothing independent records how often a human and a moving arm actually shared the space over months. This row is that record — evidence only, never a function in the loop, and never a separation-performance verdict. Sibling declared: cobot-threshold-truth supplies the crossing; this row builds the co-motion interval.

This describes the intended outcome. Readiness is shared-family mapped, 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.

Shared-family mapped

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

Two independent channels, split so neither borrows the other's weakness. The LD2410C cone is aimed across the operator side of the workspace, where its single-composite-target physics is safe: it holds a person to ~6 m by breathing micro-motion even when they stand dead still, and no machine transit crosses its cone to mask them. Arm motion is read from the CSI field: a cycling arm writes a machine-regular motion envelope — metronomic period, near-zero jitter — that ambient 6.6 Hz sampling resolves for task cycles from ~1 s upward. Neither verdict is taken from the robot controller.

02 Shared processing path

LD2410 presence + range-gate hold on the operator approach volume -> per-slot CSI motion-envelope energy + autocorrelation period with jitter statistic (machine-regular = arm cycling) -> co-occurrence interval builder (human-held AND arm-cycle-active) with entry/exit hysteresis -> event-bounded person-confirm snapshot at interval onset -> reasoning-tier classification against the declared cell mode (collaborative vs fenced, estate read-only) -> signed interval row into the session ledger.

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-cell protocol: scripted operator entries against a metronome-driven arm proxy running repeatable 2-10 s cycles; 200+ intervals hand-logged with video ground truth; metrics are interval-boundary error (target <2 s), still-operator hold ratio over 10-minute freezes, and false co-motion rate with the workspace empty. Cone-masking windows exercised deliberately and shown to be filed as no-assessment.

04 Commercial hypothesis

'Shared-Space Witness' — for the safety and compliance owner of collaborative cells: the independent record that shared-space operation occurred — when, and for how long — evidence for the audit, with the certified stack authoritative on every page.