01 / Rules
The constitution
Plain, signed policy that Mech-1 enforces. Versioned and diffable like any other source.
Mech Protocol
Open software for your fleet.
Mech Protocol is how you run Mech-1 at scale. Write your safety rules once, push them to every robot, and watch each decision the chip makes. It is open source, and it runs on Mech silicon or your own.
Your rules
Write them once. Hold them everywhere.
Your rules are plain text, the kind a person can read and an auditor can check. Force and speed limits, safe zones, allowed tools. Sign them, push them, and every robot follows the same version.
What is inside
Three parts, one place.
02 / Console
The admin plane
Fleet roles, policy pushes, and a live record of every decision. One place to run the fleet.
03 / Sequence
The identity
Each robot carries a hardware-rooted identity that signs its own logs and proves which rules it runs.
Why open source
Anyone can read the rules.
A rule that decides whether a robot near your family moves or waits should be open for anyone to read. Open source is how the rules earn trust, how the cert spreads, and how Mech becomes the standard.
- [R]
Readable
The whole rules layer is plain and auditable by anyone.
- [P]
Portable
Run it on Mech silicon, your own board, or in simulation. Same rules everywhere.
- [S]
A standard
Adoption-driven, the way UL, Dolby, and USB grew. We define the cert, the market adopts it.
Start building
Clone it and run it in simulation.
Mech Protocol is open. Pull the rules, wire them to the proving ground, and watch Mech-1 work before you touch a board.