Decide where the work belongs
Rank decision exposure
List claims and decisions supported by each stale artifact, then record what changed if the artifact is wrong. Give priority to context that controls current scope, data quality, release state, or owner action. Keep descriptive background lower when it cannot alter the recommendation.
Assess refresh value
Estimate whether a named current file, query, record sample, or owner confirmation can resolve the uncertainty. Classify the next move as refresh one artifact, reframe historically, investigate changed behavior, request context, or proceed with a limitation. Include freshness cutoff and revision.
Set a queue decision
Choose one refresh boundary, owner, evidence source, and acceptance trigger. If old context remains intentionally in scope, label the historical comparison and its date. Do not rerun the full task when a single changed artifact can determine whether the conclusion still holds.
What to carry forward
Return a ranked refresh queue linking stale artifacts to decision exposure, change likelihood, evidence source, owner, and acceptance trigger. The leading item should name the smallest update that can change the result. Mark the queue provisional where current revision or freshness need is unknown.
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