# Notes

## Learner profile
- Frontend / full-stack engineer with completed browser-platform tracks (SSE, Workers, storage APIs, etc.)
- **Motivation (issue #10):** standardize multiple projects under one repo for easier maintenance — moon as concrete tool
- **Related work:** `triosoft-git/trio-moon` and similar moon workspaces exist in the wild; use as optional grounding, not as required homework for lesson 1
- **Depth:** decision fluency first; moon hands-on after the “why / when” map

## Teaching preferences
- Decision frameworks, tradeoffs, deal-breakers (same shape as other tracks)
- ADHD-friendly: one win up front, short numbered sections, bullets over long prose, tight quizzes, no wall of theory
- Cite high-trust sources; don’t invent moon API behavior
- Lesson-first path is fine if external primaries are deferred
- moon v2+ docs are authoritative for moon claims

## Session log
- 2026-08-10: Mission established from [ayv4zyan/teach#10](https://github.com/ayv4zyan/teach/issues/10); resources seeded; lesson 1 (when monorepos fit)
- 2026-08-10: Lesson 1 passed (all correct) → lesson 2 (architecture map: workspace / graph / tasks / targets)
- 2026-08-11: Lesson 2 passed (all correct) → lesson 3 (moon everyday loop: install / init / map projects / moon run)
- 2026-08-11: Lesson 3 passed (all correct) → lesson 4 (task inheritance / shared standardization)
- 2026-08-11: Lesson 4 passed (all correct) → lesson 5 (toolchain pins / reproducible versions)
- 2026-08-11: Lesson 5 passed (all correct) → lesson 6 (deal-breakers / failure modes)
- 2026-08-12: Lesson 6 passed (all correct) → lesson 7 decision playbook (mission payoff)
- 2026-08-12: Lesson 7 passed (all correct) → **core mission complete** (issue #10 decision fluency)