Bridge family · madsci

OpenMHS family: madsci

MADSci nodes (helper:http, planned)

Recipe published4 packagessimulated
On this page 9 sections
  1. Launch
  2. Registry coverage
  3. Applicability
  4. Capability mapping
  5. Safety
  6. Fidelity
  7. Pitfalls
  8. First task cards
  9. Sources

MADSci nodes (helper:http, planned)

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

  • bridge_status: planned (blocked_on: helper:http)
  • 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:

text
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: 4
  • Decisions: bridge-runtime 2, reference 1, skip 1
  • Waves: 9: 4
  • Dispatchable now: 0
  • Modes: simulated 2

Applicability

Node actions map to catalogue classes or x-cap extensions; the workcell scheduler is a host, not a device.

Capability mapping

The mapping is fixed when the helper lands; the applicability section lists its rules.

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. Safety comes from each device behind the node.

Fidelity

Bridge only; the fidelity belongs to the service, simulator or hardware behind it.

Pitfalls

A full workcell needs running services.

First task cards

  • gh.ad-sdl/madsci: bridge-runtime, wave 9, rank 397, MHS/registry/tasks/labs/ad-sdl__madsci.json
  • gh.ad-sdl/madsci_examples: skip, wave 9, rank 1347, MHS/registry/tasks/labs/ad-sdl__madsci_examples.json
  • gh.ad-sdl/rapid350_applications: reference, wave 9, rank 1385, MHS/registry/tasks/labs/ad-sdl__rapid350_applications.json
  • gh.rorymb/simlab: bridge-runtime, wave 9, rank 1611, MHS/registry/tasks/labs/rorymb__simlab.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/.

Packages

Top 4 of 4 by stars. Filter the full list.

PackageTierRingEvidenceStars
ad-sdl/madsci
ad-sdl/madsci: control framework; protocol implementation/bridge; orchestration/scheduling (lab instrumentation track).
Tier B3agent read88
rorymb/simlab
rorymb/simlab: multi device laboratory digital twin for wet-lab automation and chemistry (lab instrumentation track). Op
Tier A3static scan4
ad-sdl/madsci_examples
ad-sdl/madsci_examples: auxiliary tooling for general (lab instrumentation track). OpenMHS plan: not integrated (skip:to
Tier D3static scan2
ad-sdl/rapid350_applications
ad-sdl/rapid350_applications: orchestration/scheduling for general (lab instrumentation track). OpenMHS plan: reference
Tier D3static scan1