# Muthukrishnan (Muthu) Bommiah

> Muthukrishnan (Muthu) Bommiah is a Distinguished Engineer at Wells Fargo who architects how banks put AI to work at scale and under control: governed Generative and agentic AI, AI-augmented software delivery, Architecture-as-Code and production machine learning.

Every page on this site is also available as Markdown by adding .md to its URL. Views are my own and do not represent my employer.

## Core pages

- [Home](https://muthub.org/index.md): who Muthu Bommiah is and what he works on
- [About](https://muthub.org/about.md): biography, career, education, certifications and speaker bios
- [Initiatives](https://muthub.org/initiatives.md): case studies of work he has led
- [Writing](https://muthub.org/writing.md): essays and notes
- [Playbook](https://muthub.org/playbook.md): Governing coding agents in a bank: a 12-point checklist
- [Now](https://muthub.org/now.md): current focus
- [Reach me](https://muthub.org/reach.md): how to get in touch

## Initiatives

- [AI-Augmented Software Development Lifecycle](https://muthub.org/initiatives/ai-augmented-sdlc.md): Coding agents brought into a large bank's software lifecycle behind one governed platform: curated context, maker/checker controls and a single gateway for every model call.
- [Architecture-as-Code Control Plane](https://muthub.org/initiatives/architecture-as-code.md): An executable, policy-aware governance engine that checks designs automatically before they reach production, so architecture keeps pace with AI-speed delivery.
- [Architecture-as-Code Reference Platform (open prototype)](https://muthub.org/initiatives/aac-reference-platform.md): aac.muthub.org: a public, working prototype of an architecture control plane, with catalogs, OPA policies, waivers, an executive scorecard, a CLI and an MCP server that brings the rules into coding agents.
- [Enterprise Generative AI Architecture](https://muthub.org/initiatives/enterprise-genai-architecture.md): An enterprise-grade Generative AI reference architecture: a governed path from experiment to production, adopted as the reference model across business lines.
- [Data & AI on Public Cloud](https://muthub.org/initiatives/multi-cloud-ai-strategy.md): A multi-cloud Data & AI strategy and reusable, pre-approved archetypes that made public-cloud onboarding much faster and modernized a legacy data warehouse.
- [Controlled Data Movement](https://muthub.org/initiatives/controlled-data-movement-archetype.md): A configuration-driven, secure data movement pattern built at USAA to move 25B+ records a day, then carried to Wells Fargo as a bank-wide framework for analytics and AI.
- [Enterprise Machine Learning Platform](https://muthub.org/initiatives/unified-ml-platform.md): An enterprise MLOps platform that moved 360 data scientists onto one governed environment, saved $25M in license costs over 3 years and cut model deployment from 8 weeks to 5 days.
- [Cloud Data & Analytics Platform](https://muthub.org/initiatives/data-analytics-platform-usaa.md): A cloud data platform at USAA processing 25B+ records a day, with an AWS architecture approved for identity, data protection and detective controls.
- [Enterprise Identity & Access Management](https://muthub.org/initiatives/enterprise-iam-oracle.md): Built USAA's first Oracle Identity Federation servers and the access-management foundation for single sign-on, multi-factor authentication and partner integrations.
- [Middleware & Global Enterprise Systems](https://muthub.org/initiatives/middleware-platforms-bunge.md): Led Bunge's middleware and business-application platforms, delivered a Hyperion upgrade for 2,000 users worldwide and set the enterprise service bus strategy adopted across Bunge companies.

## Essays

- [Self-describing knowledge: why the Open Knowledge Format matters, and what enterprises must add](https://muthub.org/writing/self-describing-knowledge-open-knowledge-format.md): In June, Google Cloud published the Open Knowledge Format: knowledge as plain Markdown with a little structured metadata. It is the right foundation. Regulated enterprises need the next step: knowledge that states its own owner, provenance, freshness and trust.
- [Passive capture: knowledge that writes itself, with humans who approve it](https://muthub.org/writing/passive-capture.md): Documentation fails because it is a second job. The knowledge we need is already produced as a by-product of work: commits, tickets, incidents, reviews and decisions. Capture it passively, distill it, and keep a human approval gate before anything becomes trusted.
- [The AI-native SDLC: when typing code stops being the bottleneck](https://muthub.org/writing/the-ai-native-sdlc.md): AI has made writing code cheap. Verification, trusted context and human judgment are now the scarce resources, and teams that redesign their lifecycle around them will pull away from teams that only add assistants.
- [Not another data lake: context needs curation, not collection](https://muthub.org/writing/not-another-data-lake.md): The tempting answer to fragmented context is to pour everything into one place. We tried that with data, and many lakes became swamps. A context layer has to be a curated overlay: retrieval-first, owned, and pointing back to the systems that hold the truth.
- [Capture the why: the knowledge layer enterprise agents are missing](https://muthub.org/writing/capture-the-why.md): Most enterprise AI pilots hit the same wall: systems record what happened, but the reasoning behind decisions evaporates. Durable, governed context about the why is the real foundation for useful agents.
- [Context fragmentation: why your agents keep starting from zero](https://muthub.org/writing/context-fragmentation.md): The knowledge an agent needs is scattered across code, tickets, chat, wikis, incident tools and people's heads. Each fragment is accurate and useless alone. Fragmentation, more than model quality, is what makes enterprise agents brittle.
- [Inside an Architecture-as-Code platform: a working example](https://muthub.org/writing/inside-an-architecture-as-code-platform.md): 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.
- [The cost of unmanaged context](https://muthub.org/writing/the-cost-of-unmanaged-context.md): Enterprises budget for compute, models and licenses, but almost none budget for the context those models depend on. Unmanaged context is the largest cost nobody tracks, and every new AI agent adds to it.
- [Model is a tool, harness is the strategy](https://muthub.org/writing/model-is-a-tool-harness-is-the-strategy.md): 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): 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): 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.
- [Three architectures for AI coding agents, and how enterprises should choose](https://muthub.org/writing/three-architectures-for-ai-coding-agents.md): Platform-embedded, sandboxed and evolutionary coding agents each earn trust in a different way. Then the editor became a fleet manager. Choose and govern agents by how their work will be verified.
- [Spec-driven development for regulated industries: audit the contract, not every line](https://muthub.org/writing/spec-driven-development-for-regulated-industries.md): For complex work in regulated sectors, prompt-to-code cannot pass an audit. Making the specification the contract an AI must fulfil can, provided the spec stays anchored to the code and machines check conformance.
- [Agent-first data architecture: five principles](https://muthub.org/writing/agent-first-data-architecture.md): Data platforms built for people asking questions will strain when the main consumer is software taking actions. Five principles for designing data platforms where agents are first-class users, and why an open lakehouse helps.
- [Designing an enterprise MCP registry: the control point agents need](https://muthub.org/writing/designing-an-enterprise-mcp-registry.md): 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.
- [Leading architecture change without direct authority](https://muthub.org/writing/leading-without-authority.md): In a large organization you rarely own the teams you need to move. Architects lead through clarity, credibility and standards people want to follow, and by treating the North Star and today's fires as one job.
- [Python or the JVM for production enterprise AI? Put the agent where the transaction lives](https://muthub.org/writing/python-or-jvm-for-enterprise-ai.md): Python is unrivaled for research and prototyping. Production enterprise AI is mostly integration, security and scale, and with JVM agent frameworks now maturing, the runtime that owns the transaction is often the right home for the agent.
- [Securing AI agents: identity, not secrets](https://muthub.org/writing/securing-ai-agents-identity-not-secrets.md): 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): 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.
- [From MLOps to AI engineering: what industrializing ML still teaches us](https://muthub.org/writing/from-mlops-to-ai-engineering.md): A trained model is the start of the work, not the end. The lessons of industrializing machine learning carry straight into generative and agentic AI, which is why AI engineering has to unify DataOps, MLOps and DevOps.

## Archive

- [Introducing the AI Agent Canvas](https://medium.com/@muthukrishnanb/introducing-the-ai-agent-canvas-45418db4aa3c): A one-page blueprint for designing and documenting AI agents across the software lifecycle, with a worked example.
- [Databricks, Delta Lake, and the Rise of the True Data Lakehouse](https://medium.com/@muthukrishnanb/databricks-delta-lake-and-the-rise-of-the-true-data-lakehouse-a-blueprint-for-modern-data-f7c4d56c231e): A blueprint for unifying the data lake and the warehouse for analytics and AI.
- [A Deep Dive into BigQuery Managed Iceberg Tables](https://medium.com/@muthukrishnanb/unlocking-your-data-lakes-potential-a-deep-dive-into-bigquery-managed-iceberg-tables-73ddc585e277): Managing large data lakes on open table formats with BigQuery.
- [Simplicity in Architecture](https://medium.com/@muthukrishnanb/simplicity-in-architecture-emphasizes-71f40e4870a6): Why designs that are easy to explain, build and maintain win over time.
- [The Architect's View: Taming Wild Intelligence with Enterprise-Grade Generative Systems](https://medium.com/@muthukrishnanb/generative-ai-3e1fe4eb20b1): Building generative AI systems that meet enterprise standards.
- [The Unrivaled Engine of Big Data: Its Architecture and Adoption](https://medium.com/@muthukrishnanb/new-article-3b2e1fc9b153): How a big data processing engine works and why organizations adopted it.
- [Demystifying AWS Data Transfer Costs: A Guide for Cloud Architects](https://medium.com/@muthukrishnanb/demystifying-aws-data-transfer-costs-a-guide-for-cloud-architects-e1c753060c83): How AWS data transfer pricing is structured and how to design around it.
- [The Rise of MLOps: Industrializing Machine Learning](https://medium.com/@muthukrishnanb/the-rise-of-mlops-industrializing-machine-learning-bd9b13d9c098): Why a trained model is the beginning, not the end, and how MLOps closes the gap to production.
- [The Accidental Revolution: How Containers Quietly Conquered the Datacenter](https://medium.com/@muthukrishnanb/containers-3712d348a036): How containers spread through the data center, largely without fanfare.

## Optional

- [Architecture-as-Code reference platform](https://aac.muthub.org): working prototype of an architecture control plane
- [LinkedIn](https://www.linkedin.com/in/mbommiah/)
- [GitHub](https://github.com/muthub-ai)
- [Medium](https://medium.com/@muthukrishnanb)