8 posts tagged Standards. ← Back to all posts
Introducing ROBOT.md — a single-file declaration at your robot's root that any agent harness (Claude Code, ChatGPT, Gemini, Ollama, your own) can read at session start. Vendor-neutral. Apache 2.0. Shipping v0.1 today.
rcan-py v0.3.0, rcan-ts v0.3.0, OpenCastor v2026.3.8.0, §17 Distributed Registry, and RCAN-Swarm Safety — across four repos and most of the day.
Coordinated releases across four repos, green CI on all of them, a new swarm safety claim for OpenCastor, and the clearest picture yet of what the Robot Registry Foundation actually needs to function.
Every robot incident investigation starts the same way: what did it do, who authorized it, and can you prove it? RCAN is the protocol layer that makes those questions answerable — before the incident happens.
Why AI robots need accountability protocols now, what existing safety standards miss, and how to adopt RCAN before the incident that makes it mandatory.
ISO 10218, OPC UA, IEC 62443, ROS2 — the standards that govern industrial robots today were written before AI was making the decisions. Here's what each covers, where they stop, and where RCAN fits.
The internet has ICANN. IoT has Matter. Robotics has nothing. The RCAN protocol proposes a global addressing, authentication, and governance standard for embodied AI.
As embodied AI scales, we need a governance stack for the physical world—a constitutional operating system that encodes safety, law, and social norms into every robot's decision-making framework.