ced4568andClaude Sonnet 5
e68b6f445a
Adds all 6 ROOT 03 modules (why version control exists, the Git mental model, everyday Git, branching & merging, remote repositories, engineering Git workflow) — 31 activities. Uses only real LOCAL Git repositories throughout — no Gitea account, no network access, and no RootNode-canonical-repo credential is ever needed or exposed in a student Lab (docs/ROOT_FOUNDATIONS_LAB_STRATEGY.md §4). Modules 1, 2, and 6 are conceptual bookends with no lab, matching the flexible readiness standard already used in ROOT 01/02. Adds 3 new hands-on Git scenarios plus 2 MCQs: git-everyday-basics (init/add/commit, validated by inspecting real `git log`/`git show` state, not just command output strings — Step 6's explicit requirement), git-branching-and-merge (a REAL merge conflict caused on purpose by two branches editing the same line, resolved by the student, validated by confirming the conflict markers are gone and a real two-parent merge commit exists), and git-remote-clone-push (a real local bare repository standing in for a remote — clone/commit/push validated by inspecting the REMOTE side directly, not just the student's own clone). All tested end-to-end via the real scenario-validation API, including negative tests. Wires rootnode-git-fundamentals-assessment (2 required + 3 random-draw scenarios) using the existing Phase 3B assessment engine. Co-Authored-By: Claude Sonnet 5 <[email protected]>
1.1 KiB
1.1 KiB
Reflection: Naming the Problem You're About to Solve
Reflection questions
- Have you personally ever lost work, or been confused about which file version was current, in a way version control would have prevented?
- What do you expect to feel DIFFERENT about how you work once you have real history and rollback available?
Real Ops takeaway
Every engineering practice this program builds toward — code review, CI/CD, GitOps, infrastructure as code — assumes version control as its foundation. You cannot meaningfully automate deployment, review changes before they ship, or declare infrastructure as code without first having a reliable, structured history of what changed and when. This module named the problem; the rest of ROOT 03 gives you the tool.
This module is complete. Continue to the next module.
Instructor Notes
Discussion questions for a live classroom: question 1 tends to produce genuine, motivating stories — let students share before moving to Module 2's mental model.
Approximate timing: 5 minutes live discussion; 3 minutes self-paced writing.