Record what the evidence actually is
Task completed, document prepared, application sent, receipt received, conversation held, public wording corrected, support contacted, or risk reduced are different evidence classes. Name the artifact or event rather than replacing it with a vague 'progress' label.
State what it does not prove
A sent application does not prove employment. A reflection does not prove therapy worked. A prototype does not prove a production product. A completed task does not prove transformed identity. Limits belong in the evidence record.
Correction is a first-class Journey event
When evidence changes the understanding, update the current path. Preserve why the old step existed, what changed, what evidence caused the correction, and what the new next step is. Correction is not a hidden embarrassment.
Metrics help listening, not judging
Possible future metrics—started pathway, completed step, return after pause, changed goal, read boundary, exported plan—can help understand system use. They should not become a moral ranking or a substitute for human context.
Reflection
Questions to sit with
- What exact evidence exists?
- What claim is proportional to that evidence?
- What correction should happen now?