OpenMHS family: unity

Unity simulators (no helper planned)

Generated by MHS/registry/build_registry.py on 2026-10-20T00:00:00Z from 20 registry records and their task cards. A plan, not a conformance claim.

• bridge_status: none
• helper: none
• exemplar: none

Launch

Every driver package starts the same way; per-repo configuration (environment id, model path, port, baud rate, VISA resource) lives in the package's driver.py, never in launch flags:

mhs serve <driver-dir>

A package is done when python3 -m mhs.driver check <driver-dir> --backend fake exits 0 (evidence contract_checked; a fake never yields an MHS-Device level).

Registry coverage

• Repos: 20
• Decisions: bridge-runtime 3, skip 17
• Waves: 9: 20
• Dispatchable now: 0
• Modes: simulated 3

Applicability

Repos the catalogue files as Unity simulators. No Driver helper is planned before or after the pilot, so their cards are recon-only (wave 4) or last (wave 6: GPU, Windows or an engine licence). A simulator family needs a structural marker in the code, never only a README or name match.

Capability mapping

Class ids come from python3 -m mhs.driver catalog search <words>. The deprecated classes cap.device.describe.v1, cap.world.state.v1, cap.world.snapshot.v1 and cap.world.restore.v1 are replaced by the protocol methods mhs.devices.get, mhs.resource.read, mhs.snapshot and mhs.restore.

Safety

The risk floor of a device is the highest catalogue risk_class of its classes (CAP-017); a driver may declare a higher risk, never a lower one. Hardware at R1 or above needs an @estop and a non-empty safe state. The risk floor of every class still comes from the catalogue.

Fidelity

Engine-specific; nothing here claims fidelity.

Pitfalls

Closed binaries, Windows or macOS builds and a GPU; ML-Agents protocol versions differ.

First task cards

• gh.allenai/ai2thor: bridge-runtime, wave 9, rank 151, MHS/registry/tasks/robots/allenai__ai2thor.json
• gh.gkjohnson/urdf-loaders: skip, wave 9, rank 199, MHS/registry/tasks/robots/gkjohnson__urdf-loaders.json
• gh.robotflow-initiative/rfuniverse: bridge-runtime, wave 9, rank 341, MHS/registry/tasks/robots/robotflow-initiative__rfuniverse.json
• gh.unity-technologies/articulations-robot-demo: skip, wave 9, rank 592, MHS/registry/tasks/robots/unity-technologies__articulations-robot-demo.json
• gh.loongopen/unity-rl-playground: bridge-runtime, wave 9, rank 602, MHS/registry/tasks/robots/loongopen__unity-rl-playground.json

Sources

• Task cards: MHS/registry/tasks/<track>/<owner>__<repo>.json (schema/taskcard.schema.json).
• Triage rules and the helper table: MHS/registry/triage.py; curated decisions: MHS/registry/overrides/.
• Driver API and gate: MHS/sdk/docs/driver-authoring.md; exemplars: MHS/drivers/.