# Simulation To Site Code Boundary

Use simulation to validate interfaces, task flow, target layouts, and safety
state machines. Do not move Isaac-specific code into site deployment.

Reusable across simulation and site:

- ROS 2 interfaces
- TCP frame protocol
- `vehicle_agent_gateway`
- workshop orchestration flow
- calibration algorithm services
- manifest/profile schema
- safety state machine semantics
- reports and logs

Simulation only:

- Isaac scene construction
- simulated vehicle URDF/USD assets
- simulated sensor creation
- synthetic telemetry publishers
- simulated target geometry generation
- WiFi/link fault injection proxy when it is not part of real deployment

Site only:

- real vehicle SDK or PLC/CAN integration
- real network addressing and certificates
- real emergency stop wiring and validation
- measured target dimensions
- measured sensor extrinsics and vehicle profile
- site acceptance logs

