Orchestrating AI Velocity: Building a Decoupled Control Plane for Agentic Development

"Building code is only half the battle; maintaining it is the other half." Working with AI agents in 2026 means code is generated faster than our human "architectural map" can often keep up. Last month, I noticed my project, Shortshub, was suffering from "architectural drift" because agents didn't have a clear boundary of where one feature ended and another began. To solve this, I’ve moved away from standard monolithic structures and built a fully decoupled Control Plane (running on port 5004). Here’s the breakdown of my experimental "Fractal Kernel" approach. Check the video below. The Problem: The "Hallucination Spread" When an AI agent has too much context, it starts making "creative" (wrong) assumptions about global state. When it has too little, it breaks dependencies. I wanted a way to give agents exactly the context they need and nothing more. Core Architectural Pillars 1. The Fractal Kernel Manifest (Experimental) The foundation of the repo. Every feature lives in its own "cell