Keep the lesson for the next incident
Document freshness semantics
Record which source timestamp, version, or event defines freshness and how quiet periods are treated. State the expected interval for each destination use, including snapshot or reporting exceptions. Make the contract specific enough that two reviewers classify the same observation alike.
Preserve lag fixtures
Keep source and destination examples for normal delivery, delayed delivery, out-of-order state, rejected input, and no source change. Assert values, versions, and freshness classification. Include the stage boundary that exposed the incident so later checks fail near the actual loss.
Review recurrence and recovery
Assign owners to source activity, delivery, processing, storage, and consuming views as needed. Review lag distribution and oldest age on a defined cadence, with triggers for widening cohorts or repeated stage delays. Close follow-up only after recovery evidence and the freshness contract agree.
What to carry forward
Close the learning record with freshness definitions, stage ownership, representative lag fixtures, and a review trigger for age or version drift. Keep unknown source activity visible. The durable outcome is earlier, more precise stale-data detection and a bounded recovery path.
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