Open specification

A portable specification for action trajectories

Make every episode self-describing with streams, clocks, provenance, rights, quality, and versioned release metadata.

Synthetic schema sampleObservation → action → next state
01
00.000sObservergb.player_view
02
00.050sActmove.forward + camera.delta
03
00.100sTransitionpose.x +0.84 m
04
00.150sOutcomeprogress 0.31 → 0.36

The values are synthetic and illustrate the public specification. They are not measurements from a commercial dataset.

Direct answer

The ActionTrajectories specification is a practical JSON baseline for packaging an episode, its synchronized streams, provenance, rights status, and quality checks. It is designed for inspection and extension.

Episodes hold the contract

Each episode identifies the environment, task, initial condition, participants or agents, start and end, terminal result, and related attempts.

Streams reference one episode timebase and declare modality, encoding, sampling behavior, schema, coordinate frame, units, and validity masks.

  • Stable release, episode, and stream identifiers
  • Declared master clock and stream offsets
  • Checksummed raw and derived artifacts
  • Rights and quality decisions with evidence

Lineage connects every derivative

Normalized tensors, annotations, clips, and shards should link back to raw inputs through checksums and transformation records.

Each operation names code version, parameters, inputs, outputs, and review status. This supports reproducibility and targeted withdrawal.

Download the machine-readable files

The public JSON Schema and synthetic example can seed internal tooling. Croissant metadata and a Citation File Format record support discovery and attribution.

The example contains synthetic values only. It is not a sample from a commercial dataset.

Questions this page should settle

Is the specification tied to one game or simulator?

No. It defines shared episode, stream, timing, provenance, rights, and quality concepts while allowing environment-specific extensions.

Does the example contain real training data?

No. All values in the public example are synthetic and provided only to illustrate the schema.

Which metadata files are available?

The site publishes a JSON Schema, synthetic JSON example, Croissant record, Citation File Format record, and llms.txt.

Bring us the training target.

We will map it to the observations, actions, state, outcomes, rights, and delivery evidence the dataset must contain.

Request access