The episode is the useful unit
Loose clips can teach visual priors. An episode preserves the initial condition, action history, environment state, task context, and terminal result needed to learn dynamics.
Each stream should resolve to one declared clock. Sampling rate, dropped frames, action delay, and uncertainty belong in the release record, not in private implementation notes.
- Observed pixels, audio, depth, language, or sensors
- Raw and normalized action signals
- Measured engine or simulator state
- Events, progress, reward, failure, and terminal state
Hours do not describe coverage
Nominal duration can hide repetition. A useful release reports coverage across environments, task states, action combinations, outcomes, rare events, failures, and recoveries.
Define the coverage matrix before collection. It becomes the contract connecting the research target to collection quotas and release acceptance.
Rights are part of the dataset
Download access is not commercial permission. The release needs a traceable source, rights holder, allowed uses, redistribution terms, attribution requirements, restrictions, and withdrawal path.
ActionTrajectories keeps external research references separate from datasets commissioned or supplied under a commercial agreement.