Aglet

Triage a file type hint that conflicts with validation

A filename extension, picker filter, declared media type, and file content can describe different things. Triage should capture each signal for one file and state which classification the workflow promises to accept. The objective is to find the first disagreement without treating any hint as definitive.

Establish what is happening

  1. Capture every type signal

    Record the filename and extension, picker or form hint, client declaration, initial bytes or signature evidence, and server validation result. Preserve capitalization and any renaming step because classification can change when labels are normalized.

  2. Compare accepted rules

    Place the signals beside the documented allowed type and identify which rule each boundary applies. Distinguish a helpful picker filter from an acceptance guarantee, and note whether the same content is classified differently after transfer or processing.

  3. Classify the user outcome

    Classify the case as misleading hint, incorrect declaration, content rejection, missing explanation, or unresolved policy. Record what the user was told before selection and what next action would be safe after validation.

What to carry forward

Triage is complete when all classification signals and the acceptance rule are recorded for one file. If the contract intentionally rejects a filename that looks acceptable, route the explanation gap separately from a content-validation defect.

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