Homelab Academy / Modules
Orient, prior check, guided practice, required Feynman, reflect.
Module: Module 2: ARR Media Automation
Activity type: Lesson (Orient → Recall → Learn → Explain → Reflect)
Learning objective: Given a known-good profile backup, the learner can choose one authoritative sync path, run dry-run/apply/rollback, and produce a drift report that matches the live apps.
Bloom level: Apply / Evaluate
Mastery unlock for this topic: reading done + Feynman complete + quiz ≥80% (when scored) + lab gate + homework submitted
Given a known-good profile backup, the learner can choose one authoritative sync path, run dry-run/apply/rollback, and produce a drift report that matches the live apps.
Manual clicking can create a correct profile once. Automation aims to keep declared policy synchronized over time. That introduces new hazards: upstream changes, destructive replacement, token exposure, and configuration drift. This class teaches controlled automation rather than blind synchronization.
Answer briefly before reading Instruction. Wrong answers are useful: they show what to review.
Complete the module reading first:
Then review the worked example inside that reading (I do).
We do: hints allowed. Check your reasoning against Instruction.
Classify three changes as safe / review / dangerous with the lesson’s change table open.
Required. Do not skip.
Describe why ARR configuration needs an authoritative control loop in your own words. No copying the lesson verbatim.
Explain the same idea to a 12-year-old. If you use a technical word, define it.
Analogy: two people editing the same spreadsheet without track changes.
What part was hard to explain? That is where your understanding is thin.
Return to that part of Instruction, restudy it, then rewrite a clearer explanation below.
Mastery note: a completed Feynman teach-back is required before the next class unlocks: “I get it” without explanation does not count.
Answers save in this browser (localStorage). Completing all five fields is part of the mastery unlock.
What would drift look like in your lab tomorrow, and how would you detect it without guessing?
Also answer:
This control-loop pattern returns for HA dashboards/automations, reverse-proxy config, voice models, and n8n workflows: same discipline, different files.