Skip to main content
The factory’s stance on openness is a split, and the split runs along a clean seam. The knowledge is public. The theses, the station designs, the standards, the lessons — this library — publish so that anyone can build their own line. Publishing is not generosity bolted onto the thesis; it follows from it. If the factory is the product, the proof of the product is the system, and a system whose discipline only works in secret is not a discipline. The manifesto goes further: the name itself means communal making — the act of creating something that belongs to no one and serves everyone. You would not say “I built this.” You would say “there was zookooree,” and the thing exists. The plant is private. The running infrastructure, the live units, their access and credentials stay behind the wall. An operating factory’s internals are its own concern — and its own attack surface. Where a public page would need operational specifics, it says see the private registry and stops there.

​
The sovereignty seam: parts versus machines

The long-term decentralization question resolves under factory logic: the parts are ours; the machines are rented. Everything that defines a unit — context files, skills, work orders, certificates, learning files, the standard work — lives in markdown and git: owned outright, portable by construction. Runtimes, gateways, and models are machines: replaceable in principle, single-sourced in practice, adapted only at the deploy boundary — one station speaks the runtime’s language, and everything upstream never learns it. Runtime-agnosticism is therefore not a project to undertake; it is a property to not lose. The test runs yearly or on runtime pain: port one certified unit to a second machine and measure the changeover. If changeover cost creeps up, the seam is eroding.

​
Decentralization, in order

Plain files and git are already the decentralized substrate — no bespoke memory infrastructure, no proprietary store; the corpus’s own benchmarks say plain files win anyway. Content-addressing of the certificate BOM is a natural future encoding, deliberately not required now. The pattern is consistent: decentralization arrives by keeping the parts portable and the formats open, not by building infrastructure ahead of need — that would be overproduction, and the factory’s do-not-build list exists precisely to refuse it.

​
Self-audit

ClaimSource
Zookooree = communal making; belongs to no one and serves everyone; “there was zookooree”manifesto/tamazukuri.md:155
The factory is the productdocs/factory-design.md:12
Parts are ours, machines are rented; markdown+git owned outright; deploy boundary is the only runtime-speaking stationdocs/factory-design.md:255
Yearly SMED port test; seam erosion measured by changeover costdocs/factory-design.md:255
Plain files beat bespoke infrastructure; content-addressed BOM natural but not requireddocs/factory-design.md:255, 144
Do-not-build list includes bespoke memory infrastructure and a second runtimedocs/factory-design.md:279