On this page 9 sections
Flowchem components (helper:http, planned)
Generated by MHS/registry/build_registry.py on 2026-10-20T00:00:00Z from 2 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:
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: 2
- Decisions: bridge-runtime 2
- Waves: 9: 2
- Dispatchable now: 0
- Modes: hardware 1, simulated 1
Applicability
Each component's HTTP API maps reads, settings (cap.device.configure.v1) and actions; virtual components are the fake.
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. Heated solvents and reactive chemistry: interlocks and operator limits are mandatory.
Fidelity
Bridge only; the fidelity belongs to the service, simulator or hardware behind it.
Pitfalls
Units differ per component; virtual components are not chemistry models.
First task cards
gh.automatedchemistry/flowchem: bridge-runtime, wave 9, rank 62,MHS/registry/tasks/labs/automatedchemistry__flowchem.jsongh.automatedchemistry/flowchem-virtual: bridge-runtime, wave 9, rank 823,MHS/registry/tasks/labs/automatedchemistry__flowchem-virtual.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 2 of 2 by stars. Filter the full list.
| Package | Tier | Ring | Evidence | Stars |
|---|---|---|---|---|
| automatedchemistry/flowchem automatedchemistry/flowchem: multi device control API for wet-lab automation and chemistry (lab instrumentation track). | Tier B | 3 | agent read | 22 |
| automatedchemistry/flowchem-virtual automatedchemistry/flowchem-virtual: virtual chemistry device API for wet-lab automation and chemistry (lab instrumentat | Tier A | 3 | agent read | 1 |