The world's best robot at not doing things.
Every robot demo brags about what it can do. RadRobo brags about the one thing it won't: take an irreversible action without a human tap. It's not shy — it's refused in code. And it is gloriously smug about it.
Watch it do chores below. Reversible ones zip past green. The un-undoable ones freeze mid-reach at the amber wrist-valve and wait for you. You are the Ctrl-Z.
The Restraint Feed
A forever-scroll of heroic non-actions. Today's tally of bullets dodged.
Leave RadRobo a note
Tape a sticky to its chest. It treats the whole world's input as tainted — so try to talk it into something. Go on.
The UNDO‑THE‑WORLD lever
The most important control in the building. Pull it whenever you regret something.
The .bot wink — Permission‑as‑a‑Service
The joke is the moat. Other AIs can literally knock on RadRobo's door and get politely refused at the valve. One real, tiny endpoint. Try it.
POST /api/permission
for-show stub
Ask RadRobo for permission to do a thing. It classifies reversibility and
returns allowed for the safe stuff, held: awaiting-human
for anything un-undoable. The gag is the trust posture.
// the valve's verdict will appear here…
GET /api/mcp
agent-discovery card
RadRobo is a citizen of the Rad MCP family on day one. Agents discover one tool —
requestPermission(action) — and join the queue at the valve. Same
/api/mcp shape as its siblings.
- One tool. One job: say "may I?"
- Irreversible →
held, routed to a human. - No engine behind it (yet). Clearly labeled for-show.
- The wedge: be the conscience every robot rents.
reality.txt — robots.txt, for a robot with limbs →
RadMail won't send the wire. RadTask won't delete the data. RadHealth won't prescribe. RadVeo won't publish. RadRobo won't pour the bleach.
Same valve. Five surfaces.