Keep the lesson for the next incident
Document the numeric convention contract
State which decimal and grouping styles are supported, how the convention is selected, and what happens when a string is ambiguous. Keep CSV delimiter handling separate. Connect the contract to preview wording so users can understand the interpreted magnitude before accepting an import with unfamiliar numeric formatting.
Preserve contrasting magnitudes
Retain fixtures that represent the same number under different supported conventions and strings that have different meanings under competing conventions. Include the original failing transformation. Record expected numbers and units independently so future checks do not reproduce the importer’s own mistaken normalization when calculating their expected result.
Review producer and normalization changes
Assign review when another export format, numeric field type, or punctuation-normalization rule is introduced. Compare preview, stored value, and one downstream use. Track confirmed magnitude changes separately from display complaints so recurrence remains visible even if every affected record still passes numeric validation.
What to carry forward
Close with a clear convention contract, discriminating numeric fixtures, and an owner for format changes. Preserve any required source-format choice in user guidance. Future confidence should come from comparing intended values, not from an assumption that a familiar locale or parseable string guarantees the right number.
Technical background: Google Cloud documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow