The hidden cost between instruments
Separate instruments can be excellent and still produce a fragile workflow. Every new display, cable and software endpoint adds a translation step. The researcher becomes responsible for aligning timestamps, interpreting status lights and deciding which reading belongs to which run.
A shared physical interface is only the first layer. The more important agreement is semantic: modules discover one another, expose state in the same way and make a measurement available to the rest of the stack without a custom connection exercise.
Integration should disappear into the work, not become the work.
Compose around the protocol
Start with the method rather than a shopping list. A culture-monitoring protocol may need environment, pH and optical density; a control protocol may add mixing and pressure. The stack changes, but the operating language stays constant.
This makes modularity practical. A module can be moved to another bench, replaced for service or added when the experiment changes. The system remains legible because each block has a specific job and a common dock.
One state, three expressions
A useful instrument tells the same story locally and remotely. The display supports the person at the bench, the light ring makes state visible across the room, and the API carries the same status into a data workflow.
That consistency is a design constraint, not decoration. It reduces ambiguity and makes an expanding system easier to trust.