# Review what Gideon learns

Learning helps you turn feedback and task experience into reusable improvements. Review proposed changes before treating them as dependable methods.

## Make a correction specific
Say what was wrong, what should happen instead, and when the rule applies. “Use our approved product names in customer copy” gives a useful scope. A vague negative reaction is harder to reuse accurately.

## Review a proposal
Open **Learning** or the relevant skill proposal view. Read the proposed method, the change from the current version, and the supporting examples. Check that it does not generalize a one-off instruction into a rule for unrelated work.

## Try it on another task
A saved lesson or approved skill is not proof that future performance has improved. Use it on another representative task and review the outcome. Keep evidence of what helped and revise what did not.

> **Try this**
> Review how we completed this task. Suggest one reusable improvement, explain the evidence for it, and identify when it should not apply. Do not present this as a measured improvement without a comparison.

## Keep memory and skills distinct
A preference belongs in memory. A repeatable procedure may belong in a skill or workflow. A source document belongs in Knowledge. Choosing the right place makes the next task easier to understand and review.