Check whether the outcome improved
Run name and format cases
Download documents with ordinary, Unicode, punctuation, repeated, and revisioned names in each supported representation. Record expected and actual names, extensions, and document identities, keeping each fixture distinct.
Check collision behavior
Download the same title from different revisions or documents and observe the resulting names. Verify collision handling preserves recognition and does not overwrite or silently merge files, while retaining meaningful revision or format cues.
Inspect saved artifacts
Open or inspect each saved file, confirm bytes and representation match the selection, and review how names appear in the intended folder or handoff. Ensure a transformed name remains understandable and any intentional normalization is documented.
What to carry forward
Accept filename behavior when names preserve document recognition, representation, and revision context under the naming policy, with safe collision handling. Fail when a saved name suggests another file, loses necessary identity, or carries an extension that misstates the bytes.
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