Skip to content

Order student packets activity-before-notes to match EFFL - #54

Open
code-layne wants to merge 1 commit into
mainfrom
claude/mathematics-syllabus-review-b78688
Open

Order student packets activity-before-notes to match EFFL#54
code-layne wants to merge 1 commit into
mainfrom
claude/mathematics-syllabus-review-b78688

Conversation

@code-layne

Copy link
Copy Markdown
Owner

What changed

One line in shared/lesson.mk:

-STUDENT_ORDER := cover warmup notes activity exit_ticket homework
+STUDENT_ORDER := cover warmup activity notes exit_ticket homework

plus a comment explaining why the order is what it is, and a matching reorder of KEYED_PAIRS.

Why

The line sat under a comment reading "Component discovery (in pedagogical order)" but listed notes ahead of activity. Every built student packet therefore handed students the formal notes before the activity those notes are supposed to emerge from — the exact inverse of the experience-first-formalize-later approach used across the math department.

This surfaced while writing the Advanced Statistics syllabus, whose Course Description now states that formal notes are "the product of the lesson, not its starting point." The packet contradicted the syllabus.

Reviewer notes

  • This repaginates every student and key packet in the course. Nothing about page counts changes — only which component lands where — but any printed or distributed packet from before this commit has a different internal order. That is the main thing worth a second opinion before merging.
  • KEY_COMPS is derived from STUDENT_COMPS, not from KEYED_PAIRS, so the key packet follows the new order automatically and the two packets stay paired 1:1 for the pagination pass.
  • KEYED_PAIRS is dead — defined here and referenced only inside a comment, never read by any rule. Reordered for consistency; could reasonably be deleted in a separate change.
  • No .tex content was touched.

Verification

make -C unit01/lesson03 student key exits 0. The pdfunite invocation now merges cover, warmup, activity, notes, exit_ticket, homework for the student packet and the corresponding _key components for the key packet.

Check Result
lesson03_student.pdf 12 pages
lesson03_key.pdf 12 pages
warmup / activity / notes / exit_ticket / homework each 1 page blank, 1 page keyed — no drift

Only unit01/lesson03 was rebuilt; a full make across all 80 lessons has not been run.

🤖 Generated with Claude Code

STUDENT_ORDER sat under a comment reading "in pedagogical order" but
listed notes ahead of activity, so every built student packet handed
students the formal notes before the activity those notes are supposed
to come out of — the opposite of the experience-first-formalize-later
approach the department teaches.

Swap the two. KEY_COMPS is derived from STUDENT_COMPS, so the key packet
follows automatically and the two stay paired 1:1 for the pagination
pass. KEYED_PAIRS is reordered for consistency only; nothing reads it.

Verified on unit01/lesson03: merge order is now cover, warmup, activity,
notes, exit_ticket, homework in both packets; student and key both come
out at 12 pages and every component matches its _key page for page.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant