Planning Rules
v0 planning runtime uses product batch limits plus family-based cleaning transitions. Global planner defaults and batch-mixing overrides are intentionally inactive.
Active Runtime Policy
Canonical v0 precedence
- Capacity comes from silo physical limits plus product density.
- Batch limits come only from product-level maxBatchesBetweenCleanings and maxBatchesInSilo.
- Cleaning checks use a matching override first; otherwise same family means BASIC and different family means EXTENDED.
Synthetic/debug tooling may still diverge on cleaning overrides until STEP 09. Production runtime is the canonical behavior.
Cleaning Rule Overrides
Use explicit family-to-family overrides only when the default rule is not sufficient.
| From family | To family | Cleaning type | Actions |
|---|---|---|---|
| No explicit overrides. Runtime falls back to same family = BASIC, different family = EXTENDED. | |||
Add override