How he works
“Bounded contexts and monadic composition. That's all you need to write code with AI.”
The line describes an architectural stance. Bounded contexts set clear limits on what an agent may call. Composition decides how tools, evaluation and guardrails stack on top of each other. That is how he designs agent harnesses.
He applies the same pattern to the software development lifecycle: specification, generation, review, testing, CI/CD and release, with a quality gate at each step.
In production, the same boundaries become access control, audit trails and human oversight. Where they apply, those controls are mapped to the EU AI Act, UK regulatory guidance, ISO/IEC 42001 and the NIST AI RMF.
Changing systems that cannot go down is slow, checked work. That is where the habit of safe change comes from: know the boundary, prove the new path, keep a way back.
