RoyOS Devlog #3

RoyOS is starting to feel less like a prototype and more like an actual operating system for autonomous work.

This week I focused heavily on reliability and the boundary between Jarvis and the RoyOS runtime.

Jarvis now handles conversational tasks directly through Claude, while RoyOS acts as the durable background worker for longer-running jobs. That separation has made the whole system much more predictable.

I also tightened up the RoyOS bridge and safety system. Jobs are forced into a scratch environment during testing, live writes require explicit authorization, and destructive operations still require human approval.

The runtime is now passing all tests, and the bridge has been heavily regression-tested as well.

The biggest lesson from this stage has been that an autonomous system doesn’t just need intelligence. It needs state, provenance, permissions, retries, observability, and clear failure behavior.

There’s still work to do, especially around getting more complex multi-step objectives to complete reliably, but the foundation is becoming much stronger.

Next up: continuing to push RoyOS toward a system that can take a real objective, break it into durable work, execute it safely, and report the result without needing constant supervision.