# Governed AI

Guardrails, provenance and policy enforced by design.

- [Inside an Architecture-as-Code platform: a working example](https://muthub.org/writing/inside-an-architecture-as-code-platform.md) (Jun 9, 2026): A tour of aac.muthub.org, the open prototype I built to show architecture as a control plane, and the design choices that mattered most: catalogs, executable guardrails, waivers as data, a computed scorecard and an MCP server for coding agents.
- [Model is a tool, harness is the strategy](https://muthub.org/writing/model-is-a-tool-harness-is-the-strategy.md) (May 26, 2026): Handing an AI agent a production codebase without a harness is like putting a teenager in a sports car with no dual brakes. Deterministic guardrails and sensors, owned as a platform, are what make agents safe to scale.
- [Architecture that runs: why AI-era governance must be code](https://muthub.org/writing/architecture-that-runs.md) (May 12, 2026): AI now writes code faster than any review board can read it, while architecture still moves at meeting speed. Governance has to become something that executes in the pipeline and in the agent's context.
- [If you can't prove why an AI wrote it, you can't ship it](https://muthub.org/writing/if-you-cant-prove-why-an-ai-wrote-it.md) (Feb 24, 2026): Shipping AI-generated code without recording where it came from is unmanaged risk. Regulated teams need deterministic provenance for non-deterministic models: line-level attribution, Git-native session history and AI bills of materials.
- [Designing an enterprise MCP registry: the control point agents need](https://muthub.org/writing/designing-an-enterprise-mcp-registry.md) (Sep 18, 2025): As agents multiply, every enterprise needs an authoritative directory of the tools they can call. What a governed MCP registry must do, what the official registry leaves to you, and the mistakes to avoid.
- [Securing AI agents: identity, not secrets](https://muthub.org/writing/securing-ai-agents-identity-not-secrets.md) (May 29, 2025): Agents act on their own, at machine speed, across many systems. Static credentials and perimeter thinking don't hold up. Attested identity, explicit delegation and policy enforced outside the model do.
- [Adopting MCP in a bank: the four risks to solve first](https://muthub.org/writing/adopting-mcp-in-a-bank.md) (Apr 22, 2025): The Model Context Protocol standardizes how agents connect to tools and data. It is silent on whether they should. Four risk areas a regulated institution should resolve before agents get tools.

---
Muthukrishnan (Muthu) Bommiah · https://muthub.org · Views are my own and do not represent my employer.