Instructor Guide and Review Status
Status: authored candidate, September 20–21, 2026. Local implementation and site checks are recorded in the repository's authoring review. Independent mathematical review, independent code review and learner pilots remain pending. No percentile outcome or measured mastery rate has been established.
Delivery and workload
Plan 70–100 hours: lessons/diagnostic/bounded reading 25–35; labs 14–20; independent practice and revision 18–26; assessment/remediation 7–10; capstone 6–9. These are estimates, not observed learner timings. Prerequisite repair and optional depth add time. At 10 hours/week this is roughly 7–10 weeks. Do not layer a full-book schedule on top without separately budgeting it.
Teach clusters in order. Stop after each for an independent explanation and a changed example. Make software transfer concrete but keep advanced systems and type theory optional. A learner can understand proof obligations without already knowing compilers, distributed consensus, or amortized analysis.
Review checklist
- Ask a subject reviewer to audit quantifiers, empty domains, typed functions, image-intersection qualifications, closure notation and quotient well-definedness.
- Check that induction repairs preserve valid alternative methods; inspect the distinction between derivations, recursive functions and representations.
- Have a code reviewer derive fixtures without using the reference helpers, inspect invalid-input behavior and introduce deliberate faults into a copy.
- Verify that each competency has a derivation, feedback, remediation and a fresh prompt; do not replace proof review with a checker pass or total score.
Pilot record to complete
| Field | Record |
|---|---|
| Learner background and prerequisite misses | Pending |
| Actual time by lesson/lab/practice/assessment/project | Pending |
| First blocked instruction and why | Pending |
| Help given and time of solution exposure | Pending |
| C1–C8 before and after remediation | Pending |
| Reviewer disagreements and resolution | Pending |
| Transfer after 7–14 days | Pending |
| Revisions motivated by observed evidence | Pending |
Start with a small pilot including a beginner and someone with programming experience. Preserve unsuccessful attempts; they reveal prerequisite and wording gaps that a polished final notebook hides. Treat a solo learner's self-review as self-review. Authored, executed, independently reviewed and piloted are distinct states.