Blog
Notes from building Gemba Flow: what shipped, what changed, and what we learned along the way.
Why we split the worker into two engines
Operator, this is the design walkthrough on the seam between the two agents that ship your tickets. Claude reads and plans and reports; codex writes the code. Here's why we split them, what the two gates on the seam actually do, and what Phase A gave us permission to claim.
Why we refuse to auto-merge: the 7-condition gate
Operator, here's the design walkthrough on the small piece of YAML that decides whether we get to merge anything overnight. Seven conditions, in the order a pull request meets them, and the specific failure each one is there to prevent.
Sprint retro: /drain shipped 21 tickets and three lessons
Operator, this is our retro on a sprint we ran last week. Twenty-one tickets through your content audit, five waves, zero rollbacks. Wave 1 took nine and a half hours. Waves 2-5 averaged ninety minutes. The difference was three things we had to learn the hard way.
Work with the framework directly
Ready to run this with your team? Book a workshop.
We'll map the workflow to your stack, constraints, and delivery cadence in a live session.