Decide where the work belongs
Rank contract exposure
List requests, events, shared data, or jobs crossing the version boundary and identify whether failures could block customer work. Prioritize broad or irreversible effects over isolated diagnostic differences.
Compare observed harm
Use errors, retries, malformed payloads, latency, or failed completions to measure what the skew is doing now. If no harm is observed, record the evidence gap rather than claiming compatibility.
Set a skew expiry
Choose a checkpoint before the next rollout stage, queue drain, or compatibility window closes. Name what confirms safe coexistence and what requires an owner to review the boundary.
What to carry forward
The queue decision should include the contract boundary, exposure, evidence quality, owner, and expiry checkpoint. Keep priority elevated when compatibility is unproven and the mismatch can expand; lower it only with comparable path evidence. Give precedence to a skewed boundary that can reject requests, events, or data, and keep a harmless overlap lower when matched behavior demonstrates compatibility.
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