Edit or reject
Correct the interpretation before it becomes part of the reflection.
Homa reviews technical and behavioral evidence while keeping uncertainty and user control visible.
Review visible structure, timeframe context, setup conditions, entry reasoning, invalidation, and the methodology you provide.
Notice urgency, hesitation, chasing, escalation, and rule-breaking language without turning reflection into a diagnosis.
One moment should not become a permanent label.
Homa identifies one visible or stated session event.
The mentor proposes what the event may mean.
You review, correct, accept, or reject the conclusion.
Confirmed evidence contributes to the completed session review.
Only recurring evidence may become a longer-term practice pattern.
Ask for missing timeframe, methodology, or chart context instead of guessing.
Keep the source of a technical or behavioral conclusion reviewable.
Correct the interpretation before it becomes part of the reflection.
Inspect, delete, or disable retained mentor context when available.
Price returned to the selected area after displacement.
The idea may depend on confirmation that has not appeared yet.
What specifically invalidates the idea before entry?