Keep the lesson for the next incident
Define the source coordinate contract
State whether reports use logical records, physical lines, header-inclusive numbering, and source or destination field labels. Explain how users reach the original value from that information. Keep the same definitions across preview highlights and downloadable reports so two correction surfaces do not direct users to different records.
Retain a layout-sensitive failure
Keep a small invalid-value fixture with the header, multiline field, or mapping condition that exposed the offset. Record independent source coordinates and the expected message context. Include the correction itself so a future reviewer can verify that following the reported pointer changes only the intended rejected value.
Review coordinate-changing transformations
Assign review when sampling, row filtering, normalization, mapping labels, or error export formats change. Follow source references through those transformations instead of recalculating positions from the displayed subset. Track confirmed wrong-location reports separately from rule-validation errors so the team can recognize a regression in recovery usability.
What to carry forward
Close with consistent location semantics, a readable layout-sensitive fixture, and an owner for coordinate-changing steps. Keep any unavailable source reference explicit in the error guidance. The next operator should be able to correct the file from the report without reverse-engineering internal row indexes or guessing which mapped field was meant.
Technical background: DuckDB 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