Build a useful investigation brief
Build a field-specific whitespace matrix
Create leading, trailing, repeated internal, and line-break examples appropriate to the affected fields. Include an unpadded control and record exact expected strings. Identify which transformations are documented before running the comparison, so a cleaner-looking output does not become the expected result merely because the current importer produces it.
Trace every string transformation
Inspect parsing, trimming, field-specific normalization, validation, persistence, and later retrieval. Record the first changed character sequence. Compare the same input across field types only where their contracts differ, and keep case conversion or other normalization visible as separate operations rather than grouping every text change under whitespace cleanup.
Compare lookup and presentation behavior
Use the saved fixture in the representative lookup or display that exposed the problem. Determine whether the comparison itself applies another spacing rule. Test one implicated change against both meaningful-whitespace and ordinary-control cases so a fix does not broaden matching or remove formatting beyond the specific field contract being investigated.
What to carry forward
Deliver exact string traces, intended field rules, and the first inconsistent transformation or comparison. State any unresolved semantic decision. A supported correction follows the field contract and preserves meaningful content; it should not be justified solely by making values look tidier or causing previously distinct identifiers to match after extra trimming.
Technical background: PostgreSQL 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