# Step 9 — Implementation Detail `docs/adr/0004-lessons-and-overlays-arrive-as-skills.md` was accepted by the owner on 2026-10-08, with its six decisions as written: 1. No lesson takes effect without a person's approval. 2. A lesson is kept only if the evaluation, run with and without it, holds quality and lowers Revisions, time or tokens. 3. Lessons are per Cloud provider, listed in that provider's bundle. 4. Overlay Skills come only from directories the deployment configures; a caller names one and cannot upload one; an unknown name refuses the Execution at the start. 5. Every Execution records the Skills it loaded and a content hash of each. 6. Lesson candidates are client data: stored with the Execution's records, never in the repository, and a lesson carries no client detail. `CONTEXT.md` gained **Lesson candidate**, **Lesson** and **Overlay Skill**. Steps 10 and 12 in `DETAIL.md` were updated to name the decisions they must meet. Already in place from earlier steps: lesson candidates are captured per Execution (step 7) under a gitignored folder, and each Execution records the version of every Skill it loaded. Not built: the curator and the lessons Skill (step 10), and overlay Skills chosen per Execution (step 12).