Mission completion under injected faults
Share of missions completed after planned faults.
Value: Pending
Track D · research agenda
How do Route, Ground and Assure apply where errors have physical consequences?
The same Route, Ground, Assure stack where errors have physical consequences. Every claim will name its testbed stage and report sim-to-real gaps.
| Step | Tools | Status |
|---|---|---|
| Simulation | ROS 2, Gazebo | Planned |
| Hardware-in-the-loop | Flight controller or board with simulated environment | Planned |
| Controlled indoor trials | Small, safe, repeatable | Planned |
| Outdoor field trials | Only with permissions and a safety pilot | Planned |
| Layer | Digital | Physical |
|---|---|---|
| Route | Policy-driven model and provider selection | Policy-driven planner, controller and fallback selection |
| Ground | Provenance-first knowledge graph | World model with sourced observations and versioned maps |
| Assure | Quality contracts before an answer ships | Runtime monitors and safety shields before an action executes |
Values stay Pending until we publish logs.
Share of missions completed after planned faults.
Value: Pending
Seconds from agent loss to a new valid plan.
Value: Pending
Share of unsafe plans stopped by the shield.
Value: Pending
Share of safe plans incorrectly blocked.
Value: Pending
Route · Ground · Assure · Foundation
Questions? Email contact@ehopn.com