# Notes

## Learner profile
- Frontend engineer; sibling tracks: SSE (complete), Web Workers (complete), IndexedDB (complete / near-complete)
- **Motivation:** general FE toolkit depth — design-review judgment for browser platform APIs
- **Prior knowledge:** Cache API already placed on the client-storage spectrum (IndexedDB lesson 1); no assumed depth on `caches` methods, SW strategies, opaque responses, or versioning cleanup
- **Depth:** system-design decisions + interactive practice; light hands-on later if useful
- **Why this topic:** GitHub issue #2; natural sequel after IndexedDB (“HTTP assets vs structured data”)

## Teaching preferences
- Decision frameworks, tradeoffs, deal-breakers
- Browser APIs and integration difficulty from an FE perspective
- Short interactive lessons (same shape as SSE / Workers / IndexedDB)
- Cite high-trust sources; don’t invent API behavior

## Session log
- 2026-07-24: Mission established from issue #2; resources seeded; lesson 1 (when Cache API fits)
- 2026-07-25: Lesson 1 passed; external primaries not read → lesson 2 (open/put/match) uses Cache API quick guide as primary
- 2026-07-25: Lesson 2 passed; primaries still unread → lesson 3 (strategies & SW) uses Offline Cookbook as primary
- 2026-07-25: Lesson 3 passed; lesson 4 deal-breakers (Storage for the web as primary for quota/eviction)
- 2026-07-26: Lesson 4 passed; external primaries still unread → lesson 5 decision playbook (mission payoff; lesson-only OK)
- 2026-07-26: Lesson 5 passed; track closed at decision playbook (issue #2 mission complete)