Skip to main content
The floor is open. The line is running. The andon cord is within reach. This library exists because the factory documents itself in public on purpose: the knowledge is the shareable half of the plant, and a practice only stays alive by being practiced — by more hands than ours.

If you want to follow the build

Start with The Thesis, then the six theses — they are the factory’s actual originality; everything else is their construction. The station pages show the system as it runs today, each claim traced to its source. The library grows as the plant does: the standard work carries a changelog, and so does everything germline, so the history of every change is part of the record.

If you want to borrow the system

Take it. The ideas here are load-bearing without the plant attached:
  • Write the work order before the unit, and make the mission paragraph state intent, never method.
  • Write the eval before the agent — the gauge before the part. If the acceptance criteria cannot become an eval, the unit is unmanufacturable, and better to learn that on paper.
  • Give every claim an expiry. Whatever you verified, the world under it is moving.
  • Wire an andon for silence: list your recurring obligations, name the artifact each one produces, and alarm on absence. A cron that ran is not a cron that worked.
  • Compile your doctrine. Any rule you care about becomes a script, a schema, or a gate; rules as prose hold about half the time, rules as scripts hold.
None of this requires our tooling. It is a discipline, and disciplines are portable — that is why publishing them costs the factory nothing and proves everything.

If you want to build alongside it

The factory is early — a one-human plant running its pilot line, pacing to a takt of single-digit certified units a week. What it can absorb right now is correspondingly small and correspondingly real: sharp questions, defect reports against the published thinking, and accounts of what happened when you ran these disciplines against your own agent work. Argue with the design; it is written to be argued with. The simplest first step, for every kind of visitor, is the same: pick one discipline from the list above and run it on something you already operate. Then you are not reading about the practice. You are practicing it — and there was zookooree. Come shape something.

Self-audit

ClaimSource
”The floor is open. The line is running. The Andon cord is within reach. Come shape something.”manifesto/tamazukuri.md:187–189
Practices kept alive by practicing themmanifesto/tamazukuri.md:7, 113
Intent over method (Paragraph 2 test); eval before the unit; expiring certificates; silence andon; doctrine compilesdocs/factory-design.md:99, 107, 34, 44–46, 54
One-human plant; takt 3–5 certified units/weekdocs/factory-design.md:71, 75
”One document, written to be argued with”docs/factory-design.md:4
”There was zookooree” — communal makingmanifesto/tamazukuri.md:155