RK's Rambling

Aegis-Chaos · Post 1 of 1 · → View on GitHub From “Vibe Coding” to Closed-Loop SRE How zero-trust policies, Git isolation, and math-based budget guardrails let an autonomous agent say “no” — and mean it. Aegis-Chaos: An autonomous SRE control plane with real-time zero-trust guardrails. Most AI coding assistants today operate on trust. You prompt, they generate, and you ship. That works—until it doesn’t. A single destructive command, an uncaught runaway loop, or a stale approval can turn an autonomous agent into a production incident. Project Aegis-Chaos was built to answer a simple question: what happens when the AI says “no”? This post walks through the zero-trust architecture, parallel isolation strategy, math-based budget guardrails, and end-to-end visual verification pipeline that make up our closed-loop SRE control plane—designed for the Google Developer Expert Sprint and built on the Antigravity SDK. The Decla...

Racecraft · Part 3 of 5 · ← Prologue Splitting the Brain to Beat the Clock How a "brake!" lands in 5 milliseconds while a cloud model thinks for five seconds — in the same app, on the same frame, without ever colliding. Two posts in, we have a coach that knows who's driving and what to say. This post is about the only thing that lets it say anything useful: structure. Specifically, the decision to give the system not one brain but three, each on its own clock, with an ironclad rule about which one is allowed to make the driver wait. I call it the Split-Brain engine , and the whole design collapses out of one observation. The three jobs a coach does — react, strategize, prepare — have wildly different deadlines. Trying to serve all three from one code path means the fastest job inherits the latency of the slowest. That's the original sin of every cloud-first coaching app. So I refused to let them share a path. The Spli...

Racecraft · Part 2 of 5 · ← Prologue Teaching the Coach to Read the Driver The best instructors don't coach the car. They coach you , and they figure out who you are in about two laps. Here's how we taught software to do the same. In Part 1 I argued that trust is the only metric that matters, and that it's mostly a latency problem. That's true , but there's a second half I glossed over. The same sentence, delivered at the exact same millisecond, can build trust or destroy it depending on who's listening. Tell a nervous first-timer "brake spike detected, modulate your input" and you've just handed them a stack trace mid-corner. Tell a fast amateur "squeeze the brakes, don't stab" for the tenth time and they'll mute you out of sheer irritation. The words have to match the driver. So before Racecraft can say anything, it has to answer a question a human coach answers instinctively: how good is this person, rig...

Racecraft · Part 1 of 5 · ← Prologue The 800-Millisecond Problem Why I stopped trusting every " AI race coach " I'd ever tried , and what it would take to build one I'd actually listen to at 130 km/h. The first time an app yelled "Brake!" at me on a track day, I'd already braked — not by a hair, but by a full corner. I was unwinding the wheel and feeding in throttle on the exit of Sonoma's Turn 7, one of the fastest corners on the circuit, when the phone told me — with great confidence — to brake. It wasn't merely lagging by a beat; for that specific high-speed corner the cue was flat wrong, because braking mid-exit at that speed is how you put the car into a spin. And I couldn't even mute it. I was a beginner on a mandatory-instructor day, both hands on the wheel, eyes up. It was the instructor in my passenger seat — there to call flags and lines, allowed to say anything but never to touch a single control — who reached...

Today I’m gonna narrate a little story…not my usual kind of post I know. But at least let me try my luck as a story teller. Once upon a time (imagine me to be an old bear or a hermit or anything telling you the story) there was company named Vigilant Technology Solutions (we will refer to it as VTS). It had its recruitment drive going on and it picked up a few lads it thought to be intelligent.  It had a training program designed for them so it admitted them to the training program. Thus started the journey of the 33 odd people who never knew each other before and now were about to become friends (somewhat). Their first meeting was at Room 13 in Vigilant Academy (that’s what they call their training wing). Everyone had a strange look upon their face, curiosity, fear, skepticism all mixed into one common emotion.  Slowly they started making friends with each other, stated expanding their branches and soon 7 khoon Maaf,n0tti,Achilles,Icegal an...