Teaching notes

Learner goal: career advancement and deeper technical security skills.
Background: CKA, CKAD, and KodeKloud CKS training completed.
Priority: build confidence through timed retrieval and hands-on feedback, not rewatching broad course material.
Learner prefers original performance-based tasks at public CKS curriculum level or harder, with multi-control requirements and strict verification, so the real exam feels comparatively easy.
Review preference: list all detected issues, then correct only one issue per round.
Mastery tracking: use CKS-MASTERY-CHECKLIST.md as the canonical cross-session dashboard. Never award Hero from lesson completion alone; require the topic's tool drill, timed capstone, verification evidence, and cold retest.
Confidence priority: deliberately rotate through named CKS tools instead of relying mainly on hand-written YAML.