Aglet

Triage document output format drift across processing runs

Output drift can affect file extensions, page count, metadata, text, rendering, or downstream compatibility even when the source is unchanged. Triage should capture the source fixture, processing context, output properties, and visible consequence for two runs. The objective is to distinguish intended versioning from unexplained change.

Establish what is happening

  1. Freeze the source and context

    Record source bytes or a trusted marker, declared format, processing options, stage versions when visible, and run times. Keep the same input and context for comparison, noting any deliberate configuration or source revision difference.

  2. Compare output properties

    Inspect format, extension, size, page count, text, metadata, rendering landmarks, and derivative identity for each result. Record which differences are visible to readers and which affect downstream use or naming.

  3. Classify the drift

    Classify the case as expected version change, nondeterministic output, option mismatch, metadata loss, rendering change, or unclear contract. State the output property that matters and preserve both results for investigation.

What to carry forward

Triage is complete when identical input and processing context are compared across outputs with a named differing property and visible consequence. If version or option context is unknown, record that evidence gap instead of declaring nondeterminism.

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