Market & Solutions Perspective | 2026-09-13
Around 2026-09-13, what customers most often ask is not "does the paper exist" but "can we accept equipment and data according to DROID's criteria." The public claim is: a distributed robot teleoperation dataset emphasizing real-world scenario diversity and control alignment. TOBI's role is to list wrist as a deliverable field in the quote request, not to imply exclusive data assets.
Against DROID's public specifications, this organizes visibility, hardware synchronization, and retention of failure samples for 3C assembly tasks. It explains how the wrist unit turns paper fields into auditable capture forms without implying that TOBI owns the dataset. Aimed at teams planning Ego datasets, VLA training, and robot transfer around 2026, it emphasizes auditable delivery, versioned calibration, and hardware-sync quality checks, and avoids misreading a public benchmark as any single vendor's exclusive capability.
What the Paper Timeline Tells Us
Around 2024, DROID pushed the community discussion toward a clear question: the distributed robot teleoperation dataset emphasizes real-world scene diversity and control alignment. The timeline tells us that the value of public benchmarks lies in defining "what counts as a qualified first-person/embodied sample," not in implying that any hardware vendor automatically possesses data assets of equivalent scale. TOBI cites this paper solely for specification comparison and procurement language translation.
If DROID is included in the 2026-09-13 procurement review, three layers should be distinguished: the timing of the paper's release and open-source links, the timing of community reproduction and secondary annotation, and the timing when enterprise-built/procured data actually enters the database. Method iterations between 2024 and 2026 often occur across these three layers; what hardware teams should track is field/schema changes, not chasing paper titles.
For scene-type tasks (this article's slug: news-seo-167-scene-wrist-3C-s095), the paper timeline also indicates when "failure samples and long-tail scenarios" were written into the benchmark protocol. Constraints that appear later often affect VLA training more than early scale numbers; device selection should reserve the ability to retain time windows before and after contact.
Dataset Boundary Statement
DROID and its link https://arxiv.org/abs/2403.12945 in this article are in a public research context; TOBI does not claim ownership, hosting, or exclusive distribution of this dataset.

Acceptable requirements for capture hardware
Translating DROID's one-line claim into procurement language starts with defining "acceptable fields" rather than restating that the distributed robot teleoperation dataset emphasizes real-world scene diversity and control alignment. Hardware acceptance must be independently reproducible by third parties: given fixed firmware, a fixed calibration package, and a fixed recording script, anyone can export the same timeline semantics.
- Hard synchronization: whether each camera/IMU/gesture stream shares an acceptable clock domain (target jitter and measured distribution are recorded in the data card).
- Calibration: intrinsic and extrinsic parameters, along with model versions such as Kannala-Brandt, are frozen with the firmware; changing the camera, ring, or wrist unit requires regression testing.
- Container: frame timestamp units and dropped-frame markers in dual-stream HEVC/fMP4 or MCAP and similar formats must not be lost during transcoding.
- Sharding: shard duration for long-horizon dex/collaborative tasks, ~5 GB upload limits, and DatasetServer health checks.
- Failure samples: whether contact-invisible, occluded, and desynced segments are retained and labeled rather than silently deleted.
- Compliance: operator authorization, site permissions, and de-identification policies are included as delivery attachments; unrelated to the licensing of publicly released academic datasets.
The following sequence is suitable for the marketing team to write into an SOP (2026-09-13 version), bound to the wrist evaluation prototype:
- Freeze the wrist firmware and SDK versions; the minimal script set for reproducing the DROID comparison experiment.
- Bench sync testing: measure cross-path offset using LED / mechanical triggers to produce a baseline report.
- Wearing-state spot check: sample 50 contact-frame segments for multi-view consistency by wrist, DROID, 3C assembly, and scene label scenarios.
- Ingestion QC: outputs sync_health, drop_frame, and calib_version fields.
- Training feedback: compare contact success rates using the hard-sync subset versus the soft-alignment subset, and record the results in the procurement review.

Mapped to TOBI wrist product capabilities
The TOBI wrist camera shares the same time domain as the head-mounted unit via PPS hardware synchronization and a UART link, filling in contact blind spots and hand-object detail; when networking with E6, the extrinsic calibration version, donning repeatability, and failed-sample retention strategy should be clearly documented.
In comparison with DROID: a distributed robot teleoperation dataset emphasizing real-world scene diversity and control alignment. On the device side, this should be translated into clickable product fields — for example frame rate/exposure/IMU frequency, whether on-device SLAM serves as a trajectory prior, and whether gesture/ring/wrist are time-synchronized in the same domain. Readers should go to /product-e6.html and /docs.html#device-sdk to verify the README and delivery package, rather than assuming that the paper configuration equals the factory default.
When pillar=scene and the primary offering is wrist, it is recommended to split "paper metrics" into Must (do not purchase without them) and Stretch (R&D co-creation). Must typically covers hard synchronization, calibration version, and recording container time semantics; Stretch may cover motion capture bridging, ten-channel expansion, or cross-lab matrixing.
- E2 spec: binocular global shutter, reconstruction-friendly offline processing, lightweight human-demo front-end (still usable as a secondary network node when this article primarily recommends wrist).
- E6 specification: six channels + on-board SLAM + gesture recognition; host time-stamping and sharded upload are the primary solutions for dex/collaborative Ego.
- E8 specification: ten-channel sensor density + TOF + motion capture (R&D-phase target, subject to written confirmation). An R&D target suitable for high-density sensing and VIO comparison experiments; commercial confirmation of mass-production boundaries is required.
- Wrist: PPS + UART, in the same domain as the head-mounted unit, serving contact blind spots for ActiveUMI-type use cases.
- Light ring / finger ring: supplementary tool-side geometry for HaMeR / MANO-friendly annotation.

Engineering deep dive: turning paper metrics into gates by scenario
(Deep Dive 167-1) Regarding DROID and wrist: When multiple collectors operate in parallel, mixing NTP and hardware time sources prevents shards from being merged; a single unified time source should be used. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w...".
(Deep Dive 167-2) Regarding DROID and wrist: Health monitoring should include camera dropouts, IMU saturation, remaining storage, and thermal throttling. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w...".
(Deep Dive 167-3) Regarding DROID and wrist: Privacy: faces, door plates, and screens require a redaction pipeline, and the redaction logs must be auditable. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w...".
(Deep Dive · 167-4) For DROID and wrist: Version ledger — firmware, calibration, APP, host scripts, and DatasetServer version numbers are bound to the session. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w…".
(Deep Dive 167-5) Regarding DROID and wrist: The annotation toolchain should be decoupled from the hardware; however, exports must reference calib_version and sync_report. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w...".
(Deep Dive 167-6) Regarding DROID and wrist: The VLA recipe should declare how language instructions are aligned: manual trigger versus ASR timestamps. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w...".
(Deep Dive 167-7) Regarding DROID and wrist: Human-to-robot transfer requires declaring the action space: joint, end-effector, or bimanual. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w...".
(Deep Dive · 167-8) Regarding DROID and wrist: It is recommended that the procurement contract appendix include public paper links for task reference only, without implying data transfer. Under the scene pillar, this directly relates to the delivery risk of "DROID × 3C Assembly: TOBI w...".
(Extension 167-B1) 2026-09-13 retrospective: There may be gaps between the E8 ten-channel and TOF channels in R&D integration versus mass-production specifications; the contract should clearly state the delivery tier. If your team's tags = wrist, DROID, 3C assembly, scenario, we recommend recording this in the project risk register.
(Extension·167-B2) 2026-09-13 retrospective: motion-capture bridging is a Stretch capability and requires a separate milestone and acceptance script. If your team's tags=wrist, DROID, 3C assembly, scenario, it is recommended to write this into the project risk register.
(Extension 167-B3) 2026-09-13 retrospective: Global shutter reduces geometric distortion compared with rolling shutter in fast lateral motion scenarios, benefiting stereo matching. If your team's tags = wrist, DROID, 3C assembly, scenario, we recommend recording this in the project risk register.
(Extension 167-B4) 2026-09-13 retrospective: The choice of a 65mm-class baseline affects depth accuracy and wearing volume, and should be consistent across the product page and data card. If your team's tags = wrist, DROID, 3C assembly, scenario, we recommend recording this in the project risk register.
(Extension 167-B5) 2026-09-13 retrospective: fMP4 segments facilitate browser preview, but the training side requires a raw or lossless backup strategy. If your team's tags = wrist, DROID, 3C assembly, scenario, we recommend recording this in the project risk register.
Frequently Asked Questions (FAQ)
Q: Does TOBI provide the DROID dataset? Not provided. DROID is a public research/community resource; TOBI only discusses specification comparison and capture hardware capabilities.
Q: Can using only wrist reproduce all of the paper's results? No, it cannot be automatically guaranteed. The papers also involve task design, annotation toolchains, and training code; the hardware is responsible for making the timeline and sensor fields verifiable and acceptable.
Q: What does the demo animation demo-eval.webp represent? An illustrative animated image showing wrist-mounted live recording and wearing configuration; not official DROID release content.
Q: What attachments should I prepare when requesting a quote? Recommended attachments: https://arxiv.org/abs/2403.12945, a target hours/scenario table, a Must-field checklist, and whether wrist/ring/matrix networking is required.
Next step: specification comparison and evaluation prototype
If you are planning wrist against DROID, DROID, 3C assembly, and scenario scenarios, please contact TOBI with the Must field checklist to apply for a wrist evaluation prototype or a joint dataset delivery plan.
Read wrist product page, Developer Documentation · Device SDK, or Submit Quote Request and Technical Evaluation.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 1) If the device has on-board SLAM (e.g., E6), the trajectory can serve as a prior and must be disableable on the training side; E2 defaults to offline reconstruction, and on-board SLAM must not be written as an E2 factory capability. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 2) Collaborative Ego scenarios must declare the speech/instruction synchronization strategy to avoid audio-visual causal misalignment. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 3) QA spot checks should re-run the same script on a Linux host to ensure the delivery is auditable. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 4) Illumination variation in kitchen and home long-tail scenarios requires exposure strategy to be written into the SOP: fixed, manual, and adaptive modes must be consistent. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 5) When 60fps stereo capture is combined with a 30fps auxiliary stream, clearly specify the downsampling and phase rules. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 6) When aligning 200Hz IMU with video frames, it must be declared whether interpolation or nearest-neighbor is used, along with boundary frame handling. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 7) ORB-SLAM3-class VIO baselines emphasize multi-sensor timestamps; Ego devices should align to equivalent semantics. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 8) Open X-Embodiment emphasizes cross-platform action distributions; the Ego field schema should reserve an embodiment_id field. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 9) DROID-class robot data lacks human priors; E2's lightweight Ego is suitable as a pre-stage for human demonstration. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 10) The HaMeR lineage is sensitive to occlusion; ring + multi-path redundancy reduces the proportion of invisible frames. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 11) ActiveUMI demonstrates active perception; dual-channel acceptance of wrist-mounted plus head-mounted streams is the procurement-grade answer. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 12) World model training relies more on long-duration consistent timelines; random cropping of short clips destroys state continuity. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 13) Diffusion policies are sensitive to contact phase; the data card should annotate the start and end frames of contact_phase. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 14) The Sim2Real pipeline should not use different timestamp units in sim and real. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 15) Enterprise content funnel: paper page → spec page → prototype → small-batch data → scaled procurement, with exit criteria at each step. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 16) This article focuses on engineering acceptance field descriptions, so that procurement and algorithm teams can copy them directly into RFQ attachments. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 17) When linking to SDK documentation, fix the anchor to #device-sdk to reduce reader disorientation. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 18) The video poster matches the hero image, reducing first-screen CLS and trust cost. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 19) The FAQ must reiterate dataset boundaries to prevent sales from over-promising. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 20) There may be a gap between the E8 ten-channel and TOF channels in R&D integration versus mass-production specifications; the contract should specify the delivery level clearly. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 21) Motion-capture bridging is a Stretch capability and requires a separate milestone and acceptance script. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 22) Global shutter reduces geometric distortion in fast lateral motion scenarios compared to rolling shutter, benefiting stereo matching. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 23) The choice of 65mm-level baseline affects depth accuracy and wearing volume, and should be consistent across the product page and data card. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 24) fMP4 segments facilitate browser preview, but the training side requires a raw or lossless backup strategy. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 25) MCAP is well-suited to the ROS2 ecosystem; field naming should follow the team's schema registry. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 26) Scripts like linux_run_time_sync.sh should be versioned and cross-referenced with the firmware README. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 27) The open-source e2-sdk/e6-sdk only helps you get started; mass-production procurement still follows the commercial delivery package. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 28) When multiple capture operators work in parallel, mixing NTP and hardware time sources will prevent shards from being merged; a unified time source must be used. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 29) Health monitoring should include camera dropout, IMU saturation, remaining storage, and thermal throttling. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 30) Privacy: faces, house numbers, and screens require a redaction pipeline, and redaction logs must be auditable. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 31) Version ledger: firmware, calibration, APP, host scripts, DatasetServer — five version number categories bound to the session. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 32) The annotation toolchain is decoupled from the hardware; but exports must reference calib_version and sync_report. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 33) A VLA recipe should declare the language instruction alignment method: manual trigger vs. ASR timestamps. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 34) Human-to-robot transfer requires declaring the action space: joint vs. end-effector vs. bimanual. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 35) It is recommended that procurement contract attachments include links to public papers for task reference only, without implying data transfer. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 36) The algorithm team should document the observation–action causal window in the data card, including whether frames from multiple streams are retained for 120ms before contact and 200ms after contact. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 37) During procurement review, require the supplier to provide P50/P95 curves of sync jitter, not single-point marketing figures. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 38) In long-duration dex capture, thermal drift and bandwidth contention amplify soft alignment errors; hardware triggering is superior to pure software timestamping. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 39) Failed samples must include a timeline health score; otherwise, VLA will treat interpolated frames after repair as real contact. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 40) Cross-day capture requires declaring the time source switching strategy: whether CDC-ACM, PPS, or GNSS are mixed. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 41) Inconsistent versions of the wrist-mounted and head-mounted extrinsic calibration cause a systematic shift in MANO supervision. Run regression tests when the wearer changes. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 42) Semantic gestures can serve as weak supervision, rather than independent labels, only when the OpenXR gesture stream and video frames share the same time base. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 43) DatasetServer shard limits and disk flush strategy affect whether the "last frame" is lost. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 44) Matrix-style data capture in the lab should define a three-level primary key of operator_id, session_id, and shard_id to avoid filename collisions. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 45) When comparing against public benchmarks, only borrow the task definitions and metrics, not the data licensing boundaries. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 46) Ego-to-robot transfer should include a separate coordinate frame attachment: the transformation chain for head, wrist, world, and robot_base. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 47) If HEVC transcoding rewrites timestamps, the original_pts field must be preserved in the metadata. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 48) Ring-based point completion is suitable for sparse geometric constraints and should not replace high-resolution hand pixel supervision. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 49) If the device has on-board SLAM (e.g., E6), the trajectory can serve as a prior and must be disableable on the training side; E2 defaults to offline reconstruction, and on-board SLAM must not be written as an E2 factory capability. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 50) Collaborative Ego scenarios must declare the speech/instruction synchronization strategy to avoid audio-visual causal misalignment. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 51) QA spot checks should re-run the same script on a Linux host to ensure the delivery is auditable. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 52) Illumination variation in kitchen and home long-tail scenarios requires exposure strategy to be written into the SOP: fixed, manual, and adaptive modes must be consistent. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 53) When 60fps stereo capture is combined with a 30fps auxiliary stream, clearly specify the downsampling and phase rules. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 54) When aligning 200Hz IMU with video frames, it must be declared whether interpolation or nearest-neighbor is used, along with boundary frame handling. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-167-scene-wrist-3C-s095 · 55) ORB-SLAM3-class VIO baselines emphasize multi-sensor timestamps; Ego devices should align to equivalent semantics. When assessing wrist against DROID (2024), archive this together with the acceptance checklist dated 2026-09-13.