top of page
How We're Approaching a County-Level Education Data System Engagement
When Los Angeles County needs to evaluate whether a multi-agency data system serving foster youth should be modernized or replaced, the work sits at the intersection of technology, policy, and people. That's exactly where we operate. The Opportunity The LA County Office of Child, Youth, and Family Well-Being is looking for a consulting team to analyze the Education Passport System (EPS), a shared data platform that connects 80+ school districts with the Department of Children
What Claude Code's Architecture Reveals About the Missing Governance Layer for AI Agents
The source code of the most widely used AI coding agent leaked today. Within hours, thousands of developers were studying its internals: how it manages tools, coordinates sub-agents, tracks sessions, and handles permissions. The architecture is impressive. But the most important takeaway is not what it contains. It is what it proves is missing from the ecosystem. What the source reveals Underneath the interface, every serious agent system converges on the same set of patterns
Why We Built a Nervous System for AI Agents Before Anyone Shipped Hooks
In February 2026, we had 13 AI agents running on a single VPS. They managed email, filed grants, coached users, processed legal documents, built partner packages, and scanned government portals. All autonomous. All running 24/7. There was no governance layer anywhere in the ecosystem. No tool that sat between the model and execution and said "should this action be allowed?" The options were: trust the model, or build something yourself. We built something ourselves. We called
YAML Policies and SQLite Audit Trails - What Production AI Governance Actually Looks Like
Most AI governance conversations stop at "we log everything." That is observability, not governance. Observability tells you what happened after the fact. Governance stops the bad thing before it executes. Today we shipped two features that make that distinction concrete: a YAML policy engine and a SQLite audit brain. Here is what they do and why they matter. The Problem We run 13 AI agents in production. Each agent has different permissions, different risk levels, and differ
We Governed 13 AI Agents for 4 Months Before Governance Was a Feature
In February 2026, we deployed 13 AI agents across 5 platforms. Telegram, Instagram, Facebook, web, and WhatsApp. Real agents doing real work: responding to leads, filing grants, managing legal docs, coaching users through 6,854 behavioral scenarios, and processing financial data. By day 3, one agent tried to delete a production config file. By day 5, another started drifting from its assigned role. By week 2, we had caught 99+ policy violations across the fleet - none of whic
bottom of page

