8. Information Framing (Active vs. Passive Voice)

Objective: Upgrade the standard vocabulary library and learn how to shift the "camera angle" of a sentence to control the narrative.

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

Note: Do not translate these word-by-word. Memorize them as complete, unbreakable blocks of code.

A. The Corporate API (Work Environment)

The Block	The Logic	Corporate Execution
Escalate the issue	To pass a problem up to a higher level of management.	"If the vendor doesn't reply, we will escalate the issue to the director."
Push to production	To make code/updates live for the actual users.	"We are ready to push the new update to production."

B. The Casual API (Friends, Family, & Daily Life)

The Block	The Logic	Casual Execution
Catch up with	To talk to someone you haven't spoken to in a while to exchange news.	"I usually catch up with my friends while taking a long walk after dinner."
Whip up	To make something quickly (usually food).	"I didn't have much time, so I just whipped up some spicy oats for brunch."

---

Part 2: System Prerequisites (Verb Data Payloads & Dependencies)

Before we can shift the "camera angle" of a sentence into the Passive Voice, we need to know what kind of Verb we are executing. In the English OS, verbs act exactly like software functions—some require you to input data (an Object) to work, and some run perfectly on their own.

1. Transitive Verbs ("Input Required")

These are actions that MUST transfer their energy to a target object. If you do not provide the target object, the sentence will not compile. The listener's brain will literally wait for you to finish the sentence.

• The QA Test: Can you ask "What?" or "Whom?" immediately after the verb? If yes, it requires an object.
• The Code Signature: Subject + Verb + [Target Object]

Corporate API Examples:

• Approve: "The manager approved..." (Approved what?) --> "...the budget."
• Resolve: "IT resolved..." (Resolved what?) --> "...the server outage."
• Schedule: "Let's schedule..." (Schedule what?) --> "...a sync."

Casual API Examples:

• Enjoy: "I really enjoyed..." (Enjoyed what?) --> "...the movie."
• Whip up: "My brother whipped up..." (Whipped up what?) --> "...dinner."

2. Intransitive Verbs ("Standalone Functions")

These are self-contained actions. They do NOT take a direct object. If you try to force an object immediately after them without a Preposition (a routing pointer), the system throws a fatal syntax error.

• The QA Test: You cannot ask "What?" after these verbs. You can only ask "Where?", "When?", or "How?"
• The Code Signature: Subject + Verb + [Stop] (or add a Prepositional Pointer).

Corporate API Examples:

• Happen: "The crash happened." (You cannot "happen" a server).
• Arrive: "The CEO arrived." (Fatal Bug: "Arrived the office." Clean Code: "Arrived at the office.")
• Respond: "The vendor responded." (Fatal Bug: "Responded the email." Clean Code: "Responded to the email.")

Casual API Examples:

• Sleep: "I slept for eight hours." (You cannot "sleep" a bed).
• Laugh: "Everyone laughed loudly."

3. Overloaded Verbs (Ambitransitive)

Just like in programming, some functions are "overloaded." They can accept an input if you want to provide one, but if you leave it blank, they default to a standalone state. They can be both.

• Start (Transitive): "I started the server." (I executed the object).
• Start (Intransitive): "The meeting starts at 9 AM." (It runs standalone).
• Run (Transitive): "She runs the marketing team."
• Run (Intransitive): "The script is running in the background."
• Eat (Transitive): "I ate the spicy oats."
• Eat (Intransitive): "I already ate."

---

The Ultimate Dependency Rule for Phase 6

Why do we need to know this? Because of this strict architectural rule:

You can ONLY compile a Passive sentence using a Transitive verb. > Because the Passive Voice requires moving the "Target Object" to the front of the sentence, if a verb doesn't have an object, the passive compilation is mathematically impossible.

• Valid Compilation (Transitive): * Active: "Deepak deployed the code." --> Passive: "The code was deployed."
• Fatal Error (Intransitive): * Active: "The server crashed." --> Passive: ERROR. You cannot say "The server was crashed." The system will reject it.

---

Part 3: The Camera Angles (Syntax Framing)

We have two ways to frame the exact same data payload.

• The Active Voice (Camera on the Doer): The Subject is the person doing the action. It is direct and takes ownership.
  • The Code: Subject (Doer) + Verb + Object (Receiver)
  • Execution: "Deepak crashed the server."
• The Passive Voice (Camera on the Object): We flip the sentence. The Object becomes the new Subject. We use this when the result is more important than the person who did it, or when we want to be diplomatic and hide blame.
  • The Code: Object + BE GATE + V3 (Done State) + (by Doer)
  • Execution: "The server was crashed (by Deepak)."

The Passive Voice Compilation Matrix (The Inner Planets)

To change the tense of a passive sentence, you NEVER change the Main Verb (it is permanently locked in the V3 "Done" state). You only change the timeline of the BE Gate.

Tense / Timeline	Active Voice (Camera on Doer)	Passive Voice (Camera on Object)	The Backend Logic
Present Simple	The team deploys the code.	The code is deployed.	is/are + V3
Past Simple	The team deployed the code.	The code was deployed.	was/were + V3
Future Simple	The team will deploy the code.	The code will be deployed.	will be + V3
Present Continuous	The team is deploying the code.	The code is being deployed.	is/are being + V3
Present Perfect	The team has deployed the code.	The code has been deployed.	has/have been + V3
Modals	The team must deploy the code.	The code must be deployed.	Modal + be + V3

System Warning: Do not attempt to use the Passive Voice with Perfect Continuous tenses (e.g., "has been being deployed"). This causes a UX crash. Revert to Active Voice or a simpler tense.

Part 4: The Strategic Use Cases

Why do we intentionally write passive code?

1. The Corporate Shield (Hiding Blame): You are writing an incident report. You do not want to throw a junior developer under the bus.

• Active (Aggressive): "John deleted the database."
• Passive (Diplomatic): "The database was deleted." (We know it happened, but we aren't pointing fingers).

2. The Casual Focus (The Doer is Unknown/Unimportant): You are telling a story to your family, and the action itself is the only thing that matters.

• Active (Weird Focus): "A thief stole my brother's car."
• Passive (Natural Focus): "My brother's car was stolen."

---

Part 5: Interactive Code Refactoring (20 Questions)

Instructions for the student: Refactor these 20 sentences. First, identify if the sentence is Active or Passive. Then, rewrite it in the opposite frame. You must successfully compile the new vocabulary blocks we learned today.

1. (Corporate): "The QA team found a critical bug, so they escalated the issue to the lead developer."

• Refactor the second half into Passive:

2. (Casual): "A delicious, spicy brunch was whipped up by my sister in under ten minutes."

• Refactor into Active:

3. (Corporate - Diplomacy): You need to tell the client that your team made a mistake and delayed the timeline.

• Write a Passive sentence to soften the blow and hide direct blame:

4. (Casual): "I was caught up with by an old friend from university during my evening walk."

• Refactor into Active (Make it sound more natural):

5. (Corporate): "The junior devs pushed the broken code to production."

• Refactor into Passive (Protect the juniors):

6. (Corporate): "The React development team pushed the final build to production on Friday."

• Refactor into Passive (Focus on the build, not the team):

7. (Casual): "A quick, spicy meal was whipped up by my brother before he left."

• Refactor into Active:

8. (Corporate - Diplomacy): You are a freelancer. The payment gateway code you wrote has a bug. Instead of saying the aggressive active sentence, "I broke the payment gateway," use the Passive voice to report the status neutrally to the client.

• Write the diplomatic Passive sentence:

9. (Casual - UX Check): "An old colleague was caught up with by me during my post-dinner walk."

• Refactor into Active (Notice how terrible the passive voice sounds for this casual phrasal verb!):

10. (Corporate): "Because the workstation kept crashing, the client escalated the issue to IT support."

• Refactor the second half of the sentence into Passive: 11. (Casual): "I whipped up a quick batch of overnight oats with chia seeds for brunch."
• Refactor into Passive:

12. (Corporate): "The untested database migration was pushed to production by the junior contractor."

• Refactor into Active:

13. (Casual): "I caught up with my sister over the phone to discuss her English lessons."

• Refactor into Passive (Even if it sounds a bit clunky, build the exact syntax):

14. (Corporate): "The client escalated the issue immediately after the server went offline."

• Refactor into Passive:

15. (Corporate - Diplomacy): A client is angry because of this reality: "Your team pushed the wrong update to production."

• Rewrite this in the Passive voice to de-escalate the blame and focus purely on the mistake:

16. (Casual): "Some extra spicy noodles were whipped up for dinner."

• Refactor into Active by adding yourself as the Doer:

17. (Corporate): "We must escalate the issue before the whole system fails."

• Refactor the first clause into Passive (Hint: Modals keep their base form, so use "be" + V3):

18. (Casual): "I usually catch up with my family when I walk around the neighborhood."

• Refactor the first clause into Passive:

19. (Corporate): "The critical security patch will be pushed to production by the lead Python developer."

• Refactor into Active:

20. (Corporate - Full Scenario): You are reviewing a student's or junior developer's code. It has a lot of syntax errors. Instead of using the active voice ("You wrote terrible code" or "You made a lot of errors"), use the Passive voice to critique the code rather than the coder.

• Write a diplomatic Passive sentence:

Click here to view the System Output (Answer Key)

1.

• The Logic: Shift the Object ("the issue") to the Subject slot and use was + V3 (Past Simple Passive).
• Clean Code: "The QA team found a critical bug, so the issue was escalated to the lead developer."

2.

• The Logic: Identify the Doer ("my sister") and move her to the Subject slot. Revert to Past Simple Active.
• Clean Code: "My sister whipped up a delicious, spicy brunch in under ten minutes."

3.

• The Logic: Remove the Doer ("we/our team") entirely to hide the blame. Focus on the objects ("a mistake", "the timeline").
• Clean Code: "A mistake was made, and the timeline was delayed."

4.

• The Logic: The Doer ("an old friend") moves to the front. This fixes the clunky, unnatural phrasing of a passive casual interaction.
• Clean Code: "An old friend from university caught up with me during my evening walk."

5.

• The Logic: Remove the junior devs from the logs to protect them. Shift the focus to the code using Past Simple Passive.
• Clean Code: "The broken code was pushed to production."

6.

• The Logic: Move the Object ("the final build") to the front. You can drop the team completely or leave them at the end with "by".
• Clean Code: "The final build was pushed to production on Friday."

7.

• The Logic: The Doer ("my brother") moves to the front. Shift the verb back to Past Simple Active.
• Clean Code: "My brother whipped up a quick, spicy meal before he left."

8.

• The Logic: Protect your freelance reputation. Remove "I" and state the broken status neutrally using Past Simple Passive.
• Clean Code: "The payment gateway was broken."

9.

• The Logic: The UX of the original passive sentence is terrible for casual conversation. The Doer ("I") must take the Subject slot.
• Clean Code: "I caught up with an old colleague during my post-dinner walk."

10.

• The Logic: Shift "the issue" to the front of the second clause.
• Clean Code: "Because the workstation kept crashing, the issue was escalated to IT support."

11.

• The Logic: Shift the Object ("a quick batch of overnight oats with chia seeds") to the front.
• Clean Code: "A quick batch of overnight oats with chia seeds was whipped up for brunch."

12.

• The Logic: Identify the Doer ("the junior contractor") and put them in the driver's seat.
• Clean Code: "The junior contractor pushed the untested database migration to production."

13.

• The Logic: This will sound incredibly clunky, but mechanically it compiles. "My sister" becomes the Subject.
• Clean Code: "My sister was caught up with over the phone to discuss her English lessons."

14.

• The Logic: Remove the client from the sentence to focus purely on the action that occurred.
• Clean Code: "The issue was escalated immediately after the server went offline."

15.

• The Logic: De-escalate the tension by removing "Your team" from the error report.
• Clean Code: "The wrong update was pushed to production."

16.

• The Logic: Inject yourself as the Doer to make the code Active.
• Clean Code: "I whipped up some extra spicy noodles for dinner."

17.

• The Logic: Modals never change their shape. Add the base "be" + V3.
• Clean Code: "The issue must be escalated before the whole system fails."

18.

• The Logic: This is another "Clunky UX" test. It compiles, but a native speaker would rarely use the passive voice for this.
• Clean Code: "My family is usually caught up with when I walk around the neighborhood."

19.

• The Logic: The Doer ("the lead Python developer") takes the front. The will be pushed passive shifts to the will push active.
• Clean Code: "The lead Python developer will push the critical security patch to production."

20.

• The Logic: Remove the pronoun "You" entirely. Focus on the code and the errors so the critique is objective, not personal.
• Clean Code: "Terrible code was written," OR "A lot of errors were made in this build."