Mapped to a shared offline runtime family and usable with a recording or compatible ESP32 CSI stream.
Intended capability
Pilot this intended outcome through the shared Zone dwell family, then validate it against site-specific ground truth: An append-only, signed record of every collaborative session a cell hosts: opened by a threshold crossing, carried by the in-cell hold, annotated with arm-active fraction and co-motion intervals, closed by an exit. A month of shared-space operation as the space saw it — dwell distributions, session counts by shift, contradictions with the declared production calendar — readable by an auditor without trusting a single robot log.
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.
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 ledger asserts nothing its feeder rows have not sensed: crossings from the threshold cone, presence from the in-cell hold, machine activity from the CSI cycle envelope. Its own contribution is bookkeeping discipline, not a sensing kernel — every entry carries its sensor scope and its no-assessment windows, and a session that ends in signal loss is closed as unresolved, never as an exit.
02 Shared processing path
Feeder events (threshold crossing, static hold, cycle envelope, co-motion intervals) -> session state machine with unresolved-exit handling -> per-session record with coverage and mask windows attached -> reasoning-tier join against declared shifts and cell modes (estate read-only) -> integrity-chained append; monthly roll-up feeds the cell certificate.
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: 50+ scripted sessions including deliberate pathological endings — sensor unplugged mid-session, operator lingering in the threshold, two-person entry; the ledger reconciled line-by-line against hand log and video; unresolved-exit and merge cases verified to be filed as such, never silently resolved.
04 Commercial hypothesis
'Session Ledger' — for the compliance officer: a month of collaborative sessions as the space saw them, append-only, with every gap on the record.