Keep the lesson for the next incident
Cluster the missing states
Group cases by hidden parsing, conversion, indexing, derivative creation, failure, revisit, and premature ready labels. Record the processing evidence, visible state, and user action each missing transition affected.
Document the lifecycle
State the stages, terminal outcomes, required derivatives, allowed actions, and meaning of ready for the document family. Include a normal path, a delayed later stage, and an intermediate failure with expected labels.
Trigger lifecycle review
Require the fixtures when adding processing stages, changing status persistence, exposing new derivatives, or altering document controls. Assign an owner for the status contract and record which capability each label promises.
What to carry forward
The learning record is useful when each processing stage has a visible meaning, a representative fixture, and a capability contract. If some work is intentionally hidden, state the bounded pending behavior and the safe action rather than implying that transfer means readiness.
Technical background: W3C guidance.
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