Vice Chair for Supervision Bowman participates in a discussion at the Kansas Bankers Association’s 2026 CEO & Senior Management Summit and Annual Meeting Watch Live: Learn more about Vice Chair for Supervision Bowman: 

Federal Reserve Vice Chair for Supervision Michelle Bowman said she expects the Fed to consider final revisions to the stress test framework in the “coming weeks"

Speech by Vice Chair for Supervision Bowman on initial findings from independent review of Silicon Valley Bank @cityoflondon: Watch live: Learn more about Vice Chair for Supervision Bowman:

Speech by Vice Chair for Supervision Bowman on stress testing @cityoflondon: Watch live: Learn more about Vice Chair for Supervision Bowman:

Given that agents still need high level supervision. And given that the human review of code is a bottleneck. And given that the models have gotten good enough that strict deterministic harnesses are suboptimal. Then how should we supervise their output. My current solution is to use an interrogation tool coupled with an agent. The tool displays the structure of the system in a UML-like diagram, color coded with crap and mutation scores. The diagram is dynamic, allowing the user to click on element and drill down through the architecture -- all the way to code. The user can detect structures that need improvement and tell the associated agent to make the appropriate changes. These changes can range from high level architectural changes, to the lowest level code refactorings. The associated agent will make those changes and cause them to be redisplayed. The tool I'm using is custom made for me, but you can point an agent at it and use it as a template to build your own custom tool. It's a work in progress, so don't be surprised if it changes a lot over the next few weeks. But then you probably won't care because by then you'll be deep in customizing it for yourself. And anyway, you can always point an agent back at mine, or someone else's, and integrate improvements into your own.