prototype
PROTOTYPE
"Objects all the way down."
The philosophy of prototype-based inheritance: no classes, just concrete examples that you clone and modify.
Lineage: Self, this skill, and multiple parents
This skill is directly inspired by Self. In MOOLLM, Self is one of this skill’s prototypes: the schemapedia self mechanism names that parent lineage (Ungar, Smith, and collaborators). The same Delegation Object Protocol applies to skills as to room instances: an ordered PROTOTYPES.yml can list several parent skills—Self is not the only possible parent. Because prototype inherits from Self, it already follows the rules that let any MOOLLM object inherit from multiple prototypes (local wins, then each parent in order, first match wins).
The Problem with Classes
Classical inheritance says:
- Define an abstract blueprint (class)
- Instantiate it to create objects
- Objects are "instances of" classes
More from simhacker/moollm
self-repair
Missing state triggers repair, not failure.
41probability
Motto: The LLM is the dice. It narrates the outcome.
32memory-palace
Spatial organization of knowledge in navigable directories
29persona
Identity layers for characters — WHO they are vs WHAT they do
26dog
Canine interactions, loyalty mechanics, and pack dynamics
22storytelling-tools
Build narrative capture and sharing into the system.
20