diff --git a/_posts/weeks/2023-11-27-week9.md b/_posts/weeks/2023-11-27-week9.md
index 39c0654..d1ff1fb 100644
--- a/_posts/weeks/2023-11-27-week9.md
+++ b/_posts/weeks/2023-11-27-week9.md
@@ -268,3 +268,47 @@ advice, ignore it, adapt it, put it off until later, and so on. But remember
 that issues and pull requests are largely positive things – they are a sign that
 your project has people paying attention to it, and they are a normal and common
 part of managing a software system.
+
+## Lab Report 5 {#week9-lab-report}
+
+### Part 1 – Debugging Scenario
+
+Design a debugging scenario, and write your report as a conversation on EdStem.
+It should have:
+
+1. The original post from a student with a screenshot showing a symptom and a
+description of a guess at the bug/some sense of what the failure-inducing input
+is. (Don't actually make the post! Just write the content that would go in such
+a post)
+2. A response from a TA asking a leading question or suggesting a command to try
+(To be clear, you are *mimicking* a TA here.)
+3. Another screenshot/terminal output showing what information the student got
+from trying that, and a clear description of what the bug is.
+4. At the end, all the information needed about the setup including:
+  - The file & directory structure needed
+  - The contents of each file *before* fixing the bug
+  - The full command line (or lines) you ran to trigger the bug
+  - A description of what to edit to fix the bug
+
+You should actually set up and run the scenario from your screenshots. It should
+involve at least **a Java file and a bash script**. Describing the bug should
+involve reading some output at the terminal resulting from running one or more
+commands. Design an error that produces more interesting output than a single
+message about a syntax or unbound identifier error – showcase some interesting
+wrong behavior! Feel free to set this up by cloning and breaking some existing
+code like the grading script or code from class, or by designing something of
+your own from scratch, etc.
+
+### Part 2 – Reflection
+
+In a couple of sentences, describe something you learned from your lab
+experience in the second half of this quarter that you didn't know before. It
+could be a technical topic we addressed specifically, something cool you found
+out on your own building on labs, something you learned from a tutor or
+classmate, and so on. It doesn't have to be specifically related to a lab
+writeup, we just want to hear about cool things you learned!
+
+### A Note on Grading at the End of the Quarter
+
+We will try, but there **might not** be a resubmission window for lab report 5,
+so do your best to be thorough, creative, and clear in your submission.