Aglet

Prioritize download content mismatches by decision consequence

Content mismatches deserve urgent attention when a reader approves, signs, imports, or shares a file believing it represents another document. Prioritization should weigh the decision and detection path, separating a visible format choice from bytes that silently belong to the wrong revision.

Decide where the work belongs

  1. Name the downstream decision

    Record what the reader does with the file and when its revision matters. Note whether the downloaded artifact is checked before use, whether it feeds another workflow, and what evidence would reveal a wrong document.

  2. Assess identity exposure

    List selected identity, page state, request context, response metadata, filename, content signature, and revision labels visible to the reader. Mark paths where the file looks complete and plausible despite a different source.

  3. Choose the queue

    Queue identity binding when evidence shows a different revision or document, representation repair when only format is wrong, or detection-copy work when content is correct but identity is hidden. Attach selection and response comparisons.

What to carry forward

Prioritize the issue when a completed, plausible file can be used in a decision while representing another document or revision, before a reader can detect the difference. A visible format conversion with correct identity can rank below silent content substitution.

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