Aglet

Prioritize preview orientation drift by downstream visibility

Orientation drift is most consequential when the preview is the approval surface for a file that will be rendered elsewhere. Prioritization should consider the final use and the confidence a user can place in the preview, separating a cosmetic metadata difference from a visibly wrong output.

Decide where the work belongs

  1. Name the approval decision

    Record whether users select, crop, annotate, print, or publish based on the preview. Note the final consumer and whether it applies orientation metadata the same way, using a real or controlled output path.

  2. Assess visible divergence

    Compare the size, rotation, mirroring, crop, and metadata state in preview and final output. Identify file classes and processing paths affected, and separate a difference users can correct from one that reaches delivery unnoticed.

  3. Select the queue

    Queue transform correctness when final pixels are wrong, metadata contract work when consumers disagree, or preview fidelity work when the final file is right but approval is misleading. Attach the orientation fixture and boundary comparison.

What to carry forward

Prioritize the case when a preview can cause approval of a visibly misoriented deliverable or when correction requires repeating edits. A metadata-only difference with a documented consumer rule can wait behind drift that changes the delivered image.

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