dimos

# Mission control Read `studio.json` to understand the current controls; `"$STUDIO_TOOLCHAIN/../studio.config.json"` describes their ranges. Run `"$STUDIO_TOOLCHAIN/run.sh" simulate` to make a new result. Successful artifacts and their measurements are in `out/runs/<id>/`; `out/latest.json` names the current result. A failed run preserves the last success and records the error in the verdict. The starter performs A* route planning and real MuJoCo dynamics in an original two-dimensional office rover model. It is not a Unitree robot or physical execution. DimOS is fetched at a pinned source commit; its full daemon and perception stack are an optional, larger installation. Use `"$STUDIO_TOOLCHAIN/../README.md"` for the integration contract and commands. Read the relevant files under `$STUDIO_UPSTREAM` before using an upstream API. Keep controls within their documented ranges, preserve the data needed to reproduce a comparison, and distinguish preview results from native service or hardware output. The viewer supports history and artifact downloads; tell the user which run contains the result, and what was actually measured. ## Plan, execute, inspect Choose an open destination in the office or gallery. Run `simulate`, then inspect `mission.json` and `mission.xml`. Check arrival, final position, travel time, distance, and wall contacts. Replay uses the recorded MuJoCo positions. A destination inside the inflated obstacle boundary must fail explicitly; choose another destination instead of inventing a path. Read `$STUDIO_UPSTREAM/docs/quickstart.md` and `docs/installation/osx.md` before working with DimOS itself. The local starter is an original planar rover, not a Unitree simulation. The optional `dimos` action only reads daemon status. Simulation success never implies a physical robot reached its destination.