# Notes

## Learner profile
- Frontend engineer; sibling tracks: SSE, Web Workers, IndexedDB, OPFS, Cache API (decision fluency complete or near-complete)
- **Motivation:** general FE toolkit depth — design-review judgment for browser platform APIs
- **Prior knowledge:** Cache Storage as HTTP Request/Response warehouse; dedicated/shared workers as compute offload; service workers only as comparison labels so far
- **Depth:** system-design decisions + interactive practice; light hands-on later if useful
- **Why this topic:** GitHub issue #9; natural sequel after Cache API (“strategies sit behind a service worker”) and Web Workers (“SW is a different tool”)

## Teaching preferences
- Decision frameworks, tradeoffs, deal-breakers
- Browser APIs and integration difficulty from an FE perspective
- Short interactive lessons (same shape as Cache API / Workers)
- Cite high-trust sources; don’t invent API behavior
- Lesson-first path is fine if external primaries are deferred (established habit on sibling tracks)
- **ADHD (from 2026-08-01):** Prefer scannable lessons — one win up front, short numbered sections, bullets over long prose, tight quizzes, restate state, no wall of theory. Working memory is small; one concept cluster per lesson.

## Session log
- 2026-07-30: Mission established from issue #9; resources seeded; lesson 1 (when service workers fit)
- 2026-07-31: Lesson 1 passed (all quiz correct); external primaries unread → lesson 2 (registration, scope, first install → activate); Archibald lifecycle as primary
- 2026-08-01: Lesson 2 finished; primaries still unread; ADHD lesson shape requested → lesson 3 (update dance: waiting / skipWaiting)
- 2026-08-01: Lesson 3 passed (all quiz correct) → lesson 4 (fetch + respondWith interception)
- Session: Lesson 4 passed → lesson 5 (deal-breakers & debugging)
- Session: Lesson 5 passed (all correct, no external reads) → lesson 6 decision playbook (mission payoff)
- Session: Lesson 6 passed (all correct) → **core mission complete** (issue #9 decision fluency)
