Making Self-Driving Laboratories Auditable:A Unified Framework for Hybrid Actions,Measurements, and Safe Execution
Organizations: SII–ECNU Joint Autonomous Chemistry Laboratory, Shanghai Innovation Institute · Nankai University · Shanghai Lixun Intelligent Technology Co.,Ltd · Shanghai Jiao Tong University ·
Abstract
Self-driving laboratories (SDLs) are laboratory systems that couple experimental planning, automated execution, and measurement feedback in a closed loop. Integrating flexible robot control with the typed application programming interfaces (APIs) and continuous measurements exposed by laboratory instruments remains an execution-interface challenge. To address this challenge, we propose a traceable framework comprising four components: LAM (Lab Action Model), OpenSDL, Safe-SDL, and L3-Bench. LAM is a proposed measurement-conditioned policy architecture that extends vision-language-action paradigms to generate both continuous robot trajectories and typed instrument API calls. OpenSDL is an execution substrate with an initial control implementation, designed to map role-level operations to heterogeneous devices, coordinate execution, and record timestamped causal events. The proposed Safe-SDL runtime gate combines pre-dispatch schema and resource checks with signal temporal logic monitoring during execution, including extended waiting periods. L3-Bench (Level-3 Laboratory Benchmark) specifies an episode-level evaluation protocol covering physical outcomes, timing, reproducibility, safety violations, and fault recovery. Together, these components provide an end-to-end design for linking hybrid action generation, monitored device execution, measurement feedback, and experimental evaluation, addressing coordination and traceability challenges in SDL workflows.
Figures & tables
| Field group | Examples | Audit invariant |
|---|---|---|
| Identity | episode ID, event ID, parent IDs | Every action and return is traceable to one episode and its causal predecessors. |
| Observation | RGB/RGB-D, , , quality flags | Sensors carry units, calibration version, sample time, and stale/missing status. |
| Action | role, op, typed parameters, idempotency key | The submitted action is identical to the schema-validated action used for evaluation. |
| Execution | provider, protocol version, ack, completion, raw bytes | Device-level failures are separated from model errors and safety blocks. |
| Safety | formula version, robustness, gate decision, operator override | A blocked or approved action has an explicit, replayable reason. |
| Environment | asset commit, configuration hash, seed, clock offset | A replay can reconstruct the software, asset, and timing context. |
| Evaluation setting | Controlled intervention | Primary question | Required report |
|---|---|---|---|
| Nominal | Same devices, protocol, and measurement range | Can the full loop execute the task? | , , completion rate |
| Measurement shift | Noise, latency, or target-range change | Do measurement tokens improve adaptation ( RQ1 )? | , , calibration error |
| Fault injection | Offset, slip, timeout, over-temperature | Does gating contain and recover from faults ( RQ3 )? | SVR, interception, recovery time |
| Device transfer | New provider with the same role descriptor | Are action semantics portable ( RQ4 )? | Schema failures, transfer gap |
| Component | Status and evidence |
|---|---|
| OpenSDL 1.0 mother/edge/transport | Control engine, adapters, transports, and SQLite logging implemented; end-to-end replay validation pending. |
| Role/DeviceProvider and SDL-Traj | Proposed research contracts; full schema and compatibility validation pending. |
| LAM hybrid action heads | Proposed architecture and training objectives; trained checkpoints and ablations pending. |
| Clean-3D assets and digital twin | Asset specification; released manifests and validated scene inventory required. |
| L3-Bench | Metrics, scenarios, and evaluation protocol defined; full results pending. |
| Hardware transfer and safety statistics | Hardware-transfer experiments and safety statistics remain pending. |
Appendix figures & tables1 asset
Supplementary material from the paper’s appendix.
Appendix
| Label | Operational definition |
|---|---|
| MODEL | LAM proposes an incorrect role, trajectory, or parameter despite valid inputs. |
| SCHEMA | Type, unit, range, or required-field validation rejects the proposal. |
| RESOURCE | A device, workspace, or barrier dependency cannot be acquired. |
| DEVICE | Provider returns a hardware, calibration, or communication failure. |
| SAFETY | STL, heartbeat, or data-quality gate blocks or aborts execution. |
| REPLAY | The episode cannot be reconstructed from its manifest and event ledger. |
Laboratory Automation
Laboratory automation uses robotics, software, and AI to plan, execute, monitor, and analyze experiments with less manual intervention.
See all 62 papers