Keep the lesson for the next incident
Cluster naming failures
Group findings by Unicode loss, punctuation normalization, extension changes, revision omission, collisions, wrong identity, and representation-specific names. Record the reader task and the name needed to recognize the artifact later.
Document the naming policy
State which source name is used, how unsafe or unsupported characters are handled, where extension comes from, how revisions and collisions are represented, and whether display title remains separate. Include representative difficult names.
Trigger naming review
Require fixtures when changing document titles, formats, conversion, response construction, local save behavior, or collision handling. Assign an owner for the policy and record the identity comparison that proves names still describe the delivered bytes.
What to carry forward
The learning record is useful when display and saved names have distinct documented roles, difficult characters and collisions are covered, and content identity is checked. If local behavior varies by client, record the response policy and the client boundary that remains outside control.
Technical background: RFC Editor 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