Overview
The paper Affordance Agent Harness: Verification-Gated Skill Orchestration (arXiv:2605.00663, 2026-04-30) by Haojian Huang, Jiahao Shi, Yinchuan Li, and Yingcong Chen tackles a fundamental robotics problem: affordance grounding—enabling AI to understand what actions an object offers (an oven door can be opened, a faucet dispenses water, a cabinet handle can be pulled).
Challenges in Open-World Affordance Grounding
1. Small, hidden actionable regions — drawer handles of a few centimeters, occluded buttons, switches hidden at the back. 2. Visual ambiguity — reflective surfaces, transparent objects like glass doors, and visually similar objects with different functions. 3. Skill composition complexity — single skills (detection, segmentation, interaction imagination) are insufficient, yet fixed pipelines cannot adapt to varying difficulty.
Existing systems suffer from rigid pipelines, no error recovery, and no experience reuse.
The Proposed Approach
The core insight: test-time grounding must acquire the *right* evidence. Instead of executing a fixed skill sequence, the agent dynamically selects, verifies, and adjusts based on current state. Three mechanisms:
- Difficulty-aware skill selection: easy instances need only detection; hard ones add segmentation and interaction imagination, chosen based on evidence sufficiency.
- Verification gating: after every skill execution, results are validated. Untrustworthy outputs trigger recovery; trustworthy ones proceed.
- Experience reuse: recurring objects trigger reuse of previously successful strategies, avoiding repeated exploration.
- Fixed pipelines over-process simple tasks (wasted compute, extra errors) and under-process hard ones (unrecoverable failures).
- Dynamic orchestration adapts effort to difficulty, tolerates errors via verification, and learns through reuse—mirroring human cognitive strategy (familiar door: just pull; unfamiliar device: observe, probe, confirm).
The analogy: a skilled repairman doesn't disassemble the whole machine every time—he diagnoses, picks the right tool, verifies each step, and applies known solutions to familiar failures.
Why Dynamic Orchestration Beats Fixed Pipelines
Takeaways for Agent Builders
1. Does your system have difficulty awareness—adjusting strategy to task complexity? 2. Is there a verification mechanism after each step? 3. Can errors be recovered, or does one failure collapse everything? 4. Can experience be reused?
An agent's intelligence lies not in how many skills it has, but in how it orchestrates them. When AI learns "what to look at, what to touch, and what to use," it moves from passive observer to active actor.