Aglet

Prioritize missing document derivatives by blocked capability

A missing derivative matters according to the capability it provides: reading text, reviewing a preview, downloading a converted file, or handing content to another step. Prioritization should weigh the blocked decision and source identity, separating an optional convenience from an output required for completion.

Decide where the work belongs

  1. Name the blocked capability

    Record the derivative needed, the user action it enables, and any alternative representation available. Note preparation cost and deadline, and distinguish a missing convenience from a source that cannot enter its intended workflow.

  2. Assess identity and reach

    List document revisions, derivative formats, pages, exports, and downstream consumers affected. Mark whether the source remains usable, whether another revision has a derivative, and whether a missing association could expose the wrong output.

  3. Choose the queue

    Queue processing repair when output was not produced, association repair when it exists but is detached, or contract review when the derivative promise is unclear. Attach source and output evidence with the affected capability.

What to carry forward

Prioritize the gap when a required derivative blocks document use or when a detached output could be mistaken for the selected revision. An optional representation with a clear alternative can rank behind a missing text or preview capability needed to finish.

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