Skip to main content

Systems engineer · independent builder

I’m a deaf engineer who ships entire software ecosystems as a team of one.

By day I keep enterprise systems running for member utilities. By night I build open infrastructure for robots — a whole stack, alone, by pairing with Claude Code. Accessibility isn’t a feature I add; it’s the reason I build.

Sacramento, California · deaf engineer · accessibility-first by default

Craig Merry
Sacramento, CA

What I’m building now

OpenCastor

ROBOT.md is to a robot what CLAUDE.md is to a codebase.

One file — YAML frontmatter and plain markdown — that lets Claude Code, Claude Desktop, Cursor, or any MCP-aware agent safely understand and operate a physical robot. I’m building the spec, the runtimes in two languages, the agent surfaces, and the public registry that keeps it honest. One person, one coherent system.

ROBOT.md manifestMCP serverAgent SDK dispatcherPublic registry
your terminal
pip install robot-md robot-md-mcp
robot-md init --yes
Read the spec on GitHub
robotmd.dev — Wire any robot to Claude, get a signed audit bundle

robotmd.dev — the public home for ROBOT.md

Proof it’s real

A team of one, shipping at the cadence of a whole org. One month, measured:

1,083
commits across the ecosystem · April 2026
67
GitHub releases in 30 days
~1,981
tests across the three core repos
11
active repos, one shared spec

Hardware in the loop: a SO-ARM101 arm named bob, registered as RRN-000000000001. Every feature is exercised against real servos before it merges.

The system

One stack, four layers

Each layer is its own repo with its own release cadence and one clear concern. A change at the bottom ripples up cleanly — which is the only reason one person can hold it all.

Surfaces MCP · Agent SDK · Plugins How agents touch the robot — an MCP server, a BYOK Agent SDK dispatcher over HTTPS, a Claude Code plugin marketplace, a voice pendant on a Pi. 01
Manifest robot-md The ROBOT.md spec + CLI. The single declarative file every other layer reads and writes. 02
Registry Robot Registry Foundation Public identity + compliance. Ed25519-signed registrations and the first five EU AI Act-aligned endpoints, live. 03
Protocol RCAN The wire protocol underneath, with peer runtimes in Python and TypeScript. Everything above speaks it. 04

Selected work

The same thread, further back

Computer vision, accessibility, edge AI, open standards — every one a system built to keep someone safer or more included. The robotics work didn’t come from nowhere.

Scientific computing · AI

Heat Protein Lab

An interactive, browser-based lab that walks you down a temperature gradient and shows — with real PDB/AlphaFold structures and rigorous prose — how proteins like HSF1 sense and survive heat. The thing I built after I built the wrong thing.

Open standards · registry

Robot Registry Foundation

Public identity and compliance for AI-driven robots — permanent RRNs, Ed25519 ownership proof, and the first five EU AI Act-aligned endpoints, live.

Accessibility · XR

LiveCaptionsXR

On-device spatial captioning for deaf/HoH users in XR — captions appear in 3D near whoever is speaking, running on the Qualcomm Hexagon NPU.

Edge AI · detection

Dronevade

Edge computer-vision platform for drone detection — custom YOLO models with RF and thermal fusion, designed for the field.

Computer vision · safety

BicycleRadar

Sensor fusion + ML that gave cyclists a 3.2-second collision warning window at 96% prediction accuracy.

Wearable · safety

HeatCompass

A wrist-worn wearable that runs heat-stress inference on-device to warn outdoor workers and athletes before they're in danger.

How I learned to ship at scale

Fifteen years keeping big systems running

Before the robots, I spent fifteen years making enterprise platforms ship safely — migrations, automation, governance, CI/CD. That’s where I learned that the hard part of any system isn’t the code; it’s keeping every moving piece coherent.

2022 — now
Systems Engineer · Northern California Power Agency
Microsoft 365 + Power Platform modernization for member utilities.
2018 — 2022
Application Admin Lead · California Earthquake Authority
PowerShell + Azure DevOps CI/CD; cut release time ~75%.
2014 — 2016
Founder & Product Lead · Beacon Safety Co.
LiDAR hazard-detection prototypes. Won Startup Weekend Sacramento (hardware).
earlier
Ops & SharePoint · Apple · Sutter Health · State of CA
Portals, BI dashboards, and automation that turned weeks of manual work into hours.

Why I build

“I build the infrastructure I wish existed — for robots, and for the people who usually get left out of the brief.”

Being deaf shaped how I work: I read systems for a living, I document everything, and I design for the person who isn’t in the room. The accessibility tools and the robot registry come from the same place — a belief that the things that decide for us should be legible, signed, and accountable.

Let’s talk

If you’re building something that has to ship coherently — let’s talk.

I work best with teams who value clear documentation, fast iteration, and inclusive design. Send a brief and I’ll come back with next steps and a prototype.

[email protected]· (916) 996-7105· github.com/craigm26