THE REASONING GAP
Robots can see. They can grasp. They cannot reason.
Current robotics systems excel at perception and manipulation but lack the structured procedural knowledge required for autonomous task execution in real-world environments.
SAMPLE OUTPUT
{
"procedure_id": "PROC_DW_LOAD_001",
"name": "Load Lower Rack",
"appliance": {
"oem": "Bosch",
"model": "SHPM88Z75N",
"type": "dishwasher"
},
"steps": [
{
"id": "STEP_01",
"action": "OpenDoor",
"target": "door_main",
"precondition": {"state": "cycle_complete"},
"postcondition": {"state": "door_open"},
"hazards": ["h1_steam_risk"]
},
{
"id": "STEP_02",
"action": "Pull",
"target": "lower_rack",
"params": {"distance_m": 0.4},
"constraints": {"max_force_n": 15}
}
],
"failure_modes": ["rack_stuck", "door_blocked"],
"exports": ["BehaviorTree.xml", "PDDL", "ROS2"]
}Real extraction from Bosch dishwasher manual. Full schema documentation on Product page.
WHAT WE MODEL THAT OTHERS CAN'T
| CAPABILITY | PDF PARSERS | VIDEO DATASETS | SYNGRAPH |
|---|---|---|---|
| Step extraction | |||
| State transitions | |||
| Preconditions/Postconditions | |||
| Constraint graphs | |||
| Hazard propagation | |||
| Failure modes | |||
| Cross-OEM normalization |
Robotics companies can scrape PDFs. They cannot model what's missing, what breaks, or what kills.
STACK INTEGRATION
Export formats designed for seamless integration with your robotics stack
M-IDL
Machine-Interpretable Device Language. Our native format capturing procedures, constraints, and control semantics.
PDDL
Planning Domain Definition Language. Export to standard planning formats for task and motion planning systems.
ROS2
Robot Operating System 2. Direct integration with ROS2 action servers and behavior trees.
READY TO DEPLOY
500+ procedures extracted. 12 appliance categories. 0.988 quality score. Zero hallucinations.
Isaac Sim compatible. BehaviorTree.CPP ready. Full provenance tracking.