Operations & Delivery Perspective | 2026-09-13 SOP Draft
As of 2026-09-13, when incorporating Ego-OSCAR into the content funnel, the operations side needs an executable chain: readers enter from the paper abstract, leave with the acceptance questions corresponding to "open-source stereo plus IMU low-cost Ego capture route, emphasizing a reproducible hardware stack," and receive an acceptance attachment template for E6. This likewise does not claim that TOBI holds the public benchmark embodiment.
Against the public Ego-OSCAR specifications, organize visibility, hardware synchronization, and failed-sample retention for commercial kitchen tasks. Explain how E6 turns paper fields into auditable capture forms, without implying that TOBI owns this dataset. Aimed at teams planning Ego datasets, VLA training, and robot transfer around 2026, emphasizing auditable delivery, versioned calibration, and hardware synchronization quality checks, while avoiding misreading public benchmarks as any single vendor's exclusive capability.
What the Paper Timeline Tells Us
Around 2024, Ego-OSCAR pushed community discussion toward a clear question: an open-source stereo plus IMU low-cost Ego capture approach, emphasizing a reproducible hardware stack. The timeline tells us that the value of a public benchmark 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 for specification comparison and procurement language translation only.
If Ego-OSCAR 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-078-scene-e6-餐饮-s006), 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
Ego-OSCAR and its link https://github.com/china-langhui-ego/e2-sdk 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 Ego-OSCAR's one-line claim into procurement language starts with defining "acceptable fields" rather than restating that the open-source stereo plus IMU low-cost egocentric capture approach emphasizes a reproducible hardware stack. 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 ops team to write into the SOP (2026-09-13 edition), bound to the E6 evaluation prototype:
- Freeze the E6 firmware and SDK versions, and provide the minimal script set to reproduce the Ego-OSCAR comparison experiment.
- Bench sync testing: measure cross-path offset using LED / mechanical triggers to produce a baseline report.
- Worn-state spot check: randomly sample 50 contact frames for multi-view consistency across scenarios tagged E6, Ego-OSCAR, commercial kitchen.
- 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.

Mapping to TOBI E6 Product Capabilities
TOBI E6 is a six-channel camera production-grade capture platform with on-board SLAM and OpenXR gesture pipeline integration. Host-side CDC-ACM time synchronization, DatasetServer sharding, and health monitoring form a standard delivery loop; suitable for dexterity, collaborative Ego, and multimodal long-horizon tasks.
Compared with Ego-OSCAR: an open-source stereo-plus-IMU low-cost egocentric capture route emphasizing a reproducible hardware stack. On the device side, this should be translated into clickable product fields — for example, frame rate / exposure / IMU frequency, whether on-board SLAM serves as a trajectory prior, and whether gesture / ring / wrist devices share the same time domain. Readers should go to /product-e6.html and /docs.html#device-sdk to verify the README and delivery package, rather than assuming the paper configuration equals the factory default.
When pillar=scene and the primary recommendation is E6, it is recommended to split "paper metrics" into Must (no 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-laboratory matrix networking.
- E2 positioning: binocular global shutter, offline-reconstruction-friendly, lightweight human-demonstration front-end (can still serve as a secondary network node when this article primarily recommends E6).
- 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 · 78-1) For Ego-OSCAR and E6: the algorithm team should document the observation–action causal window in the data card: whether multi-stream frames are retained for 120 ms before and 200 ms after contact. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × Commercial Kitchen: TOB...".
(Deep Dive · 78-2) For Ego-OSCAR and E6: during procurement review, suppliers are required to provide P50/P95 curves for sync jitter rather than a single headline figure. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × commercial kitchen: TOB…".
(Deep Dive · 78-3) For Ego-OSCAR and E6: in long-duration dexterous capture, thermal drift and bandwidth contention amplify soft-alignment error; hardware triggering is preferable to pure software timestamping. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × Commercial Kitchen: TOB...".
(Deep Dive · 78-4) For Ego-OSCAR and E6: failed samples must carry timeline health scores, otherwise VLA training will treat interpolated frames after repair as real contact. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × Commercial Kitchen: TOB...".
(Deep Dive · 78-5) For Ego-OSCAR and E6: cross-day capture must declare the time-source switching strategy: whether CDC-ACM, PPS, or GNSS are mixed. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × Commercial Kitchen: TOB...".
(Deep Dive · 78-6) For Ego-OSCAR and E6: when extrinsic versions for wrist and head-mounted cameras are inconsistent, MANO supervision will be systematically offset; changing the wearer requires regression testing. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × Commercial Kitchen: TOB...".
(Deep Dive · 78-7) For Ego-OSCAR and E6: only when the OpenXR hand gesture stream and video frames share the same domain can semantic gestures be used as weak supervision rather than independent labels. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × Commercial Kitchen: TOB...".
(Deep Dive · 78-8) For Ego-OSCAR and E6: the DatasetServer sharding limit and disk flush strategy affect whether the "last frame" is lost. Under the scene pillar, this directly relates to the delivery risk of "Ego-OSCAR × Commercial Kitchen: TOB…".
(Extension · 78-B1) 2026-09-13 retrospective: matrix-style laboratory capture should define three-level primary keys — operator_id, session_id, shard_id — to avoid filename collisions. If your team's tags = E6, Ego-OSCAR, commercial kitchen, scenario, it is recommended to record this in the project risk register.
(Extension · 78-B2) 2026-09-13 retrospective: when comparing against public benchmarks, only borrow task definitions and metrics, not data licensing boundaries. If your team's tags = E6, Ego-OSCAR, commercial kitchen, scenario, it is recommended to record this in the project risk register.
(Extension · 78-B3) 2026-09-13 retrospective: Ego-to-robot transfer should include a separate coordinate-frame appendix: the transform chain for head, wrist, world, and robot_base. If your team's tags = E6, Ego-OSCAR, commercial kitchen, scenario, it is recommended to record this in the project risk register.
(Extension · 78-B4) 2026-09-13 retrospective: If HEVC transcoding rewrites timestamps, the original_pts field must be preserved in the metadata. If your team's tags=E6,Ego-OSCAR,commercial kitchen,scenario, this should be written into the project risk register.
(Extension · 78-B5) 2026-09-13 retrospective: ring-based point supplementation is suitable for sparse geometric constraints and should not replace high-resolution hand-pixel supervision. If your team's tags = E6, Ego-OSCAR, commercial kitchen, scenario, it is recommended to record this in the project risk register.
Frequently Asked Questions (FAQ)
Q: Does TOBI provide the Ego-OSCAR dataset? No. Ego-OSCAR is a public research/community resource; TOBI only discusses specification comparison and capture hardware capabilities.
Q: Can E6 alone reproduce all the results in the paper? 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-stream.webp represent? An illustrative animated image showing E6 live recording and wearing form, not official Ego-OSCAR released content.
Q: What attachments should I prepare when requesting a quote? It is recommended to attach https://github.com/china-langhui-ego/e2-sdk, a target hours/scene table, a Must-field checklist, and whether wrist/ring/matrix networking is required.
Next step: specification comparison and evaluation prototype
If you are planning E6, Ego-OSCAR, commercial kitchen, scene scenarios against Ego-OSCAR, please contact TOBI with the Must field list to apply for an E6 evaluation prototype or a joint dataset delivery plan.
Read E6 Product Page, Developer Documentation · Device SDK, or Submit Quote Request and Technical Evaluation.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 1) Privacy: faces, house numbers, and screens require a redaction pipeline, and redaction logs must be auditable. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 2) Version ledger: firmware, calibration, APP, host scripts, DatasetServer — five version number categories bound to the session. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 3) The annotation toolchain is decoupled from the hardware; but exports must reference calib_version and sync_report. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 4) A VLA recipe should declare the language instruction alignment method: manual trigger vs. ASR timestamps. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 5) Human-to-robot transfer requires declaring the action space: joint vs. end-effector vs. bimanual. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 6) It is recommended that procurement contract attachments include links to public papers for task reference only, without implying data transfer. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 7) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 8) During procurement review, require the supplier to provide P50/P95 curves of sync jitter, not single-point marketing figures. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 9) In long-duration dex capture, thermal drift and bandwidth contention amplify soft alignment errors; hardware triggering is superior to pure software timestamping. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 10) Failed samples must include a timeline health score; otherwise, VLA will treat interpolated frames after repair as real contact. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 11) Cross-day capture requires declaring the time source switching strategy: whether CDC-ACM, PPS, or GNSS are mixed. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 12) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 13) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 14) DatasetServer shard limits and disk flush strategy affect whether the "last frame" is lost. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 15) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 16) When comparing against public benchmarks, only borrow the task definitions and metrics, not the data licensing boundaries. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 17) Ego-to-robot transfer should include a separate coordinate frame attachment: the transformation chain for head, wrist, world, and robot_base. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 18) If HEVC transcoding rewrites timestamps, the original_pts field must be preserved in the metadata. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 19) Ring-based point completion is suitable for sparse geometric constraints and should not replace high-resolution hand pixel supervision. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 20) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 21) Collaborative Ego scenarios must declare the speech/instruction synchronization strategy to avoid audio-visual causal misalignment. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 22) QA spot checks should re-run the same script on a Linux host to ensure the delivery is auditable. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 23) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 24) When 60fps stereo capture is combined with a 30fps auxiliary stream, clearly specify the downsampling and phase rules. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 25) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 26) ORB-SLAM3-class VIO baselines emphasize multi-sensor timestamps; Ego devices should align to equivalent semantics. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 27) Open X-Embodiment emphasizes cross-platform action distributions; the Ego field schema should reserve an embodiment_id field. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 28) DROID-class robot data lacks human priors; E2's lightweight Ego is suitable as a pre-stage for human demonstration. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 29) The HaMeR lineage is sensitive to occlusion; ring + multi-path redundancy reduces the proportion of invisible frames. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 30) ActiveUMI demonstrates active perception; dual-channel acceptance of wrist-mounted plus head-mounted streams is the procurement-grade answer. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 31) World model training relies more on long-duration consistent timelines; random cropping of short clips destroys state continuity. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 32) Diffusion policies are sensitive to contact phase; the data card should annotate the start and end frames of contact_phase. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 33) The Sim2Real pipeline should not use different timestamp units in sim and real. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 34) Enterprise content funnel: paper page → spec page → prototype → small-batch data → scaled procurement, with exit criteria at each step. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 35) This article focuses on engineering acceptance field descriptions, so that procurement and algorithm teams can copy them directly into RFQ attachments. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 36) When linking to SDK documentation, fix the anchor to #device-sdk to reduce reader disorientation. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 37) The video poster matches the hero image, reducing first-screen CLS and trust cost. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 38) The FAQ must reiterate dataset boundaries to prevent sales from over-promising. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 39) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 40) Motion-capture bridging is a Stretch capability and requires a separate milestone and acceptance script. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 41) Global shutter reduces geometric distortion in fast lateral motion scenarios compared to rolling shutter, benefiting stereo matching. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 42) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 43) fMP4 segments facilitate browser preview, but the training side requires a raw or lossless backup strategy. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 44) MCAP is well-suited to the ROS2 ecosystem; field naming should follow the team's schema registry. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 45) Scripts like linux_run_time_sync.sh should be versioned and cross-referenced with the firmware README. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 46) The open-source e2-sdk/e6-sdk only helps you get started; mass-production procurement still follows the commercial delivery package. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 47) 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 E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 48) Health monitoring should include camera dropout, IMU saturation, remaining storage, and thermal throttling. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 49) Privacy: faces, house numbers, and screens require a redaction pipeline, and redaction logs must be auditable. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 50) Version ledger: firmware, calibration, APP, host scripts, DatasetServer — five version number categories bound to the session. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 51) The annotation toolchain is decoupled from the hardware; but exports must reference calib_version and sync_report. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 52) A VLA recipe should declare the language instruction alignment method: manual trigger vs. ASR timestamps. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.
(Appendix · news-seo-078-scene-e6-餐饮-s006 · 53) Human-to-robot transfer requires declaring the action space: joint vs. end-effector vs. bimanual. When assessing E6 against Ego-OSCAR (2024), archive this together with the acceptance checklist dated 2026-09-13.