Aglet

Verify document derivatives match source revisions and promises

Verification should test each promised derivative against its source revision and expected capability. Include a delayed output, a failure, and a revised source. Compare identity, content markers, format, availability, and controls so an old or partial derivative cannot appear ready.

Check whether the outcome improved

  1. Run derivative cases

    Process a source that should yield each promised output, a slower fixture, and a deliberate failure. Record expected derivative type, format, identity, ready state, and allowed action before reviewing results.

  2. Compare source binding

    Inspect derivative metadata, content markers, revision, and visible association with the source. Verify a revised document does not reuse an older output silently and that a partial or failed derivative remains clearly unavailable.

  3. Check user paths

    Open preview, text, converted download, and downstream handoff controls after each state. Confirm each capability appears only when its derivative is ready, and that missing output explains the next action without hiding the source.

What to carry forward

Accept derivative behavior when every promised output is present, correctly bound to its source revision, and exposed with accurate controls across delay and failure cases. Fail when an output is absent, detached, stale, or presented as ready without evidence.

Technical background: W3C guidance.

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