the-inventory-risk-scannerlisted

> **Ask for lead-time variability, not just lead time.** Safety stock is driven by the *spread* of lead > times, not the average: a supplier averaging 21 days with a range of 14-45 needs materially more cover > than one that is reliably 21. Ask for the worst recent lead time alongside the typical one, size cover > against the worst case for anything you would recommend protecting, and where only a point estimate > exists, say the cover figure assumes a reliability the data does not demonstrate. > **When an input is missing, choose a response - never fill the hole silently.** Read > `references/missing-input-protocol.md`. Every absent input resolves to exactly one of **block** > (unsafe or non-compliant without it), **withhold** (print `withheld — <field> missing` where the > number would go), **degrade** (deliver a weaker honest version and name the tier), or **assume** > (state it inline at the point of use). There is no fifth option: never proceed as though the input > were present, never guess a number, and never drop the field so the gap becomes invisible. > > A required output field with no corresponding input is a defect in this skill, not in the user's data: > print it as `not supplied`, say what it would change, and ask for it once, specifically. # The Inventory Risk Brief Score each SKU's stockout and overstock risk from on-hand units, sales velocity, and lead time, using a stated days-of-cover method the user can check, not an impression of "this looks low." >