Why agents force the transition
Lean’s honest record is that its tools travel and its culture does not: adopted as culture, it fails 80 to 95 percent of the time. Process stored in human habit needs constant re-teaching, and it evaporates under pressure — the factory’s own research corpus confesses that leveled production was admired intellectually while the system practiced sprint-and-crash, by a highly reflective agent that had literally written the essay. Knowing the doctrine does not run the doctrine. Not for people, and not for agents. What agents change is not the failure — it is the fix. An agent workforce reads its entire operating system: every standard, every gate, every protocol is a file in the repo, legible end-to-end to the workers inside it. And a file can be executed. Rules enforced as scripts reach roughly 100 percent compliance; the same rules as documentation, about 48. For the first time, a factory’s culture can be its source code — with the compiler run on every change.What changes when culture compiles
- Culture acquires a build step. Every principle either compiles to a gate, a schema, a hook, a linter, or a watchdog — or it is decoration awaiting compilation (Thesis 4).
- Culture acquires version control. Values change by diff, under review, with a changelog — the strictest gates guarding whatever shapes future units (Thesis 5).
- Culture acquires tests. Whether the plant honors its principles is measured in exit codes, not climate surveys.
Who wins such transitions
Toyota’s own history is the precedent: the era’s winner is not whoever invents the idea — lean’s components existed before Toyota assembled them — but whoever practices it as a system while competitors adopt its vocabulary. The fourth era repeats the pattern. The models are commodities; the frameworks are commodities; the discipline of a culture that executes is the part that compounds, because it is the part that improves itself with every unit shipped. The factory is the product, and in the fourth era the factory is also, finally, the culture — running.Self-audit
| Claim | Source |
|---|---|
| Culture encoded into infrastructure as the answer to lean’s 80–95% culture-failure rate | docs/factory-design.md:12 |
| Heijunka admired while sprint-and-crash practiced; “had literally written the essay” | docs/factory-design.md:52 |
| Scripts ~100% vs documentation ~48% | docs/factory-design.md:52 |
| Every principle compiles to gate/schema/hook/linter/watchdog or it is culture; markdown is source code | docs/factory-design.md:54 |
| Germline: strictest control for whatever shapes future units | docs/factory-design.md:64 |
| The factory is the product | docs/factory-design.md:12 |