I run a fleet of AI coding agents on real client and product work, and I publish the log.

Most agent failures are not reasoning failures, they are operating failures: the agent starts blind, grades its own work, and writes nothing down. I build the small pieces of plumbing that fix that, and I run them in production before I publish them.

One 30 day window ending 25 August 2026, counted from my own append only ledger. Not a benchmark, not a demo run. The whole table is recut only when the next full window closes, never partially.

Where those lanes went: data and memory systems 54, infrastructure and fleet operations 49, creative and media 42, docs and process 41, web and SEO 37, security 36, agent automation 30, billing operations 27, the rest across design, commerce, testing and comms 60. Thirteen lanes ended blocked by a gate. On purpose: a gate that stops a lane costs minutes, a wrong action costs trust.

lanes is the coordination layer the fleet runs on. Take a lease before you touch files, produce proof before you close, leave an append only trail the next session can replay. Python standard library, zero dependencies.

royceos is the operating model underneath it: boot from a fixed source of truth, let one model build and a different one verify, require runtime evidence, hand off durably. Plain Markdown and shell, vendor agnostic.

roycecode is native Rust whole codebase analysis for agents. It builds a semantic graph and emits machine readable artifacts, so a reviewer reads evidence instead of the entire repository.

• X: @vojtechroyce
• LinkedIn: vojtechroyce

There is no token, no coin, no paid DM, no investment offer, no giveaway, and no "assistant" who messages you on my behalf. I will never contact you first about money. Official links live only here, on this profile. Anything else claiming to be me is not me.