What we are building

Work

The consortium's named efforts: the safety functions it is implementing, the evidence it is producing for them, and what comes next. Each is public from the first commit.

ActiveBeing worked on now.

The Protective Stop remote: a red mushroom stop button on a 3D-printed yellow and white enclosure, with an ethernet socket in the side.

Protective Stop

An open source safety stop for robots and industrial machines, with its assurance case written in public alongside the device.

A PoE- or USB-powered ESP32-S3 remote sends operator intent to the machine ten times a second over an encrypted link. When the messages stop, because the operator let go, the link dropped, or the remote lost power, the machine brings itself to a controlled halt rather than losing power where it stands. The project targets SIL 3 under IEC 61508 and PL e under ISO 13849. The firmware runs lockstep across both cores, the protocol library sits on its own certification track behind a MISRA checker, and a chaos proxy in the test suite mangles the network on purpose. Software is Apache-2.0, hardware CERN-OHL-P-2.0, documentation CC-BY-4.0, and the open items are recorded as open items.

UpcomingCommitted to, not yet started.

The SAHARA card: a small desert-and-sun icon above the name in wide serif capitals, the expansion beneath, and the line "A HARA is a vast, dry expanse. This gets you across it."

SAHARA: Structured Automation of Hazard Analysis & Risk Assessment

A tool for running HARAs in the context of robotics.

Under development at Polymath Robotics and will be open sourced soon. Hazards are written once and inherited by every project below. Changes raise review flags, an internal or external reviewer signs each entry, and approvals freeze a hashed, exportable record.

Propose the next one.

Work starts where a member needs a safety function that has no adequate open implementation, or evidence that nobody has published. If you have one of those, say so.