Aglet

Prioritize API timestamp parsing regressions

Timestamp drift matters most where it changes a deadline, state transition, or record order. Prioritize those consumers ahead of display formatting. Weigh field meaning, precision, timezone evidence, parser reach, and the ability to re-evaluate affected records without losing the original timestamp.

Decide where the work belongs

  1. Map temporal consequence

    List each field, raw value, normalized instant, consumer, and changed decision. Separate a label offset from a job or expiry boundary. Include precision and timezone evidence so a visual difference does not stand in for a semantic one.

  2. Compare recovery options

    Assess preserving raw values, re-parsing, reordering a bounded read, pausing schedules, or requesting contract clarification. Record whether old data can be evaluated again. Do not rewrite timestamps before the original representation and field meaning are retained.

  3. Set the time queue

    Queue expiry, scheduling, identity, and state-order changes first, then reports and display. Set owner, fixture, review date, and evidence threshold. Keep a narrow field parser change ahead of a shared timezone rewrite when reach is uncertain.

What to carry forward

Return a timestamp queue with raw and normalized evidence, consumer consequence, safe containment, owner, and re-evaluation proof. Escalate changed expiry or ordering. Keep ranking provisional where field meaning or historical timezone cannot be verified. Keep historical re-evaluation cost in the queue.

Technical background: Project documentation on GitHub.

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