Part 1 described what gets produced and in what order: requirements feed event storming, event storming feeds bounded contexts and aggregates, those feed RFCs, ADRs, C4 diagrams, and backlog items. This part covers how each step actually runs.There are two failure modes for AI-assisted...
Event storming has a whole book. arc42 has a website with 12 numbered sections. ADRs have Michael Nygard's original 2011 post and a hundred adaptations of it. C4 has Simon Brown teaching it to thousands of people across 40 countries. Not one of them tells you what output to hand to the next...
My company had a marketing asset library with over ten thousand images. Designers scrolled through folders. Ops teams pinged colleagues asking if someone knew where last quarter's campaign photos were. Executives pulled the wrong hero shot for a presentation because the filename said nothing...
A year ago, smoke tests on my projects were a luxury: too expensive to justify, too slow to run on every PR, too hard to maintain alongside a fast-moving codebase. Today they're the default output of every feature cycle. Not because I added a QA team. Because I built an AI-orchestrated development...
9 min readAgentic AI does not introduce new classes of bugs.It amplifies assumptions that were never made explicit.The better the model, the more convincing the output — and the harder the failure is to detect.In production systems, these failures don’t look like hallucinations.They pass...