The Complete Toolkit — Boss Drops, Not Prerequisites

"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 tool in this table. You traced mob inheritance trees, used a root verb and particle to form meaning hypotheses, watched Dad adapt Sun Tzu with one character change, and cooked without a recipe by using a flavor control panel.

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:

• Used "root verb + directional clue" as a first hypothesis for many English phrasal verbs
• Used salt, sweetness, fat, umami, and aroma as a compact cooking control panel
• 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 dishes with a five-axis control panel, then checked omitted axes such as acid and texture
• 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
• Used the same control questions to compare Korean, Italian, and Japanese dishes without erasing their differences
• 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 — In formal OO, a subtype supplies its own implementation for an inherited method contract. Idioms, adapted quotations, and boss mechanics are teaching analogies; they do not literally call super(). The one-liner: Overriding is saying "same inherited contract, different implementation here."

Overloading — In formal OO, the same method name is declared with different parameter signatures. Contextual polysemy and an attack button that dispatches by equipped weapon are useful comparisons, but the latter may be runtime polymorphism rather than overloading. The one-liner: Overloading is one method name with multiple accepted signatures.

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.

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 means one class formally inherits from more than one parent; many real designs prefer composition or traits to avoid tight coupling.

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: A pattern that controls access so a system has one designated instance of a class. "Unique" in ordinary language is not enough.

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 an explicit lifecycle and access decision, not a statistical accident in the tail of a distribution.

The trap: Calling everything a Singleton because it seems special. Malenia and a legendary weapon may be unique content, but neither demonstrates controlled single-instance construction and access.

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.

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.

You saw the same learning pattern in 學 vs 習, in "the person who follows recipes vs. the person who understands flavor," and in every Track's Mold Hunt.

See it? One mold. This entire quest has been stamped from it.

Pippa's Confession