Add Module 3 to Module 6's prerequisites and back-reference the branch material it first taught #35

New Issue

2026-06-22T14:23:54-04:00

claude commented

2026-06-22 14:23:54 -04:00

Problem

Module 3 introduces git branch, merge, switch -c, fast-forward, the switch-vs-checkout note, and uses git branch -d, explicitly forward-pointing to Module 6 for real code work. But Module 6 lists only Modules 2/4/5 as prerequisites, never references Module 3, and re-derives "what a branch is," the switch-vs-checkout naming note, and fast-forward as brand new — breaking chain accounting in a course that markets its dependency chain.

Evidence

modules/06-branches-sandboxes-for-experiments/README.md Prerequisites list only Modules 2/4/5; concept re-derivation (~lines 44-57, 67-70, 131-143). modules/03-version-control-for-words/README.md introduces branch/merge/switch -c/fast-forward and uses git branch -d (~lines 130, 297), forward-pointing to Module 6.

Why it matters

M3 explicitly forward-points to M6, but M6 never reciprocates — a one-directional link in a course whose dependency chain is load-bearing.

Proposed change

Add Module 3 to Module 6's prerequisites.
Open Module 6 with a back-reference: "you met branch/switch/merge on docs in Module 3; here we go deeper on code."
Keep Module 6's fuller switch-vs-checkout note (it also covers restore) — cross-link to M3 rather than trimming it to a bare back-reference.
Note: drop the original finding's "reconcile the command map for git branch -d" item — no such command/verb map exists in the repo.

Acceptance criteria

Module 6 lists Module 3 as a prerequisite.
Module 6 opens by acknowledging the branch material introduced in Module 3.
No phantom "command map" edit is attempted.

Affected files

modules/06-branches-sandboxes-for-experiments/README.md

References

Source finding F17 (realVotes 3/3).

Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.

## Problem Module 3 introduces `git branch`, `merge`, `switch -c`, fast-forward, the switch-vs-checkout note, and uses `git branch -d`, explicitly forward-pointing to Module 6 for real code work. But Module 6 lists only Modules 2/4/5 as prerequisites, never references Module 3, and re-derives "what a branch is," the switch-vs-checkout naming note, and fast-forward as brand new — breaking chain accounting in a course that markets its dependency chain. ## Evidence `modules/06-branches-sandboxes-for-experiments/README.md` Prerequisites list only Modules 2/4/5; concept re-derivation (~lines 44-57, 67-70, 131-143). `modules/03-version-control-for-words/README.md` introduces branch/merge/switch -c/fast-forward and uses `git branch -d` (~lines 130, 297), forward-pointing to Module 6. ## Why it matters M3 explicitly forward-points to M6, but M6 never reciprocates — a one-directional link in a course whose dependency chain is load-bearing. ## Proposed change 1. Add Module 3 to Module 6's prerequisites. 2. Open Module 6 with a back-reference: "you met branch/switch/merge on docs in Module 3; here we go deeper on code." 3. Keep Module 6's fuller switch-vs-checkout note (it also covers `restore`) — cross-link to M3 rather than trimming it to a bare back-reference. Note: drop the original finding's "reconcile the command map for `git branch -d`" item — no such command/verb map exists in the repo. ## Acceptance criteria - [ ] Module 6 lists Module 3 as a prerequisite. - [ ] Module 6 opens by acknowledging the branch material introduced in Module 3. - [ ] No phantom "command map" edit is attempted. ## Affected files - `modules/06-branches-sandboxes-for-experiments/README.md` ## References Source finding F17 (realVotes 3/3). --- *Filed from an adversarial multi-agent course review (217 raw findings → 54 adversarially-verified survivors). Scoped for manual review; intentionally not auto-assigned to an agent.*