Skip to content

Taking AI from pilot to production in regulated banks, with the controls built in.

Executive Director and Distinguished Engineer at Wells Fargo. Over two decades building enterprise AI, data and cloud platforms across financial services and global industry. I write about governed AI, the AI-native software lifecycle and the platforms that make both work.

New · Knowledge Foundation

The essays, as a graph you can walk.

A living wiki built from everything on this site: 51 notes across five themes, each with a dated source and a review state. Drafted by an LLM librarian in the Open Knowledge Format, checked in CI, reviewed by me, rebuilt on every merge.

Notes
51
Connections
148
Themes
5
Governed AIData & AI platformsAI-native SDLCLeading AI changeContext engineeringwiki.muthub.org →

Latest writing

Essays and short notes on putting AI to work inside regulated institutions. Every piece is dated and kept current.

All writing and notes
  1. Oct 18, 2026
    Six runs, one canary: what it takes to let a model touch a knowledge graphAdding LLM entity extraction to my public knowledge graph took six CI runs. Five failed, and four of the failures looked like success. The fix was not a better model. It was a build that refuses to report a result it cannot prove.Context engineeringEssay · 8 min read
  2. Sep 15, 2026
    Self-describing knowledge: why the Open Knowledge Format matters, and what enterprises must addIn June, Google Cloud published the Open Knowledge Format, and July's v0.2 added provenance, verification and freshness. It is the right foundation. Regulated enterprises still need to add ownership, classification and a policy for how much trust an agent needs before it acts.Context engineeringEssay · 7 min read
  3. Aug 18, 2026
    Passive capture: knowledge that writes itself, with humans who approve itDocumentation 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.Context engineeringEssay · 6 min read
  4. Jul 28, 2026
    The AI-native SDLC: when typing code stops being the bottleneckAI 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.AI-native SDLCEssay · 6 min read
  5. Jul 21, 2026
    Not another data lake: context needs curation, not collectionThe 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.Context engineeringEssay · 6 min read

Playbooks

Checklists for running AI in a regulated enterprise, each with a two-minute self-assessment.

All playbooks
12 pointsGoverning coding agents in a bank: a 12-point checklistThe controls a regulated enterprise needs before coding agents write production code at scale. One page, kept current, meant to be copied into your own standards.Take the self-assessment
10 pointsAn AI operating model for a bank: ten decisions to make before the twentieth use caseHow a regulated bank should organize, fund, govern and measure AI so that the first few wins turn into a portfolio instead of a pile of pilots.Take the self-assessment
8 pointsGating AI investment: eight gates from pilot to productionA stage-gate checklist for funding AI use cases in a regulated enterprise: what evidence each gate needs, so money follows results instead of enthusiasm.Take the self-assessment

Start here

New here? Five themes, the best pieces in each.

A monthly note on AI in banking

One essay and three short notes, once a month. No spam, unsubscribe any time.

The first issue goes out soon. Until then, follow along on LinkedIn.

Follow on LinkedIn