惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Google DeepMind News
Google DeepMind News
博客园 - 司徒正美
WordPress大学
WordPress大学
爱范儿
爱范儿
小众软件
小众软件
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
罗磊的独立博客
博客园_首页
V
V2EX
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
T
Tailwind CSS Blog
大猫的无限游戏
大猫的无限游戏
The Cloudflare Blog
MyScale Blog
MyScale Blog
IT之家
IT之家
H
Help Net Security
Blog — PlanetScale
Blog — PlanetScale
Microsoft Security Blog
Microsoft Security Blog
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Recent Announcements
Recent Announcements
F
Fortinet All Blogs
The GitHub Blog
The GitHub Blog
Y
Y Combinator Blog
人人都是产品经理
人人都是产品经理

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Embodied AI Has a $30B Problem: Nobody Knows What 'Good' ...
keeper · 2026-06-19 · via DEV Community

keeper

Q1 2026. $30 billion into embodied AI. 14 deals over $1B each. Job postings up 15x.

The money arrived. The talent arrived. One thing didn't: a shared standard for what "good" means.

I've been asking friends who build robots a simple question: how do you know your robot is good?

Nobody has a clean answer. Not because they're bad engineers. Because the industry never defined it.

The benchmarks everyone uses — RLBench, Maniskill, MetaWorld, CALVIN — all run in simulation. You train a robot to open a door in simulation, 98 out of 100. 95 score. You deploy it in a factory — different lighting, different handle friction, different floor angle. Success rate drops to 10%.

This is an open secret. Everyone knows simulation scores shrink in the real world. Nobody wants to be the first to admit their score doesn't mean what it claims.

I think the problem is deeper than "simulation isn't accurate enough."


Four Layers of Verification

I built a four-layer verification framework, originally for LLM outputs. I've been working with the WorldArena team on their evaluation pipeline, and I realized this framework maps onto the physical world even more naturally.

Layer 1: Rule Following

Simulation says "push the red block to the target position." The real world says "bring me the cup on the table."

Understanding a rule and understanding intent are different things. Most benchmarks stop at Layer 1.

Layer 2: Closed-Loop Feedback

Simulation is perfectly observable — constant lighting, no sensor noise, zero latency. The real world has changing light, drifting sensors, communication delays. Can the robot detect it's off course? Can it correct its trajectory within milliseconds?

Existing benchmarks don't ask this. The reason is pragmatic: adding this dimension reshuffles the rankings, and nobody takes that risk when submitting a paper.

Layer 3: Self-Consistency

Yesterday it learned to grip a cup. Today you hand it the same cup — is the success rate the same?

Catastrophic forgetting isn't unique to LLMs. Fine-tune a new skill, and old skills can degrade. I asked a researcher once: how many papers report long-term stability data in their appendix?

Layer 4: Framework Calibration

I don't have an answer for Layer 4. I only have a question.

Your goal: a robot that works in a factory for 8 hours without incident. Your test: open a door in simulation 100 times with 98 successes.

These two things are separated by a river the industry pretends doesn't exist.


Sim2Real Is Not an Engineering Problem

The standard explanation for the Sim2Real gap is "simulation fidelity." I don't buy it.

The Sim2Real gap isn't an accuracy problem. It's an information compression problem.

Every layer of simulation applies lossy compression to the physical world:

  • Physics accuracy — friction, deformation, thermal expansion. All simplified or ignored.
  • Perception — perfect lighting, no noise. Change a single light bulb in the real world and the model breaks.
  • Interaction — objects are rigid bodies in simulation. The real world has soft objects. Your robot treats grabbing an egg the same as grabbing a rock.
  • Temporal — no sensor drift in simulation. Run for 3 hours in the real world and the accumulated error is significant.

The simulation isn't bad. You just never figured out what information you lost before training.

The framework I keep coming back to: compress → quantify → verify → optimize.

In Sim2Real terms: compression is simulation, quantification is the benchmark score, verification is the Sim2Real gap, optimization is tuning simulation parameters. Every link in this chain needs its own independent verification method.

The industry standard practice is: skip verification, report the score.


The Silent Cost

When "good" is undefined, a significant portion of $30 billion gets misallocated. Not because the technology isn't ready — because there's no standard for measuring whether it works, so investors can only bet on storytelling.

Some teams are working on this. WorldArena Track2 tries to evaluate multi-agent collaboration closer to real-world conditions. A few international competitions added Sim2Real tracks this year.

But scattered efforts don't make a standard.

Benchmarks define direction. Whoever defines "good" defines where the industry goes.

This is the question embodied AI faces in summer 2026: the money arrived, the talent arrived, but the standard for "good" is still waiting for an answer.