Video alone hides the control signal
The same visual context can lead to different futures when an agent turns, waits, accelerates, selects a tool, or issues a higher-level command. Passive frames show change, but they do not identify which control caused it.
A usable release keeps recorded actions separate from inferred actions. Estimated controls can add research value, but they are not measured ground truth and should retain model, confidence, and review metadata.
- Frames, audio, depth, and observation timestamps
- Raw and normalized controls with action semantics
- Action issue time, effective time, and latency
- State, events, progress, failure, and terminal outcome
Synchronization is the label
A control recorded after its visual consequence teaches the wrong causal order. Every stream should resolve to one declared clock with frame rate, action rate, capture delay, dropped-frame handling, and resampling method documented.
Commanded and executed actions can differ when a game, simulator, robot, or vehicle clips, blocks, delays, or overrides input. Preserve both when the environment exposes them.
Source type and rights survive packaging
First-party instrumented capture, publisher-authorized footage, public video with inferred actions, and generated or simulated episodes are different evidence classes. Combining them without source labels makes quality and rights impossible to audit.
Commercial supply requires authority for collection, model training, delivery, and customer use. Public research references can inform a specification without implying ownership or resale permission.