Numeric shorthand requires an explicit annotation-scale policy

When a tool-routing contract requests a numeric amount but does not define how spoken shorthand is scaled, annotators should not silently select either the literal value or a domain-expanded value. Preserve the schema-valid alternatives or mark explicit scale ambiguity until the contract names the normalization owner. Keep semantic annotation separate from handler normalization; two values producing the same backend behavior does not make either one the uniquely correct gold label.

This applies when the utterance clearly expresses pricing intent but leaves magnitude convention unspecified. It does not authorize repairing missing or corrupted digits, and it does not apply when the speaker states the complete amount. Evaluate model error only after the annotation policy is frozen.