Aglet

Investigate document output format drift with paired artifacts

Investigation should test repeatability with the same source and context, then vary one known factor at a time. Preserve paired artifacts and compare semantic as well as binary properties. The brief should identify the first changed output property and whether a contract permits it.

Build a useful investigation brief

  1. Build a stable source fixture

    Choose a document containing text, metadata, multiple pages, and a visible landmark. Record source marker, expected output properties, processing options, and context so paired runs can be compared without source drift.

  2. Run controlled pairs

    Process the fixture twice under the same context, then repeat after one documented version or option change. Capture output identity, format, metadata, page structure, text, rendering, and timestamps for every result.

  3. Compare semantic boundaries

    Diff bytes and structured properties, then inspect rendered landmarks and searchable text. Identify the first changed property and test whether it affects capability, naming, or downstream compatibility rather than treating all binary differences as equivalent.

What to carry forward

The investigation is sufficient when paired artifacts identify the first meaningful output change and its processing context. If binary variation has no semantic effect, record that distinction; if semantic drift lacks a documented contract, preserve the comparison for an owner decision.

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