Before the block leaves the dock
Record the active run and confirm which processes depend on the module. A sensing block may be safe to replace while a control block requires the process to enter a defined holding state. The operating procedure should make that distinction explicit.
Check the replacement module identity, range and service state before docking. Physical compatibility is necessary; experimental compatibility is the real requirement.
A changed block should produce a clear event, not a silent ambiguity.
Discovery is part of the measurement
After docking, the stack should identify the module and expose its state through the same display, indicator and API channels. The event belongs in the run history so later analysis can explain a gap, a new range or a changed calibration context.
A short verification measurement closes the loop. Do not treat a successful connection as proof that the replacement is ready for the protocol.
Design for recovery
A good swap procedure has a reversible path. If discovery or verification fails, the system should preserve unrelated measurements and make the affected block easy to isolate.
The goal is not speed at any cost. It is a calm, observable transition that protects the experiment and the person running it.