13. Injecting Data Payloads (Relative Clauses)

Objective: Learn how to attach descriptive metadata tags directly to Nouns using relative pronouns so you can identify exact variables without starting a new sentence.

Part 1: Standard Library Upgrade (Pre-Compiled Blocks)

Note: Memorize these as complete, unbreakable blocks of code.

A. The Corporate API

The Block	The Logic	Execution
Scope out	To carefully assess or investigate a situation before acting.	"I need to scope out the new React documentation."
Bring up	To introduce a topic into a conversation or meeting.	"I will bring up the database issue during the sync."

B. The Casual API

The Block	The Logic	Execution
Check out	To look at or explore something interesting.	"We should check out that new cafe in Brookefield."
Run out of	To consume your entire supply of an item.	"I need to buy pink salt; we completely ran out of it."

Part 2: The System Boundaries (The Data Tagging Matrix)

When you want to attach metadata to a Noun, you must choose the correct "Routing Tag." The tag you use depends entirely on the Data Type of the Noun you are modifying.

The Routing Tag	Target Data Type	Execution Example
Who	Human Variables	"The developer who wrote this Python script is brilliant."
Which	Inanimate / Tech Variables	"The server, which we rebooted yesterday, is crashing again."
That	Universal Fallback (Human or Tech)	"The Lenovo workstation that I bought is incredibly fast."
Whose	Foreign Key (Ownership/Possession)	"The client whose project we are scoping out is very strict."

Part 3: System Warnings & Deprecated Code

Note: These are the two most common syntax crashes when injecting metadata.

1. The Double Variable Crash (Duplicate Pointers): When you use a Routing Tag (that, which, who), it replaces the pronoun (it, him, them). You cannot use both, or the system will try to assign two values to the same slot and crash.

Fatal Error: "The Python script that I wrote it is running smoothly."
Clean Code: "The Python script that I wrote is running smoothly."

2. The Essential vs. Non-Essential Commas (The 'That' Restriction):

Essential Metadata: Information required to identify the variable. Do not use commas. You can use That, Who, or Which. ("The laptop that I bought yesterday is fast.")
Non-Essential Metadata: Extra "bonus" information. You MUST isolate it with commas. Crucial Rule: You can NEVER use That inside commas. You must use Which (for tech) or Who (for humans).
Fatal Error: "My MacBook Pro, that is from 2019, needs a battery replacement."
Clean Code: "My MacBook Pro, which is from 2019, needs a battery replacement."

Part 4: Interactive Code Refactoring (25 Questions)

Instructions for the student: Refactor the sentences by choosing the correct Routing Tag (Who, Which, That, Whose). Fix any Double Variable crashes, apply the correct comma rules, and integrate the new Standard Library vocabulary where instructed. Write your clean code directly below each corrupted sentence.

1. (Corporate): "The project manager which called the meeting wants to (introduce) the new budget." (Inject Standard Library API)

2. (Casual): "The overnight oats who I made them last night are in the fridge." (Fix the Routing Tag and the Double Variable Crash)

3. (Corporate): "We need to (investigate) the API rate limits that they are causing the timeout." (Inject Standard Library API and fix the Double Variable Crash)

4. (Casual - Bug Fix): "My sister that works at a large MNC needs help with English grammar." (Fix the Non-Essential Comma rule—she only has one sister, so this is bonus metadata!)

5. (Corporate): "The Lenovo ThinkStation, that I use for heavy Python compiling, is incredibly powerful." (Apply the Non-Essential Comma rule for the Routing Tag)

6. (Casual): "I need to go to the store because I (have zero left) the high-protein paneer." (Inject Standard Library API)

7. (Corporate): "The junior developer, who he pushed the broken code, is fixing the errors." (Fix the Double Variable Crash)

8. (Corporate): "The client who his website we are building wants to change the wireframes." (Apply the Foreign Key / Ownership Routing Tag)

9. (Casual): "I want to (look at) the new gym in Brookefield which it opened last week." (Inject Standard Library API and fix the Double Variable)

10. (Corporate): "The React components that I scoped them out yesterday are ready for deployment."

11. (Casual - Bug Fix): "The pink salt who I put in my pre-workout drink makes it taste better."

12. (Corporate): "My manager, that is currently on vacation, asked me to hold off on the launch."

13. (Casual): "I ran out of the chia seeds which I usually put them in my breakfast."

14. (Corporate): "The software engineer which wrote the documentation is out sick today."

15. (Corporate - Bug Fix): "The new Macbook Pro, that has the M4 chip, is arriving on March 1st."

16. (Casual): "The friend who her trip we are planning wants to go to Europe." (Apply the Foreign Key / Ownership Routing Tag)

17. (Corporate): "Please bring up the database migration who failed last night."

18. (Casual): "The traffic in Brookefield, that is always terrible at 6 PM, made me late."

19. (Corporate): "The freelancer whose code we reviewed it did a fantastic job." (Fix the Double Variable Crash hidden inside the Ownership clause)

20. (Casual): "I checked out the new recipe that you sent it to me."

21. (Corporate): "The team needs to scope out the new requirements that they were sent by Capgemini."

22. (Casual): "The treadmill which I use it for my cardio routine is broken."

23. (Corporate): "I will bring up the server logs, that show a massive memory leak." (Fix the Non-Essential Comma tag)

24. (Casual): "My 2019 laptop that I use for freelance work is starting to slow down." (Since she only has one 2019 laptop, this is non-essential metadata. Add the commas and fix the tag!)

25. (Corporate/Casual - Full Refactor): "The lead architect, that his job is to scope out the systems, brought up a bug which it crashes the Python script." (Fix all 3 Routing errors)

Click here to view the System Output (Answer Key)

The Bug: which, (introduce)
The Logic: "Which" is only for inanimate tech/objects. A project manager requires "Who".
Clean Code: "The project manager who called the meeting wants to bring up the new budget."

The Bug: who, them
The Logic: Oats are inanimate (use "that" or "which"). The pronoun "them" causes a Double Variable crash.
Clean Code: "The overnight oats that I made last night are in the fridge."

The Bug: (investigate), that they are
The Logic: Double Variable crash. "That" replaces "they".
Clean Code: "We need to scope out the API rate limits that are causing the timeout."

The Bug: that (with missing commas)
The Logic: Because she only has one sister, the information is non-essential (bonus metadata). It requires commas, and you cannot use "that" inside commas for humans. Use ", who... ,"
Clean Code: "My sister**, who** works at a large MNC**,** needs help with English grammar."

The Bug: , that
The Logic: You can never use "that" immediately following a comma for non-essential metadata. Because the ThinkStation is tech, it requires "which".
Clean Code: "The Lenovo ThinkStation**, which** I use for heavy Python compiling, is incredibly powerful."

The Bug: (have zero left)
The Logic: Standard Library Integration.
Clean Code: "I need to go to the store because I completely ran out of the high-protein paneer."

The Bug: who he pushed
The Logic: Double Variable crash. "Who" replaces "he".
Clean Code: "The junior developer, who pushed the broken code, is fixing the errors."

The Bug: who his website
The Logic: This is a Foreign Key showing ownership. Use "whose" to replace "who his".
Clean Code: "The client whose website we are building wants to change the wireframes."

The Bug: (look at), which it opened
The Logic: Standard Library Integration. Double Variable crash ("which" replaces "it").
Clean Code: "I want to check out the new gym in Brookefield which opened last week."

10.

The Bug: that I scoped them out
The Logic: Double Variable crash. "That" replaces "them".
Clean Code: "The React components that I scoped out yesterday are ready for deployment."

11.

The Bug: who
The Logic: Salt is not human. Use "that" or "which".
Clean Code: "The pink salt that I put in my pre-workout drink makes it taste better."

12.

The Bug: , that
The Logic: You cannot use "that" after a comma. Because a manager is human, use "who".
Clean Code: "My manager**, who** is currently on vacation, asked me to hold off on the launch."

13.

The Bug: which I usually put them
The Logic: Double Variable crash. "Which" replaces "them".
Clean Code: "I ran out of the chia seeds which I usually put in my breakfast."

14.

The Bug: which
The Logic: A software engineer is human. Use "who" or "that".
Clean Code: "The software engineer who wrote the documentation is out sick today."

15.

The Bug: , that
The Logic: You cannot use "that" after a comma for non-essential metadata. Switch to "which".
Clean Code: "The new Macbook Pro**, which** has the M4 chip, is arriving on March 1st."

16.

The Bug: who her trip
The Logic: Foreign Key / Ownership. Replace "who her" with "whose".
Clean Code: "The friend whose trip we are planning wants to go to Europe."

17.

The Bug: who failed
The Logic: A database migration is inanimate tech. Use "that" or "which".
Clean Code: "Please bring up the database migration that failed last night."

18.

The Bug: , that
The Logic: You cannot use "that" inside non-essential commas.
Clean Code: "The traffic in Brookefield**, which** is always terrible at 6 PM, made me late."

19.

The Bug: whose code we reviewed it
The Logic: Double Variable crash hidden in an ownership clause. "Whose code" replaces "it".
Clean Code: "The freelancer whose code we reviewed did a fantastic job."

20.

The Bug: that you sent it to me
The Logic: Double Variable crash. "That" replaces "it".
Clean Code: "I checked out the new recipe that you sent to me."

21.

The Bug: that they were sent
The Logic: Double Variable crash. "That" replaces "they".
Clean Code: "The team needs to scope out the new requirements that were sent by Capgemini."

22.

The Bug: which I use it
The Logic: Double Variable crash. "Which" replaces "it".
Clean Code: "The treadmill which I use for my cardio routine is broken."

23.

The Bug: , that show
The Logic: You cannot use "that" after a comma. Use "which" for tech/logs.
Clean Code: "I will bring up the server logs**, which** show a massive memory leak."

24.

The Bug: laptop that I use... is
The Logic: She only has one 2019 laptop, so the metadata is non-essential. Add commas and change "that" to "which".
Clean Code: "My 2019 laptop**, which** I use for freelance work**,** is starting to slow down."

25.

The Bug: , that his job is, brought up a bug which it crashes
The Logic: Triple crash. Fix the ownership tag inside commas (", whose job is..."). Fix the Double Variable crash ("which crashes").
Clean Code: "The lead architect , whose job is to scope out the systems, brought up a bug which crashes the Python script."

Part 1: Standard Library Upgrade (Pre-Compiled Blocks)​

A. The Corporate API​

B. The Casual API​

Part 2: The System Boundaries (The Data Tagging Matrix)​

Part 3: System Warnings & Deprecated Code​

Part 4: Interactive Code Refactoring (25 Questions)​