autonomation
v0.0.1
Published
Operating doctrine for multi-agent software factories — Toyota Production System and TSMC manufacturing principles translated into artifacts for agentic engineering.
Maintainers
Readme
autonomation
Operating doctrine for multi-agent software factories. Toyota Production System and TSMC manufacturing principles translated into artifacts for agentic engineering — schemas, halt conditions, gates, yield dashboards, and rituals that turn a capable agent substrate into one that ratchets every cycle.
Status: v0.0.1 — early scaffolding. The conceptual frame is in place; implementation surfaces are built incrementally.
- See
DESIGN.mdfor the top-level design, surface inventory, and build order. - See
doctrine/for the principle documentation — start withprime-directive.mdandjidoka.md.
What this is
Autonomation is the doctrine layer for the swarmkit ecosystem. It is not a runtime, learning system, memory layer, or task tracker — those already exist in macro-agent, cognitive-core, minimem, opentasks, and friends. Autonomation supplies the discipline layer those components are missing: explicit halt signals, structured failure taxonomies, yield decomposition, signal-driven kaizen, externalization-as-closure protocols, and standardized work contracts.
The framing target is a dark factory — multi-agent swarms producing software with minimal human-in-the-loop, where every TPS principle that used to be carried by human attention has to be carried by an artifact instead.
Surfaces (planned)
| Surface | Purpose | Status |
|---|---|---|
| doctrine/ | Cultural layer in artifact form — TPS/TSMC principles with carriers | initial |
| standards/ | Schemas, taxonomies, role contracts (poka-yoke + standardized work) | next |
| halts/ | Andon condition library + halt-signal schema (jidoka) | planned |
| gates/ | Promotion + eval policies (jidoka + disciplined cadence) | planned |
| yield/ | Metrics, queries, dashboards (yield obsession) | planned |
| rituals/ | Retrospective, trace-walk, tournament, skill-harvest workflows (kaizen) | planned |
| playbooks/ | Packaged standardized work | deferred until friction data exists |
See DESIGN.md for the build order with stop-conditions per phase.
Install
npm install autonomation