Physical ≠ simulated

A run says which world it was in.

Every run records its reality once, before its first device or simulator record. Simulated and physical records never mix, and only a physical run of a physical world reaches hardware.

Tres brazos SO-101 en un banco en la simulación: el brazo izquierdo deja un cubo rojo en la base compartida y el brazo central lo lleva hacia el brazo derecho.
Recorded in the workbench: three simulated SO-101 arms relay a cube. A simulation, and it says so.

One reality a run

Only one path reaches hardware.

A physical world has physical runs and simulated ones: its twin, a fork, a proposal. A simulation world, and every other file, has simulated runs only.

Which runs reach hardwareA physical world, such as CommandAGI's shop, has physical runs, whose records come from its devices, and simulated runs, its twin, a fork or a proposal. A simulation world and every other file, a 3D document, a study, a schematic, have simulated runs only. Only a physical run of a physical world reaches hardware, and a record's src must match its run's reality.A physical worldkind: physical · worlds/fleet/world.tsxA simulation world, a 3D file, astudykind: simulation, or any other filereality: physicalrecords from the devicesreality: simulationthe twin, a fork, a proposalHardwarethrough a driver, under a grantThe enginenever physical evidenceWhich runs reach hardwareA physical world, such as CommandAGI's shop, has physical runs, whose records come from its devices, and simulated runs, its twin, a fork or a proposal. A simulation world and every other file, a 3D document, a study, a schematic, have simulated runs only. Only a physical run of a physical world reaches hardware, and a record's src must match its run's reality.A physical worldkind: physical ·worlds/fleet/world.t-sxA simulationworld, a 3D file, astudykind: simulation, orany other filereality: physicalrecords from thedevicesreality: simulationthe twin, a fork, aproposalHardwarethrough a driver,under a grantThe enginenever physicalevidence

The reality is the run's first word.

One of 160 simulated SO-101 runs with drags in CommandAGI's Drive, as it is stored. The run's file says reality: simulation and names the world it is of; its commands say who gave them.

cloud://home/user-commandagi/simulations/so101-cube/drags/runs/20261103t055752z-rud2/real records · production · 2026-11-03
run.json  "of": "cloud://global/worlds/so101-cube/world.tsx"  "reality": "simulation"  "kind": "session"
          "simulator": { "driver": "sim", "settings": { "hz": 240, "record_hz": 30, "trajectory": 155 } }
05:57:52.400 command agent:policy-mover: trajectory robot=arm, 6 waypoints over 0.3 s

Counted in the Drive

583 runs. Each knows what it was.

Every run.json under simulations/ and worlds/ in CommandAGI's production Drive, read on 2026-11-04 (case-studies/physical-vs-simulated/stats.json).

No physical run yet, and it says so. CommandAGI's shop is a physical world of 92 units. Its 34 devices are uncommissioned, so none of its runs is physical yet. A surrogate says it is one. A neural surrogate's prediction carries reality: surrogate. It is never a simulator's evidence, and never physical evidence. A lost link is unknown. A reply never implies the commanded state. A lost link records state: unknown, and a stream with no end is interrupted.

run.json files read
583
say reality: simulation
577
physical runs yet
0
Runs in CommandAGI's Drive by reality
Los números
Runs in CommandAGI's Drive by reality
RunsRuns
reality: simulation577
recipes: no device record6
reality: physical0
ProcedenciaArchivo cloud://home/user-commandagi/simulations/ (production)Resultado case-studies/physical-vs-simulated/stats.jsonHerramienta scripts/sites/case-studies.mjs physical-vs-simulatedSe ejecutó en This computer (dell-gb10-1), reading the production DriveCuándo

Try it in simulation. Then run it for real.

The same file, the same commands, a different reality, written on the record.