tdwhere123 Retrospective
Reason from the observed episode: what outcome was intended, what happened, which cause best explains the difference, and what change would address it. Distinguish evidence from conjecture and recurring causes from one-off friction.
Keep lessons proportional to the evidence. A useful conclusion may be a local code or documentation fix, a better question, or no policy change. Retrospective reasoning does not enable automatic recording, personalization, or policy promotion. Use native host instructions or memory for preferences only when the user requests persistence; do not access or modify old do-it profiles by default.