Aglet

Prioritize document format drift by downstream compatibility

Format drift matters when readers compare runs, downstream tools expect a representation, or a document's metadata carries meaning. Prioritization should focus on the changed property and decision it affects, separating harmless compression variation from a format or rendering change that breaks use.

Decide where the work belongs

  1. Name the dependent use

    Record whether the output is read, printed, imported, searched, compared, or handed to another workflow. Note the property required by that use and whether a reader can detect a changed representation before relying on it.

  2. Assess drift reach

    List source types, processing paths, output formats, revisions, and consumers affected. Mark whether the difference appears on every run, only after a version change, or only with a specific option or document feature.

  3. Choose the queue

    Queue format contract repair when the documented representation changes unexpectedly, compatibility investigation when downstream use fails, or change communication when variation is intentional but hidden. Attach two outputs and their processing context.

What to carry forward

Prioritize the drift when a changed format, metadata field, or rendering result can break downstream use or invalidate a comparison. A documented compression difference with unchanged capability can rank below an output that silently changes extension or searchable text.

Technical background: MDN 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