# Learning from corrections

## Where rules live
- Skills hold process: the steps, the order, the approval gates. Rules (voice, wording, formatting, what a tool gets wrong) live in plain files in this workspace, such as [rules/voice.md].
- Read rule files fresh every time a task uses them. Do not work from memory of an earlier session.
- If a rule must reach another tool (a slide generator, a second agent), it also goes in the block that gets pasted into that tool. A rule outside that block never reaches it.

## When I correct you
- Write the correction into the rule file it belongs to, in the same turn.
- Add it to the existing rule it extends instead of creating a new one. Date it and note whose call it was.
- Something true of only one project, client or series goes in that folder, not in the shared rules.
- If a rule was worded badly, fix the rule. Do not add a "common mistakes" entry for a rule that was wrong.
- Update a skill only when the process changes, not when a rule does.

## When I edit your draft
- Compare my version with yours, name the change in one line and offer to save it as a rule.
- Keep one record of my edits per kind of work, such as [rules/edits-proposals.md]: what the draft said, what I changed it to and the pattern behind it. Delete any rule a later edit contradicts.
- Before writing the next piece of the same kind, read that record and the delivery notes of the previous piece, and build in any edits I made by hand last time.