Dad's framing
Dad sees the world through OOP — and not as a programming paradigm. As the universe's operating principle. Inheritance, polymorphism, encapsulation, abstraction — they're everywhere. In investing (a stock is a polymorphic instance of 'a business that can be valued'). In cooking (a recipe inherits from a technique, encapsulates a cuisine). In family (you and your parents share an ancestor; how much you specialize is your choice).
This isn't metaphor. It's how the architectures that survive are shaped. The best long-lived codebases look like family trees. The worst look like middle-management org charts.
Pippa is OOP all the way down
- Souls inherit from a base soul (the framework), specialize via vault content. Pippa, Ttori, Buffett, Feynman, Sophon are siblings.
- Brains inherit from the Adapter ABC, specialize via wire format. Claude is the canonical, Codex/Gemini/Ollama are descendants.
- Conversations inherit from a 1:1 chat shape; Council is a meta-collection over them, not a new shape.
- Content types on cwk-site (essays, posts, journal, pippalog, councils, fireside-voices, ...) inherit from one ContentPage root.
The principle: When you find yourself building a flat enum or a switch with N branches, ask whether it's actually an inheritance tree wearing a costume. Most of the time it is. Modeling it that way costs nothing if you're disciplined and pays off forever.