3. The Power Source (The 5 Verb States)
Objective: Master the raw "States" of a verb. Just like data types in Python, a verb must be in the correct state (V1-V5) to plug into a Tense Formula without causing a system crash.
Part 1: Standard Library Upgrade (The Corporate & Casual API)
Note: Memorize these as complete, unbreakable functional blocks.
| The Block | The Logic | Execution |
|---|---|---|
| Sign off on | To give official approval or final agreement. | "I need the lead architect to sign off on the PR." |
| Catch up (with) | To talk to someone to learn the latest news. | "I'll catch up with my sister after my workout." |
| Look into | To investigate or research a bug/issue. | "I'll look into why the Python script is failing." |
| Wrapped up | Finished or completed successfully. | "We wrapped up the meeting five minutes early." |
Part 2: The 5-State Matrix
Every action (Verb) in the English OS has 5 specific states. Before we learn Tenses, you must be able to "type-check" your verbs.
| State | Role | Example (Regular) | Example (Irregular) |
|---|---|---|---|
| V1 | Base / Root | Work | Go |
| V2 | Past (The History) | Worked | Went |
| V3 | Perfect / Passive | Worked | Gone |
| V4 | Continuous (-ing) | Working | Going |
| V5 | 3rd Person (-s) | Works | Goes |
System Rule: V5 is strictly for singular subjects (He, She, It, The Manager). If the subject is plural (They, We, The Developers), use V1.
Part 3: The System Boundaries (The Bigger Picture)
Before we start compiling verbs into these states, we need to define the boundaries of the English verb system. Every verb in the English OS falls into four specific categorization matrices. We will not learn all of these today, but this is your complete architectural roadmap:
1. By Compilation Rule: Regular vs. Irregular (Learning Today)
This dictates how a verb changes from its Base Form (V1) to its Past (V2) and Past Participle (V3) states.
- Regular (The Standard API): Predictable. Just append
-ed. - Irregular (Legacy Code): Hardcoded exceptions. Must be memorized.
2. System Routers: Auxiliaries & Modals (Scheduled for Day 4)
Helper scripts that bypass standard rules to change tenses or set parameters (e.g., Do, Be, Have, Can, Should, Will).
3. By Data Payload: Transitive vs. Intransitive (Scheduled for Day 8)
This dictates if a command crashes without an Object Noun attached.
- Transitive: Requires a payload to execute (e.g., I sent the email.)
- Intransitive: Executes perfectly alone (e.g., The server crashed.)
4. By Hardware Limitation: Action vs. Stative (Scheduled for Day 16)
This dictates if a verb can run in a continuous loop (-ing).
- Action (Dynamic): Observable physical processes (e.g., Running, Coding).
- Stative (Invisible): Background states that crash if run continuously (e.g., Knowing, Belonging).
Part 4: The Standard API (Top 50 Regular Verbs)
For Day 3, we are strictly focusing on Boundary #1: Regular vs. Irregular.
These 50 Standard API commands are highly predictable. To compile them into the Simple Past (V2) or Past Participle (V3), the system simply appends the -ed suffix. Over 90% of all English words follow this framework.
(Note: We have excluded the Continuous [-ing] and Singular [-s] forms from these reference tables, as they are constant across almost all verbs).
- If it ends in
e(Update), just addd--> Updated. - If it ends in consonant +
y(Try), drop theyand addied--> Tried. - If it ends in a short vowel + consonant (Stop), double the consonant --> Stopped.
| Base Form (V1) | Simple Past (V2) | Past Participle (V3) |
|---|---|---|
| Allow | Allowed | Allowed |
| Answer | Answered | Answered |
| Ask | Asked | Asked |
| Boot | Booted | Booted |
| Call | Called | Called |
| Change | Changed | Changed |
| Check | Checked | Checked |
| Clean | Cleaned | Cleaned |
| Click | Clicked | Clicked |
| Close | Closed | Closed |
| Compile | Compiled | Compiled |
| Copy | Copied | Copied |
| Crash | Crashed | Crashed |
| Create | Created | Created |
| Delete | Deleted | Deleted |
| Deploy | Deployed | Deployed |
| Design | Designed | Designed |
| Develop | Developed | Developed |
| Drop | Dropped | Dropped |
| Edit | Edited | Edited |
| Explain | Explained | Explained |
| Fail | Failed | Failed |
| Finish | Finished | Finished |
| Fix | Fixed | Fixed |
| Format | Formatted | Formatted |
| Help | Helped | Helped |
| Install | Installed | Installed |
| Listen | Listened | Listened |
| Log | Logged | Logged |
| Look | Looked | Looked |
| Move | Moved | Moved |
| Need | Needed | Needed |
| Open | Opened | Opened |
| Play | Played | Played |
| Printed | Printed | |
| Push | Pushed | Pushed |
| Reply | Replied | Replied |
| Save | Saved | Saved |
| Search | Searched | Searched |
| Share | Shared | Shared |
| Start | Started | Started |
| Stop | Stopped | Stopped |
| Talk | Talked | Talked |
| Test | Tested | Tested |
| Try | Tried | Tried |
| Update | Updated | Updated |
| Use | Used | Used |
| Walk | Walked | Walked |
| Want | Wanted | Wanted |
| Work | Worked | Worked |
Part 5: Legacy Code (Top 50 Irregular Verbs)
These 50 commands are built into the oldest parts of the English OS. They do not use the -ed suffix. They must be cached in your memory manually.
To prevent a buffer overflow, we have grouped them into three strict "Crash Patterns."
Pattern A: The Static Variables (No Change)
The Base, Past, and Past Participle forms are completely identical.
| Base Form (V1) | Simple Past (V2) | Past Participle (V3) |
|---|---|---|
| Cost | Cost | Cost |
| Cut | Cut | Cut |
| Hit | Hit | Hit |
| Hurt | Hurt | Hurt |
| Let | Let | Let |
| Put | Put | Put |
| Quit | Quit | Quit |
| Read | Read (pronounced red) | Read (pronounced red) |
| Set | Set | Set |
| Shut | Shut | Shut |
Pattern B: The V2/V3 Twins (One Change)
The base code changes once. The Simple Past and Past Participle share the exact same compiled spelling.
| Base Form (V1) | Simple Past (V2) | Past Participle (V3) |
|---|---|---|
| Bring | Brought | Brought |
| Build | Built | Built |
| Buy | Bought | Bought |
| Catch | Caught | Caught |
| Feel | Felt | Felt |
| Find | Found | Found |
| Get | Got | Got |
| Have | Had | Had |
| Hear | Heard | Heard |
| Hold | Held | Held |
| Keep | Kept | Kept |
| Leave | Left | Left |
| Lose | Lost | Lost |
| Make | Made | Made |
| Meet | Met | Met |
| Pay | Paid | Paid |
| Say | Said | Said |
| Send | Sent | Sent |
| Think | Thought | Thought |
| Win | Won | Won |
Pattern C: The Complete Fork (Total Change)
This is the most unstable legacy code. All three states have completely different spellings.
| Base Form (V1) | Simple Past (V2) | Past Participle (V3) |
|---|---|---|
| Be | Was / Were | Been |
| Begin | Began | Begun |
| Break | Broke | Broken |
| Choose | Chose | Chosen |
| Do | Did | Done |
| Drink | Drank | Drunk |
| Drive | Drove | Driven |
| Eat | Ate | Eaten |
| Fly | Flew | Flown |
| Forget | Forgot | Forgotten |
| Give | Gave | Given |
| Go | Went | Gone |
| Know | Knew | Known |
| See | Saw | Seen |
| Speak | Spoke | Spoken |
| Take | Took | Taken |
| Throw | Threw | Thrown |
| Wake | Woke | Woken |
| Wear | Wore | Worn |
| Write | Wrote | Written |
Do not try to memorize all the Legacy Code in one sitting. Pick 3 random commands from the tables above every morning and write a short sentence testing them in the Simple Past and Past Participle. Your brain will identify the patterns over time.
Part 6: Debugging Gauntlet (20 Questions)
Instructions: Identify the incorrect Verb State and refactor the sentence. Integrate the Standard Library API where indicated. Write your clean code directly below each prompt.
1. (Corporate): "The manager usually sign off on the budget every Monday." (Fix V1 to V5)
2. (Casual): "I have went to the Brookefield gym three times this week." (Fix V2 to V3)
3. (Corporate): "The developer is look into the memory leak right now." (Fix V1 to V4)
4. (Casual): "We wrapped up the workout and then we go home." (Fix V1 to V2)
5. (Corporate): "She work as a freelancer for several tech companies."
6. (Casual): "I am catch up with my friends at the cafe."
7. (Corporate): "The client has saw the new wireframes already."
8. (Casual): "He whip up a healthy brunch every morning."
9. (Corporate): "We hold off on the launch because the code was broken."
10. (Casual): "I running late because of the traffic in Bangalore."
11. (Corporate): "My sister want to learn Python for her new job."
12. (Casual): "I have drink 3 liters of water today."
13. (Corporate): "The team discuss the API requirements yesterday."
14. (Casual): "She coming to Brookefield this weekend."
15. (Corporate): "The lead dev sign off on the code after he look into it." (Fix both to V2/Past)
16. (Casual): "The pink salt make the oats taste better."
17. (Corporate): "They have finish the React training module."
18. (Casual): "I thinks it is a doable task."
19. (Corporate): "The server crash every time I run this script."
20. (Casual): "We catch up with each other yesterday evening."
Click here to view the System Output (Answer Key)
1.
- Clean Code: "The manager usually signs off on the budget every Monday."
- Logic: The Subject is singular (The manager), so the Power Source must be V5 (-s).
2.
- Clean Code: "I have gone to the Brookefield gym three times this week."
- Logic: After the "HAVE" gate, the verb must be in V3 (gone), not V2 (went).
3.
- Clean Code: "The developer is looking into the memory leak right now."
- Logic: After the "BE" gate (is), the verb must be in V4 (-ing).
4.
- Clean Code: "We wrapped up the workout and then we went home."
- Logic: The sentence is in the past; "go" (V1) must be shifted to V2 (went).
5.
- Clean Code: "She works as a freelancer for several tech companies."
- Logic: 3rd Person Singular subject (She) requires V5.
6.
- Clean Code: "I am catching up with my friends at the cafe."
- Logic: Continuous action (am) requires V4.
7.
- Clean Code: "The client has seen the new wireframes already."
- Logic: Perfect tense (has) requires the V3 state (seen).
8.
- Clean Code: "He whips up a healthy brunch every morning."
- Logic: Routine action by a singular subject (He) requires V5.
9.
- Clean Code: "We held off on the launch because the code was broken."
- Logic: The second half of the sentence is past (was), so the first verb must be V2 (held).
10.
- Clean Code: "I am running late because of the traffic in Bangalore."
- Logic: "Running" (V4) cannot stand alone as a main verb; it needs the "BE" gate (am).
11.
- Clean Code: "My sister wants to learn Python for her new job."
- Logic: 3rd Person Singular (My sister) requires V5.
12.
- Clean Code: "I have drunk 3 liters of water today."
- Logic: After "have," the irregular verb "drink" must be in the V3 state (drunk).
13.
- Clean Code: "The team discussed the API requirements yesterday."
- Logic: "Yesterday" triggers the V2 past state.
14.
- Clean Code: "She is coming to Brookefield this weekend."
- Logic: Future-planned continuous action requires the "BE" gate + V4.
15.
- Clean Code: "The lead dev signed off on the code after he looked into it."
- Logic: Both actions are in the past history (V2).
16.
- Clean Code: "The pink salt makes the oats taste better."
- Logic: Uncountable subjects (Salt) are treated as singular, requiring V5.
17.
- Clean Code: "They have finished the React training module."
- Logic: After "have," use the V3 state.
18.
- Clean Code: "I think it is a doable task."
- Logic: The Subject "I" is an exception; it uses the V1 state, not V5.
19.
- Clean Code: "The server crashes every time I run this script."
- Logic: Singular subject (The server) in a routine/habitual state requires V5.
20.
- Clean Code: "We caught up with each other yesterday evening."
- Logic: Past history trigger (yesterday) requires the V2 state.