Aglet

Verify file type guidance against content validation

Verification should prove that type guidance prepares users for the validation rule without promising acceptance from a filename alone. Test valid content, misleading names, incorrect declarations, and a rejected file. Confirm each state offers an accurate next action and keeps the file identity clear.

Check whether the outcome improved

  1. Exercise naming and content cases

    Use valid content with an expected name, the same content under a different name, and familiar names containing incompatible content. Record picker behavior, transfer outcome, and final validation result for each fixture.

  2. Check signals at each stage

    Inspect the visible hint, request declaration, validation message, preview, and processing status. Verify labels do not contradict the accepted rule and that a changed classification explains why the file cannot continue.

  3. Confirm recovery guidance

    For rejection and mismatch cases, follow the provided next action: rename, convert, replace, or review the file. Ensure the action matches the policy and does not imply that changing a label can make incompatible bytes acceptable.

What to carry forward

Accept type guidance when the tested signals align with the documented rule, mismatches are explained at the earliest useful boundary, and rejected files have a correct next action. Fail when a hint implies acceptance or a label change is presented as content repair.

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