Keep the lesson for the next incident
Cluster the type cases
Group findings by extension, client declaration, content signature, processing format, and missing explanation. Record whether the issue wasted a transfer, blocked selection, or allowed a file too far into processing.
Write the classification matrix
For each supported file family, state the useful picker hint, declaration expectation, content rule, processing outcome, and rejection action. Include a renamed valid file and familiar-name invalid file so the matrix cannot rely on extensions alone.
Add a change trigger
Require the contrast fixtures when changing accepted types, picker filters, validation, previews, or processing adapters. Assign an owner for the matrix and note which wording must change when a classification boundary moves.
What to carry forward
The learning record is complete when each type signal has a defined role, contrast fixtures remain available, and rejection guidance follows the actual acceptance rule. If two stages intentionally use different labels, document the translation rather than hiding the transition.
Technical background: MDN reference.
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