Lean

From Toyota-specific production history to portable engineering properties—without turning IMPLEMENTAUDIT into a Lean programme or toolkit.

Genealogy

Toyoda loom defect-stop and Kiichiro Toyoda's needed-quantity/time ideas preceded the later jidoka and just-in-time system.
Toyota combined flow with kanban, levelling, quality, maintenance, training, labour institutions, supplier relations, and bounded response to abnormality.
Statistical quality and Training Within Industry are shared ancestries, not proof that either generated the complete Toyota Production System.
Lean production became an external comparative category; Lean Thinking abstracted value, value stream, flow, pull, and perfection.
Product-development, learning-system, and socio-technical interpretations exposed option, sustainment, worker, and power boundaries hidden by toolkit accounts.
Lean software and software Kanban translated selected properties. Continuous Delivery and DevOps are hybrids and convergences, not simply direct Toyota descendants.

Selected sources and claim limits

Source	Supports	Does not establish
Toyota, The Birth of Jidoka	A corporate historical account of the loom defect-stop antecedent.	The complete later TPS doctrine or causal outcome proof.
Toyota, Origins of Just-in-Time and Supermarket Method	The documented needed-quantity/time and replenishment lineage.	Zero inventory or make-to-order everywhere.
Sugimori et al., Toyota production system and Kanban system	A participant account connecting JIT, kanban, and respect-for-human-system doctrine.	Neutral worker-experience evidence or universal superiority.
Holweg, The genealogy of lean production	The longer genealogy and diffusion beyond one invented moment.	Validation of every later Lean claim.
Williams et al., Against lean production	Criticism of early universal-superiority and mass-production caricatures.	That every Lean mechanism is ineffective.
Landsbergis et al., worker-health review	Workload, autonomy, and worker outcomes as first-order context.	One universal labour-governance design.
Hopp and Spearman, To Pull or Not to Pull	Mechanism- and context-sensitive pull/flow reasoning.	A universal WIP or buffer formula.
Netland, Just-in-time for supply chains in turbulent times	Segmented resilience-aware JIT/JIC reasoning.	Resolved quantitative calibration across domains.

Surviving properties

Inspect actual work and triangulate it with traceable system evidence.
Expose abnormality, then supply bounded stop, containment, escalation, recovery, and recurrence learning.
Prefer system flow and queue-aware capacity to maximum local utilisation.
Use WIP, batch, cadence, and buffers only when their live economics justify them.
Maintain a revisable baseline with challenge, qualification, expiry, and retirement.
Retain options only while uncertainty and irreversible commitment justify their carrying cost.

Rejected caricatures and ceremonies

Historical TPS, Lean production, Lean Thinking, learning-system Lean, and toolkit Lean are not interchangeable. Waste elimination is not the master objective. Zero inventory, maximum utilisation, zero slack, the smallest possible batch everywhere, and exact Toyota-tool conformance are rejected universals.

5S, value-stream maps, kanban boards, A3 sheets, exactly five whys, kaizen events, and standard-work forms may instantiate a property in context. Their presence is not evidence that the property works. Labour and trust language also cannot be converted into unsupported claims of autonomy, humane workload, or fair distribution.

Native route

IMPLEMENTAUDIT maps the surviving properties to existing owner/source, Smoke A/B, Andon, Hansei, recurrence, capacity, action-selection, and closure controls. The bounded cross-method changes are classified on Evolved-LAW; no Lean-specific runtime or certification was added.