Somebody in the building has already written the code MHS proposes to delete. Counting the proteins in a sample means several instruments handling it in a fixed order [6], and that order currently lives in glue code written against each machine's own API, one taking Python where the next takes Java [5]. The person who wrote that glue is the person who gets paged when a firmware update breaks it.
The unified command set [4] gets the attention, and the machine-readable description file is the part that changes the work. An instrument that publishes its own arm weight, or the wavelengths its sensor can read, gives an agent something to plan against rather than probe for [11]. That file is also a procurement artifact. Whoever ships it is doing integration work the buyer currently pays a developer to do.
Then there is the cost line. Anthropic says the Claude-generated laser-positioning script from its internal test runs cheaper than an inference-based device configuration workflow [10]. The useful reading is about billing shape rather than savings. The model is an authoring expense paid once per workflow; the script is a maintained artifact that runs with no model in the loop. Bench automation priced that way sits in a software or capital line rather than on a per-action inference meter.
The evidence base is thin, and worth naming as thin. Anthropic has put forward two working deployments and three groups of integrators, with no count of instrument models that actually speak MHS [16], and the account comes from a single publisher's report [17].
Which leaves a lab manager a grid with two axes. First, does the instrument vendor ship MHS itself, or do you wrap it. Second, does the workflow freeze into a script, or does it need a model on every run. Vendor-native plus frozen script is a line item, and you can ask for a delivery date. Self-wrapped plus model-in-loop is a staffed project with an inference bill attached, whatever the standard on the box is called. Most labs will spend the next year in the two mixed boxes, and those are the ones to cost honestly before somebody's roadmap slide does it for them.
So the question for the next instrument quote is which fields of that description file the vendor has filled in, and what happens to the ones left blank [11].
