Overview
Design chain: Backward Design → Bloom’s Taxonomy → Learn / Practice / Test / Reflect → Mastery → Spiral Review
Feynman teach-back is required in every lesson.
Backward design: module outcome
Student can virtualize a safe lab host, run persistent Compose services on isolated Docker networks, operate containers with update/rollback evidence, and read IPv4 address/mask/gateway to decide same-LAN vs via-gateway delivery.
Bloom arc
Remember/Understand (IPv4, VM basics) → Apply (Compose, ops) → Analyze (networking)
Module learning cycle
Orient → Recall → Learn (reading) → Demonstrate (worked example) → Guided practice → Independent practice / homework → Feynman → Lab → Quiz → Feedback → Module project → Module exam → Reflect
Module assessments
| Activity | Purpose | Link |
|---|---|---|
| Module project | Integrated skill (Apply/Create) | project.md |
| Module quiz | Retention across topics | module-quiz.md |
| Module exam | Mastery verification | exam.md |
| Remediation | Re-teach weak areas | remediation.md |
Practical mastery gate: pass before you continue
Spiral review
Every later module reuses Compose, networks, ops runbooks, and IP literacy when services cannot talk.
Practical gate
Feedback → targeted reading → new practice → redo Feynman Retry → reassessment (see remediation.md).
Topics: activity paths
VMs, hypervisors, and Proxmox
Docker Compose
Docker networking
Container operations
IPv4 addresses and gatewaysModule assessments
- Project: integrated Apply/Create
- Module quiz: retention
- Exam: mastery
- Remediation: re-teach weak areas