Principlev1
Cap work-in-progress to match constraint consumption rate,
Cap work-in-progress to match constraint consumption rate, preventing upstream processes from flooding the system with tasks the constraint cannot process.
Why This Is a Principle
Derives from Little's Law (Average cycle time equals work-in-progress divided by) and the necessity of slack (Intentional underutilization (slack) is necessary for). The principle prescribes explicit WIP limits as a pull-based control mechanism. This is derived operational guidance, not foundational system behavior.