Ideas from the team building infrastructure for governed agentic systems.
The industry is optimizing the wrong layer. Model governance asks whether a model is safe to run. Decision governance asks whether a specific decision was authorized — under what constraints, with what evidence. Almost the entire field is focused on the first question.
Intuit compressed months of OBBB tax code implementation into days using Claude plus custom infrastructure. They built a bespoke knowledge engine by hand. Here’s the productized version — and the model drift problem they didn’t mention.
The summarizer becomes the sender becomes the transactor. AI agents escalate from T1 reading to T4 autonomous action one feature at a time — but governance is reviewed at launch, not at each capability expansion. The gap is your risk.
Anthropic’s 1M token context window makes the problem worse, not better. Your governance rules are tokens competing for attention weight — and they’re losing. The solution isn’t a better text file. It’s an architecture.
Anthropic’s RSP v3 is an honest post-mortem. The model maker couldn’t govern the model through the model. The lesson for every enterprise deploying AI at scale: build the external governance layer.
A system that cannot forget cannot govern. Enterprise AI governance requires both provenance and decay — capture with attribution, curate with evidence, forget with evidence. The WSJ described half the problem. This is the other half.
The Wall Street Journal describes enterprise AI capturing employee knowledge without governance. The answer isn’t to stop capturing — it’s to capture correctly. Structural attribution, earned maturity, governance by constraint.
The open-source coding agent ecosystem solved execution. It did not solve institutional memory. MindMeld is the missing layer between agents and governed enterprise deployment.
The Anthropic-Pentagon controversy exposed a structural pattern: governance by policy drifts under pressure. Governance by architecture holds. Here's why every enterprise AI buyer should know the difference.
CircleCI's data across 29 million CI workflows shows main branch success rates at a five-year low. Nearly one in three merges fails. The model isn't the variable. The architecture is.
Six hundred years after mastering the explosion, someone built the engine. We are in the fireworks phase of agentic AI. Everyone is impressed by the explosion. Nobody has built the chamber yet.
Every generation promotes impressive technology from tool to container. OLE, Flash, RPA, and now LLM agents. The pattern is identical. The resolution is older than the problem.
There is a 1968 animated film that most people remember as a psychedelic curiosity. They missed the architecture. An allegory for why governed AI requires a submarine, not a fleet.
The AWS Kiro incident exposed the gap between build-time configuration and runtime authority. Agent governance lives in three layers. Most platforms only have one.
AI agents are contingent workers. The governance expectations should match. We built an open scorecard—6 dimensions, 20 criteria—to make that evaluation concrete.
Cursor's research showed agents spiral in endless correction loops. We built an open-source solution: inject standards before the first token is generated.
AI systems are becoming unbiased record keepers. Whether that exposes the humans behind the system or the humans using it depends entirely on how we build them.
34 researchers from Stanford, Harvard, Berkeley, and Caltech explain the adaptation gap. We mapped our production system against their framework.
The scaling era is ending. The architecture era is beginning. Why frontier models need governance infrastructure, not bigger parameters.
At re:Invent, Werner didn't hype AI. He described the control plane problem that most agent architectures ignore—and why governed autonomy is the path forward.
No single model should have unilateral authority over critical decisions. Here's the architecture that prevents single points of failure.
Explainable. Auditable. Accountable. What it actually takes to deploy agents in regulated environments.
Occasional updates on governance, architecture, and the future of autonomous systems.
Subscribe