Embodied AI Field Map

中文版

Embodied AI is a closed-loop systems field, not a single model family. This map separates capability coverage from repository evidence so that a topic name never implies a reproduced result.

For prerequisite-level navigation, use the 45-node Knowledge System. The field map answers what capabilities exist; the knowledge graph answers what must be learned first and how it is assessed; Pipelines answer how capabilities become a runnable system.

Capability stack

Capability	Engineering question	Best foundation	Pipeline contract
Sensing & calibration	Are observations synchronized, calibrated, and healthy?	Perception and sensors	Perception & state estimation
State estimation	What state is safe to use, with what uncertainty?	Probability and optimization	Perception & state estimation
Data & simulation	How are tasks, demonstrations, splits, and perturbations produced?	MuJoCo · Dataset and training	Simulation & data
Policy learning	How does observation and language become action?	Deep learning · Transformers	VLA policy
Predictive models	What will happen after an action?	Probability and optimization	World model planning
Interactive improvement	How should behavior improve from reward and failure?	Control	RL post-training
Generalist policies	How are models adapted across datasets and bodies?	Dataset and training	RFM & cross-embodiment
Task reasoning	How is a long instruction decomposed and replanned?	Robot systems and safety	Embodied reasoning
Manipulation & dexterity	How do commands become constrained motion, stable contact, and task progress?	FK, Jacobian, and IK · Control	Dexterous retargeting · Dexterous manipulation
Navigation & locomotion	How does an embodiment move while remaining localized and stable?	Control · Systems and safety	Navigation & locomotion
Transfer & deployment	What must pass before risk is increased?	Evaluation and reproducibility	Sim-to-Real

Evidence today

Level	Tracks	Meaning
Smoke-tested	Simulation/data, VLA, world model, RL, dexterous retargeting, dexterous manipulation, perception/state, navigation	A lightweight repository path completes; synthetic wiring and performance claims remain separate.
Interface-tested	RFM/cross-embodiment, embodied reasoning	Local schemas, adapters, or planners connect without proving real weights or hardware.
Documented	Sim-to-Real	The engineering contract and gates exist; hardware deployment cannot be represented by a universal local command.

Choose by research goal

For a complete question → prerequisites → Pipelines → deliverable → metrics → gate contract, use the seven research routes.

Goal	Start	Then prove
Learn robot learning from zero	Knowledge System → Foundations overview	Resolve prerequisites, pass their assessments, then complete one smoke-tested Pipeline and retain its artifacts.
Build a multimodal policy	VLA pipeline	Closed-loop success, language ablation, latency, and failure cases.
Study prediction and planning	World-model pipeline	Multi-step rollout error and planned task success separately.
Work across robot bodies	RFM pipeline	Action semantics, adapter coverage, and per-embodiment results.
Study dexterous hands	Retargeting pipeline → grasping pipeline	Geometry, temporal quality, contact, retention, task, and hardware evidence separately.
Build mobile or legged systems	Navigation/locomotion contract	Localization, tracking, collision/fall, recovery, and transfer evidence.

Deliberate non-claims

The repository does not currently claim a reproduced SLAM or standard navigation benchmark, legged-locomotion policy, production-hand manipulation policy, general-purpose hardware deployment, or competitive large-scale foundation-model result. The system smokes are deterministic synthetic fixtures, not substitutes for those results.