Keep the lesson for the next incident
Compare stale boundaries
Align record change, view, route, update mechanism, cache or client path, duration, and consequence across episodes. Separate delayed processing from a representation that incorrectly claims to be current.
Define current-state evidence
Document which authoritative value, timestamp, and rendered indicator must agree for each consequential view. State acceptable pending states and the refresh paths that must preserve them.
Set a recurrence check
Create a review trigger for cache, partial-render, navigation, or update changes affecting the view. Name the paths and delayed windows that should be checked before freshness is trusted again.
What to carry forward
The lesson should add one freshness contract and a recurrence rule for the affected read paths. Treat the improvement as provisional until later changes show current data and honest pending states across navigation boundaries. Preserve a freshness review for pages whose state drives decisions and rerun it after caching, Turbo, presenter, navigation, or response-header changes.
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