Aglet

Triage downloaded bytes that do not match selection

A successful response can still represent another revision, format, or document. Triage should bind the user's selection to a stable identity and compare it with response context and bytes. The aim is to separate a wrong-content result from a valid representation that merely differs in display.

Establish what is happening

  1. Freeze the selected identity

    Record document identifier, revision or version, visible title, requested format, filters, and click time. Save a trusted comparison artifact or content signature for the selected item before starting the download.

  2. Compare response context

    Capture response identity, revision, content type, length, suggested name, and final saved bytes. Note cache, retry, redirect, or stale-page boundaries only as observed events, and distinguish a different representation from a different document.

  3. Classify the mismatch

    Classify the case as wrong revision, wrong document, wrong format, partial content, stale selection, or unproven comparison. State the first evidence that differs and whether a reader could detect the mismatch before using the file.

What to carry forward

Triage is complete when selection identity, response context, and downloaded bytes are compared for one attempt. If no trusted selected artifact exists, record that comparison gap and avoid claiming a content mismatch from title or length alone.

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