What makes it different
Most AI coding setups give you a fast way to write code. Gemba Flow gives you a supervised production line — the affordances of a factory manager, not an extra-fast typist.
| Differentiator | What it means in practice |
|---|---|
| Production-line paradigm | The affordances are those of a factory manager — Ready column, WIP limits, gemba walks — not those of a code-review tool. Covers ideation through last-mile delivery, not just the coding step. |
| Encode intent, not prompts | Each bootstrap phase writes durable artifacts (PRD, architecture, agent configs) that downstream phases read. Your intent isn’t a prompt; it’s the DNA the whole system inherits from. |
| Defense-in-depth controls | Platform-level branch protection, account separation, Claude Code permission denies, and workflow conventions stack so no single layer is a single point of failure. |
Why this matters when agents are typing
A single agent session can produce hundreds of lines of code in minutes. Without structure, that speed becomes a liability: changes are too large to review, history is too noisy to audit, and the human’s attention becomes the single point of failure.
Gemba Flow distributes that load across the system — trunk-based branches keep diffs small, structured commits keep history legible, preview environments let you see the change before you spend attention reviewing it, and the agent roster keeps authority explicit.
Speed is only valuable when you can verify what was built. Gemba Flow keeps verification affordable.