A reusable module needs a small, documented input and output contract. Type constraints express the shape the caller must supply, while validation can reject values that have the right type but violate a rule. A map of capacities, for example, has different meaning from a single capacity number. Choose the simplest shape that represents the caller’s needs.
Keep business defaults in one place and explain when a caller should override them. These tasks keep the module boundary intact while changing its numeric capacity input; the wrong input name is deliberately nearby so a typo cannot be mistaken for a valid override.
A typed capacity input is the child module’s contract.