OpenMHS family: other

Other engines and protocols (no helper planned)

Generated by MHS/registry/build_registry.py on 2026-10-20T00:00:00Z from 392 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: 392
• Decisions: bridge-runtime 41, reference 29, skip 322
• Waves: 9: 392
• Dispatchable now: 0
• Modes: hardware 4, simulated 40

Applicability

Repos the catalogue files as other engines and protocols. 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

No mapping is fixed for this family; recon cards decide per repo.

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

The family groups heterogeneous projects; treat it as needing design.

First task cards

• gh.carla-simulator/carla: bridge-runtime, wave 9, rank 87, MHS/registry/tasks/robots/carla-simulator__carla.json
• gh.dqrobotics/python-interface-coppeliasim-zmq: bridge-runtime, wave 9, rank 93, MHS/registry/tasks/robots/dqrobotics__python-interface-coppeliasim-zmq.json
• gh.facebookresearch/sapiens: skip, wave 9, rank 120, MHS/registry/tasks/robots/facebookresearch__sapiens.json
• gh.projectchrono/chrono: bridge-runtime, wave 9, rank 139, MHS/registry/tasks/robots/projectchrono__chrono.json
• gh.rickbassham/node-indi-client: bridge-runtime, wave 9, rank 150, MHS/registry/tasks/labs/rickbassham__node-indi-client.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/.