Robotics / Embodied AI

A robot failure is evidence only when the physical boundary is stated.

This page connects robot learning from failure to public evidence boundaries: simulation, local proxy, shadow evidence, physical tests, and no real deployment claims.

robot learning from failure embodied AI humanoid robot safety robot recovery physical failure learning robot reliability evidence

Evidence Map Papers Registries Counterexamples

Search Intent

Readers want to know whether a robot or embodied AI system can recover after failure in the real world.

How can a robot learn from physical failure?
What evidence distinguishes simulation from real-world deployment?
What does local proxy evidence prove and not prove?
How should physical failure be reported without overclaiming?

Physical Boundary

Embodied evidence depends on where the body actually was.

A robot-related claim should state whether evidence came from simulation, local proxy, shadow observation, constructed witness, or real hardware deployment.

Without that boundary, readers cannot know whether the result proves perception, planning, recovery logic, interface behavior, or actual physical control.

Failure

Failure is useful only if it enters the record.

A credible embodied system keeps failure cases, recovery attempts, and boundary downgrades visible. It does not discard awkward cases after a polished demo.

The public challenge route asks external readers to name the missing physical boundary, missing baseline, or overstated deployment claim.

Evidence Route

Where the claim can be checked.

This page is an entry point. The claim should be evaluated through DOI records, evidence maps, registries, GitHub/HF technical routes, and public counterexamples.

KindAnchorURLRole

Evidence MapPublic claim and evidence maphttps://mianzhang.org/evidence/Start from supported claims and known boundaries.

Paper IndexDOI and paper status maphttps://mianzhang.org/papers/Use paper-specific DOI records for paper claims.

RegistriesMachine-readable public registrieshttps://mianzhang.org/registries/Inspect claim, evidence, action, and counterexample records.

Challenge RouteCounterexample submission pathhttps://mianzhang.org/counterexamples/Attack overbroad claims through public routes.

ArchiveZenodo portfolio indexhttps://zenodo.org/records/20027295Long-term archive index; cite specific DOI records when available.

ConceptRobot/Vision Downgrade Rulehttps://mianzhang.org/concepts/robot-vision-downgrade-rule.htmlPerception uncertainty and deployment-language boundary.

Boundary

What this page does not prove.

This page does not claim real robot deployment unless a specific public record says so.
It does not treat local proxy or shadow evidence as full physical-world validation.
It does not claim universal robot recovery or production robotics readiness.

FAQ