A dedicated controller.
A physical intervention control, an isolated management path and a stop state that remains latched until authorized recovery.
SYNTONY HARDWARE02 / BATON
In developmentBATON.
Keep the whole
operation in hand.
An independent hardware platform in development for coordinated intervention across AI agents, robots and autonomous labs.
Explore the stop sequenceCONTROLLER + SYSTEM INTERFACESIndustrial design study
Final form subject to engineering
Final form subject to engineering
One intervention.
A different response from every system.
Like a conductor’s baton, BATON is designed to coordinate the whole operation. Stop new AI actions, bring connected equipment to its defined safe state, and establish what is still running.
01 / THE STOP SEQUENCE
Bring the operation
to a controlled stop.
Explore a proposed response across three connected systems. Each has its own stopping condition.
INTERACTIVE CONCEPT / NO LIVE EQUIPMENT
An AI planner, a transfer robot and a liquid-handling instrument share one workflow.
01 / COMMAND
AI planner
Scheduling the next operation
Evidence retained02 / MOTION
Transfer robot
Moving a sample carrier
Gripping force retained03 / OPERATION
Lab instrument
Executing an instrument task
Required protective services retainedB A T O NINDEPENDENT CONTROL
RUNNING / ILLUSTRATIVE
Three systems. One operation.
The planner, robot and instrument are active. Trigger a simulated intervention to inspect their different responses.
Rearming does not restart the previous task.
Illustrative states, not measured hardware results. This page does not connect to or control equipment.
02 / THE HARDWARE DIRECTION
Separate control.
Shared intent.
A dedicated controller and qualified system interfaces would connect one human intervention to several forms of enforcement.
The right interface.
Network isolation, agent-access controls and connections to equipment’s own protective-stop functions. Each integration needs its own qualification.
Evidence of the response.
Read back the resulting state. Separate confirmed stops from missing feedback, outstanding remote work and functions intentionally kept active.
03 / DEVELOPMENT & SCOPE
Designed for breadth.
Qualified system by system.
What exists today?
The product direction, industrial design study and browser demonstration shown here. Physical prototyping, equipment integration and independent qualification are development work ahead. No hardware performance or safety-certification claim is made.
What does “kill switch” mean here?
Intervention on the paths BATON is connected to and authorized to control. The intended response can include blocking new actions, isolating a connection or initiating an equipment-specific safe stop. It cannot undo completed effects or guarantee that an unconnected system has stopped.
How would it work across different equipment?
Through a common controller and qualified interfaces, with a defined stop profile for each installation. Essential holding, cooling or protective functions may need to remain active. Existing machine safety systems remain part of the design; a web API alone is not a hardware emergency-stop circuit.
How is it different from METRONOME?
METRONOME is designed to keep action authorization and destination credentials outside an agent host. BATON is a separate hardware direction for coordinated intervention across an operation already in progress.
Explore METRONOME ↗TECHNICAL REVIEW / EARLY COLLABORATION
What needs
to stop together?
Bring your agent workflow, robot or lab setup. Discuss the control paths, stopping conditions and evidence a BATON integration would need.
Discuss BATON