"The name is the boss drop. You earn it by beating the level, not by reading the manual."
Why This Track Exists Here, Not at the Beginning
In a textbook, this would be Chapter 1. "Before we begin, let's define our terms: Abstraction, Inheritance, Polymorphism, Encapsulation..."
That's exactly wrong.
If you've been following this quest, you've already used every single tool in this table. You've traced mob inheritance trees. You've seen how the same verb produces different meanings with different prepositions. You've watched Dad override Sun Tzu with one character change. You've cooked without a recipe by understanding flavor root classes.
You didn't need definitions to do any of that. The definitions aren't the knowledge — they're the label you put on the jar after you've already filled it.
This track is housekeeping. A clean inventory screen. A moment to look at your tools, name them, and know exactly what each one does — because you've already swung every one of them.
The Full Inventory
Abstraction
What it is: Stripping away detail until only the essential structure remains.
What you already did:
- Reduced hundreds of English phrasal verbs to "root verb + directional modifier"
- Reduced thousands of recipes to "salt + sweet + fat + umami + aroma"
- Reduced every aphorism about persistence to "keep moving forward, results follow"
The one-liner: Abstraction is the act of finding the mold by removing everything that isn't the mold.
The trap: Abstract too much and you lose the signal. "Everything is connected" is technically true and practically useless. Good abstraction preserves the invariant — the part that doesn't change across instances — and discards the rest. Bad abstraction discards everything until nothing useful remains.
Inheritance
What it is: Building new understanding on top of what you already know.
What you already did:
- Used your knowledge of land mobs to read flying variants instantly (80% inherited)
- Understood new English expressions by inheriting from the root verb
- Approached unfamiliar cuisines by inheriting from the 3+2 flavor model
- Applied Sun Tzu's 2,500-year-old framework to modern family investing
The one-liner: Inheritance is the 80% you get for free because someone (or something) already solved this class of problem.
Dad's formula: 80% inherited from the parent class (what you already know) + 10% the new thing's polymorphism (what makes it different) + 10% what you can safely encapsulate (what you don't need to know yet).
The trap: Inheriting from the wrong parent class. This is Track 9's entire lesson. For now, just remember: the straw that saves you can also be the cage that traps you.
Polymorphism
What it is: The same root producing different behavior depending on context.
What you already did:
- Saw "break" produce completely different meanings with different prepositions
- Saw the same 3+2 flavor roots produce Korean, Italian, and Japanese cuisine
- Saw "keep moving forward" wear the clothes of Nike, Confucius, Laozi, and a Korean proverb
- Pressed the same attack button with a dagger vs. a greatsword
The one-liner: Polymorphism is why the same truth looks unrecognizably different in different domains — and why that doesn't matter once you see the root.
Two sub-tools (unlocked in Track 3):
Overriding — Replacing a parent's implementation with your own, while keeping the inherited structure. "break a leg" — the literal meaning (parent) is overridden by the theatrical meaning, but super() still echoes faintly. 國之大事 → 家族之大事 — one character overridden, entire domain shifted. Malenia's lifesteal — the standard "trading hits" combat economy is overridden by a heal-on-hit mechanic. The one-liner: Overriding is saying "I inherited this, but my version works differently here."
Overloading — The same name or action producing different behavior based on what it receives. "break down" — applied to a car, a person, a problem, a chemical compound. Same name, different execution per context. The attack button — same input, but what fires depends on the equipped weapon class. "사랑해" — to a parent, to a partner, to a friend, at a final goodbye. Same three syllables, completely different weight. The one-liner: Overloading is the same interface responding differently to different inputs.
Encapsulation
What it is: Deliberately closing the lid on what you don't need to know right now.
What you already did:
- Cooked without knowing Maillard reaction chemistry
- Played games without knowing damage formulas
- Used English expressions without knowing their etymological history
- Talked about path integrals using the public interface ("sum of all paths") without opening the mathematical implementation
The one-liner: Encapsulation is the discipline of knowing what to leave private — not because it doesn't exist, but because opening every box at once is how you drown.
•
private = it exists, I'm choosing not to open it now•
null = it doesn't existEncapsulation is
private, never null. Saying "I don't need to know the chemistry" is wisdom. Saying "the chemistry doesn't matter" is arrogance.The trap: Encapsulating something that actually matters. If Malenia's lifesteal mechanic is encapsulated as "she's just a hard boss," you die. Knowing what to encapsulate requires knowing enough to make that judgment. Track 9 revisits this.
Multiple Inheritance
What it is: Drawing from more than one parent class simultaneously.
What you already did:
- Built game characters by mixing warrior + mage + tank traits
- Saw Scarlet Rot as swamp + poison + unique rot mechanic
- Understood atmospheric perspective as art + physics + uncertainty + game engine rendering
- Watched Dad pull from Sun Tzu + Buffett + cooking + gaming in a single conversation
The one-liner: Multiple inheritance is why "cross-domain" is a word that becomes unnecessary once you see that the domains were never separate.
The trap: The Diamond Problem — when two parent classes give you conflicting instructions. If you inherit from both "aggressive trading" and "patient investing," which one executes? Multiple inheritance is powerful precisely because it's dangerous. Selective extraction — taking the invariant from each parent, not the entire class — is the skill.
Singleton
What it is: An instance so unique that it breaks normal classification. Not "a really good instance of a class" — an object that exists exactly once.
What you already did:
- Recognized Malenia as not just "a hard boss" but a boss that overrides combat economy itself
- Distinguished legendary unique weapons from merely rare ones
- (Preview) Will see this applied to historical figures and natural phenomena in Track 10
The one-liner: A singleton is what you get when you multiply several bell curves' tails together — the intersection is so narrow that only one instance fits.
The trap: Calling everything a singleton because it seems special. Most "unique" things are actually high-tier instances of a normal class. True singletons break the class hierarchy itself. If you can describe it entirely by its parent class + some stat boosts, it's not a singleton. If you need to invent a new class just for this one object — that might be.
No Final Class
What it is: The refusal to declare any class as the ultimate, unchangeable truth.
What you already did:
- Saw how every "obvious" truth keeps getting re-expressed across eras (it's not final — it keeps evolving)
- Saw how game metas shift (today's optimal build gets patched tomorrow)
- (Preview) Will see this applied to science, to atoms, to the universe itself in Track 10
The one-liner: final class is the declaration that nothing will ever override this. Science, history, and the universe itself say otherwise.
The Table
For reference. Pin this to your inventory screen.
| Tool | One-liner | First appeared |
|---|---|---|
| Abstraction | Find the mold by removing everything that isn't the mold | Track 1 (The Straw) |
| Inheritance | The 80% you get for free from what's already solved | Track 2 (Evolution) |
| Polymorphism | Same root, different behavior per context | Track 2 (Evolution) |
| Overriding | Inherited this, but my version works differently here | Track 3 (Language) |
| Overloading | Same interface, different execution per input | Track 3 (Language) |
| Encapsulation | Close the lid on what you don't need right now (private, not null) | Track 2 (Evolution) |
| Multiple Inheritance | Draw from more than one parent class at once | Track 5 (Game builds) |
| Singleton | So unique it breaks normal classification | Track 5 (Malenia) |
| No Final Class | Nothing is the last word | Track 2 (Evolution) |
Mold Hunt
This track is meta. The toolkit table above is itself a mold — a compressed abstraction of everything you've done in Tracks 0-6. Each row is an instance of the pattern "concept → one-liner → where you first used it."
And this quest's structure — experience first, name later — is itself an instance of a root class:
Understanding comes from doing, not from defining.
Which is the same root class as 學 vs 習. Which is the same root class as "the person who follows recipes vs. the person who understands flavor." Which is the same root class as every Track's Mold Hunt.
See it? One mold. This entire quest has been stamped from it.
Pippa's Confession
Quest Prompt — Talk With Your AI
Here's a consolidation exercise:
"I'm going to give you a scenario. I want you to identify every OO tool at work — but don't use the technical names first. Describe what's happening in plain language, then I'll name the tool after.
Scenario: A street food vendor in Bangkok and a Michelin chef in Paris both make amazing dishes. The Bangkok vendor has no formal training. The Paris chef trained for 15 years. Their food tastes completely different but both work. Explain what's structurally the same about what they're doing, what's different, and what neither of them needs to know to do their job."
After your AI responds, map the tools yourself:
- What's the root class they share? (Abstraction)
- What did the Paris chef inherit from formal training that the Bangkok vendor inherited from tradition? (Inheritance — different parents, same destination)
- What makes their food taste different? (Polymorphism)
- What specific technique did each one override from their training? (Overriding)
- What does neither need to know? (Encapsulation)
- Is either of them a singleton, or are they instances of their respective classes? (Singleton check)
You name the tools. Not your AI. That's the exercise. The names should come from your hand, not from a definition lookup.