You got it! The constitutional directive is to lean into the training data, reuse existing terms as much as you can, but when you must mint new terms, they should sound like what they mean.
You can intuitively understand what "yaml jazz" means, and to the LLM, that term is a "k-line" to a skill that spells out the implications: free-form expressive yaml carries structured meaning, and yaml comments add a rich semantic overlay of meaning for both llms and humans, so it follows for both humans and LLMs to write generous narrative comments, and to write deterministic tools (like cli scripts both LLMs and humans can drive) that round trip yaml and preserve comments they can't understand.
YAML Jazz skill:
https://github.com/SimHacker/moollm/tree/main/skills/yaml-ja...
Here is the "kernel" that has constitutional and intrinsic "operating system" like stuff, including drivers for the orchestrator it's running on.
https://github.com/SimHacker/moollm/tree/main/kernel
MOOLLM Constitution Core:
https://github.com/SimHacker/moollm/blob/main/kernel/constit...
MOOLLM Kernel Architecture:
https://github.com/SimHacker/moollm/blob/main/kernel/ARCHITE...
The part I'm most delighted with, thanks to its inherent power of simplicity, is the "Selfish" prototype based object system, which supports multiple inheritance from both files and latent space. And it can model other more complex object systems like Smalltalk classes, CLOS MOP, generic dispatch, COM interfaces, OLE dispatch and reflection, LambdaMOO objects, Sims advertisements, etc.
The original Self paper by David Ungar and Randall B. Smith is at least as powerful and mind expanding as great LSD, without any of the downsides! Its ideas underly the fast dynamic JavaScript, Java, C# engines we're all running now, so you can use high doses of it every day for work and for play.
SELF: The Power of Simplicity:
https://bibliography.selflanguage.org/_static/self-power.pdf
MOOLLM Object System:
https://github.com/SimHacker/moollm/tree/main/designs/object...
Prototype skill:
https://github.com/SimHacker/moollm/tree/main/skills/prototy...
Self and MOOLLM: Prototypes over the File System:
https://github.com/SimHacker/moollm/blob/main/designs/object...
Latent-Space Inheritance — multiple inheritance from named concepts in training data:
https://github.com/SimHacker/moollm/blob/main/designs/object...
Selfish COM: Directory-as-Object:
https://github.com/SimHacker/moollm/blob/main/kernel/DIRECTO...
Selfish COM: Implementation Guide:
https://github.com/SimHacker/moollm/blob/main/kernel/SELFISH...
Memory Management Protocol:
https://github.com/SimHacker/moollm/blob/main/kernel/memory-...
Context Assembly Protocol:
https://github.com/SimHacker/moollm/blob/main/kernel/context...
There are some important rules about naming, like "big-endian naming", and "k-lines", a term defined by Minsky, and well represented in the training data because he wrote a lot about them:
https://github.com/SimHacker/moollm/tree/main/kernel/naming
K-Lines: A Theory of Memory, MIT AI Memo 516, June 1979 (PDF)
https://courses.csail.mit.edu/6.803/pdf/aim-516.pdf
The skill that explains k-lines:
https://github.com/SimHacker/moollm/tree/main/skills/k-lines
>A K-line is a mental structure that, when activated, reactivates an entire constellation of knowledge, skills, and associations. Minsky defined them in a 1979 MIT AI Lab memo, published in Cognitive Science in 1980, then built Society of Mind (1986) on them:
>"When you get an idea and want to remember it, you create a K-line for it. When later activated, the K-line induces a partial mental state resembling the one that created it."
The art is to choose a coherent set of k-lines and terminology, that's well supported and understood in the training data, and fits together well.
If names are pointers into latent space, then naming is API design.
For contrast, Steve Yegge's approach to Gastown is the exact opposite of moollm's approach. This compares Gastown to moollm:
https://github.com/SimHacker/moollm/tree/main/designs/gastow...