Robot Payload Reference

Applied payload layer

Use robot payloads when an example needs a stable handoff.

Core Retriever gives you Flow, Pipeline, clocks, sync, execution, IR, replay, and Hub loading. Golden adds the applied vocabulary around robot boundaries: world state, belief, skills, plans, trajectories, stamped spatial values, event buffers, and dataset records.

First payload proof

pixi run demo-robotics-typing-catalog

Expected result: stamped spatial payloads are constructed, resolved through the registry, and validated with a compact summary.

Core owns runtime mechanics.

Use core docs for Flow, Pipeline, clocks, sync, IR, replay, execution, and the registry loader.

Golden owns robot-facing reuse.

Use Golden for payload choices that appear across examples: world state, belief, plans, trajectories, events, and dataset rows.

Projects own lab-specific schemas.

Keep camera rigs, private robot fields, and simulator quirks local until the boundary is stable enough to share.

Keep the boundary simple. Use core docs for runtime mechanics. Use Golden when the question becomes: what robot state, belief, plan, trajectory, event, or dataset payload should this applied example expose?

Choose By Boundary

ChooseWhich payload should this Flow use?

Pick the smallest payload that preserves frame, time, source, scene, plan, trajectory, command, or status semantics.

ComposeHow should payloads cross Flows?

Use stable I/O objects, qualified fields, and validation boundaries instead of dict glue.

RecordHow should robot data become replayable?

Use event time, event buffers, stream joins, windows, lineage, and export profiles.

ExportHow do event records become dataset rows?

Bridge Golden event profiles into LeRobot-style rows while retaining provenance.

First Runnable Checks

Payload catalogpixi run demo-robotics-typing-catalog

Constructs canonical spatial and robot-facing payloads.

Flow contractpixi run demo-robotics-typing-contract

Checks composite I/O access and stable field behavior.

Boundary proofpixi run demo-robotics-typing-boundary

Preserves frame, time, and source metadata across a perception-to-control boundary.

What Golden Owns

Area	Golden provides	Core Retriever provides
Robot payload reference	WorldState, BeliefGraph, Skill, Plan, Trajectory, status, stamped spatial examples.	Runtime, clocks, Flow/Pipeline execution, IR, replay, and registry mechanics.
Flow contracts	Composite I/O, qualified fields, and validation boundaries for applied examples.	The graph semantics used by those examples.
Event/data profiles	Event, EventBuffer, event-time joins, manifests, and LeRobot bridge examples.	Runtime event-buffer mechanics and scheduler behavior.
Hub pack readiness	Pack boundary, export catalog, smoke demos, and promotion guidance.	Hub loader and registry integration.

Promotion Rule

A robot payload belongs in Golden when it can help more than one applied example without importing optional robot, simulator, camera, model, network, or private dataset dependencies. Keep lab-specific capture procedures, simulator quirks, and one-off policy fields inside the example until the boundary is stable.