Reference
Architecture in one page
The four pillars, the handoffs, and the few identities that survive the whole loop
Experience ──▶ Worlds ──▶ Autonomy ──▶ Fleet
▲ │
└─ episodes, corrections, outcomes ─┘The four owners
| Pillar | Owns | Hands off |
|---|---|---|
| Experience | task contracts, episodes, corpora, lineage, access | exact governed inputs |
| Worlds | executable environments, generations, held-out evaluations | promotion evidence |
| Autonomy | training, applications, approvals, improvement decisions | deployable exact graphs |
| Fleet | deployment, station authority, supervision, physical research | executed outcomes and corrections |
The objects worth remembering
- Project — the authorization and product boundary for one robotics application.
- Task contract reference — the content identity that says exactly what work means.
- Episode — canonical RRD evidence with embodiment, action, provenance, and lineage.
- Corpus snapshot — immutable membership used for training or evaluation.
- Robot application — the complete digest-pinned deployable graph, not just a model.
- Qualification and approval — evidence that the exact graph and task may move forward.
- Operation reference — durable ownership of long-running work across disconnects.
The handoff law
Every gate passes an exact identity plus governed evidence. A receiver does not rebuild another pillar's facts, infer success from a name, or continue with substitute behavior when authority is missing.
Navigate by pillar, debug by owner
Use Experience, Worlds, Autonomy, and Fleet in product and agent language. Use repository names only after you need the implementation owner.