Aglet

Verify downloads bind bytes to the selected document revision

Verification should challenge identity binding with lookalike documents, changed revisions, alternate formats, and repeated requests. Compare saved bytes with a trusted selected artifact and confirm the visible outcome preserves enough context for a reader to detect any mismatch before downstream use.

Check whether the outcome improved

  1. Run identity challenge cases

    Select two similarly named documents, two revisions with different markers, and one alternate format. Record expected identity and content before each download, then compare response and final saved metadata.

  2. Exercise timing and retries

    Download after a page revisit, repeat a request, and change the selected revision before completion where the workflow permits. Verify a late response cannot attach to a newer selection and a retry cannot silently change identity.

  3. Inspect final evidence

    Compare bytes, length, format, revision, and visible name with the selected artifact. Confirm completion controls and downstream handoff use the verified result, and that an identity discrepancy produces a useful failure rather than a plausible success.

What to carry forward

Accept the download when every challenge case preserves selected identity and source-equivalent content for the requested representation. Fail when a completed artifact belongs to another revision, when retries change identity silently, or when the workflow lacks evidence to verify selection.

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