Start
Platform concepts
Four pillars, exact resources, and one closed robotics loop
sx organizes the robotics lifecycle by the owner of each fact:
Experience ──▶ Worlds ──▶ Autonomy ──▶ Fleet
▲ │
└──── episodes, outcomes, corrections ─┘Four pillars
| Pillar | Owns | Typical SDK entry |
|---|---|---|
| Experience | tasks, embodiments, episodes, corpora, lineage, access | client.experience and client.embodiment |
| Worlds | sessions, generations, held-out evaluations | client.worlds |
| Autonomy | training, applications, approvals, improvement programs | client.autonomy, client.train, client.deploy |
| Fleet | deployment, station authority, supervision, physical research | client.fleet |
Use the pillar names in code, agent prompts, and product language. Runtime services and internal topology are not part of the customer contract.
Objects worth remembering
- Project — the authorization and product boundary for one robotics application.
- Task contract — the exact definition of the work.
- Embodiment — the complete body, sensors, actuation, and action-interface facts.
- Episode — canonical robot or simulated evidence with task and lineage.
- Corpus snapshot — immutable membership used by training or evaluation.
- Robot application — the complete digest-pinned deployable graph, not just a model.
- Evaluation, qualification, and approval — evidence that the exact application may advance.
- Deployment — one application and capability set active on a target group.
- Operation reference — durable ownership of long-running work across disconnects.
The golden path
Define and gather Experience
Resolve one exact task, capture or generate canonical episodes, then freeze the training selection as an immutable snapshot.
Iterate in Worlds
Develop in sessions and generations. Evaluate the exact candidate on held-out work when it is ready for a gate.
Build in Autonomy
Train from admitted inputs and assemble the complete application graph.
Promote through Fleet
Qualify the target, bind capability approvals, deploy to canary, and supervise execution.
Close the loop
Return executed outcomes and corrections to Experience with task, application, approval, and deployment lineage.
One contract, three projections
| Surface | Role |
|---|---|
| Python SDK | the primary integration and automation contract |
| MCP + Skills | the agent projection of the same verbs and operation model |
| Console | the human projection for visual inspection and decisions |
No surface owns a private shortcut. If an action needs a different object, weaker identity, or hidden fallback on one surface, it is not the same platform operation.
The handoff law
Every gate passes an exact identity plus owned evidence. A receiver does not rebuild another pillar's facts, infer success from submission, or continue with substitute behavior when authority is missing.