diff --git a/classroom/DAY1_STUDENT_SETUP.md b/classroom/DAY1_STUDENT_SETUP.md
new file mode 100644
index 0000000..f4b47a1
--- /dev/null
+++ b/classroom/DAY1_STUDENT_SETUP.md
@@ -0,0 +1,307 @@
+# Day 1: Git Setup Guide
+## Get Ready to Track Your Learning!
+
+---
+
+## What You Need
+
+- [ ] A computer (school or personal)
+- [ ] Internet connection
+- [ ] 15 minutes
+- [ ] The class repository URL (teacher will provide)
+
+---
+
+## Step-by-Step Setup
+
+### Step 1: Install Git (5 minutes)
+
+#### On Windows:
+1. Go to [https://git-scm.com/download/win](https://git-scm.com/download/win)
+2. Download the installer
+3. Run the installer
+4. Click "Next" through all options (defaults are fine)
+5. Click "Finish"
+
+#### On Mac:
+1. Open Terminal (in Applications > Utilities)
+2. Type: `git --version`
+3. If it says "command not found", install Xcode Command Line Tools:
+   - Type: `xcode-select --install`
+   - Click "Install" in the popup
+   - Wait 5-10 minutes for installation
+
+#### On Chromebook/School Computer:
+Ask your teacher - Git might already be installed!
+
+**Test it worked:**
+```bash
+git --version
+```
+You should see something like: `git version 2.39.0`
+
+---
+
+### Step 2: Tell Git Who You Are (2 minutes)
+
+Open Terminal (Mac) or Git Bash (Windows) and type:
+
+```bash
+git config --global user.name "Your Name"
+```
+Press Enter, then type:
+```bash
+git config --global user.email "youremail@school.edu"
+```
+
+**Example:**
+```bash
+git config --global user.name "Jane Smith"
+git config --global user.email "jsmith@school.edu"
+```
+
+**Check it worked:**
+```bash
+git config --list
+```
+
+Look for your name and email in the output!
+
+---
+
+### Step 3: Create Your Class Folder (1 minute)
+
+**Windows:**
+```bash
+cd Documents
+mkdir ClassWork
+cd ClassWork
+```
+
+**Mac:**
+```bash
+cd ~/Documents
+mkdir ClassWork
+cd ClassWork
+```
+
+**Chromebook:**
+```bash
+cd ~
+mkdir ClassWork
+cd ClassWork
+```
+
+---
+
+### Step 4: Clone the Class Repository (3 minutes)
+
+Your teacher will give you a URL. It looks like:
+- `https://github.com/teacher-name/geometry-period3`
+- `https://gitlab.com/teacher-name/physics-class`
+
+```bash
+git clone <PASTE-THE-URL-HERE>
+```
+
+**Example:**
+```bash
+git clone https://github.com/mrjones/geometry-period3
+```
+
+Press Enter and wait. You might see:
+```
+Cloning into 'geometry-period3'...
+remote: Counting objects: 100, done.
+...
+```
+
+**Success!** You'll see a message like:
+```
+Receiving objects: 100% (...), done.
+```
+
+---
+
+### Step 5: Enter Your Class Folder (1 minute)
+
+```bash
+cd <repository-name>
+```
+
+**Example:**
+```bash
+cd geometry-period3
+```
+
+**Check you're in the right place:**
+```bash
+ls
+```
+
+You should see folders like `students`, `class-resources`, etc.
+
+---
+
+### Step 6: Test Everything Works (2 minutes)
+
+```bash
+git status
+```
+
+You should see:
+```
+On branch main
+Your branch is up to date with 'origin/main'.
+
+nothing to commit, working tree clean
+```
+
+**If you see that - YOU'RE DONE!** 🎉
+
+---
+
+## Quick Troubleshooting
+
+### "git: command not found"
+- Git isn't installed. Go back to Step 1.
+
+### "Permission denied"
+- Check the URL your teacher gave you
+- Make sure you typed your email correctly in Step 2
+
+### "fatal: not a git repository"
+- You're not in the right folder
+- Use `cd` to go back to your class folder (Step 5)
+
+### "I don't know how to use Terminal/Git Bash"
+- Don't worry! Ask your teacher or a classmate
+- The commands are exactly as written - just copy and paste
+
+---
+
+## Daily Routine (Practice This!)
+
+Now that you're set up, here's what you'll do every class:
+
+```bash
+# 1. Go to your class folder
+cd ~/Documents/ClassWork/geometry-period3
+
+# 2. Get updates
+git pull origin main
+
+# 3. Do your work (take notes, practice, etc.)
+
+# 4. Save your work
+git add .
+git commit -m "Describe what you did today"
+git push origin main
+```
+
+**Let's practice right now:**
+
+1. Create a test file:
+```bash
+echo "Hello! I'm learning Git!" > test.txt
+```
+
+2. Check what changed:
+```bash
+git status
+```
+
+3. Add the file:
+```bash
+git add test.txt
+```
+
+4. Commit it:
+```bash
+git commit -m "My first commit - testing Git"
+```
+
+5. Push it:
+```bash
+git push origin main
+```
+
+**Did it work?** You should see:
+```
+Counting objects: 3, done.
+...
+To https://github.com/...
+   abc1234..def5678  main -> main
+```
+
+---
+
+## Your Checklist
+
+By the end of today, you should have:
+
+- [ ] Git installed on your computer
+- [ ] Your name and email configured
+- [ ] Class repository cloned
+- [ ] Successfully made a test commit
+- [ ] Successfully pushed to the cloud
+- [ ] Know where to find the STUDENT_GIT_GUIDE.md for help
+
+---
+
+## Getting Help
+
+**If you get stuck:**
+
+1. Try the command again (sometimes it just works the second time!)
+2. Ask the person next to you
+3. Raise your hand for the teacher
+4. Check STUDENT_GIT_GUIDE.md for more detailed help
+
+**Don't stress!** Everyone finds Git confusing at first. It gets easier fast!
+
+---
+
+## Tomorrow
+
+Tomorrow we'll start using Git with real classwork. Make sure:
+- You know where your class folder is
+- You remember the basic commands (or know where to find them)
+- You can open Terminal/Git Bash
+
+---
+
+## Cheat Sheet (Print This!)
+
+```
+┌─────────────────────────────────────────┐
+│          GIT CHEAT SHEET                │
+├─────────────────────────────────────────┤
+│ Go to class folder:                     │
+│   cd ~/Documents/ClassWork/class-name   │
+│                                         │
+│ Get updates:                            │
+│   git pull origin main                  │
+│                                         │
+│ Check what changed:                     │
+│   git status                            │
+│                                         │
+│ Save work:                              │
+│   git add .                             │
+│   git commit -m "what I did"            │
+│   git push origin main                  │
+│                                         │
+│ See history:                            │
+│   git log --oneline                     │
+│                                         │
+│ Help!:                                  │
+│   git status (shows where you are)      │
+│   Ask teacher!                          │
+└─────────────────────────────────────────┘
+```
+
+---
+
+**Congratulations!** You're now set up to track your learning journey with Git!
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/MASTERY_CHECK_GUIDE.md b/classroom/MASTERY_CHECK_GUIDE.md
new file mode 100644
index 0000000..2af851f
--- /dev/null
+++ b/classroom/MASTERY_CHECK_GUIDE.md
@@ -0,0 +1,561 @@
+# Mastery Check Submission Guide
+## Using Git for Assessment
+
+---
+
+## What is a Mastery Check?
+
+A mastery check is your opportunity to show you've mastered a unit's concepts. Using Git to submit:
+- Shows your teacher your work process (not just the final answer)
+- Creates a permanent record of your assessment
+- Allows for easy revision if needed
+- Builds your learning portfolio
+
+---
+
+## Mastery Levels Explained
+
+| Level | Score | Meaning | What's Next |
+|-------|-------|---------|-------------|
+| **Mastery** | 4 | You've got it! | Move to next unit |
+| **Proficient** | 3 | Solid understanding | Move on or revise for 4 |
+| **Developing** | 2 | Getting there | Revision required |
+| **Beginning** | 1 | Need more practice | Review & resubmit |
+
+---
+
+## Before the Mastery Check
+
+### Step 1: Signal You're Ready (2 minutes before deadline)
+
+When you've completed all practice and feel ready:
+
+```bash
+# Make sure all your prep work is saved
+git add .
+git commit -m "Unit 3 Prep Complete: Ready for mastery check"
+
+# Create a "ready" tag
+git tag -a mastery-unit3-ready -m "Ready for Unit 3 assessment"
+
+# Push everything
+git push origin main --tags
+```
+
+**What this does:**
+- Tells your teacher you're ready
+- Bookmarks your preparation work
+- Allows teacher to review your readiness
+
+### Step 2: Teacher Reviews (Teacher's Part)
+
+Your teacher will:
+- See that you've tagged as ready
+- Review your preparation work
+- Confirm you can take the mastery check
+- Give you the green light
+
+### Step 3: Get the Assessment
+
+Your teacher will provide:
+- The mastery check problems (paper or digital)
+- Time limit
+- Resources you can use
+- Any special instructions
+
+---
+
+## During the Mastery Check
+
+### Step 1: Create Your Assessment File (1 minute)
+
+```bash
+# In your unit folder, create the assessment file
+# Name format: UnitX-MasteryCheck.md
+
+# Example for Unit 3:
+cd students/your-name/Unit3
+touch Unit3-MasteryCheck.md
+```
+
+**Open the file in your editor and add:**
+```markdown
+# Unit 3 Mastery Check
+**Name:** Your Name
+**Date:** 2025-11-16
+**Time Started:** 1:30 PM
+
+---
+
+## Problem 1
+[Your work here]
+
+## Problem 2
+[Your work here]
+
+## Problem 3
+[Your work here]
+
+---
+```
+
+### Step 2: Save Your Progress (Every 10-15 minutes)
+
+**As you work, save periodically:**
+
+```bash
+git add Unit3-MasteryCheck.md
+git commit -m "Mastery Check Unit 3: Working on problems 1-3"
+git push origin main
+```
+
+**Why save during the check?**
+- Protects against computer crashes
+- Shows your teacher your thinking process
+- Proves when you did the work
+- Allows teacher to see if you're stuck
+
+### Step 3: Show Your Work
+
+**Use markdown formatting to show your thinking:**
+
+```markdown
+## Problem 1: Prove triangle ABC is congruent to triangle DEF
+
+**Given:**
+- AB = DE
+- BC = EF
+- ∠B = ∠E
+
+**Strategy:** I'll use SAS (Side-Angle-Side) theorem
+
+**Proof:**
+1. AB = DE (given)
+2. ∠B = ∠E (given)
+3. BC = EF (given)
+4. Therefore, △ABC ≅ △DEF by SAS
+
+**Reasoning:** Since two sides and the included angle are equal,
+the triangles must be congruent.
+```
+
+**For calculations (Physics):**
+```markdown
+## Problem 2: Calculate velocity
+
+**Given:**
+- Distance: 150 meters
+- Time: 30 seconds
+
+**Work:**
+v = d/t
+v = 150m / 30s
+v = 5 m/s
+
+**Answer:** 5 m/s
+
+**Check:** Does this make sense? 5 m/s = 18 km/h, which is
+about jogging speed. That seems reasonable for this scenario.
+```
+
+---
+
+## Submitting Your Mastery Check
+
+### Final Submission (When you're done)
+
+```bash
+# Make absolutely sure all your work is saved
+git add .
+
+# Commit with clear submission message
+git commit -m "Mastery Check Unit 3: COMPLETE - Ready for grading"
+
+# Create submission tag with today's date
+git tag -a mastery-unit3-submit-$(date +%Y%m%d) -m "Unit 3 Mastery Check Submission"
+
+# Push everything including tags
+git push origin main --tags
+
+# Verify it worked
+git status
+```
+
+**You should see:**
+```
+On branch main
+Your branch is up to date with 'origin/main'.
+
+nothing to commit, working tree clean
+```
+
+### Notify Your Teacher
+
+**After pushing:**
+1. Raise your hand or use class notification system
+2. Say: "I've submitted Unit 3 mastery check via Git"
+3. Your teacher will confirm they received it
+
+**Alternative notification (if your teacher uses this):**
+```bash
+# Add a submission file
+echo "SUBMITTED: $(date)" > Unit3-SUBMITTED.txt
+git add Unit3-SUBMITTED.txt
+git commit -m "SUBMISSION FLAG: Unit 3 complete"
+git push origin main
+```
+
+---
+
+## After Submission
+
+### Checking for Feedback (Next Day)
+
+```bash
+# Pull any updates from teacher
+git pull origin main
+
+# Look for feedback file
+ls Unit3-Feedback.md
+
+# If it exists, read it
+cat Unit3-Feedback.md
+```
+
+**Feedback file will look like:**
+```markdown
+# Unit 3 Mastery Check Feedback
+**Student:** Your Name
+**Score:** 3/4 (Proficient)
+**Date Graded:** 2025-11-17
+
+## Strengths
+✓ Problem 1: Perfect! Clear SAS proof
+✓ Problem 3: Excellent work showing all steps
+✓ Good use of diagrams
+
+## Growth Areas
+⚠ Problem 2: Small calculation error in step 3
+⚠ Problem 4: Missed one case in your proof
+
+## Next Steps
+- [ ] Review angle relationships (section 3.4)
+- [ ] Option to revise for Mastery (4) - see below
+- [ ] OR move to Unit 4 (Proficient is acceptable!)
+
+## Revision Opportunity
+If you want to improve to Mastery (4):
+- Fix problems 2 and 4
+- Submit revision by Friday
+- Use revision workflow
+```
+
+---
+
+## Revision Workflow (If Needed)
+
+### Step 1: Create Revision Branch
+
+```bash
+# Create a branch for your revision
+git checkout -b unit3-revision
+
+# Copy your original work
+cp Unit3-MasteryCheck.md Unit3-MasteryCheck-REVISED.md
+```
+
+### Step 2: Make Corrections
+
+**Open Unit3-MasteryCheck-REVISED.md and:**
+1. Read teacher feedback carefully
+2. Review the concepts mentioned
+3. Fix the specific problems noted
+4. Show what you learned
+
+**Add a revision section:**
+```markdown
+---
+# REVISION SECTION
+**Date:** 2025-11-18
+**Problems Revised:** 2 and 4
+
+## Problem 2 - REVISED
+**What I learned:** I made a calculation error in step 3.
+The correct calculation is...
+
+[Show corrected work]
+
+**Why I made the mistake:** I confused the formula for...
+**How I fixed it:** I reviewed section 3.2 and...
+
+## Problem 4 - REVISED
+[Corrected work with explanation]
+```
+
+### Step 3: Submit Revision
+
+```bash
+# Save your revision
+git add Unit3-MasteryCheck-REVISED.md
+git commit -m "Unit 3 Revision: Fixed problems 2 and 4"
+
+# Tag the revision
+git tag -a mastery-unit3-revision1 -m "Unit 3 Mastery Revision #1"
+
+# Push the revision branch
+git push origin unit3-revision --tags
+
+# Notify teacher
+```
+
+### Step 4: Teacher Regrades
+
+Your teacher will:
+- Review your revisions
+- Check that you understand your mistakes
+- Update your score
+- Provide final feedback
+
+**Possible outcomes:**
+- Score improves to 4 (Mastery) ✓
+- Score stays at 3 (you tried!)
+- Option for second revision (rare)
+
+---
+
+## Special Scenarios
+
+### Taking Mastery Check at Home
+
+**If allowed by teacher:**
+
+```bash
+# Same process, just make sure to:
+1. Start at the agreed-upon time
+2. Commit timestamps show honest timing
+3. Submit by deadline
+```
+
+**First commit should show:**
+```bash
+git commit -m "Mastery Check Unit 3: Started at 3:00 PM - Home"
+```
+
+### Extended Time Accommodation
+
+**If you have extended time:**
+
+```bash
+# Your teacher will give you extra time
+# Just note it in your file:
+
+# Unit 3 Mastery Check
+**Extended Time:** 1.5x (45 minutes instead of 30)
+**Time Started:** 1:30 PM
+**Time Ended:** 2:15 PM
+```
+
+### Technical Issues During Check
+
+**If Git/computer crashes:**
+
+1. **Don't panic!** Raise your hand immediately
+2. Teacher can see your last commit
+3. Worst case: You continue from last save
+4. This is why we commit every 10-15 minutes!
+
+**If you can't access computer:**
+```bash
+# Paper backup option
+# Complete on paper
+# Teacher will scan and add to your repo
+# OR you transcribe it afterward (within same day)
+```
+
+### Late Submission
+
+**If you miss the deadline:**
+
+```bash
+# Still submit via Git
+git commit -m "Mastery Check Unit 3: LATE SUBMISSION"
+git tag -a mastery-unit3-late -m "Late submission - see teacher"
+git push origin main --tags
+
+# Your teacher's late policy applies
+# But at least it's submitted with timestamp!
+```
+
+---
+
+## Viewing Your Mastery History
+
+### See All Your Mastery Checks
+
+```bash
+# List all mastery tags
+git tag -l "mastery-*"
+
+# Output:
+mastery-unit1-submit-20250901
+mastery-unit2-submit-20250915
+mastery-unit2-revision1
+mastery-unit3-ready
+mastery-unit3-submit-20251116
+```
+
+### Review a Past Mastery Check
+
+```bash
+# See the commit for a specific tag
+git show mastery-unit2-submit-20250915
+
+# See all commits during that mastery check
+git log --since="2025-09-15" --until="2025-09-15" --oneline
+```
+
+### Track Your Progress
+
+```bash
+# See all mastery checks in order
+git tag -l "mastery-*-submit*" | sort
+
+# Count how many units you've mastered
+git tag -l "mastery-*-submit*" | wc -l
+```
+
+---
+
+## Best Practices
+
+### Do:
+✓ Commit every 10-15 minutes during the check
+✓ Write clear, descriptive commit messages
+✓ Show ALL your work and thinking
+✓ Ask questions if Git breaks (not about the problems!)
+✓ Double-check your submission before notifying teacher
+
+### Don't:
+✗ Wait until the end to save everything
+✗ Copy from another student's repository
+✗ Edit your work after submission (it's timestamped!)
+✗ Delete your work if you think it's wrong (show your process!)
+✗ Stress if you make a Git mistake (teacher can fix it!)
+
+---
+
+## Academic Honesty with Git
+
+**Git creates a permanent record. This means:**
+
+**Good things:**
+- Your hard work is documented
+- Your growth is visible
+- You can prove you did your own work
+- Revision process is transparent
+
+**Things to avoid:**
+- Don't copy another student's repository
+- Don't edit commits after submission (teacher can see!)
+- Don't share your solutions during the assessment
+- Don't claim work you didn't do
+
+**Remember:** Git timestamps everything. Your teacher can see:
+- When you committed
+- What you changed
+- If work matches another student's exactly
+- If you edited after the deadline
+
+**Play fair!** Mastery grading gives you chances to revise honestly.
+
+---
+
+## Mastery Check Checklist
+
+### Before Assessment:
+- [ ] Completed all practice problems
+- [ ] Reviewed lesson notes
+- [ ] Tagged as "ready"
+- [ ] Teacher approved you to take check
+
+### During Assessment:
+- [ ] Created assessment file
+- [ ] Showing all work clearly
+- [ ] Committing every 10-15 minutes
+- [ ] Using proper formatting
+- [ ] Checking my work as I go
+
+### At Submission:
+- [ ] All work is complete
+- [ ] Final commit with "COMPLETE" message
+- [ ] Submission tag created
+- [ ] Pushed to origin with --tags
+- [ ] Verified with git status
+- [ ] Notified teacher
+
+### After Grading:
+- [ ] Pulled feedback from teacher
+- [ ] Read all feedback carefully
+- [ ] Decided: Move on OR revise for higher score
+- [ ] If revising: Created revision branch
+- [ ] Documented what I learned
+
+---
+
+## Sample Timeline
+
+**Unit 3 Mastery Check Example:**
+
+| Time | Action | Git Command |
+|------|--------|-------------|
+| Monday | Finish practice | `git commit -m "Unit 3 practice complete"` |
+| Monday | Tag ready | `git tag -a mastery-unit3-ready` |
+| Tuesday 1:30 | Start check | `git commit -m "Started Unit 3 check"` |
+| Tuesday 1:45 | Progress save | `git commit -m "Completed problems 1-2"` |
+| Tuesday 2:00 | Progress save | `git commit -m "Working on problem 4"` |
+| Tuesday 2:15 | Submit | `git tag -a mastery-unit3-submit-...` |
+| Wednesday | Receive feedback | `git pull origin main` |
+| Thursday | Revise (if needed) | `git commit -m "Revision: Fixed problem 2"` |
+| Friday | Final score | Teacher updates gradebook |
+
+---
+
+## FAQ
+
+**Q: What if I finish early?**
+A: Submit! Then you can work ahead or help peers (if allowed).
+
+**Q: Can I undo a submission?**
+A: No - but you can do a revision. Talk to your teacher.
+
+**Q: What if I forget the submission tag?**
+A: Your teacher can still see your work, but add the tag ASAP.
+
+**Q: Do spelling mistakes in commit messages matter?**
+A: Not for your grade, but try to be clear!
+
+**Q: Can I use the internet during the check?**
+A: Ask your teacher - it depends on what they allow.
+
+**Q: What if Git gives me an error?**
+A: Raise your hand immediately. Git errors don't count against you.
+
+**Q: How many times can I revise?**
+A: Ask your teacher - usually 1-2 times per mastery check.
+
+**Q: Does the time I commit matter?**
+A: Yes! Timestamps show you did work during the allowed time.
+
+---
+
+## Need Help?
+
+**During setup/submission:** Use this guide or STUDENT_GIT_GUIDE.md
+**During the actual problems:** Ask your teacher (not about Git, about content!)
+**Technical issues:** Raise your hand immediately
+
+---
+
+**Good luck on your mastery checks! Show what you've learned!**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/PEER_COLLABORATION_GUIDE.md b/classroom/PEER_COLLABORATION_GUIDE.md
new file mode 100644
index 0000000..475189e
--- /dev/null
+++ b/classroom/PEER_COLLABORATION_GUIDE.md
@@ -0,0 +1,782 @@
+# Peer Collaboration Guide
+## Working Together Using Git
+
+---
+
+## Why Collaborate with Git?
+
+When you help a classmate or work on a group project:
+- Your teacher can see who contributed what
+- You get extra credit for helping others
+- Your explanations show your mastery
+- Work is saved and shared safely
+- No more "who did what?" confusion
+
+**Teacher's Perspective:** Git lets them see:
+- How advanced students practice mastery by teaching
+- Quality of peer explanations
+- Group dynamics in projects
+- Individual contributions
+
+---
+
+## Types of Collaboration
+
+### 1. Peer Teaching (Advanced Student Helps Struggling Student)
+**Scenario:** You've mastered Unit 3, and a classmate is struggling with triangle proofs.
+
+### 2. Study Groups (Students at Same Pace)
+**Scenario:** Three students working together on practice problems for Lesson 4.2.
+
+### 3. Group Projects (Team Assignment)
+**Scenario:** Lab group collecting and analyzing data together in Physics.
+
+### 4. Peer Review (Checking Each Other's Work)
+**Scenario:** Two students reviewing each other's notes before a mastery check.
+
+---
+
+## 1. Peer Teaching Workflow
+
+### When You're the Helper (Advanced Student)
+
+**Step 1: Create a Teaching Branch**
+
+```bash
+# Format: helping-[student-name]-[topic]
+git checkout -b helping-sarah-unit3
+
+# Verify you're on the new branch
+git branch
+```
+
+**Step 2: Create Teaching Materials**
+
+Create a file to help your peer:
+```bash
+# In your folder, create a teaching file
+touch Peer-Teaching-Unit3-Triangles.md
+```
+
+**Example content:**
+```markdown
+# Helping Sarah with Unit 3: Triangle Congruence
+**Teacher:** Your Name
+**Student:** Sarah
+**Date:** 2025-11-16
+**Topic:** Triangle congruence proofs
+
+---
+
+## What Sarah Was Struggling With
+Sarah was confused about when to use SSS vs SAS vs ASA.
+
+## My Explanation
+[Your teaching here - use simple language, examples, diagrams]
+
+### SSS (Side-Side-Side)
+When all three sides of one triangle equal all three sides of another:
+- Think: "Same size sticks = same triangle"
+- Example: ...
+
+### SAS (Side-Angle-Side)
+When two sides and the INCLUDED angle are equal:
+- Think: "Two sticks with the angle between them"
+- Example: ...
+
+## Practice Problems We Did Together
+1. [Problem you made up for Sarah]
+2. [How Sarah solved it]
+3. [Where she got stuck and how we fixed it]
+
+## What Sarah Learned
+- Now understands the difference between theorems
+- Can identify which theorem to use
+- Feeling more confident!
+
+---
+**Time spent:** 20 minutes
+**Sarah's confidence before:** 3/10
+**Sarah's confidence after:** 7/10
+```
+
+**Step 3: Commit Your Teaching**
+
+```bash
+git add Peer-Teaching-Unit3-Triangles.md
+git commit -m "Peer teaching: Helped Sarah with triangle congruence"
+git push origin helping-sarah-unit3
+```
+
+**Step 4: Tag for Extra Credit**
+
+```bash
+git tag -a peer-teaching-$(date +%Y%m%d)-sarah -m "Peer teaching session with Sarah"
+git push origin --tags
+```
+
+**Step 5: Return to Your Work**
+
+```bash
+git checkout main
+git pull origin main
+```
+
+### When You're Being Helped (Student Receiving Help)
+
+**Step 1: Note the Help Session in Your Work**
+
+```bash
+# In your Unit 3 folder
+echo "# Peer Help Session
+**Date:** 2025-11-16
+**Helper:** [Name]
+**Topic:** Triangle congruence
+**What I learned:** [Your notes from the session]
+" > Unit3-Peer-Help-Notes.md
+```
+
+**Step 2: Save It**
+
+```bash
+git add Unit3-Peer-Help-Notes.md
+git commit -m "Unit 3: Got help from [Name] on triangle proofs"
+git push origin main
+```
+
+**This shows your teacher:**
+- You sought help (good!)
+- Who helped you
+- What you learned
+- Your progress after help
+
+---
+
+## 2. Study Group Workflow
+
+**Scenario:** You and two classmates are all working on Lesson 4.2 together.
+
+### Step 1: Decide on a Collaboration Model
+
+**Option A: Everyone Stays on Their Own Branch**
+- Each person works in their own repo
+- Share ideas verbally
+- Each commits their own notes
+
+**Option B: Create a Shared Study Group Branch**
+- One person creates a study group file
+- Everyone contributes to it
+- Better for group problem-solving
+
+### Option B Process:
+
+**Organizer creates the group file:**
+```bash
+git checkout -b study-group-lesson4.2
+
+# Create shared file
+touch Study-Group-Lesson4.2.md
+
+# Initial content
+echo "# Lesson 4.2 Study Group
+**Date:** 2025-11-16
+**Members:** Alex, Jordan, Sam
+
+---
+
+## Problems We're Working On
+1. [Problem description]
+
+## Alex's Approach:
+[Alex's solution method]
+
+## Jordan's Approach:
+[Jordan's solution method]
+
+## Sam's Approach:
+[Sam's solution method]
+
+## What We Figured Out Together:
+[Group conclusions]
+" > Study-Group-Lesson4.2.md
+
+git add Study-Group-Lesson4.2.md
+git commit -m "Study group: Started Lesson 4.2 collaboration"
+git push origin study-group-lesson4.2
+```
+
+**Each member adds their contributions:**
+
+Each person takes turns:
+```bash
+# Pull latest version
+git pull origin study-group-lesson4.2
+
+# Add your part
+# Edit Study-Group-Lesson4.2.md
+
+# Commit YOUR contribution
+git add Study-Group-Lesson4.2.md
+git commit -m "Study group: Added my solution to problem 3 - Jordan"
+git push origin study-group-lesson4.2
+```
+
+**Important:** Take turns! Don't all edit at once (causes conflicts).
+
+### Step 3: Move Learning Back to Individual Repos
+
+After the study session:
+```bash
+# Copy what you learned to YOUR notes
+cp Study-Group-Lesson4.2.md ~/Unit4/Lesson4.2-Group-Notes.md
+
+# Go back to your main work
+git checkout main
+
+# Add the notes to YOUR repo
+git add Unit4/Lesson4.2-Group-Notes.md
+git commit -m "Lesson 4.2: Notes from study group session"
+git push origin main
+```
+
+**Now:**
+- Study group work is documented
+- Your individual learning is tracked
+- Teacher sees collaboration AND individual understanding
+
+---
+
+## 3. Group Project Workflow (Physics Lab Example)
+
+**Scenario:** Four students doing a velocity lab together.
+
+### Step 1: Create Project Branch
+
+**Team leader:**
+```bash
+git checkout -b physics-lab-velocity-team1
+
+# Create project structure
+mkdir Physics-Lab-Velocity
+cd Physics-Lab-Velocity
+
+# Create files for different parts
+touch Lab-Setup.md
+touch Data-Collection.md
+touch Data-Analysis.md
+touch Conclusions.md
+touch Team-Roles.md
+
+git add .
+git commit -m "Lab setup: Created velocity lab structure"
+git push origin physics-lab-velocity-team1
+```
+
+### Step 2: Assign Roles (Document This!)
+
+**Team-Roles.md:**
+```markdown
+# Velocity Lab Team 1 Roles
+
+**Team Members:** Alex, Jordan, Sam, Taylor
+
+## Role Assignments
+- **Data Collection:** Alex, Sam
+- **Calculations:** Jordan
+- **Analysis:** Taylor
+- **Write-Up:** All (Alex leads)
+
+## Contribution Tracking
+Each member will commit their own work with their name in the commit message.
+```
+
+```bash
+git add Team-Roles.md
+git commit -m "Lab: Assigned team roles - Alex"
+git push origin physics-lab-velocity-team1
+```
+
+### Step 3: Work and Commit Individually
+
+**Alex (collecting data):**
+```bash
+git pull origin physics-lab-velocity-team1
+
+# Edit Data-Collection.md with trial data
+git add Data-Collection.md
+git commit -m "Lab: Added trials 1-3 velocity data - Alex"
+git push origin physics-lab-velocity-team1
+```
+
+**Jordan (doing calculations):**
+```bash
+git pull origin physics-lab-velocity-team1
+
+# Edit Data-Analysis.md with calculations
+git add Data-Analysis.md
+git commit -m "Lab: Calculated average velocities - Jordan"
+git push origin physics-lab-velocity-team1
+```
+
+**Taylor (analyzing results):**
+```bash
+git pull origin physics-lab-velocity-team1
+
+# Edit Conclusions.md
+git add Conclusions.md
+git commit -m "Lab: Wrote conclusions section - Taylor"
+git push origin physics-lab-velocity-team1
+```
+
+### Step 4: Final Submission
+
+**Team leader:**
+```bash
+# Make sure everyone's work is pulled
+git pull origin physics-lab-velocity-team1
+
+# Create final submission tag
+git tag -a lab-velocity-team1-final -m "Velocity Lab Final Submission - Team 1"
+git push origin physics-lab-velocity-team1 --tags
+
+# Merge to main if teacher requires
+git checkout main
+git merge physics-lab-velocity-team1
+git push origin main
+```
+
+### Step 5: Individual Reflection
+
+Each team member adds reflection to THEIR main branch:
+
+```bash
+git checkout main
+
+# Create reflection file
+echo "# Velocity Lab Reflection
+**My Role:** Data collection
+**What I contributed:** Collected all trial data, helped with setup
+**What I learned:** How to use motion sensors, calculate velocity
+**Team collaboration:** Great! Everyone did their part.
+**What I'd do differently:** Start earlier, check calculations more carefully
+" > Physics-Lab-Velocity-Reflection.md
+
+git add Physics-Lab-Velocity-Reflection.md
+git commit -m "Reflection: Velocity lab experience"
+git push origin main
+```
+
+**Teacher can now see:**
+- Group's combined work (the lab branch)
+- Individual contributions (commit messages with names)
+- Individual reflections (in each student's main branch)
+- Who did what and when
+
+---
+
+## 4. Peer Review Workflow
+
+**Scenario:** Two students reviewing each other's notes before mastery check.
+
+### Step 1: Create Review Branch
+
+```bash
+git checkout -b peer-review-unit3-with-jordan
+```
+
+### Step 2: Review Partner's Work
+
+**Option A: Partner gives you access to their repo**
+```bash
+# Clone or pull partner's work (if allowed)
+git clone <partner-repo-url> partner-review
+
+cd partner-review
+# Review their Unit 3 notes
+```
+
+**Option B: Partner copies their notes to your repo**
+```bash
+# Your partner sends you their notes file
+# You add it to your review branch
+
+git add Jordan-Unit3-Notes.md
+git commit -m "Peer review: Added Jordan's notes for review"
+```
+
+### Step 3: Provide Feedback
+
+Create a review file:
+```markdown
+# Peer Review: Jordan's Unit 3 Notes
+**Reviewer:** Your Name
+**Date:** 2025-11-16
+
+## Strengths
+- ✓ Clear explanations of SSS theorem
+- ✓ Good diagrams
+- ✓ Organized by lesson
+
+## Suggestions
+- ⚠ Section on ASA could use more examples
+- ⚠ Missing notes from Lesson 3.4
+- 💡 Try adding color-coding for different theorems
+
+## Questions to Discuss
+1. Do you understand the difference between ASA and AAS?
+2. Want to practice some proofs together?
+
+## Overall
+Good prep! You'll do great on the mastery check!
+```
+
+```bash
+git add Peer-Review-Jordan.md
+git commit -m "Peer review: Feedback for Jordan on Unit 3 notes"
+git push origin peer-review-unit3-with-jordan
+```
+
+### Step 4: Receive Feedback on Your Own Notes
+
+When Jordan reviews YOUR notes:
+```bash
+git pull origin main
+# Check for Jordan's review of your work
+cat Jordan-Review-Of-My-Notes.md
+```
+
+### Step 5: Improve Based on Feedback
+
+```bash
+# Go back to main
+git checkout main
+
+# Update your notes based on feedback
+git add Unit3-Notes.md
+git commit -m "Updated Unit 3 notes based on peer review from Jordan"
+git push origin main
+```
+
+---
+
+## Collaboration Best Practices
+
+### Do's:
+✓ **Always commit with your name:** "Helped Sarah with... - Alex"
+✓ **Take turns editing:** Avoids conflicts
+✓ **Pull before you push:** Get latest changes first
+✓ **Document who did what:** Clear role assignments
+✓ **Give credit:** "Thanks to Jordan for explaining..."
+✓ **Be respectful:** Kind feedback, no put-downs
+✓ **Communicate:** "I'm about to push changes"
+
+### Don'ts:
+✗ Do someone else's mastery check for them
+✗ Copy-paste solutions without understanding
+✗ Edit someone else's personal notes without permission
+✗ Take credit for others' work
+✗ Share mastery check answers during assessment
+✗ Force push (overwrites others' work)
+
+---
+
+## Handling Merge Conflicts
+
+**What's a conflict?**
+When two people edit the same part of a file at the same time.
+
+**Example:**
+Alex and Jordan both edit line 5 of the lab report.
+
+**How to fix:**
+
+```bash
+# When you pull and get a conflict:
+git pull origin project-branch
+
+# You'll see:
+CONFLICT (content): Merge conflict in Lab-Report.md
+Automatic merge failed; fix conflicts and then commit the result.
+
+# Open the file, you'll see:
+<<<<<<< HEAD
+Alex's version of the text
+=======
+Jordan's version of the text
+>>>>>>> origin/project-branch
+
+# Decide what to keep (or combine both)
+# Delete the conflict markers (<<<, ===, >>>)
+# Save the file
+
+# Then:
+git add Lab-Report.md
+git commit -m "Fixed merge conflict - kept both contributions"
+git push origin project-branch
+```
+
+**Pro tip:** Talk to your partner to decide together!
+
+---
+
+## Extra Credit Opportunities
+
+### Document Your Teaching
+Every time you help a peer:
+```bash
+git tag -a peer-teaching-YYYYMMDD -m "Description"
+```
+
+**Teacher can:**
+- Count teaching sessions
+- Review quality of explanations
+- Award extra credit based on helping others
+
+### Study Group Leadership
+Organize and document study groups:
+```bash
+# Create recurring study groups
+git checkout -b study-group-unit4
+# Document multiple sessions
+git commit -m "Study group session 3: Unit 4"
+```
+
+**Teacher sees:**
+- Leadership initiative
+- Consistent collaboration
+- Helping multiple students
+
+### Quality of Collaboration
+It's not just about helping - it's about HOW you help:
+
+**Good peer teaching (full credit):**
+```markdown
+## My Explanation
+[Clear, simple explanation in your own words]
+[Examples you created]
+[Checking if they understand]
+```
+
+**Bad peer teaching (little credit):**
+```markdown
+## My Explanation
+Just read the textbook page 45.
+```
+
+---
+
+## Privacy and Ethics
+
+### What to Share
+**OK to share:**
+- Practice problem approaches
+- Note-taking strategies
+- Study techniques
+- Explanations of concepts
+- Your own understanding
+
+**NOT OK to share:**
+- Mastery check answers during assessment
+- Direct answers without explanation
+- Copy of your notes for them to submit as theirs
+
+### Giving Appropriate Help
+
+**During practice:** Help freely!
+**Before mastery check:** Review together, explain concepts
+**During mastery check:** Hands off! They need to show their own mastery
+
+---
+
+## Collaboration Examples
+
+### Example 1: Successful Peer Teaching
+
+**Branch:** `helping-taylor-geometry`
+**Commits:**
+```
+commit abc1234
+Peer teaching: Created triangle proof examples for Taylor
+20 minutes ago
+
+commit def5678
+Peer teaching: Worked through 3 practice problems with Taylor
+10 minutes ago
+
+commit ghi9012
+Peer teaching: Taylor now understands SSS vs SAS - Success!
+5 minutes ago
+```
+
+**Result:** Teacher sees quality teaching, awards extra credit
+
+### Example 2: Good Study Group
+
+**Branch:** `study-group-physics-unit2`
+**Commits:**
+```
+commit abc1234
+Study group: Meeting 1 - discussed Newton's laws - Alex, Jordan, Sam
+1 week ago
+
+commit def5678
+Study group: Meeting 2 - practice problems - Alex
+1 week ago
+
+commit ghi9012
+Study group: Added my solutions to problems 5-7 - Jordan
+1 week ago
+
+commit jkl3456
+Study group: Summary of what we learned - Sam
+1 week ago
+```
+
+**Result:** Teacher sees collaborative learning, everyone benefits
+
+### Example 3: Excellent Group Project
+
+**Branch:** `physics-lab-momentum-team2`
+**Commits:**
+```
+commit abc1234
+Lab setup: Created experiment structure - Sam (team leader)
+2 days ago
+
+commit def5678
+Lab: Collected trial data 1-5 - Alex
+2 days ago
+
+commit ghi9012
+Lab: Data analysis and calculations - Jordan
+1 day ago
+
+commit jkl3456
+Lab: Graphed results - Taylor
+1 day ago
+
+commit mno7890
+Lab: Wrote conclusions - Sam
+1 day ago
+
+commit pqr1234
+Lab: Final review and submission - Team
+1 day ago
+```
+
+**Result:** Teacher sees equal contribution, clear roles, quality work
+
+---
+
+## Troubleshooting
+
+### "I can't push - it says rejected"
+
+```bash
+# Someone else pushed first
+# Solution: Pull their changes first
+git pull origin branch-name
+
+# If there are conflicts, resolve them (see above)
+# Then try pushing again
+git push origin branch-name
+```
+
+### "My partner's changes disappeared"
+
+```bash
+# They probably forgot to push
+# Ask them to push their commits
+# Then you can pull them
+git pull origin branch-name
+```
+
+### "We both edited the same thing"
+
+```bash
+# Merge conflict (see conflict section above)
+# Talk to your partner
+# Decide together what to keep
+```
+
+### "I don't know which branch I'm on"
+
+```bash
+# Check current branch
+git branch
+
+# The one with * is your current branch
+# Switch if needed:
+git checkout branch-name
+```
+
+---
+
+## Collaboration Checklist
+
+### Starting Collaboration:
+- [ ] Created appropriate branch
+- [ ] Documented who's collaborating
+- [ ] Assigned roles (if group project)
+- [ ] Everyone knows what to do
+
+### During Collaboration:
+- [ ] Pulling before editing
+- [ ] Committing with clear messages
+- [ ] Including your name in commits
+- [ ] Communicating with team
+- [ ] Taking turns (avoiding conflicts)
+
+### Ending Collaboration:
+- [ ] All work committed and pushed
+- [ ] Created submission tag (if needed)
+- [ ] Merged to main (if teacher requires)
+- [ ] Individual reflections completed
+- [ ] Extra credit tagged appropriately
+
+---
+
+## FAQ
+
+**Q: Can I work with anyone, anytime?**
+A: Ask your teacher - they might have guidelines about when collaboration is appropriate.
+
+**Q: Does collaboration hurt my grade?**
+A: No! It can help (extra credit) if done properly.
+
+**Q: What if my partner doesn't pull their weight?**
+A: Git shows exactly who did what. Talk to your teacher.
+
+**Q: Can I collaborate on mastery checks?**
+A: NO! Those must be individual to show YOUR mastery.
+
+**Q: What if we have a merge conflict?**
+A: Talk to your partner and resolve it together, or ask teacher for help.
+
+**Q: How many times can I help peers for extra credit?**
+A: Ask your teacher - usually unlimited (within reason)!
+
+**Q: Can I collaborate with students in other class periods?**
+A: Ask your teacher about cross-period collaboration.
+
+---
+
+## Remember
+
+**Collaboration is about:**
+- Learning together
+- Teaching each other
+- Supporting classmates
+- Building understanding
+
+**Collaboration is NOT about:**
+- Copying work
+- Avoiding effort
+- Cheating on assessments
+- Taking credit for others' work
+
+**Git makes collaboration visible, fair, and rewarding!**
+
+---
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/README.md b/classroom/README.md
new file mode 100644
index 0000000..84048e2
--- /dev/null
+++ b/classroom/README.md
@@ -0,0 +1,490 @@
+# Git for High School Classroom
+## Complete Guide for Self-Paced, Mastery-Based Learning
+
+---
+
+## Overview
+
+This collection of guides integrates Git version control into a **blended, self-paced classroom** using **mastery grading** for Geometry and Physics courses.
+
+**Created:** 2025-11-16
+**Subject Areas:** Geometry, Physics (adaptable to other subjects)
+**Grade Level:** High School
+**Classroom Model:** Self-paced, mastery-based with peer collaboration
+
+---
+
+## What's Included
+
+### For Students
+
+| Guide | Purpose | When to Use |
+|-------|---------|-------------|
+| **[DAY1_STUDENT_SETUP.md](DAY1_STUDENT_SETUP.md)** | Initial Git installation and setup | First day of class |
+| **[STUDENT_GIT_GUIDE.md](STUDENT_GIT_GUIDE.md)** | Complete student reference guide | Daily reference, ongoing |
+| **[MASTERY_CHECK_GUIDE.md](MASTERY_CHECK_GUIDE.md)** | How to submit assessments via Git | Before each mastery check |
+| **[PEER_COLLABORATION_GUIDE.md](PEER_COLLABORATION_GUIDE.md)** | Working together using Git | During study groups, peer teaching |
+
+### For Teachers
+
+| Guide | Purpose | When to Use |
+|-------|---------|-------------|
+| **[TEACHER_WORKFLOW.md](TEACHER_WORKFLOW.md)** | Complete classroom integration guide | Setup and daily management |
+
+### Additional Resources
+
+| Resource | Purpose |
+|----------|---------|
+| **[GIT_GUIDE.md](../GIT_GUIDE.md)** | Comprehensive Git reference (all users) |
+
+---
+
+## Quick Start
+
+### For Teachers (Setting Up)
+
+**Week Before School Starts:**
+1. Read [TEACHER_WORKFLOW.md](TEACHER_WORKFLOW.md)
+2. Create GitHub/GitLab account for your class
+3. Set up class repository structure
+4. Prepare Day 1 materials
+
+**First Week of School:**
+- **Day 1:** Introduce Git concept, students install (use [DAY1_STUDENT_SETUP.md](DAY1_STUDENT_SETUP.md))
+- **Day 2-3:** Practice daily workflow
+- **Day 4:** First real assignment using Git
+- **Day 5:** Troubleshooting and Q&A
+
+### For Students (Getting Started)
+
+**First Time:**
+1. Follow [DAY1_STUDENT_SETUP.md](DAY1_STUDENT_SETUP.md) to install and configure Git
+2. Clone your class repository
+3. Practice with a test commit
+
+**Every Day:**
+1. `git pull origin main` (get updates)
+2. Do your work
+3. `git add .` (mark changes)
+4. `git commit -m "what I did"` (save)
+5. `git push origin main` (backup)
+
+**When Needed:**
+- **Submitting mastery checks:** See [MASTERY_CHECK_GUIDE.md](MASTERY_CHECK_GUIDE.md)
+- **Working with peers:** See [PEER_COLLABORATION_GUIDE.md](PEER_COLLABORATION_GUIDE.md)
+- **Detailed reference:** See [STUDENT_GIT_GUIDE.md](STUDENT_GIT_GUIDE.md)
+
+---
+
+## Why Git in the Classroom?
+
+### Benefits for Students
+- ✅ Never lose work (everything backed up)
+- ✅ See their own progress over time
+- ✅ Learn real-world professional skills
+- ✅ Build a portfolio automatically
+- ✅ Safe collaboration environment
+- ✅ Develop metacognition through commit messages
+
+### Benefits for Teachers
+- ✅ Track student effort and process (not just products)
+- ✅ See who's working, who's stuck, in real-time
+- ✅ Monitor individual contributions in group work
+- ✅ Provide timestamped feedback
+- ✅ Catch academic dishonesty more easily
+- ✅ Generate progress reports automatically
+- ✅ Support differentiation (advanced students, struggling students)
+
+### Real-World Skills
+- **Version control** - Used by all professional developers
+- **Documentation** - Writing clear commit messages
+- **Collaboration** - Working on teams safely
+- **Problem-solving** - Recovering from mistakes
+- **Digital literacy** - Command line basics
+
+---
+
+## Classroom Models Supported
+
+### Self-Paced Learning
+- Students work at individual paces
+- Git tracks where each student is
+- Teachers can see who's ahead, who needs support
+- Advanced students can work on next units (on branches)
+
+### Mastery Grading
+- Clear submission process via tags
+- Revision workflow built-in
+- Teachers can see growth over time
+- Students can demonstrate mastery through process
+
+### Blended Learning
+- Works at school or at home (always synced)
+- Supports async work
+- Flipped classroom compatible
+- Hybrid learning ready
+
+### Peer Teaching
+- Advanced students help struggling students
+- Collaboration documented for extra credit
+- Quality of teaching visible to teacher
+- Builds student leadership
+
+---
+
+## Document Guide
+
+### Student Path
+
+```
+Start Here
+    ↓
+DAY1_STUDENT_SETUP.md
+    ↓
+STUDENT_GIT_GUIDE.md (keep for reference)
+    ↓
+Daily work → Mastery check coming up → MASTERY_CHECK_GUIDE.md
+    ↓                                         ↓
+    ↓                                    Submit & get feedback
+    ↓                                         ↓
+Working with peers ← ← ← ← ← ← ← ← ← ← ← ← ←
+    ↓
+PEER_COLLABORATION_GUIDE.md
+    ↓
+Return to daily work
+```
+
+### Teacher Path
+
+```
+TEACHER_WORKFLOW.md (comprehensive guide)
+    ↓
+Set up class repository
+    ↓
+Introduce students to Git (use student guides)
+    ↓
+Daily: Monitor commits, grade mastery checks
+    ↓
+Weekly: Review progress, provide feedback
+    ↓
+Monthly: Generate reports, student conferences
+    ↓
+End of semester: Student portfolios
+```
+
+---
+
+## Implementation Timeline
+
+### Phase 1: Introduction (Week 1)
+- Install Git on all devices
+- Set up class repository
+- Practice basic workflow
+- Troubleshoot technical issues
+
+**Success metrics:**
+- [ ] All students can commit and push
+- [ ] Students understand daily routine
+- [ ] Teacher can view student work
+
+### Phase 2: Daily Integration (Weeks 2-4)
+- Students use Git for all classwork
+- Establish daily routines
+- Build muscle memory for commands
+- Handle simple errors independently
+
+**Success metrics:**
+- [ ] 90%+ of students commit daily
+- [ ] Commit messages are descriptive
+- [ ] Students sync work between school/home
+- [ ] Teacher reviews commits regularly
+
+### Phase 3: Mastery Checks (Weeks 4-8)
+- First mastery check via Git
+- Practice submission workflow
+- Implement revision process
+- Use tags for tracking
+
+**Success metrics:**
+- [ ] All mastery checks submitted via Git
+- [ ] Submission tags created properly
+- [ ] Feedback delivered through Git
+- [ ] Revision workflow functioning
+
+### Phase 4: Collaboration (Weeks 8-12)
+- Introduce peer teaching branches
+- Set up study groups
+- Start group projects
+- Implement extra credit system
+
+**Success metrics:**
+- [ ] Peer teaching documented in Git
+- [ ] Group projects tracked by contribution
+- [ ] Students helping each other
+- [ ] Extra credit awarded based on Git logs
+
+### Phase 5: Full Integration (Semester 2)
+- Students automatic with Git
+- Complex collaboration workflows
+- Portfolio building
+- Student-led troubleshooting
+
+**Success metrics:**
+- [ ] Git is invisible (just how work gets done)
+- [ ] Students teach each other Git
+- [ ] Rich portfolios developing
+- [ ] Parent/admin engagement via portfolios
+
+---
+
+## Customization Tips
+
+### Adapting to Other Subjects
+
+**English/History:**
+- Essays in markdown
+- Research notes
+- Annotation of texts
+- Revision tracking for writing process
+
+**Math:**
+- Problem-solving work
+- Show all steps
+- Practice problems
+- Formula sheets
+
+**Science (any):**
+- Lab reports
+- Data collection
+- Analysis and conclusions
+- Experiment procedures
+
+**Arts:**
+- Project documentation
+- Sketches (images)
+- Process journals
+- Critiques and reflections
+
+### Different Grade Levels
+
+**Middle School:**
+- Simplify vocabulary
+- More visual guides
+- Pair students for support
+- Use GUI tools (GitHub Desktop)
+
+**College:**
+- More advanced Git features
+- Industry-standard workflows
+- Integration with coding projects
+- Professional portfolio building
+
+---
+
+## Technical Requirements
+
+### Minimum Requirements
+- Computer with Git installed
+- Internet access (for push/pull)
+- Text editor (VS Code, Atom, or built-in)
+- GitHub/GitLab account
+
+### Recommended Setup
+- **GitHub Desktop** or **GitKraken** (GUI for visualization)
+- **VS Code** (good Git integration, markdown preview)
+- **GitHub Education** (free private repos, Student Developer Pack)
+- Backup system (regular repository backups)
+
+### Platform Support
+- **Windows:** Full support (Git Bash)
+- **Mac:** Native support (Terminal)
+- **Linux:** Native support
+- **Chromebook:** Limited support (use web-based options or Linux mode)
+
+---
+
+## Support and Resources
+
+### Getting Help
+
+**For Students:**
+1. Check the relevant guide (see links above)
+2. Ask a classmate
+3. Ask your teacher
+4. Search error message online
+5. Check main [GIT_GUIDE.md](../GIT_GUIDE.md)
+
+**For Teachers:**
+1. Check [TEACHER_WORKFLOW.md](TEACHER_WORKFLOW.md)
+2. GitHub Education Support
+3. Git documentation
+4. Online teacher communities
+
+### External Resources
+
+- **GitHub Education:** https://education.github.com/
+- **GitLab for Education:** https://about.gitlab.com/solutions/education/
+- **Git Documentation:** https://git-scm.com/doc
+- **Learn Git Branching:** https://learngitbranching.js.org/ (interactive tutorial)
+- **GitHub Classroom:** https://classroom.github.com/ (automated student setup)
+
+---
+
+## Common Questions
+
+### For Teachers
+
+**Q: How much time does this add to my workflow?**
+A: Initial setup: 2-3 hours. Daily: 5-10 minutes. Weekly grading: Actually saves time!
+
+**Q: What if I'm not technical?**
+A: Start simple! Use the basic workflow first. The guides are designed for beginners.
+
+**Q: What about students without home computers?**
+A: Work can be done entirely at school. Git keeps everything in sync.
+
+**Q: How do I grade using Git?**
+A: Review commits, check tags for submissions. See TEACHER_WORKFLOW.md for rubrics.
+
+**Q: What about privacy/FERPA?**
+A: Use private repositories. GitHub/GitLab support educational privacy requirements.
+
+### For Students
+
+**Q: What if I mess up?**
+A: Almost everything can be undone! See the guides for recovery procedures.
+
+**Q: Do I need to be a coder?**
+A: No! You're just saving files and writing notes.
+
+**Q: What if I can't install Git?**
+A: Ask your teacher about web-based options or school computers.
+
+**Q: Will this help me in the future?**
+A: YES! Version control is used in almost every technical field.
+
+---
+
+## Assessment Integration
+
+### What to Grade
+
+**Process (40%):**
+- Commit frequency (consistent effort)
+- Commit message quality (metacognition)
+- Revision patterns (growth mindset)
+- Collaboration (peer teaching)
+
+**Product (60%):**
+- Mastery check scores (content knowledge)
+- Project quality (application)
+- Lab reports (scientific method)
+- Participation (engagement)
+
+### How Git Helps Grading
+
+**Evidence of effort:**
+```bash
+# See how many commits in the last week
+git log student-name/main --since="1 week ago" --oneline | wc -l
+```
+
+**Quality of work:**
+```bash
+# Review their actual work
+git show student-name/main:Unit3/notes.md
+```
+
+**Collaboration:**
+```bash
+# See peer teaching
+git log --all --grep="peer teaching"
+```
+
+**Growth over time:**
+```bash
+# Compare early vs. late work
+git diff commit-from-sept commit-from-dec
+```
+
+---
+
+## Success Stories (Anticipated)
+
+Based on this workflow, expect to see:
+
+- **Student A (struggling):** Went from irregular work to daily commits, sought peer help (documented), revised mastery checks to proficiency
+- **Student B (advanced):** Worked ahead on branches, taught 5 peers (extra credit), built impressive portfolio
+- **Student C (absent):** Caught up easily after illness by reviewing Git history, stayed on track
+- **Student D (group project):** Clear individual contribution visible, despite quiet personality
+
+---
+
+## Future Enhancements
+
+Possible additions as you get comfortable:
+
+- **Automated reporting scripts**
+- **GitHub Pages for student portfolios**
+- **Integration with learning management system**
+- **Parental access to student repos**
+- **Cross-class collaboration**
+- **Summer learning continuity**
+
+---
+
+## License and Sharing
+
+These materials are designed for educational use. Feel free to:
+- ✅ Use in your classroom
+- ✅ Adapt to your subject/grade level
+- ✅ Share with other teachers
+- ✅ Modify for your needs
+
+Please:
+- Keep educational and free
+- Share improvements back
+- Give credit where due
+
+---
+
+## Feedback and Contributions
+
+This is a living document! As you use these guides:
+- Note what works and what doesn't
+- Adapt to your classroom needs
+- Share improvements
+- Build a community of practice
+
+---
+
+## File Index
+
+```
+classroom/
+├── README.md (this file)
+├── DAY1_STUDENT_SETUP.md
+├── STUDENT_GIT_GUIDE.md
+├── MASTERY_CHECK_GUIDE.md
+├── PEER_COLLABORATION_GUIDE.md
+└── TEACHER_WORKFLOW.md
+
+parent directory:
+└── GIT_GUIDE.md (comprehensive reference)
+```
+
+---
+
+## Version History
+
+- **v1.0** (2025-11-16): Initial creation
+  - All guides completed
+  - Ready for classroom pilot
+
+---
+
+**Ready to transform your classroom with Git? Start with [TEACHER_WORKFLOW.md](TEACHER_WORKFLOW.md) for setup!**
+
+**Questions? Review the guides or reach out to your school's tech support.**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/STUDENT_GIT_GUIDE.md b/classroom/STUDENT_GIT_GUIDE.md
new file mode 100644
index 0000000..76dbd5a
--- /dev/null
+++ b/classroom/STUDENT_GIT_GUIDE.md
@@ -0,0 +1,404 @@
+# Git Guide for Students
+## Track Your Learning Journey
+
+---
+
+## What is Git?
+
+Git is like a **super-powered save button** for your schoolwork. It:
+- Saves every version of your work (so you can go back if you make a mistake)
+- Shows your teacher what you've learned and when
+- Lets you collaborate with classmates safely
+- Builds a portfolio of your learning
+
+**Real-world use:** Every app on your phone, every website you visit, was built using Git!
+
+---
+
+## Setup (You'll Do This Once)
+
+### Day 1: Getting Started
+
+```bash
+# 1. Tell Git who you are
+git config --global user.name "Your Name"
+git config --global user.email "your.email@school.edu"
+
+# 2. Go to your class folder
+cd path/to/your/class/folder
+
+# 3. Connect to the class repository
+git clone <your-teacher-will-give-you-this-url>
+
+# 4. Go into your folder
+cd <repository-name>
+
+# 5. Check that everything works
+git status
+```
+
+**You're done!** You only do this once at the beginning of the year.
+
+---
+
+## Daily Classroom Workflow
+
+### Every Class Period:
+
+```bash
+# STEP 1: Update your work from home/last class
+git pull origin main
+
+# STEP 2: Do your work (take notes, practice problems, etc.)
+# Edit your files, watch videos, work on assignments
+
+# STEP 3: Save your progress (at end of class or when done with a task)
+git add .
+git commit -m "Lesson 3.2: Triangle congruence notes"
+
+# STEP 4: Back it up to the cloud
+git push origin main
+```
+
+**That's it!** Four steps every day.
+
+---
+
+## What Each Command Does
+
+### `git pull origin main`
+**What it does:** Downloads any updates (like if you worked at home)
+**When to use:** Beginning of class, before you start working
+**Think of it as:** Syncing your work like Google Docs
+
+### `git add .`
+**What it does:** Marks all your changes to be saved
+**When to use:** When you're ready to save your work
+**Think of it as:** Selecting which files to save
+
+### `git commit -m "message"`
+**What it does:** Actually saves your work with a description
+**When to use:** After `git add`, when you finish a task
+**Think of it as:** Hitting "Save" with a note about what you did
+
+### `git push origin main`
+**What it does:** Uploads your saved work to the cloud
+**When to use:** End of class or after committing
+**Think of it as:** Backing up to Google Drive
+
+### `git status`
+**What it does:** Shows what's changed since your last save
+**When to use:** Anytime you want to check what's different
+**Think of it as:** Checking "unsaved changes"
+
+---
+
+## Writing Good Commit Messages
+
+Your commit message should describe **what you did** in that work session.
+
+### Good Examples:
+```bash
+git commit -m "Completed Lesson 2.1 notes on parallel lines"
+git commit -m "Finished practice problems for sections 4.1-4.3"
+git commit -m "Added lab data for velocity experiment"
+git commit -m "Completed mastery check for Unit 3"
+git commit -m "Fixed mistake in problem #5"
+```
+
+### Bad Examples:
+```bash
+git commit -m "stuff"
+git commit -m "work"
+git commit -m "idk"
+git commit -m "done"
+```
+
+**Why it matters:** Your teacher can see your progress, and YOU can look back and see what you learned when!
+
+---
+
+## Submitting Mastery Checks
+
+When you're ready to submit a mastery check:
+
+```bash
+# 1. Make sure all your work is saved
+git add .
+git commit -m "Mastery Check: Unit 3 - Triangles (Ready for grading)"
+
+# 2. Create a special tag for this submission
+git tag -a "mastery-unit3-$(date +%Y%m%d)" -m "Unit 3 Mastery Check"
+
+# 3. Push everything including the tag
+git push origin main
+git push origin --tags
+
+# 4. Let your teacher know you've submitted
+# (Your teacher will tell you their preferred notification method)
+```
+
+---
+
+## Working Ahead (For Fast-Paced Learners)
+
+If you finish early and want to work on the next lesson:
+
+```bash
+# Create a branch for the next lesson
+git checkout -b lesson-4.2
+
+# Do your work on the new lesson
+# (take notes, practice problems, etc.)
+
+# Save your work
+git add .
+git commit -m "Started Lesson 4.2: Quadrilaterals"
+
+# Push this branch
+git push origin lesson-4.2
+
+# When you're done, go back to main
+git checkout main
+```
+
+**Why use branches?** Your teacher can see you're working ahead, but it keeps your required work separate from bonus work.
+
+---
+
+## Helping a Classmate (Peer Teaching)
+
+When you help another student:
+
+```bash
+# 1. Create a branch for collaborative work
+git checkout -b helping-student-name
+
+# 2. Work together on their problems
+# (You might add explanations, example problems, etc.)
+
+# 3. Save your collaborative work
+git add .
+git commit -m "Peer teaching: Helped with triangle proofs"
+
+# 4. Push the collaboration
+git push origin helping-student-name
+
+# 5. Go back to your own work
+git checkout main
+```
+
+**Extra credit note:** Your teacher can see exactly how you helped!
+
+---
+
+## Common Problems & Solutions
+
+### "I forgot to commit yesterday's work!"
+```bash
+# No problem! Just commit it now
+git add .
+git commit -m "Lesson 2.3 notes (from yesterday)"
+git push origin main
+```
+
+### "I accidentally deleted my notes!"
+```bash
+# See your recent commits
+git log --oneline
+
+# Go back to a previous version (before you deleted)
+git checkout HEAD~1 -- filename.md
+
+# Save the recovered file
+git add filename.md
+git commit -m "Recovered deleted notes"
+```
+
+### "I made changes but need to switch tasks"
+```bash
+# Save your work in progress
+git add .
+git commit -m "WIP: Working on problem set (not finished)"
+git push origin main
+
+# Come back later and keep working
+```
+
+### "Git says I have conflicts"
+```bash
+# This happens if you worked on two computers
+
+# 1. Ask your teacher for help the first time
+# 2. They'll show you how to resolve it
+
+# Usually it's:
+git pull origin main
+# (Edit the file to fix conflicts)
+git add .
+git commit -m "Fixed sync conflict"
+git push origin main
+```
+
+### "I don't know what I changed"
+```bash
+# See what's different
+git status           # Shows which files changed
+git diff            # Shows exactly what changed
+```
+
+---
+
+## Checking Your Progress
+
+### See your learning history:
+```bash
+# See all your commits (your learning timeline)
+git log --oneline
+
+# See visual timeline
+git log --graph --oneline --all
+
+# See what you did in a specific commit
+git show <commit-hash>
+```
+
+---
+
+## Quick Reference Card
+
+**Print this and keep it by your computer!**
+
+```
+DAILY ROUTINE:
+1. git pull origin main          (Get updates)
+2. [Do your work]                (Learn!)
+3. git add .                     (Mark changes)
+4. git commit -m "what I did"    (Save with note)
+5. git push origin main          (Backup to cloud)
+
+CHECKING STATUS:
+- git status                     (What changed?)
+- git log --oneline             (What did I do?)
+
+MASTERY CHECK:
+1. git add .
+2. git commit -m "Mastery Check: Unit X"
+3. git tag -a "mastery-unitX-date" -m "Unit X Done"
+4. git push origin main --tags
+
+OOPS COMMANDS:
+- git checkout -- filename       (Undo changes to file)
+- git reset HEAD filename        (Unstage a file)
+```
+
+---
+
+## Pro Tips
+
+1. **Commit often** - At least once per class period, more is better!
+2. **Write clear messages** - Your future self will thank you
+3. **Pull before push** - Always start class with `git pull`
+4. **Ask for help** - Git can seem weird at first, that's normal!
+5. **Don't panic** - Almost everything can be undone
+
+---
+
+## Understanding Git Vocabulary
+
+- **Repository (repo):** Your project folder that Git tracks
+- **Commit:** A save point in your work
+- **Push:** Upload to the cloud
+- **Pull:** Download from the cloud
+- **Branch:** A separate timeline for working ahead or experimenting
+- **Main:** Your primary timeline where required work lives
+- **Merge:** Combining two timelines (branches) together
+- **Clone:** Making a copy of a repository
+- **Tag:** A bookmark for important commits (like mastery checks)
+
+---
+
+## Why We Use Git in Class
+
+1. **You can't lose your work** - It's backed up constantly
+2. **Your teacher sees your effort** - Not just the final product
+3. **You learn real tools** - Used by professionals everywhere
+4. **You build a portfolio** - Show colleges/employers what you've learned
+5. **You learn from mistakes** - You can always go back
+6. **Collaboration is easier** - Work with classmates safely
+
+---
+
+## Getting Help
+
+**In order of preference:**
+
+1. Check this guide
+2. Ask a classmate who knows Git
+3. Ask your teacher
+4. Google your error message
+5. Check the full guide (GIT_GUIDE.md)
+
+**When asking for help, share:**
+- What command you ran
+- What error message you got
+- What you were trying to do
+
+---
+
+## Practice Challenges
+
+### Challenge 1: Basic Workflow
+```bash
+# 1. Create a new file called practice.md
+# 2. Write "Hello Git!" in it
+# 3. Add, commit, and push it
+# 4. Check git log to see your commit
+```
+
+### Challenge 2: Making Changes
+```bash
+# 1. Edit practice.md and add a new line
+# 2. Use git diff to see your changes
+# 3. Commit with a descriptive message
+# 4. Push to backup
+```
+
+### Challenge 3: View History
+```bash
+# 1. Make 3 different commits
+# 2. Use git log to see them all
+# 3. Use git show to look at each one
+```
+
+---
+
+## Success Checklist
+
+By the end of Week 1, you should be able to:
+- [ ] Clone the class repository
+- [ ] Pull updates at the start of class
+- [ ] Add and commit your work
+- [ ] Push to backup your work
+- [ ] Write good commit messages
+- [ ] Check your status and history
+
+By the end of Month 1, you should be able to:
+- [ ] Do the daily routine without looking at notes
+- [ ] Submit mastery checks properly
+- [ ] Use branches for working ahead
+- [ ] Recover from simple mistakes
+- [ ] Help a classmate with basic Git
+
+By the end of the semester:
+- [ ] Use Git automatically without thinking
+- [ ] Understand your full learning history
+- [ ] Collaborate using branches
+- [ ] Troubleshoot common problems
+- [ ] Have a portfolio of your learning!
+
+---
+
+**Remember:** Everyone struggles with Git at first. It gets easier with practice!
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/TEACHER_WORKFLOW.md b/classroom/TEACHER_WORKFLOW.md
new file mode 100644
index 0000000..8d9c876
--- /dev/null
+++ b/classroom/TEACHER_WORKFLOW.md
@@ -0,0 +1,772 @@
+# Git-Integrated Classroom Workflow
+## For Self-Paced, Mastery-Based Learning
+
+---
+
+## Overview
+
+This guide integrates Git version control into your blended, self-paced classroom for **Geometry and Physics** using mastery grading.
+
+**Benefits:**
+- Track individual student progress in real-time
+- See effort and process, not just final products
+- Enable safe collaboration between students at different paces
+- Build student portfolios automatically
+- Reduce "I lost my work" issues to zero
+- Teach real-world professional skills
+
+---
+
+## Repository Structure Options
+
+### Option A: Individual Student Repositories (Recommended)
+
+```
+ClassGeometry2025/
+├── student-john-doe/
+│   ├── Unit1-Foundations/
+│   │   ├── Lesson1.1-notes.md
+│   │   ├── Lesson1.2-practice.md
+│   │   └── Unit1-MasteryCheck.md
+│   ├── Unit2-Triangles/
+│   └── Unit3-Quadrilaterals/
+├── student-jane-smith/
+│   └── [same structure]
+```
+
+**Pros:**
+- Complete privacy for each student
+- Clear ownership
+- Easy to grade individually
+
+**Cons:**
+- More repositories to manage
+- Harder to see class-wide progress
+
+### Option B: Single Class Repository with Folders
+
+```
+Geometry-Period3-2025/
+├── students/
+│   ├── john-doe/
+│   │   ├── Unit1/
+│   │   └── Unit2/
+│   ├── jane-smith/
+│   │   ├── Unit1/
+│   │   └── Unit2/
+└── class-resources/
+    ├── lesson-templates/
+    └── rubrics/
+```
+
+**Pros:**
+- Single repo to manage
+- Easy to see whole class
+- Students can see peers' progress (motivation)
+
+**Cons:**
+- Less privacy
+- Students might accidentally edit others' work
+
+**Recommendation:** Start with Option B, move to Option A if privacy concerns arise.
+
+---
+
+## Daily Classroom Flow with Git
+
+### Student Arrival (5 minutes)
+```
+1. Phone check-in
+2. Daily learner check-in (paper/digital)
+3. Git sync:
+   - Student opens terminal/Git client
+   - Runs: git pull origin main
+   - Checks git status
+```
+
+**Teacher Action:**
+```bash
+# Quick morning check - see who's synced
+# (Use GitHub/GitLab web interface or run:)
+git fetch --all
+git log --all --oneline --since="1 day ago"
+```
+
+### Student-Teacher Check-in (5-10 minutes)
+
+**Student prepares:**
+```bash
+# Student shows teacher their recent progress
+git log --oneline -5
+git diff HEAD~1  # Shows changes since last commit
+```
+
+**Teacher reviews:**
+- Recent commits (what they've been working on)
+- Quality of notes/work
+- Mastery check readiness
+- Can see WHEN work was done (effort tracking)
+
+### Work Time (30-40 minutes)
+
+#### Students on New Lesson:
+```bash
+# Create new lesson folder/file
+# Watch videos, take notes
+# At checkpoints (every 10-15 min or after each concept):
+git add .
+git commit -m "Lesson 3.2: Completed triangle congruence theorems"
+git push origin main
+```
+
+**Teacher can:**
+- Monitor commits in real-time (GitHub web interface)
+- See who's stuck (no commits in 20+ minutes)
+- Review notes quality while students work
+
+#### Students on Skills Practice:
+```bash
+# Working on practice problems
+# After each problem set:
+git add .
+git commit -m "Completed practice problems 1-10 for Lesson 3.2"
+git push origin main
+```
+
+#### Students Doing Peer Teaching:
+```bash
+# Advanced student creates collaboration branch
+git checkout -b helping-john-lesson3
+
+# They work together, commit explanations/work
+git add .
+git commit -m "Peer teaching: Explained triangle congruence to John"
+git push origin helping-john-lesson3
+
+# Teacher can review collaboration quality for extra credit
+```
+
+### End of Class (5 minutes)
+
+**Student checklist:**
+```bash
+git add .
+git commit -m "End of class: [what they accomplished]"
+git push origin main
+git status  # Should show "nothing to commit"
+```
+
+**Teacher checklist:**
+```bash
+# Pull all updates
+git fetch --all
+
+# Quick review of day's commits
+git log --all --since="today" --oneline
+
+# Note students who didn't commit (follow up next class)
+```
+
+---
+
+## Mastery Check Workflow
+
+### Before Mastery Check
+
+**Student signals readiness:**
+```bash
+git add .
+git commit -m "Mastery Check Unit 3: Ready for assessment"
+git tag -a mastery-unit3-ready -m "Ready for Unit 3 mastery check"
+git push origin main --tags
+```
+
+**Teacher reviews readiness:**
+```bash
+# See all students who tagged as ready
+git tag -l "mastery-*-ready"
+
+# Review their prep work
+git log student-name/main --oneline
+```
+
+### During Mastery Check
+
+**Student procedure:**
+1. Teacher provides mastery check problems
+2. Student creates file: `Unit3-MasteryCheck.md`
+3. Works on problems
+4. Saves periodically:
+```bash
+git add Unit3-MasteryCheck.md
+git commit -m "Mastery Check Unit 3: In progress"
+```
+
+5. When complete:
+```bash
+git add .
+git commit -m "Mastery Check Unit 3: COMPLETE - Ready to grade"
+git tag -a mastery-unit3-submit-$(date +%Y%m%d) -m "Unit 3 Mastery Submission"
+git push origin main --tags
+```
+
+### Grading Mastery Check
+
+**Teacher workflow:**
+```bash
+# Pull student's submission
+git fetch origin
+git checkout student-name/main
+
+# Review their mastery check file
+# Can see their work process (all commits during the check)
+git log --since="today" --oneline
+
+# Provide feedback directly in Git
+# Option 1: Create a feedback file
+echo "# Feedback for Unit 3 Mastery Check
+Score: 3/4 (Approaching Mastery)
+Strengths: ...
+Growth areas: ...
+Next steps: ..." > Unit3-Feedback.md
+
+git add Unit3-Feedback.md
+git commit -m "Feedback: Unit 3 Mastery Check"
+git push origin student-name/main
+
+# Option 2: Use GitHub/GitLab comments on their commit
+```
+
+### After Grading
+
+**Student views feedback:**
+```bash
+git pull origin main
+# Sees new Unit3-Feedback.md file
+```
+
+**If revision needed:**
+```bash
+# Student creates revision branch
+git checkout -b unit3-revision
+
+# Makes corrections
+git add .
+git commit -m "Unit 3 Revision: Fixed triangle proof errors"
+
+# Resubmits
+git tag -a mastery-unit3-revision -m "Unit 3 Revision Submission"
+git push origin unit3-revision --tags
+```
+
+---
+
+## Tracking Class-Wide Progress
+
+### Dashboard Commands
+
+```bash
+# See all students' most recent commits
+git log --all --oneline --graph --decorate -20
+
+# See who worked in the last 24 hours
+git log --all --since="24 hours ago" --author=".*" --oneline
+
+# See who's on which unit (check their directories)
+# (Best done through GitHub/GitLab web interface)
+
+# See all mastery check submissions
+git tag -l "mastery-*-submit*"
+
+# See students working ahead
+git branch -a | grep -v main
+```
+
+### Weekly Progress Review
+
+**Friday afternoon routine:**
+```bash
+# Generate weekly report (manual or scripted)
+# For each student:
+git log student-name/main --since="1 week ago" --oneline > weekly-reports/student-name-week$(date +%W).txt
+
+# Review:
+# - Number of commits (engagement)
+# - Quality of commit messages (metacognition)
+# - Lessons completed
+# - Mastery checks submitted
+```
+
+---
+
+## Special Scenarios
+
+### Student Working from Home
+
+**Student:**
+```bash
+# At home
+git pull origin main  # Get latest
+# Do work
+git commit -m "Homework: Completed Unit 2 practice"
+git push origin main
+
+# At school next day
+git pull origin main  # Syncs automatically
+```
+
+**Teacher:** No extra work needed! Work is already synced.
+
+### Group Project/Lab (Physics)
+
+**Setup:**
+```bash
+# Create group branch
+git checkout -b group-velocity-lab-team1
+
+# All team members work on this branch
+```
+
+**During collaboration:**
+```bash
+# Each student commits their contributions
+git add lab-data.csv
+git commit -m "Added trial 3 velocity measurements - John"
+git push origin group-velocity-lab-team1
+
+# Partner pulls updates
+git pull origin group-velocity-lab-team1
+```
+
+**Teacher grading:**
+```bash
+# Can see each student's individual contributions
+git log group-velocity-lab-team1 --oneline
+# Each commit shows who did what
+```
+
+### Student Catches Up After Absence
+
+**Student returns:**
+```bash
+git pull origin main  # Gets any class materials added
+# Reviews commit history to see what they missed
+git log --since="3 days ago" --oneline
+```
+
+**Teacher can provide:**
+```bash
+# Add catch-up materials to their folder
+git add students/student-name/makeup-work/
+git commit -m "Added makeup materials for Student Name"
+git push origin main
+```
+
+---
+
+## Grading Integration
+
+### Effort Tracking (Process Points)
+
+```bash
+# Check commit frequency
+git log student-name/main --since="1 month ago" --oneline | wc -l
+
+# Quality of commits (review messages)
+git log student-name/main --since="1 month ago"
+
+# Consistency (commits spread over time vs. cramming)
+git log student-name/main --since="1 month ago" --format="%ad" --date=short
+```
+
+**Rubric example:**
+- 10+ commits per week = Full credit
+- 5-9 commits = Partial credit
+- <5 commits = Needs improvement
+- Quality of commit messages (descriptive vs. "stuff")
+
+### Mastery Level Tracking
+
+```bash
+# See all mastery attempts
+git tag -l "mastery-unit3-*"
+
+# Track revision history
+git log --grep="Revision" student-name/main
+```
+
+**Gradebook integration:**
+- Tag format: `mastery-unit3-score4` (Unit 3, score of 4)
+- Script to parse tags and update gradebook
+- Or manual review of tags weekly
+
+### Portfolio Building
+
+```bash
+# End of semester: Create student portfolio
+git log student-name/main --oneline > student-portfolio.txt
+
+# Better: Use GitLab/GitHub "Insights" to generate:
+# - Contribution graph
+# - Commit history
+# - Code frequency
+# - Shows growth over time visually
+```
+
+---
+
+## Setup & Maintenance
+
+### Beginning of Year Setup
+
+**Week before school:**
+```bash
+# Create class repository
+git init Geometry-Period3-2025
+cd Geometry-Period3-2025
+
+# Create structure
+mkdir -p class-resources/lesson-templates
+mkdir -p class-resources/rubrics
+mkdir students
+
+# Add template files
+# (lesson templates, rubric documents, etc.)
+
+git add .
+git commit -m "Initial class setup"
+
+# Push to GitHub/GitLab
+git remote add origin <url>
+git push -u origin main
+```
+
+**First week of school:**
+- Day 1: Intro to Git (what and why)
+- Day 2: Setup git on student devices
+- Day 3: Practice workflow with dummy assignment
+- Day 4: First real assignment using Git
+- Day 5: Troubleshooting day
+
+### Ongoing Maintenance
+
+**Daily:**
+- Quick commit scan (5 min)
+- Respond to student questions
+
+**Weekly:**
+- Review mastery check submissions
+- Generate progress reports
+- Clean up old branches
+
+**Monthly:**
+- Back up entire repository
+- Review and update lesson templates
+- Student progress conferences (show them their git history)
+
+### Backup Strategy
+
+```bash
+# Weekly backup
+git clone --mirror <repository-url> backup-$(date +%Y%m%d)
+
+# Or use GitHub/GitLab's built-in backup features
+```
+
+---
+
+## Tools & Resources
+
+### Essential Tools
+
+**For Teacher:**
+- **GitHub Desktop** or **GitKraken** (GUI for easier visualization)
+- **VS Code** with Git extension (for reviewing student work)
+- **GitHub/GitLab web interface** (best for class overview)
+
+**For Students:**
+- **GitHub Desktop** (easiest for beginners)
+- OR **Command line** (for students who want to go deeper)
+- **VS Code** (for editing markdown notes)
+
+### Recommended Platforms
+
+**GitHub:**
+- Free for education (GitHub Education)
+- Great web interface
+- Student Developer Pack (bonus resources)
+
+**GitLab:**
+- Free private repositories
+- Built-in CI/CD (advanced projects)
+- Self-hosted option
+
+### Scripts to Create
+
+```bash
+# daily-summary.sh - Shows today's class activity
+#!/bin/bash
+echo "Today's Commits:"
+git log --all --since="today" --oneline
+
+# weekly-report.sh - Generates weekly summary
+#!/bin/bash
+for student in students/*; do
+    echo "=== $student ==="
+    git log $student/main --since="1 week ago" --oneline | wc -l
+    echo "commits this week"
+done
+
+# mastery-checks.sh - Lists pending mastery checks
+#!/bin/bash
+git tag -l "mastery-*-ready"
+```
+
+---
+
+## Student Differentiation with Git
+
+### For Struggling Students
+
+**Extra support:**
+```bash
+# More frequent check-ins via commits
+# Require commits every 10 minutes during class
+
+# Provide more scaffolding in their folder
+# Teacher adds templates/examples directly to their branch
+```
+
+### For Advanced Students
+
+**Enrichment:**
+```bash
+# Work ahead on branches
+git checkout -b unit5-advanced
+
+# Deeper exploration projects
+git checkout -b physics-project-advanced-kinematics
+
+# Peer teaching branches (extra credit)
+git checkout -b peer-teaching-week12
+```
+
+### For Students Needing Accommodations
+
+**Flexibility:**
+- Extended deadlines tracked via tags
+- Alternative formats (voice notes converted to text, diagrams)
+- Commit frequency adjusted to their needs
+- Can submit evidence of understanding in multiple formats
+
+---
+
+## Parent Communication
+
+### Sharing Progress
+
+**Weekly parent email:**
+```
+Dear Parent,
+
+This week [Student Name]:
+- Completed Lessons 3.1-3.3 (Triangle Properties)
+- Made 12 commits (showed consistent effort)
+- Submitted Mastery Check for Unit 3 (score: 3/4)
+- Helped peer with triangle proofs (extra credit)
+
+View their work portfolio: [GitHub link]
+
+Next week: Unit 4 - Quadrilaterals
+```
+
+**Portfolio sharing:**
+- Give parents read-only access to student's repository
+- They can see real-time progress
+- Shows effort, not just grades
+
+---
+
+## Troubleshooting Common Issues
+
+### "Student forgot to commit before deadline"
+
+**Solution:**
+```bash
+# Check git history for evidence of work
+git log student-name/main --all --full-history
+
+# If work exists but wasn't committed, discuss time management
+# If no evidence, follow your late work policy
+```
+
+### "Two students worked on same file (conflict)"
+
+**Teacher resolution:**
+```bash
+# Pull both versions
+git fetch --all
+
+# Manual merge or ask students to redo individually
+# Use as teaching moment about collaboration workflow
+```
+
+### "Student deleted important work"
+
+**Recovery:**
+```bash
+# Find the commit with the work
+git log --all --full-history -- path/to/file
+
+# Restore it
+git checkout <commit-hash> -- path/to/file
+
+# Commit the recovery
+git commit -m "Recovered deleted work for student"
+```
+
+### "Student copied another student's work"
+
+**Detection:**
+```bash
+# Compare commit histories
+git log student1/main --oneline
+git log student2/main --oneline
+
+# Check timestamps - if identical work at identical times, red flag
+# Compare actual work:
+git diff student1/main:file.md student2/main:file.md
+```
+
+---
+
+## Assessment Examples
+
+### Formative Assessment via Git
+
+**Daily engagement:**
+- Did they commit today? (participation)
+- Quality of commit messages (metacognition)
+- Frequency of commits (work ethic)
+
+**Process tracking:**
+- How many attempts on practice problems?
+- Do they revise work after feedback?
+- Do they ask questions (via commit messages or notes)?
+
+### Summative Assessment via Git
+
+**Mastery checks:**
+- Tagged submissions
+- Work quality in committed files
+- Can see their thinking process (commits during the check)
+
+**Projects:**
+- Final product quality
+- Process evident in commit history
+- Collaboration visible in shared branches
+
+### Bonus/Extra Credit
+
+**Peer teaching:**
+- Count of peer collaboration branches
+- Quality of explanations in commits
+
+**Consistency:**
+- Streak of daily commits
+- Working ahead branches
+
+---
+
+## Sample Grading Rubric
+
+### Process Grade (40% of course grade)
+
+| Criteria | Mastery (4) | Proficient (3) | Developing (2) | Beginning (1) |
+|----------|-------------|----------------|----------------|---------------|
+| **Commit Frequency** | 12+ commits/week | 8-11 commits/week | 4-7 commits/week | <4 commits/week |
+| **Commit Quality** | Descriptive messages | Adequate messages | Vague messages | Missing messages |
+| **Work Consistency** | Daily work pattern | 3-4 days/week | 1-2 days/week | Sporadic |
+| **Revision Practice** | Revises after feedback | Sometimes revises | Rarely revises | Never revises |
+
+### Product Grade (60% of course grade)
+
+- Mastery checks (traditional grading)
+- Projects/labs
+- Participation
+
+---
+
+## Year-End Portfolio
+
+### Student Reflection
+
+**Final assignment:**
+```bash
+# Students review their entire year
+git log --oneline --all
+
+# Create reflection document:
+# - What lesson was hardest (find the commits with most revisions)
+# - What they're most proud of
+# - How they've grown (compare early vs. late commits)
+# - Evidence of mastery
+```
+
+### Portfolio Presentation
+
+Students can show:
+- Contribution graph (visual of their year)
+- Selected best work
+- Growth examples (early work vs. final work)
+- Peer teaching contributions
+
+**Export options:**
+```bash
+# Generate PDF of commits
+git log --oneline > my-learning-journey.txt
+
+# Create visualization (use GitLab/GitHub insights)
+# - Commit graph
+# - Heat map of activity
+```
+
+---
+
+## Next Steps
+
+### This Week:
+1. Decide on repository structure
+2. Create GitHub/GitLab account
+3. Set up class repository
+4. Create student setup instructions
+
+### Next Week:
+1. Introduce Git to students (use STUDENT_GIT_GUIDE.md)
+2. Help students set up
+3. Practice workflow with dummy assignment
+
+### First Month:
+1. Establish daily routines
+2. Troubleshoot common issues
+3. Refine workflow based on student feedback
+
+### First Semester:
+1. Implement mastery check workflow
+2. Try peer teaching branches
+3. Generate first portfolios
+
+---
+
+## Resources for Teachers
+
+- [GitHub Education](https://education.github.com/) - Free tools
+- [GitLab for Education](https://about.gitlab.com/solutions/education/) - Free private repos
+- [GitHub Classroom](https://classroom.github.com/) - Automated setup for students
+- [Learn Git Branching](https://learngitbranching.js.org/) - Visual tutorial for students
+
+---
+
+**Remember:** Start simple! You don't need to use every feature right away. Master the daily workflow first, then add complexity as you and students get comfortable.
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/LESSON_STUDENT_WORKFLOW_One_Hundred_Eighty.md b/classroom/lessons/LESSON_STUDENT_WORKFLOW_One_Hundred_Eighty.md
new file mode 100644
index 0000000..600923f
--- /dev/null
+++ b/classroom/lessons/LESSON_STUDENT_WORKFLOW_One_Hundred_Eighty.md
@@ -0,0 +1,456 @@
+# Student Workflow: One Hundred Eighty (Triangle Angle Sum Theorem)
+## Lesson with Git Integration
+
+---
+
+## Before Class Starts
+
+### Step 1: Sync Your Work (2 minutes)
+
+```bash
+# Navigate to your class folder
+cd ~/Documents/ClassWork/geometry-class
+
+# Get latest updates
+git pull origin main
+
+# Verify you're in the right place
+git status
+```
+
+---
+
+## Lesson Overview (50 minutes)
+
+Today you'll prove that the angles in any triangle add up to 180°. You'll:
+- Fix a proof that has errors (Warm-up)
+- Prove the theorem three different ways (Activities 1, 2, Cool-down)
+- Track all your work using Git
+
+**Git commits today: Minimum 5 (one after each activity)**
+
+---
+
+## Warm-up: What Went Wrong? (10 minutes)
+
+### Step 1: Open Your Warm-up File (1 minute)
+
+```bash
+# Navigate to today's lesson folder
+cd Unit-Angles-Proof/Lesson-One-Hundred-Eighty
+
+# Open the warm-up file
+# File: Warmup-What-Went-Wrong.md
+```
+
+**Your file already has:**
+- A triangle with angles: 50°, 60°, 70°
+- A proof with mistakes in it
+- Your job: Find and fix the errors
+
+### Step 2: Complete the Warm-up (7 minutes)
+
+In your file, you'll see:
+```markdown
+## Given Proof (Contains Errors!)
+[The incorrect proof will be here]
+
+## My Work: Finding the Errors
+
+### Error 1:
+**What's wrong:**
+**Why it's wrong:**
+**How to fix it:**
+
+### Error 2:
+**What's wrong:**
+**Why it's wrong:**
+**How to fix it:**
+```
+
+Fill in your analysis!
+
+### Step 3: Commit Your Warm-up (2 minutes)
+
+```bash
+# Check what you changed
+git status
+
+# Add your work
+git add Warmup-What-Went-Wrong.md
+
+# Commit with clear message
+git commit -m "Lesson One-Eighty: Completed warm-up - found proof errors"
+
+# Push to backup
+git push origin main
+```
+
+**Teacher will review:** Your teacher can now see your error analysis in real-time!
+
+---
+
+## Activity 1: Triangle Angle Sum One Way (15 minutes)
+
+### Step 1: Open Activity 1 File (1 minute)
+
+```bash
+# File: Activity1-Angle-Sum-Proof.md
+```
+
+### Step 2: Work Through the Proof (10 minutes)
+
+**What you'll do:**
+1. Look at the triangle provided (or use the digital applet)
+2. Follow the proof method shown
+3. Write your own version of the proof
+4. Justify each step
+
+**In your file:**
+```markdown
+## Triangle Information
+**Vertices:** A, B, C
+**Given information:** [What you're told]
+
+## My Proof (Method 1: Auxiliary Line)
+
+**Step 1:**
+**What I did:**
+**Why this is valid:**
+
+**Step 2:**
+**What I did:**
+**Why this is valid:**
+
+...
+
+**Conclusion:**
+Therefore, m∠A + m∠B + m∠C = 180°
+
+## My Reasoning
+[Explain in your own words WHY this proof works]
+
+## Questions I Have
+[Any confusion or things you want to ask]
+```
+
+### Step 3: Save Progress During Activity (twice during 10 min)
+
+```bash
+# After completing proof steps
+git add Activity1-Angle-Sum-Proof.md
+git commit -m "Activity 1: Completed proof steps 1-3"
+git push origin main
+
+# After finishing reasoning
+git add Activity1-Angle-Sum-Proof.md
+git commit -m "Activity 1: Finished proof and reasoning"
+git push origin main
+```
+
+**Why commit twice?**
+- Saves your work if computer crashes
+- Teacher can see if you're stuck
+- You can see your thinking process later
+
+### Step 4: Collaboration Time (4 minutes)
+
+**Compare with a partner:**
+
+```bash
+# If doing peer review (optional)
+git checkout -b peer-review-with-[partner-name]
+
+# Add notes from discussion
+echo "## Peer Discussion with [Partner Name]
+**What we agreed on:**
+**What we disagreed on:**
+**How we resolved it:**
+" >> Activity1-Peer-Notes.md
+
+git add Activity1-Peer-Notes.md
+git commit -m "Activity 1: Peer discussion notes"
+git checkout main
+git merge peer-review-with-[partner-name]
+git push origin main
+```
+
+---
+
+## Activity 2: Triangle Angle Sum Another Way (10 minutes)
+
+### Step 1: Open Activity 2 File (1 minute)
+
+```bash
+# File: Activity2-Another-Proof.md
+```
+
+### Step 2: Second Proof Method (7 minutes)
+
+**This time:**
+- Different approach (maybe paper folding or rotation)
+- Same conclusion (angles = 180°)
+- Your job: Follow the method and explain each step
+
+**In your file:**
+```markdown
+## Triangle Setup
+[Describe your triangle - you can use the same 50°, 60°, 70° triangle]
+
+## My Proof (Method 2: [Name of method])
+
+**Diagram/Sketch:**
+[Draw or describe what you're doing]
+
+**Step-by-step:**
+1.
+2.
+3.
+
+**Conclusion:**
+
+## Comparing Methods
+**How is this different from Method 1?**
+**Which method do I prefer and why?**
+**Do both methods work for ANY triangle?**
+```
+
+### Step 3: Commit Activity 2 (2 minutes)
+
+```bash
+git add Activity2-Another-Proof.md
+git commit -m "Activity 2: Completed second proof method"
+git push origin main
+```
+
+### Extension (If You Finish Early): "Are You Ready for More?"
+
+```bash
+# File: Activity2-Extension.md
+
+# Work on extension problem
+# Commit when done
+git add Activity2-Extension.md
+git commit -m "Activity 2: Completed extension problem"
+git push origin main
+```
+
+---
+
+## Lesson Synthesis (10 minutes)
+
+### Class Discussion (8 minutes)
+**No Git work during discussion** - listen and take mental notes!
+
+### Update Your Reference Chart (2 minutes)
+
+```bash
+# File: Reference-Chart.md
+# Add today's theorem
+
+# Your reference chart should include:
+## Triangle Angle Sum Theorem
+**Statement:** The sum of the measures of the angles in a triangle is 180°.
+**Proof methods I know:**
+1. [Method from Activity 1]
+2. [Method from Activity 2]
+**Key vocabulary:**
+- [Terms you learned]
+**When to use:**
+- [Applications]
+```
+
+```bash
+git add Reference-Chart.md
+git commit -m "Reference chart: Added Triangle Angle Sum Theorem"
+git push origin main
+```
+
+---
+
+## Cool-down: Triangle Angle Sum a Third Way (5 minutes)
+
+### Step 1: Final Proof (4 minutes)
+
+```bash
+# File: Cooldown-Third-Proof.md
+```
+
+**Your task:**
+- THIRD way to prove the same theorem
+- Write it independently (this shows YOUR understanding)
+- This is your exit ticket!
+
+**In your file:**
+```markdown
+# Cool-down: Triangle Angle Sum Theorem (Method 3)
+**Name:** Your Name
+**Date:** [Today's date]
+
+## The Triangle
+[Describe or sketch the triangle]
+
+## My Proof
+
+**Given:**
+
+**To Prove:** m∠A + m∠B + m∠C = 180°
+
+**Proof:**
+[Your proof here - be clear and complete!]
+
+## Reflection
+**Which of the three methods makes the most sense to me?**
+**Do I feel confident I could prove this for ANY triangle?** (Yes/Somewhat/Not yet)
+**Questions I still have:**
+```
+
+### Step 2: Submit Cool-down (1 minute)
+
+```bash
+# This is graded as your exit ticket!
+git add Cooldown-Third-Proof.md
+git commit -m "Cool-down: Completed third proof method (EXIT TICKET)"
+
+# Tag it so teacher knows it's complete
+git tag -a lesson-one-eighty-complete-$(date +%Y%m%d) -m "One Hundred Eighty lesson complete"
+
+# Push everything
+git push origin main --tags
+```
+
+**Important:** The tag tells your teacher you've finished the lesson!
+
+---
+
+## After Class
+
+### Check Your Work (Optional but recommended)
+
+```bash
+# See everything you did today
+git log --oneline --since="today"
+
+# Should show approximately:
+# - Warm-up commit
+# - Activity 1 commits (2)
+# - Activity 2 commit
+# - Reference chart commit
+# - Cool-down commit
+# - Tag for completion
+```
+
+### If You Need to Finish at Home
+
+```bash
+# All your work is saved - just pull it at home
+cd ~/Documents/ClassWork/geometry-class
+git pull origin main
+
+# Continue working
+# Commit when done
+# Push before next class
+```
+
+---
+
+## Git Checklist for This Lesson
+
+By the end of class, you should have:
+- [ ] Pulled at start of class
+- [ ] Committed warm-up work
+- [ ] Committed Activity 1 (at least once)
+- [ ] Committed Activity 2
+- [ ] Updated reference chart
+- [ ] Committed cool-down
+- [ ] Tagged lesson as complete
+- [ ] Pushed all work to origin
+
+**Minimum commits:** 5
+**Recommended commits:** 6-7
+
+---
+
+## Troubleshooting
+
+### "I can't find my lesson folder"
+```bash
+cd ~/Documents/ClassWork/geometry-class
+ls Unit-Angles-Proof/
+cd Unit-Angles-Proof/Lesson-One-Hundred-Eighty
+```
+
+### "Git says I have uncommitted changes when I try to pull"
+```bash
+# Commit what you have first
+git add .
+git commit -m "Work in progress"
+git pull origin main
+```
+
+### "I made a mistake in my proof"
+```bash
+# Just edit the file and commit again
+git add [filename]
+git commit -m "Fixed error in proof step 2"
+git push origin main
+```
+
+### "I forgot to commit during the lesson"
+```bash
+# That's okay! Commit everything now
+git add .
+git commit -m "One Hundred Eighty: All lesson work"
+git push origin main
+```
+
+---
+
+## What Your Teacher Will See
+
+Your teacher can see:
+- ✓ When you started working (first commit timestamp)
+- ✓ Your thought process (commits throughout the lesson)
+- ✓ Which activities you completed
+- ✓ Your questions and confusion points
+- ✓ When you finished (tag timestamp)
+- ✓ Your complete work (all files)
+
+**This is GOOD!** Your teacher can:
+- Help if you get stuck
+- See your effort
+- Grade your understanding
+- Provide specific feedback
+
+---
+
+## Learning Goals Check
+
+At the end of this lesson, can you:
+- [ ] Prove the Triangle Angle Sum Theorem in at least two ways?
+- [ ] Explain WHY the angles add to 180°?
+- [ ] Apply this theorem to find missing angles?
+- [ ] Justify each step in your proof?
+
+If you answered "yes" to all four - great work!
+If "no" to any - that's okay! Check:
+1. Your committed work (review what you wrote)
+2. Your peer notes (what did classmates say?)
+3. Your questions (ask teacher tomorrow!)
+
+---
+
+## Preview: Next Lesson
+
+**Next:** Transformations, Transversals and Proof
+- You'll use today's theorem
+- Similar Git workflow
+- Build on your reference chart
+
+**Make sure** your work is committed so you can reference it next lesson!
+
+---
+
+**Ready to prove some triangles? Let's go!**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/LESSON_STUDENT_WORKFLOW_Transformations_Transversals.md b/classroom/lessons/LESSON_STUDENT_WORKFLOW_Transformations_Transversals.md
new file mode 100644
index 0000000..f85fe21
--- /dev/null
+++ b/classroom/lessons/LESSON_STUDENT_WORKFLOW_Transformations_Transversals.md
@@ -0,0 +1,540 @@
+# Student Workflow: Transformations, Transversals and Proof
+## Lesson with Git Integration
+
+---
+
+## Before Class Starts
+
+### Step 1: Sync Your Work (2 minutes)
+
+```bash
+# Navigate to your class folder
+cd ~/Documents/ClassWork/geometry-class
+
+# Get latest updates
+git pull origin main
+
+# Verify you're in the right place
+git status
+```
+
+---
+
+## Lesson Overview (50 minutes)
+
+Today you'll use what you learned about the Triangle Angle Sum Theorem to prove angle relationships created by transversals cutting parallel lines. You'll:
+- Use transformations to understand angle relationships
+- Prove theorems about transversals and parallel lines
+- Apply multiple theorems together
+- Track all your work using Git
+
+**Git commits today: Minimum 5 (one after each activity)**
+
+**Building on:** Last lesson (One Hundred Eighty) - you'll USE the Triangle Angle Sum Theorem today!
+
+---
+
+## Warm-up: Transformation Review (10 minutes)
+
+### Step 1: Open Your Warm-up File (1 minute)
+
+```bash
+# Navigate to today's lesson folder
+cd Unit-Angles-Proof/Lesson-Transformations-Transversals
+
+# Open the warm-up file
+# File: Warmup-Transformation-Review.md
+```
+
+**Your task:**
+- Review transformations (translations, rotations, reflections)
+- Identify which transformations preserve angle measures
+- Connect to angle relationships
+
+### Step 2: Complete the Warm-up (7 minutes)
+
+In your file, you'll explore:
+```markdown
+## Transformation Properties
+
+### Translation (Slide)
+**Does it preserve angle measures?** (Yes/No)
+**Example:**
+
+### Rotation (Turn)
+**Does it preserve angle measures?** (Yes/No)
+**Example:**
+
+### Reflection (Flip)
+**Does it preserve angle measures?** (Yes/No)
+**Example:**
+
+## Connection to Angles
+**How can transformations help us prove angle relationships?**
+```
+
+Fill in your analysis!
+
+### Step 3: Commit Your Warm-up (2 minutes)
+
+```bash
+# Check what you changed
+git status
+
+# Add your work
+git add Warmup-Transformation-Review.md
+
+# Commit with clear message
+git commit -m "Lesson Transformations: Completed warm-up on transformation properties"
+
+# Push to backup
+git push origin main
+```
+
+---
+
+## Activity 1: Alternate Interior Angles (15 minutes)
+
+### Step 1: Open Activity 1 File (1 minute)
+
+```bash
+# File: Activity1-Alternate-Interior-Angles.md
+```
+
+### Step 2: Explore the Relationship (10 minutes)
+
+**What you'll do:**
+1. Look at parallel lines cut by a transversal
+2. Identify alternate interior angles
+3. Use a transformation to show they're congruent
+4. Write a formal proof
+
+**In your file:**
+```markdown
+## The Diagram
+[You'll see parallel lines cut by a transversal]
+
+## Identifying Angles
+**Line 1 (parallel):**
+**Line 2 (parallel):**
+**Transversal:**
+**Alternate interior angles:** ∠___ and ∠___
+
+## Using Transformations
+**What transformation maps one angle onto the other?**
+
+**Step-by-step description:**
+
+## My Proof
+**Given:** Lines l and m are parallel, cut by transversal t
+**Prove:** Alternate interior angles are congruent
+
+**Proof:**
+[Your proof using transformations and Triangle Angle Sum]
+```
+
+### Step 3: Save Progress During Activity (twice)
+
+```bash
+# After identifying angles and transformation
+git add Activity1-Alternate-Interior-Angles.md
+git commit -m "Activity 1: Identified alternate interior angles and transformation"
+git push origin main
+
+# After completing proof
+git add Activity1-Alternate-Interior-Angles.md
+git commit -m "Activity 1: Completed alternate interior angles proof"
+git push origin main
+```
+
+### Step 4: Check Your Understanding (4 minutes)
+
+**Practice problem in your file:**
+- Apply the theorem to find missing angles
+- Justify using the theorem you just proved
+
+---
+
+## Activity 2: Other Angle Relationships (15 minutes)
+
+### Step 1: Open Activity 2 File (1 minute)
+
+```bash
+# File: Activity2-Angle-Relationships.md
+```
+
+### Step 2: Prove More Relationships (12 minutes)
+
+**This time you'll prove:**
+- Corresponding angles are congruent
+- Same-side interior angles are supplementary
+- OR explore your choice of relationship
+
+**In your file:**
+```markdown
+## Relationship 1: Corresponding Angles
+
+**What are corresponding angles?**
+
+**My conjecture:**
+
+**My proof:**
+[Use what you learned from Activity 1]
+
+## Relationship 2: Same-Side Interior Angles
+
+**What are same-side interior angles?**
+
+**My conjecture:**
+
+**My proof:**
+[Hint: Use Triangle Angle Sum Theorem from last lesson!]
+
+## Comparing Relationships
+**How are these relationships connected?**
+**Which theorem depends on which?**
+```
+
+### Step 3: Commit Activity 2 (2 minutes)
+
+```bash
+git add Activity2-Angle-Relationships.md
+git commit -m "Activity 2: Proved angle relationships with transversals"
+git push origin main
+```
+
+---
+
+## Activity 3: Applying Multiple Theorems (10 minutes)
+
+### Step 1: Open Activity 3 File (1 minute)
+
+```bash
+# File: Activity3-Complex-Diagrams.md
+```
+
+### Step 2: Solve Complex Problems (7 minutes)
+
+**Challenge:**
+- Diagrams with multiple parallel lines and transversals
+- Multiple triangles
+- Use BOTH Triangle Angle Sum AND transversal theorems
+
+**In your file:**
+```markdown
+## Problem 1: Multi-step Angle Finding
+
+[Diagram provided]
+
+**What I know:**
+
+**What I need to find:**
+
+**Step 1:** [Use which theorem?]
+
+**Step 2:** [Use which theorem?]
+
+**Step 3:** [Combine information]
+
+**Solution:**
+
+## Problem 2: Proof with Multiple Theorems
+
+**Given:**
+
+**Prove:**
+
+**My proof:**
+[Use both lessons' theorems!]
+```
+
+### Step 3: Commit Activity 3 (2 minutes)
+
+```bash
+git add Activity3-Complex-Diagrams.md
+git commit -m "Activity 3: Applied multiple theorems to complex diagrams"
+git push origin main
+```
+
+---
+
+## Lesson Synthesis (5 minutes)
+
+### Class Discussion (3 minutes)
+**No Git work during discussion** - listen and take notes!
+
+### Update Your Reference Chart (2 minutes)
+
+```bash
+# File: Reference-Chart.md
+# Add today's theorems
+
+## Theorems About Transversals and Parallel Lines
+
+**Alternate Interior Angles Theorem:**
+When parallel lines are cut by a transversal, alternate interior angles are congruent.
+
+**Corresponding Angles Theorem:**
+[Your notes]
+
+**Same-Side Interior Angles Theorem:**
+[Your notes]
+
+**How to use:**
+- Identify parallel lines
+- Identify transversal
+- Classify angle pairs
+- Apply appropriate theorem
+
+**Connection to Triangle Angle Sum:**
+[How did you use last lesson's theorem today?]
+```
+
+```bash
+git add Reference-Chart.md
+git commit -m "Reference chart: Added transversal angle theorems"
+git push origin main
+```
+
+---
+
+## Cool-down: Proof Challenge (5 minutes)
+
+### Step 1: Final Proof (4 minutes)
+
+```bash
+# File: Cooldown-Proof-Challenge.md
+```
+
+**Your task:**
+- Complex diagram with parallel lines, transversal, and triangle
+- Find missing angles using ALL theorems from both lessons
+- This is your exit ticket!
+
+**In your file:**
+```markdown
+# Cool-down: Proof Challenge
+**Name:** Your Name
+**Date:** [Today's date]
+
+## The Problem
+[Complex diagram provided]
+
+**Given:**
+
+**Find:** All missing angle measures
+
+## My Solution
+
+**Step 1:** [Which theorem? Why?]
+
+**Step 2:** [Which theorem? Why?]
+
+**Step 3:** [Which theorem? Why?]
+
+**Final answers:**
+∠A = ___°
+∠B = ___°
+∠C = ___°
+[etc.]
+
+## Reflection
+**Theorems I used today:**
+- [ ] Triangle Angle Sum Theorem
+- [ ] Alternate Interior Angles Theorem
+- [ ] Corresponding Angles Theorem
+- [ ] Same-Side Interior Angles Theorem
+- [ ] Other: _________
+
+**Which step was hardest?**
+
+**Do I feel ready for the mastery check?** (Yes/Somewhat/Not yet)
+```
+
+### Step 2: Submit Cool-down (1 minute)
+
+```bash
+# This is graded as your exit ticket!
+git add Cooldown-Proof-Challenge.md
+git commit -m "Cool-down: Completed proof challenge (EXIT TICKET)"
+
+# Tag it so teacher knows it's complete
+git tag -a lesson-transformations-complete-$(date +%Y%m%d) -m "Transformations and Transversals lesson complete"
+
+# Push everything
+git push origin main --tags
+```
+
+**Important:** The tag tells your teacher you've finished the lesson!
+
+---
+
+## After Class
+
+### Check Your Work (Optional but recommended)
+
+```bash
+# See everything you did today
+git log --oneline --since="today"
+
+# Should show approximately:
+# - Warm-up commit
+# - Activity 1 commits (2)
+# - Activity 2 commit
+# - Activity 3 commit
+# - Reference chart commit
+# - Cool-down commit
+# - Tag for completion
+```
+
+### Prepare for Mastery Check
+
+**If you feel ready:**
+```bash
+# Signal readiness for mastery check
+git tag -a mastery-angles-proof-ready -m "Ready for Angles and Proof mastery check"
+git push origin --tags
+```
+
+**Your teacher will review your work from BOTH lessons and confirm you're ready!**
+
+---
+
+## Git Checklist for This Lesson
+
+By the end of class, you should have:
+- [ ] Pulled at start of class
+- [ ] Committed warm-up work
+- [ ] Committed Activity 1 (at least twice)
+- [ ] Committed Activity 2
+- [ ] Committed Activity 3
+- [ ] Updated reference chart
+- [ ] Committed cool-down
+- [ ] Tagged lesson as complete
+- [ ] Pushed all work to origin
+
+**Optional:**
+- [ ] Tagged as ready for mastery check (if you feel prepared)
+
+---
+
+## Connection to Previous Lesson
+
+**Last lesson (One Hundred Eighty):**
+- Proved Triangle Angle Sum Theorem
+- Used multiple proof methods
+- Built proof-writing skills
+
+**Today (Transformations, Transversals):**
+- USED Triangle Angle Sum Theorem
+- Added transversal theorems
+- Combined multiple theorems
+- More complex applications
+
+**Tomorrow:**
+- Review both lessons
+- Mastery check preparation
+- OR begin mastery check (if ready!)
+
+---
+
+## Mastery Check Preview
+
+**The mastery check will assess:**
+- Triangle Angle Sum Theorem (understanding and application)
+- Transversal angle relationships
+- Writing formal proofs
+- Applying multiple theorems together
+- Finding missing angles in complex diagrams
+
+**To prepare:**
+- Review your Reference-Chart.md
+- Look at your work from both lessons
+- Practice the cool-down problems
+- Make sure you can explain WHY each theorem works
+
+**Mastery check file:** `Mastery-Check-Angles-Proof.md`
+(Available when you tag as ready!)
+
+---
+
+## Troubleshooting
+
+### "I don't see today's folder"
+```bash
+cd ~/Documents/ClassWork/geometry-class
+git pull origin main
+ls Unit-Angles-Proof/
+cd Unit-Angles-Proof/Lesson-Transformations-Transversals
+```
+
+### "I'm confused about which theorem to use"
+Check your Reference-Chart.md from both lessons:
+- **Triangle in diagram?** → Triangle Angle Sum
+- **Parallel lines and transversal?** → Transversal theorems
+- **Both?** → Use both!
+
+### "I forgot what we did last lesson"
+```bash
+# Review your previous work
+git show HEAD:../Lesson-One-Hundred-Eighty/Cooldown-Third-Proof.md
+
+# Or just read your reference chart
+cat Reference-Chart.md
+```
+
+---
+
+## What Your Teacher Will See
+
+Your teacher can see:
+- ✓ When you started working
+- ✓ Your thought process through both activities
+- ✓ Which problems challenged you
+- ✓ How you combined theorems
+- ✓ Your readiness for mastery check
+- ✓ Your complete learning progression
+
+---
+
+## Learning Goals Check
+
+At the end of this lesson, can you:
+- [ ] Identify angle pairs created by transversals?
+- [ ] Prove alternate interior angles are congruent?
+- [ ] Use transformations to justify angle relationships?
+- [ ] Apply Triangle Angle Sum and transversal theorems together?
+- [ ] Find missing angles in complex diagrams?
+
+If you answered "yes" to all five - you might be ready for the mastery check!
+If "no" to any - review those areas before the mastery check.
+
+---
+
+## Extension Opportunities
+
+**If you finish early:**
+
+1. **Prove all the relationships:**
+   - Alternate interior angles (done in Activity 1)
+   - Corresponding angles
+   - Same-side interior angles
+   - Alternate exterior angles
+   - Same-side exterior angles
+
+2. **Create your own problem:**
+   - Draw complex diagram
+   - Mark some angles
+   - Challenge a classmate to find the rest
+   - Submit via peer collaboration branch!
+
+3. **Prepare for mastery check:**
+   - Review both lessons
+   - Practice complex problems
+   - Update reference chart with examples
+
+---
+
+**Ready to connect theorems and transformations? Let's go!**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/README_LESSON_One_Hundred_Eighty.md b/classroom/lessons/README_LESSON_One_Hundred_Eighty.md
new file mode 100644
index 0000000..ed3c64b
--- /dev/null
+++ b/classroom/lessons/README_LESSON_One_Hundred_Eighty.md
@@ -0,0 +1,477 @@
+# Lesson: One Hundred Eighty (Triangle Angle Sum)
+## Complete Git-Integrated Lesson Package
+
+---
+
+## Overview
+
+**Lesson Topic:** Proving that the sum of measures of angles in a triangle is 180°
+**Duration:** 50 minutes
+**Grade Level:** High School Geometry
+**Git Integration Level:** Full
+
+This lesson package demonstrates how to integrate Git version control into a geometry lesson using the workflows described in the classroom guides.
+
+---
+
+## What's Included
+
+### For Teachers
+
+| File | Purpose | When to Use |
+|------|---------|-------------|
+| **[TEACHER_SETUP_One_Hundred_Eighty.md](TEACHER_SETUP_One_Hundred_Eighty.md)** | Complete lesson plan with Git integration | Before/during/after class |
+
+### For Students
+
+| File | Purpose | When to Use |
+|------|---------|-------------|
+| **[LESSON_STUDENT_WORKFLOW_One_Hundred_Eighty.md](LESSON_STUDENT_WORKFLOW_One_Hundred_Eighty.md)** | Student guide for the lesson | Reference during class |
+
+### Student Work Templates
+
+All templates are in the `templates/` folder:
+
+| Template | Activity | Time | Git Commits Expected |
+|----------|----------|------|---------------------|
+| **Warmup-What-Went-Wrong.md** | Find errors in a proof | 10 min | 1 commit |
+| **Activity1-Angle-Sum-Proof.md** | First proof method | 15 min | 2 commits |
+| **Activity2-Another-Proof.md** | Second proof method | 10 min | 1 commit |
+| **Activity2-Extension.md** | Extension problem | Optional | 1 commit (bonus) |
+| **Cooldown-Third-Proof.md** | Exit ticket | 5 min | 1 commit + tag |
+| **Reference-Chart.md** | Ongoing reference | 2 min | 1 commit |
+
+**Total expected commits per student:** 5-7 (plus completion tag)
+
+---
+
+## Quick Start for Teachers
+
+### Day Before Class
+
+1. **Read the teacher guide:**
+   - Open [TEACHER_SETUP_One_Hundred_Eighty.md](TEACHER_SETUP_One_Hundred_Eighty.md)
+   - Review lesson timeline
+   - Note monitoring points
+
+2. **Set up repository:**
+```bash
+# Create lesson folder in your class repo
+cd YourClassRepository
+mkdir -p Unit-Angles-Proof/Lesson-One-Hundred-Eighty
+
+# Copy templates to lesson folder
+cp templates/*.md Unit-Angles-Proof/Lesson-One-Hundred-Eighty/
+
+# Commit and push
+git add Unit-Angles-Proof/
+git commit -m "Lesson setup: One Hundred Eighty templates"
+git push origin main
+```
+
+3. **Prepare physical materials:**
+   - Triangles with 50°, 60°, 70° angles
+   - Class reference chart display
+   - Digital applets (optional)
+
+### Day of Class
+
+1. **Students pull templates:**
+   - Display on board: `git pull origin main`
+   - Students navigate to lesson folder
+   - Verify everyone has files
+
+2. **Monitor throughout lesson:**
+   - Check commits every 10-15 minutes
+   - Help students who haven't committed
+   - Watch for questions in student files
+
+3. **Check completion at end:**
+   - Count completion tags
+   - Note who needs follow-up
+
+### After Class
+
+1. **Review student work:**
+   - Pull all student branches
+   - Spot-check cool-downs (exit tickets)
+   - Note patterns/misconceptions
+
+2. **Provide feedback:**
+   - Create feedback files
+   - Or use inline comments (GitHub/GitLab)
+   - Push feedback to student branches
+
+---
+
+## Quick Start for Students
+
+### Before Lesson
+
+```bash
+# Sync your work
+cd ~/Documents/ClassWork/geometry-class
+git pull origin main
+
+# Navigate to lesson
+cd Unit-Angles-Proof/Lesson-One-Hundred-Eighty
+
+# Verify files are there
+ls
+```
+
+### During Lesson
+
+**Follow this pattern for each activity:**
+1. Open the activity file
+2. Complete the work
+3. Commit with clear message
+4. Push to backup
+
+**Example:**
+```bash
+# After completing warm-up
+git add Warmup-What-Went-Wrong.md
+git commit -m "Warm-up: Found proof errors"
+git push origin main
+```
+
+### End of Lesson
+
+```bash
+# Submit exit ticket
+git add Cooldown-Third-Proof.md
+git commit -m "Cool-down complete (EXIT TICKET)"
+git tag -a lesson-one-eighty-complete-$(date +%Y%m%d) -m "Complete"
+git push origin main --tags
+```
+
+---
+
+## Learning Goals
+
+### Students will be able to:
+- Prove that the sum of the measures of angles in a triangle is 180°
+- Use multiple methods to prove the Triangle Angle Sum Theorem
+- Justify each step in a geometric proof
+- Compare different proof strategies
+- Apply the theorem to find missing angles
+
+### Git Skills Students Practice:
+- Pull updates at start of class
+- Commit work incrementally
+- Write descriptive commit messages
+- Tag important submissions
+- Push work to remote repository
+- Navigate directory structures
+
+---
+
+## Lesson Structure with Git Integration
+
+### Timeline
+
+| Time | Activity | Student Action | Git Action |
+|------|----------|----------------|------------|
+| 0-5 min | Arrival & setup | Pull updates, open files | `git pull` |
+| 5-10 min | Warm-up | Find proof errors | Commit warm-up |
+| 10-15 min | Warm-up discussion | Share findings | - |
+| 15-25 min | Activity 1 | First proof method | Commit 2x during activity |
+| 25-30 min | Activity 1 discussion | Compare with peers | Optional peer branch |
+| 30-40 min | Activity 2 | Second proof method | Commit activity |
+| 40-45 min | Synthesis | Update reference chart | Commit reference chart |
+| 45-50 min | Cool-down | Third proof (exit ticket) | Commit + tag |
+
+---
+
+## Assessment
+
+### Formative (Process)
+
+**Via Git logs:**
+- Participation (commits throughout lesson)
+- Work completion (all files committed)
+- Time management (timestamp spread)
+- Effort (quality of commit messages)
+
+**How to check:**
+```bash
+# Count student commits
+git log student-name/main --since="today" --oneline | wc -l
+
+# Review commit quality
+git log student-name/main --since="today" --oneline
+```
+
+### Summative (Product)
+
+**Cool-down (Exit Ticket):**
+- Valid third proof method: ___/4 points
+- Clear justification: ___/3 points
+- Correct conclusion: ___/3 points
+**Total: ___/10 points**
+
+**How to grade:**
+```bash
+# View student's cool-down
+git show student-name/main:Unit-Angles-Proof/Lesson-One-Hundred-Eighty/Cooldown-Third-Proof.md
+```
+
+---
+
+## Differentiation
+
+### For Struggling Students
+
+**In templates:**
+- Step-by-step scaffolding provided
+- Visual aids and diagrams
+- Sentence starters
+- Multiple attempts encouraged (can commit revisions)
+
+**Teacher support:**
+- Monitor commits - see who's stuck
+- Provide just-in-time feedback
+- Can add hints to student's file directly (via Git)
+
+### For Advanced Students
+
+**Extension provided:**
+- Activity2-Extension.md (polygon angle sums)
+- Generalization patterns
+- Formula development
+- Extra credit via Git commits
+
+**Track via:**
+```bash
+git log --all --grep="extension"
+```
+
+---
+
+## Multilingual Learner Support (MLR7)
+
+**Compare and Connect:** Built into Activity 1
+- Students compare proof methods
+- Use mathematical language
+- Identify similarities/differences
+- Document in writing (Git tracked)
+
+**Language scaffolds in templates:**
+- Sentence frames provided
+- Key vocabulary highlighted
+- Multiple representations (diagrams + words)
+
+---
+
+## Access for Diverse Abilities
+
+**Representation (Activity 1):**
+- Visual diagrams in templates
+- Digital applet option
+- Physical triangle models
+- Multiple proof methods shown
+
+**Action and Expression (Activity 2):**
+- Choice of proof method
+- Can draw instead of write formal proof
+- Voice-to-text option for dictation
+- Extended time (visible in Git timestamps)
+
+---
+
+## Common Issues and Solutions
+
+### Technical
+
+| Issue | Solution |
+|-------|----------|
+| Can't find files | `git pull origin main` then navigate |
+| Forgot to commit | Commit at end with all work |
+| Made a mistake | Edit file and commit again (revision) |
+| Computer crashed | Work saved at last commit |
+
+### Pedagogical
+
+| Issue | Solution |
+|-------|----------|
+| Student stuck on proof | Check their commits - see where they stopped |
+| Misconception evident | Add feedback to their file, push to their branch |
+| Absent student | All materials in Git - can make up easily |
+| Needs scaffolding | Create branch with extra hints |
+
+---
+
+## Connection to Other Lessons
+
+### Previous Lesson: Evidence, Angles and Proof
+Students learned:
+- Angle relationships
+- Parallel lines and transversals
+- Beginning proof structure
+
+### This Lesson: One Hundred Eighty
+Students prove:
+- Triangle Angle Sum Theorem
+- Multiple proof methods
+- Formal justification
+
+### Next Lesson: Transformations, Transversals and Proof
+Students will use:
+- Triangle Angle Sum Theorem
+- Apply with transversals
+- More complex proofs
+
+**Git connection:** Reference chart builds across lessons
+
+---
+
+## Standards Alignment
+
+**Common Core:**
+- HSG-CO.C.10: Prove theorems about triangles
+- MP3: Construct viable arguments and critique reasoning
+- MP7: Look for and make use of structure
+
+**Git integration supports:**
+- MP3: Written arguments visible in commits
+- MP7: Comparing structures across proof methods
+- MP6: Precision in communication (commit messages)
+
+---
+
+## Materials Needed
+
+### Physical
+- [ ] Triangles with angles 50°, 60°, 70° (one per student or pair)
+- [ ] Class reference chart display
+- [ ] Whiteboard/projector
+- [ ] Optional: Patty paper for folding method
+
+### Digital
+- [ ] Computer/device per student
+- [ ] Git installed and configured
+- [ ] Access to class repository
+- [ ] Optional: Digital applets for Activities 1-2
+
+### Files
+- [ ] All templates committed to repository
+- [ ] Student workflow guide available
+- [ ] Teacher setup guide printed/accessible
+
+---
+
+## Extension Opportunities
+
+### During Lesson
+- Activity2-Extension.md (polygon angle sums)
+- Third proof method variations
+- Peer teaching (create collaboration branch)
+
+### After Lesson
+- Apply theorem to complex diagrams
+- Multi-triangle problems
+- Proof writing practice
+
+**Track extensions:**
+```bash
+git log --all --grep="extension\|peer-teaching"
+```
+
+---
+
+## Parent Communication
+
+**Example update:**
+```
+This week in Geometry, students proved the Triangle Angle Sum
+Theorem using three different methods. [Student Name] demonstrated
+strong understanding and completed all activities, including the
+extension problem on polygon angle sums.
+
+You can view their work at: [GitHub link to student repo]
+
+Next week: Transformations and Transversals
+```
+
+---
+
+## Reflection Questions (For You)
+
+After teaching this lesson:
+
+**What worked well?**
+
+
+**What would you change?**
+
+
+**How did Git enhance the lesson?**
+
+
+**Student misconceptions noticed:**
+
+
+**Notes for next year:**
+
+
+---
+
+## Files Checklist
+
+Before class, verify you have:
+- [ ] TEACHER_SETUP_One_Hundred_Eighty.md (this guide)
+- [ ] LESSON_STUDENT_WORKFLOW_One_Hundred_Eighty.md (student reference)
+- [ ] Warmup-What-Went-Wrong.md (template)
+- [ ] Activity1-Angle-Sum-Proof.md (template)
+- [ ] Activity2-Another-Proof.md (template)
+- [ ] Activity2-Extension.md (template)
+- [ ] Cooldown-Third-Proof.md (template)
+- [ ] Reference-Chart.md (template)
+
+All templates committed to repository:
+- [ ] Templates in correct folder structure
+- [ ] Committed to main branch
+- [ ] Pushed to remote
+- [ ] Students can access via `git pull`
+
+---
+
+## Resources
+
+**Related guides:**
+- [Main Teacher Workflow](../TEACHER_WORKFLOW.md) - Full classroom integration
+- [Student Git Guide](../STUDENT_GIT_GUIDE.md) - General student reference
+- [Mastery Check Guide](../MASTERY_CHECK_GUIDE.md) - Assessment submission
+
+**External resources:**
+- Curriculum materials for this lesson
+- Digital applets (if using)
+- Video explanations (optional)
+
+---
+
+## Version History
+
+- **v1.0** (2025-11-16): Initial creation
+  - Complete lesson package
+  - All templates created
+  - Ready for classroom use
+
+---
+
+## Feedback
+
+After using this lesson, please note:
+- What worked
+- What needs improvement
+- Suggestions for templates
+- Git workflow adjustments
+
+This will help refine the materials for future use!
+
+---
+
+**Ready to teach! See TEACHER_SETUP_One_Hundred_Eighty.md for detailed timeline.**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/README_LESSON_Transformations_Transversals.md b/classroom/lessons/README_LESSON_Transformations_Transversals.md
new file mode 100644
index 0000000..31b9dd2
--- /dev/null
+++ b/classroom/lessons/README_LESSON_Transformations_Transversals.md
@@ -0,0 +1,404 @@
+# Lesson: Transformations, Transversals and Proof
+## Complete Git-Integrated Lesson Package
+
+---
+
+## Overview
+
+**Lesson Topic:** Using transformations to prove angle relationships with transversals and parallel lines
+**Duration:** 50 minutes
+**Grade Level:** High School Geometry
+**Prerequisites:** One Hundred Eighty (Triangle Angle Sum Theorem)
+**Git Integration Level:** Full
+**Mastery Check:** Available after this lesson
+
+This lesson builds directly on the Triangle Angle Sum Theorem to prove and apply angle relationships created by transversals cutting parallel lines.
+
+---
+
+## What's Included
+
+### For Teachers
+
+| File | Purpose |
+|------|---------|
+| **[TEACHER_SETUP_Transformations_Transversals.md](TEACHER_SETUP_Transformations_Transversals.md)** | Complete lesson plan, timeline, mastery check access protocol |
+
+### For Students
+
+| File | Purpose |
+|------|---------|
+| **[LESSON_STUDENT_WORKFLOW_Transformations_Transversals.md](LESSON_STUDENT_WORKFLOW_Transformations_Transversals.md)** | Student guide with Git workflow for the lesson |
+
+### Student Work Templates
+
+In `templates-transformations/`:
+
+| Template | Activity | Time | Commits |
+|----------|----------|------|---------|
+| **Warmup-Transformation-Review.md** | Review rigid transformations | 10 min | 1 |
+| **Activity1-Alternate-Interior-Angles.md** | Prove alternate interior angles theorem | 15 min | 2 |
+| **Activity2-Angle-Relationships.md** | Prove corresponding and same-side interior angles | 15 min | 1 |
+| **Activity3-Complex-Diagrams.md** | Apply multiple theorems together | 10 min | 1 |
+| **Cooldown-Proof-Challenge.md** | Exit ticket with complex problem | 5 min | 1 + tag |
+
+**Expected commits:** 5-7 plus completion tag and optional mastery readiness tag
+
+---
+
+## Connection to Previous Lesson
+
+**Lesson 1: One Hundred Eighty**
+- Students proved Triangle Angle Sum Theorem
+- Three different proof methods
+- Foundation for this lesson
+
+**Lesson 2: Transformations, Transversals (This Lesson)**
+- USES Triangle Angle Sum Theorem
+- Adds transversal angle theorems
+- Combines multiple theorems
+
+**Result:** Students ready for comprehensive mastery check
+
+---
+
+## Quick Start for Teachers
+
+### Before Class
+
+```bash
+# 1. Create lesson folder
+cd YourClassRepository/Unit-Angles-Proof
+mkdir Lesson-Transformations-Transversals
+
+# 2. Copy templates
+cp templates-transformations/*.md Lesson-Transformations-Transversals/
+
+# 3. Commit
+git add Lesson-Transformations-Transversals/
+git commit -m "Lesson setup: Transformations and Transversals"
+git push origin main
+```
+
+### During Class
+
+- Follow timeline in TEACHER_SETUP guide
+- Monitor commits: `git log --all --since="10 min ago"`
+- Watch for mastery readiness tags
+
+### After Class
+
+```bash
+# Check who's ready for mastery check
+git tag -l "mastery-angles-proof-ready"
+
+# Review student work
+git show student-name:path/to/Cooldown-Proof-Challenge.md
+
+# Grant mastery check access (if ready)
+cp templates-mastery/Mastery-Check-Angles-Proof.md Unit-Angles-Proof/
+git push origin student-name/main
+```
+
+---
+
+## Learning Goals
+
+### Content Goals
+- Use transformations to prove angle relationships
+- Prove: Alternate Interior Angles Theorem
+- Prove: Corresponding Angles Theorem
+- Prove: Same-Side Interior Angles Theorem
+- Apply multiple theorems in complex diagrams
+
+### Process Goals
+- Connect transformations to formal proof
+- Build on previous knowledge (Triangle Angle Sum)
+- Develop multi-step problem-solving
+- Write clear, justified proofs
+
+### Git Skills
+- Continue daily workflow (now automatic)
+- Tag readiness for assessments
+- Self-assess preparation
+
+---
+
+## Lesson Structure
+
+### Flow
+
+```
+Warm-up (10 min)
+  ↓
+Review transformations → Which preserve angles?
+  ↓
+Activity 1 (15 min)
+  ↓
+Prove alternate interior angles using 180° rotation
+  ↓
+Activity 2 (15 min)
+  ↓
+Prove corresponding and same-side interior angles
+  ↓
+Activity 3 (10 min) [Optional/Flexible]
+  ↓
+Apply ALL theorems together
+  ↓
+Cool-down (5 min)
+  ↓
+Complex problem + mastery readiness check
+```
+
+### Key Teaching Moments
+
+1. **Transformation as proof tool:** Rotation preserves angles, so rotated angles are congruent
+2. **Building theorems:** Corresponding angles proved FROM alternate interior
+3. **Triangle connection:** Same-side interior uses Triangle Angle Sum!
+4. **Pattern recognition:** Z, F, and C patterns for angle pairs
+
+---
+
+## Differentiation Built-In
+
+### For All Students
+- Step-by-step templates
+- Visual prompts
+- Multiple representations
+- Practice problems embedded
+
+### Struggling Students
+- Physical manipulatives option (transparencies)
+- Can focus on alternate interior only (Activity 1)
+- Partner work allowed
+- Teacher can add scaffolding via Git
+
+### Advanced Students
+- All five angle relationships (Activity 2)
+- Create own problems (Activity 3)
+- Peer teaching opportunities
+- Early mastery check access
+
+---
+
+## Mastery Check Protocol
+
+### Student Tags Readiness
+
+```bash
+git tag -a mastery-angles-proof-ready -m "Ready for mastery check"
+git push origin --tags
+```
+
+### Teacher Reviews
+
+**Check both lessons:**
+1. One Hundred Eighty cool-down
+2. Transformations cool-down
+3. Reference chart completeness
+4. Commit history (engagement)
+
+**Decision:**
+- **Ready:** Add Mastery-Check-Angles-Proof.md to student's folder
+- **Review:** Provide specific feedback on what to review
+
+### Mastery Check
+
+**File:** `Mastery-Check-Angles-Proof.md` (in templates-mastery/)
+**Time:** 40 minutes
+**Sections:**
+1. Triangle Angle Sum (20 pts)
+2. Transversal Theorems (30 pts)
+3. Combined Application (30 pts)
+4. Reflection (5 pts)
+
+**Scoring:**
+- 75-85: Mastery (4)
+- 65-74: Proficient (3)
+- 55-64: Developing (2)
+- <55: Beginning (1)
+
+---
+
+## Assessment
+
+### Formative (Process)
+- Daily commits
+- Activity completion
+- Questions asked (in files)
+- Peer collaboration
+
+**Via Git:**
+```bash
+git log student-name/main --since="lesson-date" --oneline
+```
+
+### Summative (Product)
+- Cool-down (exit ticket): 10 points
+- Mastery check (when ready): 85 points
+
+**Grading workflow in TEACHER_SETUP guide**
+
+---
+
+## Materials Needed
+
+### Physical
+- Transparencies or patty paper (for showing transformations)
+- Pre-drawn transversal diagrams
+- Protractors (optional)
+- Class reference chart
+
+### Digital
+- Computer/device per student
+- Git configured
+- Access to class repository
+- Optional: GeoGebra or geometry software
+
+---
+
+## Standards Alignment
+
+**Common Core:**
+- HSG-CO.C.9: Prove theorems about lines and angles
+- HSG-CO.A.5: Use transformations to define congruence
+- MP3: Construct viable arguments
+- MP7: Look for and make use of structure
+
+**Git supports:**
+- MP3: Documented reasoning in commits
+- MP6: Precision in mathematical communication
+- MP8: Repeated reasoning (patterns across angle types)
+
+---
+
+## Self-Paced Classroom Integration
+
+### Students at Different Paces
+
+**Fast pace:**
+- Complete both lessons quickly
+- Tag ready for mastery check
+- Take check early
+- Move to next unit OR peer teach
+
+**On pace:**
+- Lesson 1: Day 1
+- Lesson 2: Day 2
+- Review: Day 3 (optional)
+- Mastery check: Day 4-5
+
+**Slower pace:**
+- Lesson 1: Days 1-2
+- Lesson 2: Days 3-4
+- Review: Day 5
+- Mastery check: When ready
+
+**Git makes this easy:**
+- Everyone's progress visible
+- No one held back
+- No one rushed
+- Natural differentiation
+
+---
+
+## Extension to Next Unit
+
+**After mastery check:**
+
+**Passed with Mastery (4) or Proficient (3):**
+- Move to next unit
+- Can still help peers
+
+**Developing (2) or Beginning (1):**
+- Review specific areas (in feedback)
+- Revise for higher score
+- Take revision mastery check
+
+**Next Unit Preview:**
+- Will use triangle and transversal theorems
+- Building complexity
+- More proofs
+
+---
+
+## Files Checklist
+
+Before class:
+- [ ] TEACHER_SETUP guide read
+- [ ] All templates copied to repository
+- [ ] Templates committed and pushed
+- [ ] Physical materials ready
+- [ ] Mastery-Check template ready (for later)
+
+After class:
+- [ ] Student work pulled
+- [ ] Completion tags checked
+- [ ] Cool-downs reviewed
+- [ ] Mastery readiness assessed
+- [ ] Mastery check access granted (if ready)
+
+---
+
+## Relationship to General Guides
+
+**This lesson uses:**
+- [TEACHER_WORKFLOW.md](../TEACHER_WORKFLOW.md) - Daily classroom procedures
+- [STUDENT_GIT_GUIDE.md](../STUDENT_GIT_GUIDE.md) - Student reference
+- [MASTERY_CHECK_GUIDE.md](../MASTERY_CHECK_GUIDE.md) - Assessment submission process
+
+**This lesson demonstrates:**
+- How lessons build on each other
+- How Git tracks cumulative learning
+- How self-paced mastery works
+- How to manage different student paces
+
+---
+
+## Success Indicators
+
+**During lesson:**
+- Students commit regularly
+- Questions in files show engagement
+- Proofs show understanding
+- Reference charts complete
+
+**After lesson:**
+- Most students complete cool-down
+- Some tag mastery readiness
+- Commit messages show thinking
+- Work quality evident in Git
+
+**Mastery check:**
+- Students show combined understanding
+- Can apply both lessons' concepts
+- Write clear proofs
+- Solve complex problems
+
+---
+
+## Teacher Reflection Questions
+
+After teaching:
+
+**Pacing:**
+- Did timing work?
+- Need more/less time for any activity?
+
+**Understanding:**
+- Common misconceptions?
+- What clicked? What didn't?
+
+**Git Integration:**
+- How did commits help you monitor?
+- Issues with tagging/workflow?
+
+**Mastery Readiness:**
+- How many students ready immediately?
+- What review is needed?
+
+---
+
+**Ready to teach! See TEACHER_SETUP for detailed lesson plan.**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/TEACHER_SETUP_One_Hundred_Eighty.md b/classroom/lessons/TEACHER_SETUP_One_Hundred_Eighty.md
new file mode 100644
index 0000000..249f222
--- /dev/null
+++ b/classroom/lessons/TEACHER_SETUP_One_Hundred_Eighty.md
@@ -0,0 +1,610 @@
+# Teacher Setup: One Hundred Eighty Lesson
+## Git Integration for Triangle Angle Sum Theorem
+
+---
+
+## Quick Overview
+
+**Lesson:** One Hundred Eighty (Triangle Angle Sum Theorem)
+**Duration:** 50 minutes
+**Git Integration:** Full - students commit work throughout lesson
+**Materials Needed:** Student templates (provided), physical triangles (50°, 60°, 70°)
+
+---
+
+## Before Class (15 minutes prep)
+
+### Step 1: Set Up Lesson Repository Structure (5 minutes)
+
+```bash
+# Navigate to your class repository
+cd ~/Documents/Teaching/Geometry-Class-2025
+
+# Create lesson folder structure
+mkdir -p Unit-Angles-Proof/Lesson-One-Hundred-Eighty
+
+cd Unit-Angles-Proof/Lesson-One-Hundred-Eighty
+
+# Copy template files to the lesson folder
+# (Templates are in classroom/lessons/templates/)
+```
+
+**Folder structure should be:**
+```
+Geometry-Class-2025/
+└── Unit-Angles-Proof/
+    └── Lesson-One-Hundred-Eighty/
+        ├── Warmup-What-Went-Wrong.md
+        ├── Activity1-Angle-Sum-Proof.md
+        ├── Activity2-Another-Proof.md
+        ├── Activity2-Extension.md
+        ├── Cooldown-Third-Proof.md
+        └── Reference-Chart.md
+```
+
+### Step 2: Commit Templates to Repository (2 minutes)
+
+```bash
+# Add all template files
+git add Unit-Angles-Proof/Lesson-One-Hundred-Eighty/
+
+# Commit
+git commit -m "Lesson setup: One Hundred Eighty templates ready for students"
+
+# Push to remote
+git push origin main
+```
+
+### Step 3: Prepare Physical Materials (5 minutes)
+
+- [ ] Physical triangles with angles 50°, 60°, 70° (one per student or pair)
+- [ ] Class reference chart display ready
+- [ ] Digital applets loaded (if using)
+- [ ] Whiteboard/projector for whole-class discussion
+
+### Step 4: Prepare Monitoring Dashboard (3 minutes)
+
+**Open your monitoring setup:**
+```bash
+# Option 1: GitHub/GitLab web interface
+# Open: https://github.com/your-name/Geometry-Class-2025
+# View: Network graph or commit history
+
+# Option 2: Command line monitoring
+# Create a monitoring script
+```
+
+**Simple monitoring script (optional):**
+```bash
+#!/bin/bash
+# save as: monitor-lesson.sh
+
+echo "=== Lesson One-Eighty Progress ==="
+echo "Students who have committed in last 10 minutes:"
+git log --all --since="10 minutes ago" --pretty=format:"%an - %s" | sort -u
+
+echo ""
+echo "=== Students who have tagged completion ==="
+git tag -l "lesson-one-eighty-complete-*"
+```
+
+---
+
+## Class Period Timeline (50 minutes)
+
+### Opening (5 minutes before lesson)
+
+**As students arrive:**
+
+```bash
+# Remind students to pull
+# Display on board:
+"BEFORE WE START:
+1. Open terminal/Git Bash
+2. cd ~/Documents/ClassWork/geometry-class
+3. git pull origin main
+4. Navigate to: Unit-Angles-Proof/Lesson-One-Hundred-Eighty
+5. Open Warmup-What-Went-Wrong.md"
+```
+
+**Quick check:**
+- Students have files open
+- Students are synced
+- Any Git issues resolved
+
+---
+
+### Warm-up: What Went Wrong? (10 minutes)
+
+**[0-2 min]** Introduce the warm-up
+- Show the triangle (50°, 60°, 70°)
+- Point students to Warmup-What-Went-Wrong.md
+- Explain: Find errors in the "proof"
+
+**[2-7 min]** Students work individually
+- Circulate and monitor
+- Check: Are students typing into the file?
+- Help: Git questions, finding the file
+
+**Quick monitor check:**
+```bash
+# See who's working
+git fetch --all
+watch -n 30 'git log --all --since="5 minutes ago" --oneline'
+```
+
+**[7-9 min]** Brief share-out
+- "What errors did you find?"
+- Key point: One example ≠ proof for all cases
+- Transition: "Today we'll prove it properly"
+
+**[9-10 min]** Students commit
+- Display on board: `git add Warmup-What-Went-Wrong.md && git commit -m "Warm-up complete" && git push origin main`
+- Check: Who hasn't committed yet
+
+---
+
+### Activity 1: Triangle Angle Sum One Way (15 minutes)
+
+**[10-11 min]** Introduce Activity 1
+- "Open Activity1-Angle-Sum-Proof.md"
+- Show the auxiliary line method (on board)
+- "Follow along and justify EACH step"
+
+**[11-21 min]** Students work
+- Can work in pairs (MLR7: Compare and Connect)
+- Digital applet available (if using)
+- Remind: Commit partway through!
+
+**Mid-activity commit reminder [~16 min]:**
+- "If you've completed steps 1-3, commit now!"
+- Helps students who are behind (you can see progress)
+
+**Access for diverse abilities:**
+- Visual aids on board
+- Step-by-step template (already in file)
+- Allow drawing/sketching
+- Verbal explanation option
+
+**Monitor in real-time:**
+```bash
+# See who's stuck (no commits in last 10 min)
+git log --all --since="10 minutes ago" --author=".*" --oneline | cut -d' ' -f2 | sort -u
+```
+
+**[21-25 min]** Compare and Connect (MLR7)
+- Pairs share their proofs
+- "What did your partner do that helped?"
+- Opportunity for peer-review branch (optional)
+
+**[25 min]** Final commit for Activity 1
+- Everyone commits completed work
+
+---
+
+### Activity 2: Triangle Angle Sum Another Way (10 minutes)
+
+**[25-26 min]** Transition to Activity 2
+- "Open Activity2-Another-Proof.md"
+- Introduce Method 2 (paper folding, rotation, etc.)
+- "Different method, same conclusion"
+
+**[26-34 min]** Students work on second proof
+- More independent than Activity 1
+- Digital applet available
+- Compare to Method 1 as they go
+
+**Access for diverse abilities:**
+- Can use physical triangles
+- Can draw/sketch instead of formal proof
+- "Are You Ready for More?" for advanced students
+
+**[34-35 min]** Quick share
+- "Which method do you prefer?"
+- "Does it work for ANY triangle?"
+
+**[35 min]** Commit Activity 2
+
+**Check for extension work:**
+```bash
+# See who did extension
+git log --all --grep="extension"
+```
+
+---
+
+### Lesson Synthesis (10 minutes)
+
+**[35-43 min]** Class discussion (NO Git during this)
+
+**Discussion prompts:**
+- "We saw three methods. What's the same about all of them?"
+- "Why does this work for ANY triangle?"
+- "How is this different from Grade 8?"
+
+**Key points to emphasize:**
+- One example ≠ proof
+- Formal justification required
+- Auxiliary elements are tools
+- Structure shows why it's always 180°
+
+**[43-45 min]** Update Reference Chart
+- Add Triangle Angle Sum Theorem to class display
+- Students add to their Reference-Chart.md
+- Commit reference chart update
+
+**Whole-class commit:**
+- Display: `git add Reference-Chart.md && git commit -m "Added Triangle Angle Sum Theorem" && git push origin main`
+
+---
+
+### Cool-down: Third Proof (5 minutes)
+
+**[45 min]** Introduce cool-down
+- "Open Cooldown-Third-Proof.md"
+- "THIRD way to prove it - on your own"
+- "This is your exit ticket - shows YOUR understanding"
+
+**[45-50 min]** Students work independently
+- Silent work time
+- This assesses individual understanding
+- Circulate but minimal help
+
+**[50 min]** Submit cool-down
+- Display:
+```bash
+git add Cooldown-Third-Proof.md
+git commit -m "Cool-down complete (EXIT TICKET)"
+git tag -a lesson-one-eighty-complete-$(date +%Y%m%d) -m "Complete"
+git push origin main --tags
+```
+
+**End of class check:**
+```bash
+# Who has tagged completion?
+git tag -l "lesson-one-eighty-complete-*"
+```
+
+---
+
+## After Class (10 minutes)
+
+### Step 1: Pull All Student Work (2 minutes)
+
+```bash
+cd ~/Documents/Teaching/Geometry-Class-2025
+git fetch --all
+
+# Or if using individual repos, pull each one
+```
+
+### Step 2: Quick Review (5 minutes)
+
+**Check completion:**
+```bash
+# Who finished?
+git tag -l "lesson-one-eighty-complete-*" | wc -l
+
+# Who didn't finish?
+# (Students without the tag need follow-up)
+```
+
+**Spot-check understanding:**
+```bash
+# Review a few cool-downs
+git show student-name/main:Unit-Angles-Proof/Lesson-One-Hundred-Eighty/Cooldown-Third-Proof.md
+```
+
+**Look for:**
+- Did they complete all sections?
+- Is the third proof valid?
+- Do they show understanding?
+- Any misconceptions to address tomorrow?
+
+### Step 3: Note for Tomorrow (3 minutes)
+
+**Students who need follow-up:**
+- Didn't finish (no tag)
+- Struggled with proofs (visible in commits)
+- Asked questions (in their files)
+- Need extension (finished early, did extension)
+
+**Create follow-up list:**
+```markdown
+## Follow-up for Tomorrow:
+- **Didn't finish:** [Names] - need to complete cool-down
+- **Struggled:** [Names] - check in during next lesson
+- **Questions:** [Names] - answer these questions
+- **Advanced:** [Names] - consider pre-teaching next concept
+```
+
+---
+
+## Grading This Lesson
+
+### What to Grade
+
+**Process (Participation/Effort):**
+- [ ] Pulled at start of class
+- [ ] Committed warm-up
+- [ ] Committed Activity 1
+- [ ] Committed Activity 2
+- [ ] Updated reference chart
+- [ ] Submitted cool-down with tag
+
+**Check with:**
+```bash
+# Count commits for the lesson
+git log student-name/main --since="today" --oneline | wc -l
+# Should be 5-7 commits
+```
+
+**Product (Understanding):**
+- Cool-down proof (exit ticket)
+- Quality of reasoning in activities
+- Justification of steps
+
+**Mastery-based rubric:**
+- **4 (Mastery):** Valid third proof, clear justification, all activities complete
+- **3 (Proficient):** Valid proof with minor gaps, most justification clear
+- **2 (Developing):** Proof attempted but incomplete/flawed
+- **1 (Beginning):** Minimal understanding shown
+
+### Quick Grading Workflow
+
+```bash
+# For each student:
+
+# 1. Check completion (tag exists?)
+git tag -l "lesson-one-eighty-complete-*" | grep student-name
+
+# 2. Review cool-down (exit ticket)
+git show student-name/main:Unit-Angles-Proof/Lesson-One-Hundred-Eighty/Cooldown-Third-Proof.md
+
+# 3. Check process (number of commits)
+git log student-name/main --since="today" --oneline
+
+# 4. Assign grade
+# 5. Provide feedback (next section)
+```
+
+---
+
+## Providing Feedback
+
+### Option 1: Create Feedback File
+
+```bash
+# Checkout student's branch
+git checkout student-name/main
+
+# Create feedback file
+cat > Unit-Angles-Proof/Lesson-One-Hundred-Eighty/Teacher-Feedback.md <<EOF
+# Feedback: One Hundred Eighty Lesson
+**Student:** Student Name
+**Date Graded:** $(date +%Y-%m-%d)
+**Grade:** 3/4 (Proficient)
+
+## Strengths
+✓ Excellent work on Activity 1 - clear auxiliary line reasoning
+✓ Good comparison between methods
+✓ Completed all activities
+
+## Growth Areas
+⚠ Cool-down proof: Step 2 needs more justification
+⚠ Consider: Why does your method work for all triangles?
+
+## Questions to Think About
+- Can you explain WHY the auxiliary line method always works?
+- What happens with an obtuse triangle?
+
+## Next Steps
+- Review parallel line theorems (helpful for next lesson)
+- Consider the extension problem if you have time
+
+Great effort today!
+EOF
+
+# Commit and push feedback
+git add Unit-Angles-Proof/Lesson-One-Hundred-Eighty/Teacher-Feedback.md
+git commit -m "Teacher feedback: One Hundred Eighty lesson"
+git push origin student-name/main
+
+# Return to main
+git checkout main
+```
+
+### Option 2: Inline Comments (GitHub/GitLab)
+
+- View student's cool-down in web interface
+- Add line-by-line comments
+- Student sees feedback next time they pull
+
+### Option 3: Quick Tags (for process tracking)
+
+```bash
+# Tag students who showed mastery
+git tag -a student-name-mastery-lesson-one-eighty -m "Mastery demonstrated"
+
+# Tag students who need revision
+git tag -a student-name-revision-needed-lesson-one-eighty -m "Needs revision"
+```
+
+---
+
+## Common Issues and Solutions
+
+### "Student can't find the files"
+
+**Solution:**
+```bash
+# Check they pulled
+# Have them run:
+git pull origin main
+ls Unit-Angles-Proof/Lesson-One-Hundred-Eighty/
+```
+
+### "Student made a mistake and wants to start over"
+
+**Solution:**
+```bash
+# Restore original template
+git checkout HEAD -- Warmup-What-Went-Wrong.md
+```
+
+### "Student didn't commit during the lesson"
+
+**Solution:**
+- That's okay for first few lessons
+- Remind them to commit at the end
+- Discuss value of incremental commits
+
+### "I can't see a student's work"
+
+**Solution:**
+```bash
+# Make sure they pushed
+# Check: did they commit to the right branch?
+git branch -a | grep student-name
+
+# Have student run:
+git push origin main
+```
+
+---
+
+## Differentiation Using Git
+
+### For Struggling Students
+
+**Provide scaffolding:**
+```bash
+# Add extra hints to their template
+# Create a branch with more detailed steps
+
+git checkout -b student-name-scaffolded
+# Edit their Activity1 file with more hints
+git commit -m "Added scaffolding for Student Name"
+git push origin student-name-scaffolded
+```
+
+### For Advanced Students
+
+**Challenge them:**
+```bash
+# Point them to extension
+# OR create additional challenge
+
+echo "## Additional Challenge
+Can you prove this using transformations?
+" >> Activity2-Extension.md
+```
+
+**Track extension work:**
+```bash
+# See who did extension
+git log --all --grep="extension" --oneline
+```
+
+### For Absent Students
+
+**They can make it up easily:**
+```bash
+# All materials are in Git
+# Student pulls and works through at their own pace
+# You can see when they complete it (tag timestamp)
+```
+
+---
+
+## Next Lesson Prep
+
+**This lesson builds to:**
+- Transformations, Transversals and Proof
+- Using Triangle Angle Sum Theorem with transversals
+- More complex proofs
+
+**Reference for next time:**
+```bash
+# Students will need their reference chart
+# Make sure everyone has Triangle Angle Sum Theorem noted
+```
+
+---
+
+## Assessment Data to Collect
+
+**From Git logs:**
+
+| Metric | How to Check | What It Means |
+|--------|--------------|---------------|
+| Completion rate | Count tags | Engagement |
+| Commit frequency | Commits per student | Work ethic |
+| Time on task | Timestamp range | Pacing |
+| Extension work | Grep for "extension" | Advanced thinking |
+| Peer collaboration | Branches with "peer" | Collaboration |
+| Questions asked | Read student files | Confusion points |
+
+**Export for records:**
+```bash
+# Generate completion report
+echo "Lesson: One Hundred Eighty Completion Report" > lesson-report.txt
+echo "Date: $(date)" >> lesson-report.txt
+echo "" >> lesson-report.txt
+echo "Completed:" >> lesson-report.txt
+git tag -l "lesson-one-eighty-complete-*" >> lesson-report.txt
+echo "" >> lesson-report.txt
+echo "Total: $(git tag -l 'lesson-one-eighty-complete-*' | wc -l) students" >> lesson-report.txt
+```
+
+---
+
+## Reflection Questions for You
+
+After teaching this lesson:
+
+**What worked well with Git integration?**
+
+
+**What would you change for next time?**
+
+
+**How did Git help you see student thinking?**
+
+
+**What surprised you?**
+
+
+**Notes for next year:**
+
+
+---
+
+## Quick Reference: Commands You'll Use
+
+```bash
+# BEFORE CLASS
+git add Unit-Angles-Proof/Lesson-One-Hundred-Eighty/
+git commit -m "Lesson templates ready"
+git push origin main
+
+# DURING CLASS
+git fetch --all                          # Check student progress
+git log --all --since="10 min ago"      # See recent work
+watch -n 30 'git log --oneline'         # Auto-refresh
+
+# AFTER CLASS
+git tag -l "lesson-one-eighty-*"        # Check completion
+git show student:path/to/cooldown.md    # Review work
+
+# GRADING
+git checkout student-name/main           # Enter student's work
+# Review files
+git checkout main                        # Return to main
+```
+
+---
+
+**You're ready to teach this lesson with Git! Good luck tomorrow!**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/TEACHER_SETUP_Transformations_Transversals.md b/classroom/lessons/TEACHER_SETUP_Transformations_Transversals.md
new file mode 100644
index 0000000..7308a3b
--- /dev/null
+++ b/classroom/lessons/TEACHER_SETUP_Transformations_Transversals.md
@@ -0,0 +1,516 @@
+# Teacher Setup: Transformations, Transversals and Proof
+## Git Integration for Transversal Angle Relationships
+
+---
+
+## Quick Overview
+
+**Lesson:** Transformations, Transversals and Proof
+**Duration:** 50 minutes
+**Prerequisites:** One Hundred Eighty lesson (Triangle Angle Sum Theorem)
+**Git Integration:** Full - students commit work throughout lesson
+**Mastery Check:** Students can tag readiness after this lesson
+
+---
+
+## Learning Goals
+
+**Students will:**
+- Use transformations to prove angle relationships with transversals
+- Prove Alternate Interior Angles, Corresponding Angles, and Same-Side Interior Angles theorems
+- Apply multiple theorems together in complex diagrams
+- Combine Triangle Angle Sum Theorem with transversal theorems
+
+**Git Skills:**
+- Continue daily workflow
+- Tag readiness for mastery check
+- Use commits to show multi-step reasoning
+
+---
+
+## Before Class (10 minutes prep)
+
+### Step 1: Set Up Repository (3 minutes)
+
+```bash
+cd ~/Documents/Teaching/Geometry-Class-2025
+
+# Create lesson folder
+mkdir -p Unit-Angles-Proof/Lesson-Transformations-Transversals
+
+cd Unit-Angles-Proof/Lesson-Transformations-Transversals
+
+# Copy template files
+# (Templates from classroom/lessons/templates-transformations/)
+```
+
+**Folder should contain:**
+- Warmup-Transformation-Review.md
+- Activity1-Alternate-Interior-Angles.md
+- Activity2-Angle-Relationships.md
+- Activity3-Complex-Diagrams.md
+- Cooldown-Proof-Challenge.md
+- Reference-Chart.md (continuing from previous lesson)
+
+### Step 2: Commit Templates (2 minutes)
+
+```bash
+git add Unit-Angles-Proof/Lesson-Transformations-Transversals/
+git commit -m "Lesson setup: Transformations and Transversals templates ready"
+git push origin main
+```
+
+### Step 3: Prepare Materials (5 minutes)
+
+**Physical:**
+- [ ] Transparencies or patty paper (for demonstrating transformations)
+- [ ] Pre-drawn transversal diagrams
+- [ ] Protractors (optional - for verification)
+- [ ] Class reference chart display
+
+**Digital:**
+- [ ] GeoGebra or other geometry software (optional)
+- [ ] Transformation applets (if available)
+
+---
+
+## Lesson Timeline (50 minutes)
+
+### Opening (5 minutes)
+
+**Student arrival - display on board:**
+```
+BEFORE WE START:
+1. cd ~/Documents/ClassWork/geometry-class
+2. git pull origin main
+3. cd Unit-Angles-Proof/Lesson-Transformations-Transversals
+4. Open Warmup-Transformation-Review.md
+```
+
+**Quick check:**
+- Students synced
+- Can access files
+- Remember previous lesson (Triangle Angle Sum)
+
+---
+
+### Warm-up: Transformation Review (10 min)
+
+**[0-2 min]** Introduce warm-up
+- "Which transformations preserve angle measures?"
+- Connect to angle proofs
+- Open Warmup-Transformation-Review.md
+
+**[2-8 min]** Students work
+- Review translations, rotations, reflections
+- Identify which preserve angles (all rigid transformations do!)
+- Predict how transformations help with parallel lines
+
+**Monitor:**
+```bash
+git fetch --all
+git log --all --since="5 min ago" --oneline
+```
+
+**[8-10 min]** Brief discussion
+- All rigid transformations preserve angles
+- We'll use rotation to prove alternate interior angles
+- Students commit
+
+---
+
+### Activity 1: Alternate Interior Angles (15 min)
+
+**[10-11 min]** Introduce Activity 1
+- Parallel lines cut by transversal
+- Identify alternate interior angles
+- Open Activity1-Alternate-Interior-Angles.md
+
+**[11-23 min]** Students work (3 parts)
+
+**Part 1 (5 min):** Identify alternate interior angles
+- Interior angles vs. exterior
+- Alternate = opposite sides of transversal
+- "Z" pattern
+
+**Part 2 (5 min):** Use transformation
+- 180° rotation around midpoint
+- Maps one angle onto the other
+- Shows angles are congruent
+
+**Mid-activity commit [~16 min]:**
+```
+"If you've identified the transformation, commit now!"
+```
+
+**Part 3 (5 min):** Write formal proof
+- Given/Prove format
+- Step-by-step with justifications
+- Conclusion
+
+**Access for diverse abilities:**
+- Physical manipulatives (transparencies)
+- Draw transformation
+- Partner discussion allowed
+
+**[23-25 min]** Share proofs
+- How did you use transformations?
+- Alternative: Triangle Angle Sum method
+- Final commit
+
+---
+
+### Activity 2: Other Angle Relationships (15 min)
+
+**[25-26 min]** Transition
+- "Now prove corresponding angles and same-side interior angles"
+- Open Activity2-Angle-Relationships.md
+
+**[26-38 min]** Students prove both relationships
+
+**Corresponding Angles (7 min):**
+- Identify the pattern ("F" shape)
+- Conjecture: congruent
+- Prove using alternate interior + linear pair
+
+**Same-Side Interior Angles (7 min):**
+- Identify the pattern ("C" shape)
+- Conjecture: supplementary
+- Prove using alternate interior OR Triangle Angle Sum!
+
+**Key teaching point:**
+"Can you use last lesson's Triangle Angle Sum Theorem here?"
+
+**[38-40 min]** Quick discussion
+- How are theorems connected?
+- Which depends on which?
+- Summary table
+
+**[40 min]** Commit Activity 2
+
+---
+
+### Activity 3: Complex Diagrams (10 min) *[Optional/Flexible]*
+
+**Note:** Depending on pacing, this might be abbreviated or homework.
+
+**[40-41 min]** Introduce
+- "Now use ALL the theorems together"
+- Open Activity3-Complex-Diagrams.md
+
+**[41-48 min]** Students work
+- Multi-step angle finding
+- Triangle in transversal diagram
+- Proof with multiple theorems
+
+**Differentiation:**
+- Struggling: Do Problem 1 only (guided)
+- On-pace: Problems 1-2
+- Advanced: All problems + create own
+
+**[48 min]** Commit Activity 3
+
+---
+
+### Lesson Synthesis (3 min)
+
+**[48-50 min]** Update Reference Chart
+- Add all three transversal theorems
+- Connection to Triangle Angle Sum
+- Summary table of angle relationships
+
+**[50 min]** Commit reference chart
+
+---
+
+### Cool-down (5 min) *[Overlaps with synthesis if needed]*
+
+**[50-54 min]** Individual exit ticket
+- Complex diagram
+- Find all angles using multiple theorems
+- Check work
+
+**[54-55 min]** Submit with tag
+```bash
+git commit -m "Cool-down complete (EXIT TICKET)"
+git tag -a lesson-transformations-complete-$(date +%Y%m%d) -m "Complete"
+git push origin main --tags
+```
+
+**Optional mastery readiness tag:**
+```bash
+git tag -a mastery-angles-proof-ready -m "Ready for mastery check"
+```
+
+---
+
+## After Class (15 minutes)
+
+### Review Student Work
+
+```bash
+# Pull all student work
+git fetch --all
+
+# Check completion
+git tag -l "lesson-transformations-complete-*" | wc -l
+
+# Check mastery readiness tags
+git tag -l "mastery-angles-proof-ready"
+
+# Spot-check cool-downs
+git show student-name/main:Unit-Angles-Proof/Lesson-Transformations-Transversals/Cooldown-Proof-Challenge.md
+```
+
+### Assess Mastery Readiness
+
+**For students who tagged as ready:**
+
+1. **Check both lessons:**
+   - One Hundred Eighty cool-down
+   - Transformations cool-down
+   - Reference chart completeness
+
+2. **Review commit history:**
+   - Consistent work?
+   - Good engagement?
+   - Understanding evident?
+
+3. **Decision:**
+   - **Ready:** Grant access to mastery check
+   - **Review needed:** Provide feedback, suggest areas to review
+
+**Feedback template:**
+```bash
+cat > Unit-Angles-Proof/Mastery-Check-Readiness-Feedback.md <<EOF
+# Mastery Check Readiness - [Student Name]
+
+## Lessons Reviewed:
+✓ One Hundred Eighty (Triangle Angle Sum)
+✓ Transformations, Transversals
+
+## Readiness Assessment:
+- Triangle Angle Sum understanding: [Strong/Good/Needs review]
+- Transversal angle relationships: [Strong/Good/Needs review]
+- Multi-step problem solving: [Strong/Good/Needs review]
+- Proof writing: [Strong/Good/Needs review]
+
+## Decision:
+[✓] READY for mastery check! Access granted to Mastery-Check-Angles-Proof.md
+[ ] REVIEW suggested - see below
+
+## Areas to Review (if any):
+
+## When ready:
+Pull the latest from main to access the mastery check.
+EOF
+
+git add Unit-Angles-Proof/Mastery-Check-Readiness-Feedback.md
+git commit -m "Mastery readiness feedback for [Student Name]"
+git push origin student-name/main
+```
+
+---
+
+## Grading This Lesson
+
+### Process (Participation - 40%)
+
+**Check commits:**
+```bash
+git log student-name/main --since="lesson-date" --oneline | wc -l
+# Expected: 5-7 commits
+```
+
+**Rubric:**
+- 6+ commits with good messages: Full credit
+- 4-5 commits: Proficient
+- 2-3 commits: Developing
+- 0-1 commits: Incomplete
+
+### Product (Understanding - 60%)
+
+**Cool-down (Exit Ticket):**
+- Correct angle calculations: ___/5 points
+- Correct theorem application: ___/3 points
+- Work shown clearly: ___/2 points
+**Total: ___/10 points**
+
+**Review via:**
+```bash
+git show student-name:path/to/Cooldown-Proof-Challenge.md
+```
+
+---
+
+## Differentiation
+
+### Struggling Students
+
+**Scaffolding provided in templates:**
+- Step-by-step sections
+- Sentence frames
+- Visual prompts
+
+**Additional support:**
+```bash
+# Add hints to their file
+git checkout student-name/main
+# Edit Activity1 to add guiding questions
+git commit -m "Added scaffolding for [name]"
+git push origin student-name/main
+```
+
+### Advanced Students
+
+**Extensions:**
+- Activity 3 Problem 4: Create own problem
+- Prove ALL five angle relationships
+- Peer teaching (extra credit)
+
+**Track:**
+```bash
+git log --all --grep="peer\|create\|extension"
+```
+
+---
+
+## Common Issues
+
+### "I don't understand alternate vs. corresponding"
+
+**Solution:**
+- Use physical models (transparencies)
+- Draw multiple examples
+- Focus on patterns: Z, F, C shapes
+- Reference chart has table
+
+### "I can't remember Triangle Angle Sum"
+
+**Solution:**
+```bash
+# Student reviews previous lesson
+git show HEAD~1:../Lesson-One-Hundred-Eighty/Cooldown-Third-Proof.md
+# Or reference chart
+```
+
+### "Too many theorems - I'm confused"
+
+**Solution:**
+- Focus on alternate interior first
+- Show how others derive from it
+- Build systematically
+- Use summary table in Activity 2
+
+---
+
+## Connection to Mastery Check
+
+**Mastery check will assess:**
+1. **Triangle Angle Sum (Lesson 1)**
+   - Prove it
+   - Apply it
+
+2. **Transversal Theorems (Lesson 2)**
+   - Identify angle pairs
+   - Apply correct theorem
+   - Find missing angles
+
+3. **Combined Application**
+   - Multi-step problems
+   - Proof writing
+   - Justification
+
+**Students are ready when:**
+- Both cool-downs show understanding
+- Reference chart is complete
+- Can apply theorems independently
+- Proof writing is clear
+
+---
+
+## Mastery Check Access Protocol
+
+### When Student Tags Readiness
+
+1. **Review their work** (both lessons)
+2. **Provide feedback** (template above)
+3. **If ready:**
+   ```bash
+   # Add mastery check to their folder
+   cp Mastery-Check-Angles-Proof.md Unit-Angles-Proof/
+   git add Unit-Angles-Proof/Mastery-Check-Angles-Proof.md
+   git commit -m "Mastery check: Access granted for [Student Name]"
+   git push origin student-name/main
+   ```
+
+4. **Notify student:** "Pull from main - your mastery check is ready!"
+
+### Managing Different Paces
+
+**Fast students:**
+- Take mastery check as early as tomorrow
+- Work ahead on next unit while others catch up
+- Peer teaching opportunities
+
+**On-pace students:**
+- Review day between lessons and mastery check
+- Take check in 2-3 days
+
+**Slower students:**
+- Extra practice problems
+- Review sessions
+- Take check when ready (no rush)
+
+---
+
+## Next Lesson Options
+
+**If most students are ready:**
+- Review day (optional)
+- Begin mastery checks
+- Students who pass: Start next unit
+
+**If students need more time:**
+- Extra practice day
+- Small group instruction
+- More complex problems
+
+**Self-paced advantage:**
+- Students work at own pace
+- Git shows who's where
+- Differentiation is natural
+
+---
+
+## Quick Reference: Commands
+
+```bash
+# SETUP
+git add Unit-Angles-Proof/Lesson-Transformations-Transversals/
+git commit -m "Lesson setup"
+git push origin main
+
+# MONITOR
+git fetch --all
+git log --all --since="10 min ago" --oneline
+
+# CHECK COMPLETION
+git tag -l "lesson-transformations-complete-*"
+git tag -l "mastery-angles-proof-ready"
+
+# REVIEW WORK
+git show student-name:path/to/Cooldown-Proof-Challenge.md
+
+# GRANT MASTERY ACCESS
+cp Mastery-Check-Angles-Proof.md Unit-Angles-Proof/
+git add Unit-Angles-Proof/Mastery-Check-Angles-Proof.md
+git commit -m "Mastery check access for [Student]"
+git push origin student-name/main
+```
+
+---
+
+**You're ready to teach! This lesson builds perfectly on the previous one.**
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/templates-mastery/Mastery-Check-Angles-Proof.md b/classroom/lessons/templates-mastery/Mastery-Check-Angles-Proof.md
new file mode 100644
index 0000000..64ab845
--- /dev/null
+++ b/classroom/lessons/templates-mastery/Mastery-Check-Angles-Proof.md
@@ -0,0 +1,641 @@
+# Mastery Check: Angles and Proof
+**Name:** _________________
+**Date:** _________________
+**Time Started:** _______
+**Time Ended:** _______
+
+---
+
+## Instructions
+
+**Time Allowed:** 40 minutes (or your accommodated time)
+**Resources Allowed:**
+- [ ] Your Reference Chart (if teacher permits)
+- [ ] Blank paper for scratch work
+- [ ] Straightedge and protractor
+
+**Not Allowed:**
+- Notes from lessons (except reference chart)
+- Collaboration with other students
+- Calculator (not needed)
+
+**Submitting:**
+1. Complete all problems
+2. Show ALL work
+3. Justify each step
+4. Commit and tag when complete (instructions at end)
+
+---
+
+## Section 1: Triangle Angle Sum Theorem (20 points)
+
+### Problem 1: Basic Application (4 points)
+
+Find the missing angle in the triangle.
+
+```
+Triangle ABC:
+∠A = 68°
+∠B = 47°
+∠C = ?
+
+
+
+
+```
+
+**My work:**
+
+
+
+
+**Answer:** ∠C = _____°
+
+---
+
+### Problem 2: Proving the Theorem (8 points)
+
+**Prove:** The sum of the measures of the angles in a triangle is 180°.
+
+**Given:** Triangle ABC with angles ∠A, ∠B, and ∠C
+
+**Prove:** m∠A + m∠B + m∠C = 180°
+
+**My Proof:**
+*(Choose any method you learned - auxiliary line, paper folding, rotation, etc.)*
+
+**Diagram:**
+```
+[Draw your triangle and any auxiliary elements]
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+**Step 1:**
+
+
+
+
+**Justification:**
+
+
+
+
+---
+
+**Step 2:**
+
+
+
+
+**Justification:**
+
+
+
+
+---
+
+**Step 3:**
+
+
+
+
+**Justification:**
+
+
+
+
+---
+
+**Step 4:** *(if needed)*
+
+
+
+
+**Justification:**
+
+
+
+
+---
+
+**Conclusion:**
+
+
+
+
+---
+
+### Problem 3: Application with Algebra (8 points)
+
+In triangle DEF:
+- ∠D = x°
+- ∠E = (2x + 10)°
+- ∠F = (x - 30)°
+
+**Find:** The measure of each angle.
+
+**My work:**
+
+**Step 1:** Set up equation using Triangle Angle Sum Theorem
+
+
+
+
+---
+
+**Step 2:** Solve for x
+
+
+
+
+---
+
+**Step 3:** Find each angle measure
+
+∠D = _____°
+
+∠E = _____°
+
+∠F = _____°
+
+---
+
+**Step 4:** Check my answer
+
+Verification:
+
+
+
+
+---
+
+## Section 2: Transversal Angle Relationships (30 points)
+
+### Problem 4: Identifying Angle Pairs (6 points)
+
+```
+Diagram: Parallel lines l and m cut by transversal t
+[Diagram with 8 angles labeled 1-8]
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+**Given:** l ∥ m
+
+**Identify:**
+
+**a) Alternate interior angles:** (2 points)
+
+Pair 1: ∠___ and ∠___
+Pair 2: ∠___ and ∠___
+
+**b) Corresponding angles:** (2 points)
+
+Pair 1: ∠___ and ∠___
+Pair 2: ∠___ and ∠___
+
+**c) Same-side interior angles:** (2 points)
+
+Pair 1: ∠___ and ∠___
+Pair 2: ∠___ and ∠___
+
+---
+
+### Problem 5: Applying Theorems (8 points)
+
+Using the same diagram from Problem 4:
+
+**Given:**
+- l ∥ m
+- ∠1 = 112°
+
+**Find:** All other angles (∠2 through ∠8)
+
+Show your work and state which theorem you use for each angle.
+
+**∠2 = _____°**
+Theorem used:
+Justification:
+
+---
+
+**∠3 = _____°**
+Theorem used:
+Justification:
+
+---
+
+**∠4 = _____°**
+Theorem used:
+Justification:
+
+---
+
+**∠5 = _____°**
+Theorem used:
+Justification:
+
+---
+
+**∠6 = _____°**
+Theorem used:
+Justification:
+
+---
+
+**∠7 = _____°**
+Theorem used:
+Justification:
+
+---
+
+**∠8 = _____°**
+Theorem used:
+Justification:
+
+---
+
+### Problem 6: Proving a Theorem (10 points)
+
+**Prove:** If two parallel lines are cut by a transversal, then corresponding angles are congruent.
+
+**Given:** Lines l and m are parallel (l ∥ m), cut by transversal t
+
+**Prove:** Corresponding angles are congruent (choose one pair: ∠1 ≅ ∠5)
+
+**Diagram:**
+```
+[Draw and label your diagram]
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+**My Proof:**
+
+**Step 1:**
+
+
+
+
+**Justification:**
+
+
+
+
+---
+
+**Step 2:**
+
+
+
+
+**Justification:**
+
+
+
+
+---
+
+**Step 3:**
+
+
+
+
+**Justification:**
+
+
+
+
+---
+
+**Conclusion:**
+
+
+
+
+---
+
+### Problem 7: Same-Side Interior Angles (6 points)
+
+**Given:**
+- Lines l and m are parallel
+- Transversal t creates same-side interior angles ∠3 and ∠5
+- ∠3 = (3x + 15)°
+- ∠5 = (2x + 25)°
+
+**Find:** The value of x and the measure of each angle.
+
+**My work:**
+
+**Step 1:** Set up equation
+
+
+
+
+---
+
+**Step 2:** Solve for x
+
+
+
+
+---
+
+**Step 3:** Find each angle
+
+∠3 = _____°
+
+∠5 = _____°
+
+---
+
+**Step 4:** Verify
+
+∠3 + ∠5 = _____° *(Should be 180°)*
+
+---
+
+## Section 3: Combined Application (30 points)
+
+### Problem 8: Complex Diagram (15 points)
+
+```
+Diagram:
+- Parallel lines l and m
+- Transversal t intersects l at point A and m at point B
+- Point C is on line m
+- Triangle ABC is formed
+- ∠1 (exterior to triangle at A) = 125°
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+**Given:**
+- l ∥ m
+- ∠1 = 125° (exterior angle at vertex A)
+- ∠BCA = 32°
+
+**Find:** All angles in triangle ABC
+
+**∠CAB = _____°**
+
+**My work:**
+
+
+
+
+**Theorem(s) used:**
+
+
+
+
+---
+
+**∠ABC = _____°**
+
+**My work:**
+
+
+
+
+**Theorem(s) used:**
+
+
+
+
+---
+
+**∠BCA = 32°** (given)
+
+**Verification using Triangle Angle Sum:**
+
+
+
+
+---
+
+### Problem 9: Multi-Step Proof (15 points)
+
+**Given:**
+- Lines l and m are parallel (l ∥ m)
+- Transversal t intersects l at point P and m at point Q
+- Point R is on line l (not at P)
+- Triangle PQR is formed
+- ∠QPR = 55°
+
+**Prove:** Find m∠PQR if ∠QRP = 70°, and prove your answer using both Triangle Angle Sum and transversal theorems.
+
+**Diagram:**
+```
+[Draw and label your complete diagram]
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+**My Solution and Proof:**
+
+**Part A:** Find m∠PQR using Triangle Angle Sum Theorem
+
+**Work:**
+
+
+
+
+**Answer:** m∠PQR = _____°
+
+---
+
+**Part B:** Verify using transversal theorems
+
+**Identify alternate interior or corresponding angles:**
+
+
+
+
+**Use theorem:**
+
+
+
+
+**Verification:**
+
+
+
+
+---
+
+**Conclusion:**
+
+Both methods give m∠PQR = _____°, confirming our answer. ✓
+
+---
+
+## Section 4: Reflection and Self-Assessment (5 points)
+
+### Problem 10: Metacognition (5 points)
+
+**a) Which problem was hardest for you? Why?** (2 points)
+
+
+
+
+---
+
+**b) Which theorem do you understand best? Explain why it makes sense.** (2 points)
+
+
+
+
+---
+
+**c) If you could revise one answer, which would it be and why?** (1 point)
+
+
+
+
+---
+
+## Total Points Summary
+
+| Section | Points Earned | Points Possible |
+|---------|---------------|-----------------|
+| Section 1: Triangle Angle Sum | ___/20 | 20 |
+| Section 2: Transversal Angles | ___/30 | 30 |
+| Section 3: Combined Application | ___/30 | 30 |
+| Section 4: Reflection | ___/5 | 5 |
+| **TOTAL** | **___/85** | **85** |
+
+---
+
+## Mastery Level
+
+Your mastery level is determined by your total score:
+
+| Score | Level | What It Means |
+|-------|-------|---------------|
+| 75-85 | **Mastery (4)** | Excellent understanding! Move to next unit |
+| 65-74 | **Proficient (3)** | Good understanding! Move on or revise for mastery |
+| 55-64 | **Developing (2)** | Getting there - revision required |
+| Below 55 | **Beginning (1)** | Need more practice - review and resubmit |
+
+---
+
+## Submission Instructions
+
+### When You're Finished
+
+**Step 1:** Make sure all work is shown and clear
+
+**Step 2:** Commit your mastery check
+```bash
+git add Mastery-Check-Angles-Proof.md
+git commit -m "Mastery Check: Angles and Proof COMPLETE - Ready for grading"
+```
+
+**Step 3:** Create submission tag
+```bash
+git tag -a mastery-angles-proof-submit-$(date +%Y%m%d) -m "Angles and Proof Mastery Check Submission"
+```
+
+**Step 4:** Push everything
+```bash
+git push origin main --tags
+```
+
+**Step 5:** Notify your teacher (method they specified)
+
+---
+
+## After Grading
+
+Your teacher will provide feedback in: `Mastery-Check-Angles-Proof-FEEDBACK.md`
+
+To see your feedback:
+```bash
+git pull origin main
+cat Mastery-Check-Angles-Proof-FEEDBACK.md
+```
+
+**If you scored Developing (2) or Beginning (1):**
+- You can revise for a higher score
+- Review feedback carefully
+- Use revision workflow (see MASTERY_CHECK_GUIDE.md)
+
+**If you scored Proficient (3) or Mastery (4):**
+- Congratulations! Move to next unit
+- You may still revise for a higher score if you wish
+
+---
+
+## Academic Honesty Pledge
+
+By submitting this mastery check, I affirm that:
+- This work is entirely my own
+- I did not collaborate with other students
+- I only used permitted resources
+- I understand the consequences of academic dishonesty
+
+**Signature:** ___________________ **Date:** ___________
+
+---
+
+**Last Updated:** 2025-11-16
+**Unit:** Angles and Proof
+**Lessons Covered:** One Hundred Eighty, Transformations and Transversals
diff --git a/classroom/lessons/templates-transformations/Activity1-Alternate-Interior-Angles.md b/classroom/lessons/templates-transformations/Activity1-Alternate-Interior-Angles.md
new file mode 100644
index 0000000..1728e14
--- /dev/null
+++ b/classroom/lessons/templates-transformations/Activity1-Alternate-Interior-Angles.md
@@ -0,0 +1,277 @@
+# Activity 1: Alternate Interior Angles
+**Name:** _________________
+**Date:** _________________
+**Lesson:** Transformations, Transversals and Proof
+
+---
+
+## The Diagram
+
+```
+Draw or paste your diagram here:
+- Two parallel lines (l and m)
+- One transversal (t)
+- Label the 8 angles formed
+
+
+
+
+
+
+
+
+
+
+
+```
+
+**My diagram shows:**
+- Line l (parallel line 1)
+- Line m (parallel line 2)
+- Line t (transversal)
+- 8 angles created
+
+---
+
+## Part 1: Identifying Alternate Interior Angles
+
+### What are "interior" angles?
+
+**Interior angles** are angles that are BETWEEN the two parallel lines.
+
+**In my diagram, the interior angles are:** ∠___, ∠___, ∠___, ∠___
+
+---
+
+### What are "alternate" interior angles?
+
+**Alternate interior angles** are:
+- On OPPOSITE sides of the transversal
+- Both INTERIOR (between the parallel lines)
+- Form a "Z" pattern or backwards "Z"
+
+**In my diagram, the alternate interior angle pairs are:**
+
+**Pair 1:** ∠___ and ∠___
+**Pair 2:** ∠___ and ∠___
+
+---
+
+## Part 2: Using Transformations
+
+### Exploring the relationship
+
+**Choose one pair of alternate interior angles:** ∠___ and ∠___
+
+**What transformation maps one angle onto the other?**
+- [ ] Translation
+- [ ] Rotation (If so, around what point? By how many degrees?)
+- [ ] Reflection
+- [ ] Combination
+
+**Describe the transformation in detail:**
+
+
+
+
+
+
+**Why does this transformation work?**
+
+
+
+
+
+
+---
+
+### What does this tell us?
+
+**If the transformation preserves angle measures, then:**
+
+
+
+
+**Therefore, my conjecture is:**
+
+∠___ ≅ ∠___ because...
+
+
+
+
+---
+
+## Part 3: Formal Proof
+
+**Theorem to Prove:** If two parallel lines are cut by a transversal, then alternate interior angles are congruent.
+
+### Given:
+Lines l and m are parallel (l ∥ m)
+Transversal t intersects both lines
+
+### Prove:
+Alternate interior angles are congruent
+Specifically: ∠___ ≅ ∠___
+
+---
+
+### My Proof
+
+**Method: Using Transformations**
+
+**Step 1:** Consider a 180° rotation around point ___ (the midpoint of the segment connecting the two angles' vertices on the transversal)
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Step 2:** Under this rotation:
+- Line l maps to ___
+- Line m maps to ___
+- Transversal t maps to ___
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Step 3:** The rotation maps ∠___ to ∠___
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Step 4:** Since rotations preserve angle measures:
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Conclusion:**
+
+Therefore, ∠___ ≅ ∠___
+
+This proves that alternate interior angles are congruent when parallel lines are cut by a transversal. ∎
+
+---
+
+## Part 4: Alternative Proof Method
+
+**Can you prove this using the Triangle Angle Sum Theorem instead?**
+
+**Hint:** Create a triangle using the parallel lines and transversal.
+
+**My attempt:**
+
+
+
+
+
+
+
+
+
+
+
+**Which method do I prefer?**
+- [ ] Transformation method
+- [ ] Triangle method
+- [ ] Both are equally clear
+
+**Why:**
+
+
+
+
+---
+
+## Part 5: Check My Understanding
+
+### Practice Problem 1
+
+```
+[Diagram with parallel lines, transversal, and one angle marked 65°]
+```
+
+**If ∠1 = 65° and ∠1 and ∠5 are alternate interior angles, then:**
+
+∠5 = ____°
+
+**My reasoning:**
+
+
+
+
+---
+
+### Practice Problem 2
+
+```
+[Diagram with parallel lines, transversal, and one angle marked 110°]
+```
+
+**Find all the alternate interior angles:**
+
+∠___ and ∠___ are alternate interior angles
+If one measures 110°, the other measures ____°
+
+∠___ and ∠___ are alternate interior angles
+If one measures ___°, the other measures ____°
+
+---
+
+## Reflection
+
+**What I learned:**
+
+
+
+
+**What I'm still wondering:**
+
+
+
+
+**How confident am I with alternate interior angles?**
+- [ ] Very confident - I could teach this!
+- [ ] Confident - I understand it
+- [ ] Somewhat confident - I get the idea but need practice
+- [ ] Not confident - I need help
+
+---
+
+**Commit checkpoints:**
+```bash
+# After Part 2:
+git add Activity1-Alternate-Interior-Angles.md
+git commit -m "Activity 1: Identified angles and transformation"
+git push origin main
+
+# After Part 3:
+git add Activity1-Alternate-Interior-Angles.md
+git commit -m "Activity 1: Completed formal proof"
+git push origin main
+```
diff --git a/classroom/lessons/templates-transformations/Activity2-Angle-Relationships.md b/classroom/lessons/templates-transformations/Activity2-Angle-Relationships.md
new file mode 100644
index 0000000..c188aaf
--- /dev/null
+++ b/classroom/lessons/templates-transformations/Activity2-Angle-Relationships.md
@@ -0,0 +1,335 @@
+# Activity 2: Other Angle Relationships
+**Name:** _________________
+**Date:** _________________
+**Lesson:** Transformations, Transversals and Proof
+
+---
+
+## Overview
+
+In Activity 1, we proved that **alternate interior angles** are congruent.
+
+Now we'll prove relationships for:
+1. Corresponding angles
+2. Same-side interior angles (also called consecutive interior angles)
+
+---
+
+## Relationship 1: Corresponding Angles
+
+### Identifying Corresponding Angles
+
+**Corresponding angles** are:
+- On the SAME side of the transversal
+- One is INTERIOR, one is EXTERIOR
+- One is ABOVE the top parallel line, the other is ABOVE the bottom parallel line (or both below)
+- Form an "F" pattern or backwards "F"
+
+**In my diagram from Activity 1:**
+
+```
+[Redraw or reference your diagram]
+
+
+
+
+
+
+
+
+
+```
+
+**Corresponding angle pairs are:**
+
+Pair 1: ∠___ and ∠___
+Pair 2: ∠___ and ∠___
+Pair 3: ∠___ and ∠___
+Pair 4: ∠___ and ∠___
+
+---
+
+### My Conjecture
+
+**I think corresponding angles are:** (check one)
+- [ ] Congruent (equal)
+- [ ] Supplementary (sum to 180°)
+- [ ] Neither
+
+**My reasoning:**
+
+
+
+
+---
+
+### Proof: Corresponding Angles Theorem
+
+**Theorem:** If two parallel lines are cut by a transversal, then corresponding angles are congruent.
+
+**Given:** l ∥ m, transversal t
+
+**Prove:** ∠___ ≅ ∠___ (choose one pair of corresponding angles)
+
+---
+
+**My Proof:**
+
+**Strategy:** I will use what I know about alternate interior angles and other angle relationships.
+
+**Step 1:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Step 2:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Step 3:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Conclusion:**
+
+
+
+
+---
+
+### Practice with Corresponding Angles
+
+```
+[Diagram with parallel lines and transversal]
+```
+
+If ∠1 = 73° and ∠1 and ∠5 are corresponding angles, then:
+
+∠5 = ____°
+
+**Justification:**
+
+
+
+
+---
+
+## Relationship 2: Same-Side Interior Angles
+
+### Identifying Same-Side Interior Angles
+
+**Same-side interior angles** (also called consecutive interior angles) are:
+- On the SAME side of the transversal
+- Both INTERIOR (between the parallel lines)
+- Form a "C" pattern or backwards "C"
+
+**In my diagram:**
+
+**Same-side interior angle pairs are:**
+
+Pair 1: ∠___ and ∠___
+Pair 2: ∠___ and ∠___
+
+---
+
+### My Conjecture
+
+**I think same-side interior angles are:** (check one)
+- [ ] Congruent (equal)
+- [ ] Supplementary (sum to 180°)
+- [ ] Neither
+
+**My reasoning:**
+
+
+
+
+**Test my conjecture:**
+If ∠3 = 110°, and ∠3 and ∠5 are same-side interior angles, then:
+∠5 = ____°
+∠3 + ∠5 = ____°
+
+---
+
+### Proof: Same-Side Interior Angles Theorem
+
+**Theorem:** If two parallel lines are cut by a transversal, then same-side interior angles are supplementary.
+
+**Given:** l ∥ m, transversal t
+
+**Prove:** ∠___ + ∠___ = 180° (choose one pair)
+
+---
+
+**My Proof:**
+
+**Strategy:** I will use:
+- [ ] Alternate interior angles theorem (from Activity 1)
+- [ ] Linear pairs
+- [ ] Triangle Angle Sum Theorem (from last lesson!)
+- [ ] Other: _______________
+
+**Step 1:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Step 2:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Step 3:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+**Conclusion:**
+
+
+
+
+---
+
+### Practice with Same-Side Interior Angles
+
+```
+[Diagram with parallel lines and transversal]
+```
+
+If ∠3 = 68° and ∠3 and ∠5 are same-side interior angles, then:
+
+∠5 = ____°
+
+**Work:**
+∠3 + ∠5 = 180° (same-side interior angles are supplementary)
+68° + ∠5 = 180°
+∠5 = ____°
+
+---
+
+## Summary Table
+
+| Angle Relationship | Location | Are they... | Pattern |
+|-------------------|----------|-------------|---------|
+| **Alternate Interior** | Opposite sides, interior | Congruent | Z or backwards Z |
+| **Corresponding** | Same side, one interior/one exterior | Congruent | F or backwards F |
+| **Same-Side Interior** | Same side, both interior | Supplementary | C or backwards C |
+
+---
+
+## Comparing Relationships
+
+### How are these theorems connected?
+
+**If I know alternate interior angles are congruent, can I prove corresponding angles are congruent?**
+
+
+
+
+**If I know alternate interior angles are congruent, can I prove same-side interior angles are supplementary?**
+
+
+
+
+**Which theorem is the "foundation" that others depend on?**
+
+
+
+
+---
+
+### Using Multiple Theorems Together
+
+**Problem:** Find the missing angle.
+
+```
+[Complex diagram with multiple angle relationships]
+```
+
+∠1 = 55°
+∠2 = ____° (Why: _______________)
+∠3 = ____° (Why: _______________)
+∠4 = ____° (Why: _______________)
+
+---
+
+## Reflection
+
+**Today I proved:**
+- [ ] Corresponding Angles Theorem
+- [ ] Same-Side Interior Angles Theorem
+- [ ] Both!
+
+**The proof that was hardest:**
+
+
+
+
+**The proof that made the most sense:**
+
+
+
+
+**How I used last lesson's Triangle Angle Sum Theorem:**
+
+
+
+
+**I'm feeling:** (check one)
+- [ ] Confident with all angle relationships
+- [ ] Good with most, need practice on: ___________
+- [ ] Overwhelmed - need to review
+
+---
+
+**Commit your work:**
+```bash
+git add Activity2-Angle-Relationships.md
+git commit -m "Activity 2: Proved angle relationships with transversals"
+git push origin main
+```
diff --git a/classroom/lessons/templates-transformations/Activity3-Complex-Diagrams.md b/classroom/lessons/templates-transformations/Activity3-Complex-Diagrams.md
new file mode 100644
index 0000000..1216528
--- /dev/null
+++ b/classroom/lessons/templates-transformations/Activity3-Complex-Diagrams.md
@@ -0,0 +1,441 @@
+# Activity 3: Complex Diagrams
+**Name:** _________________
+**Date:** _________________
+**Lesson:** Transformations, Transversals and Proof
+
+---
+
+## Overview
+
+Now you'll apply MULTIPLE theorems to solve complex problems:
+- Triangle Angle Sum Theorem (from last lesson)
+- Alternate Interior Angles Theorem
+- Corresponding Angles Theorem
+- Same-Side Interior Angles Theorem
+
+**Strategy:** Work step-by-step, justify each step with a theorem!
+
+---
+
+## Problem 1: Multi-Step Angle Finding
+
+### The Diagram
+
+```
+[Diagram showing:
+- Two parallel lines
+- One transversal
+- One angle marked 115°
+- Several angles to find labeled a, b, c, d, e]
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+---
+
+### Given Information
+
+- Lines l and m are parallel (l ∥ m)
+- ∠1 = 115°
+
+---
+
+### Find All Missing Angles
+
+**∠a = ____°**
+
+**Step:**
+
+
+**Theorem used:**
+
+
+**Justification:**
+
+
+
+
+---
+
+**∠b = ____°**
+
+**Step:**
+
+
+**Theorem used:**
+
+
+**Justification:**
+
+
+
+
+---
+
+**∠c = ____°**
+
+**Step:**
+
+
+**Theorem used:**
+
+
+**Justification:**
+
+
+
+
+---
+
+**∠d = ____°**
+
+**Step:**
+
+
+**Theorem used:**
+
+
+**Justification:**
+
+
+
+
+---
+
+**∠e = ____°**
+
+**Step:**
+
+
+**Theorem used:**
+
+
+**Justification:**
+
+
+
+
+---
+
+### Check My Work
+
+**Do all the angles make sense?**
+- [ ] Alternate interior angles are congruent ✓
+- [ ] Corresponding angles are congruent ✓
+- [ ] Same-side interior angles sum to 180° ✓
+- [ ] Linear pairs sum to 180° ✓
+
+---
+
+## Problem 2: Triangle in a Transversal Diagram
+
+### The Diagram
+
+```
+[Diagram showing:
+- Two parallel lines l and m
+- Transversal t creates a triangle
+- One angle of the triangle is marked 45°
+- Find all angles in the triangle and around it]
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+---
+
+### Given Information
+
+- l ∥ m
+- ∠A = 45° (one angle in the triangle)
+- The triangle is formed by the parallel lines and transversal
+
+---
+
+### Find the Triangle's Angles
+
+**∠A = 45°** (given)
+
+**∠B = ____°**
+
+**My work:**
+- First, I need to find _______
+- Using ____________ theorem:
+- Therefore, ∠B = ____°
+
+---
+
+**∠C = ____°**
+
+**My work:**
+- Now I can use Triangle Angle Sum Theorem!
+- ∠A + ∠B + ∠C = 180°
+- 45° + ___° + ∠C = 180°
+- ∠C = ____°
+
+---
+
+### Check Using Another Method
+
+**Can I find ∠C a different way using transversal theorems?**
+
+**Alternative method:**
+
+
+
+
+**Result:** ∠C = ____°
+
+**Does it match?**
+- [ ] Yes! ✓
+- [ ] No - I need to find my error
+
+---
+
+## Problem 3: Proof with Multiple Theorems
+
+### The Challenge
+
+**Given:**
+- Lines l and m are parallel (l ∥ m)
+- Transversal t intersects both lines
+- Point P is where the transversal meets line l
+- Point Q is where the transversal meets line m
+- Point R is on line l, creating triangle PQR
+
+**Prove:** ∠QPR + ∠PQR + ∠QRP = 180°
+
+*(This proves that we can use both transversal theorems AND triangle angle sum together!)*
+
+---
+
+### My Proof
+
+**Step 1:**
+
+
+
+
+**Theorem/Definition:**
+
+
+
+
+---
+
+**Step 2:**
+
+
+
+
+**Theorem/Definition:**
+
+
+
+
+---
+
+**Step 3:**
+
+
+
+
+**Theorem/Definition:**
+
+
+
+
+---
+
+**Step 4:**
+
+
+
+
+**Theorem/Definition:**
+
+
+
+
+---
+
+**Conclusion:**
+
+
+
+
+---
+
+## Problem 4: Create Your Own
+
+### Design a Complex Problem
+
+**Your task:** Create a diagram and problem that requires using at least 3 different theorems.
+
+**My diagram:**
+```
+[Draw your diagram here]
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+---
+
+**Given information:**
+
+
+
+
+---
+
+**Question to solve:**
+
+
+
+
+---
+
+**Solution:**
+
+**Step 1:**
+
+
+**Theorem:**
+
+
+---
+
+**Step 2:**
+
+
+**Theorem:**
+
+
+---
+
+**Step 3:**
+
+
+**Theorem:**
+
+
+---
+
+**Answer:**
+
+
+
+
+---
+
+**Challenge a classmate:**
+If you want, create a peer collaboration branch and share your problem!
+
+```bash
+git checkout -b peer-challenge-problem
+git add Activity3-Complex-Diagrams.md
+git commit -m "Created challenge problem for classmates"
+git push origin peer-challenge-problem
+```
+
+---
+
+## Reflection
+
+**Today I used these theorems:** (check all that apply)
+- [ ] Triangle Angle Sum Theorem
+- [ ] Alternate Interior Angles Theorem
+- [ ] Corresponding Angles Theorem
+- [ ] Same-Side Interior Angles Theorem
+- [ ] Linear Pair (supplementary angles)
+- [ ] Vertical Angles Theorem
+
+**The hardest part was:**
+
+
+
+
+**A strategy that helped me:**
+
+
+
+
+**I'm most proud of:**
+
+
+
+
+---
+
+## Am I Ready for the Mastery Check?
+
+**Self-assessment:**
+
+**I can identify angle pairs in transversal diagrams:**
+- [ ] Yes, confidently
+- [ ] Mostly, with some review
+- [ ] Not yet
+
+**I can apply the right theorem to find missing angles:**
+- [ ] Yes, confidently
+- [ ] Mostly, with some review
+- [ ] Not yet
+
+**I can use multiple theorems in one problem:**
+- [ ] Yes, confidently
+- [ ] Mostly, with some review
+- [ ] Not yet
+
+**I can write a formal proof:**
+- [ ] Yes, confidently
+- [ ] Mostly, with some review
+- [ ] Not yet
+
+---
+
+**If you checked "Yes, confidently" for all four:**
+You're probably ready for the mastery check! Consider tagging yourself as ready.
+
+**If you have some "Mostly" or "Not yet":**
+Review those areas using your reference chart and past work. Ask for help if needed!
+
+---
+
+**Commit your work:**
+```bash
+git add Activity3-Complex-Diagrams.md
+git commit -m "Activity 3: Applied multiple theorems to complex diagrams"
+git push origin main
+```
diff --git a/classroom/lessons/templates-transformations/Cooldown-Proof-Challenge.md b/classroom/lessons/templates-transformations/Cooldown-Proof-Challenge.md
new file mode 100644
index 0000000..d8710bc
--- /dev/null
+++ b/classroom/lessons/templates-transformations/Cooldown-Proof-Challenge.md
@@ -0,0 +1,298 @@
+# Cool-down: Proof Challenge
+**Name:** _________________
+**Date:** _________________
+**Lesson:** Transformations, Transversals and Proof
+
+---
+
+## Instructions
+
+**Time:** 5 minutes
+**Work:** Individual (this is your exit ticket!)
+**Task:** Find all missing angles using the theorems from BOTH lessons
+
+---
+
+## The Problem
+
+```
+Diagram:
+- Two parallel lines l and m
+- Transversal t intersects both
+- A triangle is formed
+- One angle is marked: 52°
+
+[Draw or paste diagram here]
+
+
+
+
+
+
+
+
+
+
+
+
+
+```
+
+---
+
+## Given:
+
+- l ∥ m (lines l and m are parallel)
+- Transversal t intersects l at point A and m at point B
+- Point C is on line m, forming triangle ABC
+- ∠CAB = 52°
+
+---
+
+## Find:
+
+All missing angles labeled in the diagram:
+- ∠ABC = ?
+- ∠BCA = ?
+- ∠1 = ? (angle above ∠CAB)
+- ∠2 = ? (corresponding angle to ∠ABC)
+- ∠3 = ? (same-side interior angle with ∠ABC)
+
+---
+
+## My Solution
+
+### Step 1:
+
+**What I'm finding:**
+
+
+**Which theorem am I using?**
+
+
+**My work:**
+
+
+
+
+**Answer:**
+
+
+
+
+---
+
+### Step 2:
+
+**What I'm finding:**
+
+
+**Which theorem am I using?**
+
+
+**My work:**
+
+
+
+
+**Answer:**
+
+
+
+
+---
+
+### Step 3:
+
+**What I'm finding:**
+
+
+**Which theorem am I using?**
+
+
+**My work:**
+
+
+
+
+**Answer:**
+
+
+
+
+---
+
+### Step 4:
+
+**What I'm finding:**
+
+
+**Which theorem am I using?**
+
+
+**My work:**
+
+
+
+
+**Answer:**
+
+
+
+
+---
+
+### Step 5:
+
+**What I'm finding:**
+
+
+**Which theorem am I using?**
+
+
+**My work:**
+
+
+
+
+**Answer:**
+
+
+
+
+---
+
+## Final Answers:
+
+**∠ABC =** ____°
+
+**∠BCA =** ____°
+
+**∠1 =** ____°
+
+**∠2 =** ____°
+
+**∠3 =** ____°
+
+---
+
+## Check My Work
+
+**Verify using Triangle Angle Sum:**
+∠CAB + ∠ABC + ∠BCA = ___° + ___° + ___° = ____°
+
+**Should equal 180°:**
+- [ ] Yes! ✓
+- [ ] No - I need to find my error
+
+**Verify angle relationships:**
+- Corresponding angles are equal: ___
+- Same-side interior angles sum to 180°: ___
+- Alternate interior angles are equal: ___
+
+---
+
+## Reflection
+
+### Theorems I used today:
+- [ ] Triangle Angle Sum Theorem (from Lesson: One Hundred Eighty)
+- [ ] Alternate Interior Angles Theorem
+- [ ] Corresponding Angles Theorem
+- [ ] Same-Side Interior Angles Theorem
+- [ ] Linear Pair
+- [ ] Vertical Angles
+
+**Total different theorems used:** _____
+
+---
+
+### Which step was hardest?
+
+
+
+
+### What strategy helped me?
+
+
+
+
+---
+
+### Self-Assessment: Readiness for Mastery Check
+
+**Do I feel ready for the mastery check?**
+- [ ] Yes, definitely! I understand both lessons and can apply the theorems
+- [ ] Somewhat - I understand most but want to review ___________
+- [ ] Not yet - I need more practice with ___________
+
+**What I need to review before the mastery check:**
+
+
+
+
+**Questions I still have:**
+
+
+
+
+---
+
+### Looking Back at Both Lessons
+
+**Lesson: One Hundred Eighty**
+- I learned: Triangle Angle Sum Theorem (angles in triangle = 180°)
+- Confidence level: ___/5
+
+**Lesson: Transformations, Transversals**
+- I learned: Angle relationships with parallel lines and transversals
+- Confidence level: ___/5
+
+**Using them together:**
+- I can apply multiple theorems in one problem
+- Confidence level: ___/5
+
+---
+
+## Next Steps
+
+**If you feel ready for the mastery check:**
+- Review your Reference Chart
+- Look over your work from both lessons
+- Tag yourself as ready (see below)
+
+**If you need more practice:**
+- Review activities from both lessons
+- Ask your teacher for extra practice problems
+- Work with a study group (use peer collaboration branch!)
+
+---
+
+**IMPORTANT: Submit this as your exit ticket!**
+
+```bash
+git add Cooldown-Proof-Challenge.md
+git commit -m "Cool-down: Completed proof challenge (EXIT TICKET)"
+git tag -a lesson-transformations-complete-$(date +%Y%m%d) -m "Lesson complete"
+git push origin main --tags
+```
+
+---
+
+## Optional: Signal Readiness for Mastery Check
+
+**If you feel ready to take the mastery check**, add this tag:
+
+```bash
+git tag -a mastery-angles-proof-ready -m "Ready for Angles and Proof mastery check"
+git push origin --tags
+```
+
+**Your teacher will:**
+1. Review your work from BOTH lessons
+2. Check your cool-downs and activities
+3. Confirm you're ready or suggest review areas
+4. Give you access to the mastery check when ready!
+
+---
+
+**Last Updated:** 2025-11-16
diff --git a/classroom/lessons/templates-transformations/Warmup-Transformation-Review.md b/classroom/lessons/templates-transformations/Warmup-Transformation-Review.md
new file mode 100644
index 0000000..7a50617
--- /dev/null
+++ b/classroom/lessons/templates-transformations/Warmup-Transformation-Review.md
@@ -0,0 +1,156 @@
+# Warm-up: Transformation Review
+**Name:** _________________
+**Date:** _________________
+**Lesson:** Transformations, Transversals and Proof
+
+---
+
+## Transformation Properties
+
+### Translation (Slide)
+
+**What is a translation?**
+
+
+
+
+**Does it preserve angle measures?**
+- [ ] Yes
+- [ ] No
+
+**Example:** Describe what happens to angle measures when you slide a triangle:
+
+
+
+
+**Diagram:**
+```
+[Draw or describe a translation]
+
+
+
+
+```
+
+---
+
+### Rotation (Turn)
+
+**What is a rotation?**
+
+
+
+
+**Does it preserve angle measures?**
+- [ ] Yes
+- [ ] No
+
+**Example:** Describe what happens to angle measures when you rotate a triangle:
+
+
+
+
+**Diagram:**
+```
+[Draw or describe a rotation]
+
+
+
+
+```
+
+---
+
+### Reflection (Flip)
+
+**What is a reflection?**
+
+
+
+
+**Does it preserve angle measures?**
+- [ ] Yes
+- [ ] No
+
+**Example:** Describe what happens to angle measures when you reflect a triangle:
+
+
+
+
+**Diagram:**
+```
+[Draw or describe a reflection]
+
+
+
+
+```
+
+---
+
+## Summary of Rigid Transformations
+
+**Which transformations preserve (keep the same):**
+
+| Property | Translation | Rotation | Reflection |
+|----------|-------------|----------|------------|
+| Angle measures | Yes/No | Yes/No | Yes/No |
+| Side lengths | Yes/No | Yes/No | Yes/No |
+| Shape | Yes/No | Yes/No | Yes/No |
+| Orientation | Yes/No | Yes/No | Yes/No |
+
+---
+
+## Connection to Angles
+
+**Why does it matter that transformations preserve angle measures?**
+
+
+
+
+**How can transformations help us prove angle relationships?**
+
+
+
+
+**Preview:** Today we'll use transformations to prove that certain angle pairs are congruent (equal).
+
+**My prediction:** If I rotate a transversal diagram 180° around the midpoint, I think:
+
+
+
+
+---
+
+## Quick Check
+
+**Draw two parallel lines cut by a transversal:**
+```
+
+
+
+
+
+
+
+
+
+
+```
+
+**Mark two angles that you think might be congruent:**
+∠___ and ∠___
+
+**What transformation might map one onto the other?**
+
+
+
+
+---
+
+**Commit your work:**
+```bash
+git add Warmup-Transformation-Review.md
+git commit -m "Warm-up: Transformation properties"
+git push origin main
+```
diff --git a/classroom/lessons/templates/Activity1-Angle-Sum-Proof.md b/classroom/lessons/templates/Activity1-Angle-Sum-Proof.md
new file mode 100644
index 0000000..0a84e96
--- /dev/null
+++ b/classroom/lessons/templates/Activity1-Angle-Sum-Proof.md
@@ -0,0 +1,181 @@
+# Activity 1: Triangle Angle Sum One Way
+**Name:** _________________
+**Date:** _________________
+**Lesson:** One Hundred Eighty
+
+---
+
+## Triangle Information
+
+**Vertices:** A, B, C
+
+```
+[Draw or describe your triangle here]
+
+
+
+
+```
+
+**Given information:**
+- Triangle ABC with angles ∠A, ∠B, and ∠C
+- No specific angle measures (this proof works for ANY triangle!)
+
+---
+
+## My Proof (Method 1: Auxiliary Line)
+
+**Strategy:** I will use an auxiliary line (a helper line) parallel to one side of the triangle.
+
+### Step 1: Draw the auxiliary line
+**What I did:**
+
+
+
+
+**Why this is valid (what theorem/postulate allows this?):**
+
+
+
+
+---
+
+### Step 2: Identify angle relationships
+**What I did:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+**What theorem(s) am I using?**
+
+
+
+
+---
+
+### Step 3: Set up an equation
+**What I did:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+### Step 4: Substitute and simplify
+**What I did:**
+
+
+
+
+**Why this is valid:**
+
+
+
+
+---
+
+### Step 5: Conclusion
+**What I did:**
+
+
+
+
+**Therefore:** m∠A + m∠B + m∠C = _______°
+
+---
+
+## My Reasoning
+
+**In my own words, WHY does this proof work?**
+
+
+
+
+
+
+**Why does this proof work for ANY triangle, not just this one?**
+
+
+
+
+
+
+**The key insight of this proof is:**
+
+
+
+
+
+
+---
+
+## Checking My Understanding
+
+**Could I reproduce this proof tomorrow without looking?**
+- [ ] Yes, definitely
+- [ ] Probably, with some help
+- [ ] Not yet, need more practice
+
+**The hardest step for me was:**
+
+
+
+
+**The easiest step for me was:**
+
+
+
+
+---
+
+## Questions I Have
+
+
+
+
+
+
+
+---
+
+## Visual Summary
+
+**Draw a diagram showing the key idea of this proof:**
+
+```
+[Your diagram here - show the auxiliary line and key angles]
+
+
+
+
+
+
+
+
+
+
+
+```
+
+---
+
+**Commit checkpoints:**
+```bash
+# After completing proof steps:
+git add Activity1-Angle-Sum-Proof.md
+git commit -m "Activity 1: Completed proof steps"
+
+# After finishing reasoning:
+git add Activity1-Angle-Sum-Proof.md
+git commit -m "Activity 1: Complete with reasoning"
+```
diff --git a/classroom/lessons/templates/Activity2-Another-Proof.md b/classroom/lessons/templates/Activity2-Another-Proof.md
new file mode 100644
index 0000000..b8dfa02
--- /dev/null
+++ b/classroom/lessons/templates/Activity2-Another-Proof.md
@@ -0,0 +1,217 @@
+# Activity 2: Triangle Angle Sum Another Way
+**Name:** _________________
+**Date:** _________________
+**Lesson:** One Hundred Eighty
+
+---
+
+## Triangle Setup
+
+**My triangle:** You can use the same triangle from before, or any triangle!
+
+```
+[Draw your triangle here]
+
+
+
+
+∠A = ____°
+∠B = ____°
+∠C = ____°
+```
+
+---
+
+## My Proof (Method 2: ___________________)
+
+**Fill in the method name:** (rotation, paper folding, tearing, etc.)
+
+### Strategy
+
+**What I'm going to do:**
+
+
+
+
+
+
+---
+
+### The Proof
+
+**Step 1:**
+**What I did:**
+
+
+
+
+**What I observed:**
+
+
+
+
+---
+
+**Step 2:**
+**What I did:**
+
+
+
+
+**What I observed:**
+
+
+
+
+---
+
+**Step 3:**
+**What I did:**
+
+
+
+
+**What I observed:**
+
+
+
+
+---
+
+**Step 4:** (if needed)
+**What I did:**
+
+
+
+
+**What I observed:**
+
+
+
+
+---
+
+### Conclusion
+
+**What this shows:**
+
+
+
+
+**Therefore:** The sum of the angles in a triangle = _______°
+
+---
+
+## Comparing Methods
+
+### Activity 1 vs Activity 2
+
+**How is this method different from Method 1 (auxiliary line)?**
+
+
+
+
+
+**Similarities between the methods:**
+
+
+
+
+
+**Which method do I prefer and why?**
+
+
+
+
+
+---
+
+### Generalization
+
+**Does this method work for ANY triangle?**
+- [ ] Yes
+- [ ] No
+- [ ] I'm not sure
+
+**My reasoning:**
+
+
+
+
+
+
+**Test it:** If I had an isosceles triangle, would this proof still work?
+- [ ] Yes
+- [ ] No
+
+**What about a right triangle?**
+- [ ] Yes
+- [ ] No
+
+**What about an obtuse triangle?**
+- [ ] Yes
+- [ ] No
+
+---
+
+## Connection to Previous Learning
+
+**In Grade 8, I learned about triangle angles using:**
+(Check all that apply)
+- [ ] Cutting out triangles and arranging angles
+- [ ] Folding paper
+- [ ] Using a protractor to measure
+- [ ] Other: _________________
+
+**How is today's work different?**
+
+
+
+
+
+
+**How is it the same?**
+
+
+
+
+
+
+---
+
+## My Confidence Level
+
+Rate your confidence (1 = not confident, 5 = very confident):
+
+**I can prove the Triangle Angle Sum Theorem:** _____/5
+
+**I understand WHY it's always 180°:** _____/5
+
+**I could explain this to a classmate:** _____/5
+
+**I could find a missing angle in a triangle:** _____/5
+
+---
+
+## Questions or Confusion
+
+
+
+
+
+
+
+---
+
+**Commit your work:**
+```bash
+git add Activity2-Another-Proof.md
+git commit -m "Activity 2: Completed second proof method"
+git push origin main
+```
+
+---
+
+## Are You Ready for More? (Extension)
+
+**If you finish early**, move on to `Activity2-Extension.md`
diff --git a/classroom/lessons/templates/Activity2-Extension.md b/classroom/lessons/templates/Activity2-Extension.md
new file mode 100644
index 0000000..5848518
--- /dev/null
+++ b/classroom/lessons/templates/Activity2-Extension.md
@@ -0,0 +1,166 @@
+# Are You Ready for More?
+**Name:** _________________
+**Date:** _________________
+**Lesson:** One Hundred Eighty - Extension
+
+---
+
+## Challenge Problem: Quadrilateral Angle Sum
+
+**Question:** If the angles in a triangle sum to 180°, what do the angles in a quadrilateral (4-sided figure) sum to?
+
+### Part 1: Make a Conjecture
+
+**My guess:** The angles in a quadrilateral sum to _______°
+
+**My reasoning for this guess:**
+
+
+
+
+
+---
+
+### Part 2: Test Your Conjecture
+
+**Draw a quadrilateral:** (any 4-sided figure)
+
+```
+[Draw your quadrilateral here]
+
+
+
+
+
+
+```
+
+**Measure or assign angles:**
+∠1 = _____°
+∠2 = _____°
+∠3 = _____°
+∠4 = _____°
+
+**Sum:** _____ + _____ + _____ + _____ = _______°
+
+**Does this match my conjecture?**
+- [ ] Yes
+- [ ] No - I need to revise!
+
+---
+
+### Part 3: Prove It!
+
+**Can you use what you learned about triangles to PROVE the quadrilateral angle sum?**
+
+**Hint:** How could you split a quadrilateral into triangles?
+
+**My proof:**
+
+
+
+
+
+
+
+**Diagram showing my strategy:**
+```
+[Draw how you split the quadrilateral]
+
+
+
+
+
+
+
+
+```
+
+**My equation:**
+
+
+
+
+**Therefore, the sum of angles in a quadrilateral is** _______°
+
+---
+
+### Part 4: Generalize
+
+**What about a pentagon (5 sides)?**
+
+**My conjecture:** _______°
+
+**My reasoning:**
+
+
+
+
+
+---
+
+**Can you find a pattern?**
+
+| Shape | Sides | Angle Sum | Pattern |
+|-------|-------|-----------|---------|
+| Triangle | 3 | 180° | |
+| Quadrilateral | 4 | _____° | |
+| Pentagon | 5 | _____° | |
+| Hexagon | 6 | _____° | |
+| n-gon | n | _____° | |
+
+**The formula for an n-sided polygon:**
+
+
+
+
+---
+
+### Part 5: Challenge Your Understanding
+
+**Why does this pattern work?**
+
+
+
+
+
+
+**Could you prove this works for ANY polygon?**
+
+
+
+
+
+
+---
+
+## Reflection
+
+**This extension problem helped me understand:**
+
+
+
+
+
+**This was (easy / medium / hard) because:**
+
+
+
+
+
+**A question I still have:**
+
+
+
+
+
+---
+
+**Commit your extension work:**
+```bash
+git add Activity2-Extension.md
+git commit -m "Activity 2: Completed extension - polygon angle sums"
+git push origin main
+```
+
+**Extra Credit Note:** Your teacher may award extra credit for thoughtful extension work!
diff --git a/classroom/lessons/templates/Cooldown-Third-Proof.md b/classroom/lessons/templates/Cooldown-Third-Proof.md
new file mode 100644
index 0000000..1c48bc1
--- /dev/null
+++ b/classroom/lessons/templates/Cooldown-Third-Proof.md
@@ -0,0 +1,157 @@
+# Cool-down: Triangle Angle Sum a Third Way
+**Name:** _________________
+**Date:** _________________
+**Lesson:** One Hundred Eighty
+
+---
+
+## Instructions
+
+**Time:** 5 minutes
+**Work:** Individual (this is your exit ticket!)
+**Task:** Prove the Triangle Angle Sum Theorem using a THIRD method (different from Activities 1 and 2)
+
+---
+
+## The Triangle
+
+**Draw any triangle:**
+
+```
+[Your triangle here]
+
+
+
+
+
+
+
+Label it with vertices A, B, C
+```
+
+---
+
+## My Proof (Method 3)
+
+### Given:
+Triangle ABC with angles ∠A, ∠B, and ∠C
+
+---
+
+### To Prove:
+m∠A + m∠B + m∠C = 180°
+
+---
+
+### Proof:
+
+**Step 1:**
+
+
+
+
+
+
+**Step 2:**
+
+
+
+
+
+
+**Step 3:**
+
+
+
+
+
+
+**Step 4:** (if needed)
+
+
+
+
+
+
+**Step 5:** (if needed)
+
+
+
+
+
+
+---
+
+### Conclusion:
+
+Therefore,
+
+
+
+
+
+
+---
+
+## Reflection
+
+### Which of the three methods makes the most sense to me?
+- [ ] Method 1 (Activity 1): _________________
+- [ ] Method 2 (Activity 2): _________________
+- [ ] Method 3 (Cool-down): _________________
+
+**Why?**
+
+
+
+
+---
+
+### Do I feel confident I could prove this for ANY triangle?
+- [ ] Yes, definitely
+- [ ] Somewhat confident
+- [ ] Not yet - I need more practice
+
+---
+
+### Questions I still have:
+
+
+
+
+
+
+
+---
+
+### Self-Assessment
+
+**Today I learned:** (check all that apply)
+- [ ] How to prove the Triangle Angle Sum Theorem
+- [ ] Multiple ways to prove the same thing
+- [ ] How to write a formal proof
+- [ ] How to justify each step in a proof
+- [ ] Why all triangles have angle sum of 180°
+
+**I'm most proud of:**
+
+
+
+
+**I'm still working on:**
+
+
+
+
+---
+
+**IMPORTANT: Submit this as your exit ticket!**
+
+```bash
+git add Cooldown-Third-Proof.md
+git commit -m "Cool-down: Completed third proof (EXIT TICKET)"
+git tag -a lesson-one-eighty-complete-$(date +%Y%m%d) -m "Lesson complete"
+git push origin main --tags
+```
+
+**The tag tells your teacher you're done with the lesson!**
diff --git a/classroom/lessons/templates/Reference-Chart.md b/classroom/lessons/templates/Reference-Chart.md
new file mode 100644
index 0000000..e52400c
--- /dev/null
+++ b/classroom/lessons/templates/Reference-Chart.md
@@ -0,0 +1,199 @@
+# Geometry Reference Chart
+**Name:** _________________
+**Unit:** Angles and Proof
+
+---
+
+## Instructions
+
+This is your personal reference chart that you'll build throughout the unit. Add to it after each lesson!
+
+**Git reminder:** Commit this file after each lesson!
+```bash
+git add Reference-Chart.md
+git commit -m "Updated reference chart: [lesson name]"
+```
+
+---
+
+## Unit: Angles and Proof
+
+### Lesson: Evidence, Angles and Proof
+*(Fill in after that lesson)*
+
+**Key Concepts:**
+
+
+**Important Theorems/Postulates:**
+
+
+**Vocabulary:**
+
+
+**When to use:**
+
+
+---
+
+### Lesson: One Hundred Eighty (Triangle Angle Sum Theorem)
+
+**Theorem Statement:**
+
+**Triangle Angle Sum Theorem:** The sum of the measures of the angles in a triangle is 180°.
+
+**Symbolic notation:**
+For any triangle ABC: m∠A + m∠B + m∠C = 180°
+
+---
+
+**Proof Methods I Know:**
+
+**Method 1 (Auxiliary Line):**
+- Draw a line parallel to one side through the opposite vertex
+- Use alternate interior angles
+- Show angles form a straight line (180°)
+
+**Method 2 (______________________):**
+*(Fill in the method you used in Activity 2)*
+
+
+
+
+**Method 3 (______________________):**
+*(Fill in the method you used in Cool-down)*
+
+
+
+
+**Which method I prefer:**
+
+**Why:**
+
+
+---
+
+**Key Vocabulary:**
+
+| Term | Definition | Example/Diagram |
+|------|------------|-----------------|
+| **Auxiliary line** | A line added to a diagram to help with a proof | |
+| **Alternate interior angles** | | |
+| **Linear pair** | | |
+| | | |
+
+---
+
+**When to use this theorem:**
+
+- Finding a missing angle in a triangle when two angles are known
+- Checking if three angles can form a triangle
+- Proving other angle relationships
+-
+
+
+**Examples:**
+
+Example 1: If ∠A = 50° and ∠B = 60°, then ∠C = ______°
+*Solution:*
+
+
+
+
+Example 2: Can a triangle have angles of 90°, 45°, and 50°?
+*Solution:*
+
+
+
+
+---
+
+**Common Mistakes to Avoid:**
+
+1. Assuming one example proves it for all triangles
+2.
+3.
+
+
+---
+
+**Connection to Previous Learning:**
+
+**Grade 8:** I learned about triangle angles using _______________
+
+**How today was different:** Now I can prove it formally using rigorous definitions
+
+**How it connects:**
+
+
+---
+
+### Lesson: Transformations, Transversals and Proof
+*(Fill in after that lesson)*
+
+**Key Concepts:**
+
+
+**Important Theorems/Postulates:**
+
+
+**Vocabulary:**
+
+
+**How it connects to Triangle Angle Sum:**
+
+
+---
+
+## My Personal Notes
+
+**What I'm confident about:**
+
+
+
+
+**What I need to practice:**
+
+
+
+
+**Questions I still have:**
+
+
+
+
+---
+
+## Quick Reference: Angle Relationships
+
+*(Add to this as you learn more)*
+
+| Relationship | Diagram | Properties | When to Use |
+|--------------|---------|------------|-------------|
+| **Linear Pair** | | Sum to 180° | |
+| **Vertical Angles** | | Equal measures | |
+| **Alternate Interior** | | Equal (if lines parallel) | |
+| **Corresponding** | | | |
+| | | | |
+
+---
+
+## Problem-Solving Strategies
+
+**When I see a triangle with missing angles:**
+1. Check what angles I know
+2. Use Triangle Angle Sum: sum = 180°
+3. Set up equation
+4. Solve
+
+**When I need to prove something:**
+1. Identify what I'm trying to prove
+2. Look for helpful relationships (parallel lines, etc.)
+3. Consider adding auxiliary lines
+4. Justify each step
+5. Write clear conclusion
+
+---
+
+**Keep this updated! It's your study guide for mastery checks.**
+
+**Last Updated:** _________________
diff --git a/classroom/lessons/templates/Warmup-What-Went-Wrong.md b/classroom/lessons/templates/Warmup-What-Went-Wrong.md
new file mode 100644
index 0000000..f5dad3e
--- /dev/null
+++ b/classroom/lessons/templates/Warmup-What-Went-Wrong.md
@@ -0,0 +1,127 @@
+# Warm-up: What Went Wrong?
+**Name:** _________________
+**Date:** _________________
+**Lesson:** One Hundred Eighty (Triangle Angle Sum Theorem)
+
+---
+
+## The Triangle
+
+```
+      A
+     /\
+    /  \
+   /    \
+  /      \
+ /________\
+B          C
+
+Given angles:
+∠A = 50°
+∠B = 60°
+∠C = 70°
+```
+
+---
+
+## Given Proof (Contains Errors!)
+
+**Student's Claim:** "I can prove that the angles in this triangle add up to 180°."
+
+**Their Proof:**
+
+**Step 1:** The angles in the triangle are 50°, 60°, and 70°.
+
+**Step 2:** I added them: 50 + 60 + 70 = 180
+
+**Step 3:** Since these three angles add to 180°, I have proven that ALL triangles have angles that sum to 180°.
+
+**Conclusion:** The Triangle Angle Sum Theorem is proven! ✓
+
+---
+
+## My Work: Finding the Errors
+
+### Error 1:
+**What's wrong:**
+
+
+
+**Why it's wrong:**
+
+
+
+**How to fix it:**
+
+
+
+
+---
+
+### Error 2:
+**What's wrong:**
+
+
+
+**Why it's wrong:**
+
+
+
+**How to fix it:**
+
+
+
+
+---
+
+### Error 3 (if you find one):
+**What's wrong:**
+
+
+
+**Why it's wrong:**
+
+
+
+**How to fix it:**
+
+
+
+
+---
+
+## The Real Issue
+
+**The main problem with this "proof" is:**
+
+
+
+
+
+**What we SHOULD do instead:**
+
+
+
+
+
+
+---
+
+## My Understanding
+
+**On a scale of 1-5, how well do I understand the difference between:**
+- Checking one example: _____/5
+- Proving something for ALL cases: _____/5
+
+**Questions I have:**
+
+
+
+
+---
+
+**Remember to commit this when you're done!**
+```bash
+git add Warmup-What-Went-Wrong.md
+git commit -m "Lesson One-Eighty: Completed warm-up"
+```