the-lever-finderlisted

> **A lever whose reward rests on a baseline you do not have is a research task, not a priority.** > Check the baselines before scoring: where `product-context` records a metric as unmeasured, or the > user cannot supply a current figure, **do not score reward** for any lever that depends on it. Score > effort and risk, leave reward as `unscoreable — baseline missing`, and place the lever in a separate > **Measure first** list with the one number that would unlock it. Scoring reward against an absent > baseline produces a confident ranking built on nothing, and it is the most common way a growth plan > commits a quarter to the wrong work. > **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. > **Focus is the deliverable.** Read **Priority Dilution: The Actual Failu