rhachet-roles-ehmpathy 1.15.13 → 1.15.14

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].gravity.md

@@ -1,54 +0,0 @@
-# 🧩 .brief.demo: `brief archetypes` via `gravity`
-
-## .what
-the same set of **instances** (🔹 falling apple, 🌙 moon’s orbit, 🌊 ocean tides) can be compressed into different **brief archetypes**.
-each archetype demonstrates the concept of **gravity** through a distinct treatment: definitional, organizational, relational, or pedagogical.
-
----
-
-## 📖 brief.article — definitional
-**treatment:** clarify *what gravity is*
-**content:**
-- defines gravity as the universal attraction between masses
-- relates with the apple falling and the moon orbiting
-- explains its significance for physics and daily life
-
----
-
-## 🗂️ brief.catalog — organizational
-**treatment:** map *how gravity manifests across cases*
-**content:**
-- terrestrial gravity (apple falling, objects pulled to Earth)
-- celestial gravity (moon orbit, planetary motion)
-- tidal gravity (ocean tides pulled by the moon)
-- relates these diverse phenomena under one principle
-
----
-
-## 🎬 brief.demo — relational
-**treatment:** show *how one instance exemplifies gravity*
-**content:**
-- takes the falling apple as the focal instance
-- relates it to the same force governing planetary orbits
-- bridges the link between a simple case and a universal concept
-
----
-
-## 🎓 brief.lesson — pedagogical
-**treatment:** guide *how to learn gravity step by step*
-**content:**
-1. observe a dropped apple (instance of falling objects)
-2. compare to the moon’s orbit (celestial instance)
-3. connect both to Newton’s principle of universal gravitation
-4. practice with examples (why we stay grounded, why tides shift)
-- relates concrete cases to the abstract principle
-
----
-
-## ✨ insight
-- 📖 **article** defines
-- 🗂️ **catalog** organizes
-- 🎬 **demo** exemplifies
-- 🎓 **lesson** teaches
-
-all four compress instances into different treatments — each **relating gravity** in a way tailored to definition, organization, exemplification, or pedagogy.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].joke.md

@@ -1,56 +0,0 @@
-# 🧩 .brief.demo: `brief archetypes via joke`
-
-## .what
-the same **instances** (😂 a knock-knock pun, 🙃 an anti-joke with no punchline, 🎤 a stand-up routine, 🤡 a slapstick gag) can be compressed into different **brief archetypes**.
-this demo shows how the concept of a **joke** is materialized differently depending on the treatment: definitional, organizational, relational, or pedagogical.
-
----
-
-## 📖 brief.article — definitional
-**treatment:** clarify *what a joke is*
-**content:**
-- defines a joke as a **short narrative, phrase, or act designed to elicit humor**, often by subverting expectation
-- relates with the form of a pun (wordplay that flips meaning) and slapstick (physical incongruity)
-- explains how jokes rely on **setup → punchline**, timing, and audience context
-
----
-
-## 🗂️ brief.catalog — organizational
-**treatment:** map *how jokes vary*
-**content:**
-- **verbal jokes** → puns, one-liners, riddles
-- **narrative jokes** → anecdotes, shaggy-dog stories
-- **performative jokes** → slapstick, stand-up, pranks
-- **meta-jokes** → anti-jokes, self-referential humor
-- relates these forms as variations on incongruity, timing, and audience expectation
-
----
-
-## 🎬 brief.demo — relational
-**treatment:** show *how one instance exemplifies a joke*
-**content:**
-- takes a **knock-knock pun** as the focal instance
-- relates how it sets up a predictable pattern, then subverts it with wordplay in the punchline
-- bridges the simple case to the general principle: humor often arises from expectation + violation
-
----
-
-## 🎓 brief.lesson — pedagogical
-**treatment:** guide *how to learn jokes step by step*
-**content:**
-1. observe a simple riddle with an expected answer
-2. replace the expected answer with a surprising one → feel the shift
-3. practice with puns (homophones, double meanings)
-4. try delivering timing-based humor (pause before punchline)
-5. reflect on audience response to refine delivery
-- relates stepwise practice to the general principle of setup, timing, and incongruity
-
----
-
-## ✨ insight
-- 📖 **article** defines joke
-- 🗂️ **catalog** organizes joke types
-- 🎬 **demo** exemplifies joke via a single pun
-- 🎓 **lesson** teaches joke-telling as a learnable skill
-
-this demo shows how the everyday concept of a **joke** can be materialized through brief archetypes, each relating shared instances in a distinct way.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.1.from_instances.[demo].value.md

@@ -1,54 +0,0 @@
-# 🧩 .brief.demo: `brief archetypes via value`
-
-## .what
-the same set of **instances** (💵 a product’s price tag, ❤️ choosing family over work, ⚖️ a debate on justice) can be compressed into different **brief archetypes**.
-this demo shows how the concept of **value** is materialized differently depending on the treatment: definitional, organizational, relational, or pedagogical.
-
----
-
-## 📖 brief.article — definitional
-**treatment:** clarify *what value is*
-**content:**
-- defines value as the measure of worth or importance attributed to something
-- relates with the instances of a price tag on goods and the prioritization of relationships
-- explains how value operates across economic, ethical, and personal domains
-
----
-
-## 🗂️ brief.catalog — organizational
-**treatment:** map *how value manifests across cases*
-**content:**
-- **economic value** → exchange worth (price of a good)
-- **moral value** → ethical priority (justice, fairness)
-- **personal value** → subjective importance (family, love, passion)
-- relates these as distinct yet overlapping forms of the concept of value
-
----
-
-## 🎬 brief.demo — relational
-**treatment:** show *how one instance exemplifies value*
-**content:**
-- takes the example of choosing family over work
-- relates this decision to the broader concept of personal value
-- bridges the specific case to the general principle that humans assign worth beyond money
-
----
-
-## 🎓 brief.lesson — pedagogical
-**treatment:** guide *how to learn value step by step*
-**content:**
-1. examine a product’s price as an instance of economic value
-2. compare it with moral debates (justice vs expedience)
-3. reflect on personal decisions (time with loved ones vs career ambition)
-4. connect these examples to the general principle that “value” is the attribution of worth across domains
-- relates concrete experiences to the abstract principle of value
-
----
-
-## ✨ insight
-- 📖 **article** defines value as worth
-- 🗂️ **catalog** organizes its types
-- 🎬 **demo** exemplifies value in a single case
-- 🎓 **lesson** teaches value as a learnable, multi-domain concept
-
-this demo shows how a contested and multifaceted concept like **value** can still be materialized through brief archetypes, each relating the same set of instances in a distinct way.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2._.[catalog].md

@@ -1,43 +0,0 @@
-# 🧩 .brief.catalog: `mechanisms of document instantiation`
-
-## .what
-each document archetype (📖 article, 🗂️ catalog, 🎬 demo, 🎓 lesson) corresponds to a **mechanism** that materializes a concept in that form.
-this catalog organizes the four mechanisms — **articulate, catalogize, demonstrate, lessonize** — showing how they function in parallel.
-
----
-
-## 📖 articulate → articles (definitional treatment)
-- **mechanism:** materializes a concept *as* an article
-- **function:** defines the concept, sets boundaries, clarifies meaning
-- **example:** articulating “symmetry” by defining invariance under transformations and relating with butterfly wings, squares, and musical phrases
-
----
-
-## 🗂️ catalogize → catalogs (organizational treatment)
-- **mechanism:** materializes a concept *as* a catalog
-- **function:** organizes instances into groups, categories, or dimensions
-- **example:** catalogizing “memory” into short-term vs long-term, then declarative vs procedural
-
----
-
-## 🎬 demonstrate → demos (relational treatment)
-- **mechanism:** materializes a concept *as* a demo
-- **function:** shows how an instance exemplifies the concept, bridging abstract and concrete
-- **example:** demonstrating “walkability” by relating the city of Portland’s sidewalks, mixed-use zoning, and transit integration to the broader concept
-
----
-
-## 🎓 lessonize → lessons (pedagogical treatment)
-- **mechanism:** materializes a concept *as* a lesson
-- **function:** builds a scaffolded progression of steps and practices for learning
-- **example:** lessonizing “gravity” into a sequence: dropping an apple → comparing orbits → stating Newton’s law → practicing with tides
-
----
-
-## ✨ insight
-- 📖 **articulate** defines concepts
-- 🗂️ **catalogize** organizes concepts
-- 🎬 **demonstrate** exemplifies concepts
-- 🎓 **lessonize** teaches concepts
-
-together, these mechanisms form the **system of document instantiation**: four complementary ways to materialize concepts by arranging instances into communicable form.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.articulate.[article].md

@@ -1,27 +0,0 @@
-# 🧩 .brief.article: `articulate`
-
-## .what
-**articulate** is the mechanism that **instantiates articles**: it materializes a concept as a definitional treatment that clarifies *what it is*.
-
----
-
-## 🔬 definition
-- **mechanism:** the materialization of a concept *as* article form.
-- **function:** provides definition, boundary-setting, and explanation so the concept becomes clear and communicable.
-- **distinction:** articulation describes *what an article is*; articulating performs the *instantiation* of an article.
-
----
-
-## 📌 examples
-- to articulate “symmetry,” one defines it as **invariance under transformation**, relating with instances like butterfly wings and geometric rotations.
-- to articulate “leadership,” one defines it as **the capacity to influence and coordinate others**, relating with instances like historical figures or everyday group dynamics.
-- to articulate “entropy,” one defines it as **a measure of multiplicity/uncertainty**, relating with ice melting or shuffled cards.
-
----
-
-## ✨ insight
-**articulate** is the bridge between **concept and definition**:
-- it is the **mechanism** of clarifying meaning and boundaries.
-- it ensures that articles are not anecdotes but **systematic materializations** of conceptual definition.
-
-in knowledge architecture, **articulate** sits alongside mechanisms like **catalogize** (catalogs), **demonstrate** (demos), and **lessonize** (lessons), each materializing concepts in a distinct document mode.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.articulate.[lesson].md

@@ -1,49 +0,0 @@
-# 🧩 .brief.lesson: `how to articulate an article`
-
-## .what
-an **article** is a document that gives a **definitional treatment** of a concept: it clarifies *what the concept is*, often by setting boundaries, tracing meaning, and relating to representative instances.
-this lesson shows step by step how to **articulate an article** effectively.
-
----
-
-## 🎓 steps
-
-1. **identify the concept**
-   - choose the subject of articulation (e.g., “symmetry”)
-   - state it clearly in one sentence as the anchor
-
-2. **define the essence**
-   - provide a concise definition: *what it is at its core*
-   - ensure the definition distinguishes the concept from related ones
-
-3. **relate with instances**
-   - select 1–3 representative cases that make the definition tangible
-   - show how each instance fits the boundaries of the concept
-
-4. **contextualize**
-   - situate the concept in a larger frame: its domain, contrasts, or history
-   - explain why the concept matters or how it functions in practice
-
-5. **compress into structure**
-   - arrange into a few short, well-ordered paragraphs
-   - ensure clarity, minimal noise, maximum signal
-
----
-
-## 📌 example: articulate an article on “symmetry”
-
-- **definition:** symmetry is a structural property where an object remains invariant under a transformation (e.g., reflection, rotation).
-- **instances:** butterfly wings (reflection), square (rotation), musical phrase (repetition).
-- **context:** symmetry is central in mathematics, physics, and aesthetics; it reveals order and regularity in systems.
-- **compression:** three paragraphs, moving from definition → examples → significance.
-
----
-
-## ✨ insight
-to articulate an article:
-- start with a **clear definition**
-- **relate with key instances** to ground it
-- **situate in context** for meaning
-- **compress** into structured paragraphs for clarity
-
-this sequence ensures the article functions as a **definitional treatment** that makes the concept graspable and transmissible.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.catalogize.[article].md

@@ -1,27 +0,0 @@
-# 🧩 .brief.article: `catalogize`
-
-## .what
-**catalogize** is the mechanism that **instantiates catalogs**: it materializes a concept as an organizational treatment that maps how its instances or sub-concepts relate within a system.
-
----
-
-## 🔬 definition
-- **mechanism:** the materialization of a concept *as* catalog form.
-- **function:** organizes instances into clusters, categories, or hierarchies to reveal structure and variation.
-- **distinction:** articulation describes *what a catalog is*; catalogizing performs the *instantiation* of a catalog.
-
----
-
-## 📌 examples
-- to catalogize “memory,” one groups instances into **short-term vs. long-term**, then subdivides into **declarative vs. procedural**.
-- to catalogize “color,” one organizes by **hue, saturation, brightness** or by **additive vs. subtractive models**.
-- to catalogize “jokes,” one maps types like **puns, anecdotes, slapstick, anti-jokes**.
-
----
-
-## ✨ insight
-**catalogize** is the bridge between **concept and structure**:
-- it is the **mechanism** of arranging instances to make a system visible.
-- it ensures that catalogs are not random lists but **systematic materializations** of conceptual organization.
-
-in knowledge architecture, **catalogize** sits alongside mechanisms like **articulate** (articles), **demonstrate** (demos), and **lessonize** (lessons), each materializing concepts in a distinct document mode.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.catalogize.[lesson].md

@@ -1,54 +0,0 @@
-# 🧩 .brief.lesson: `how to catalogize a catalog`
-
-## .what
-a **catalog** is a document that gives an **organizational treatment** of a concept: it maps *how instances or sub-concepts relate* within a system.
-this lesson shows step by step how to **catalogize a catalog** — i.e., how to instantiate a catalog so its structure clearly materializes the concept.
-
----
-
-## 🎓 steps
-
-1. **identify the scope**
-   - choose the domain of organization (e.g., “types of memory”)
-   - define boundaries: what belongs in the catalog, what doesn’t
-
-2. **collect instances**
-   - gather relevant cases or sub-concepts
-   - ensure diversity, so the catalog reflects breadth
-
-3. **group by principle**
-   - decide the organizing logic (taxonomy, dimensions, categories, functions)
-   - examples: short-term vs long-term memory; declarative vs procedural
-
-4. **name and order clusters**
-   - assign clear labels to each group
-   - order them logically (hierarchy, chronology, continuum, network)
-
-5. **compress into structure**
-   - write each group with a short description
-   - present the whole as a coherent, navigable map
-
----
-
-## 📌 example: catalogize a catalog of “memory”
-
-- **scope:** human memory
-- **instances:** remembering a phone number, recalling facts, knowing how to ride a bike
-- **groups:**
-  - **short-term memory** → holding a phone number briefly
-  - **long-term memory** → stored knowledge and skills
-     - **declarative** (facts/events)
-     - **procedural** (skills/habits)
-- **compression:** sections for each cluster, presented hierarchically
-
----
-
-## ✨ insight
-to catalogize a catalog:
-- **scope** defines what’s included
-- **instances** supply the raw material
-- **grouping principles** shape the structure
-- **labels + order** make it navigable
-- **compression** ensures clarity
-
-a catalog succeeds when it reveals the **systematic structure** of a concept, turning scattered instances into an organized map.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.demonstrate.[article].md

@@ -1,26 +0,0 @@
-# 🧩 .brief.article: `demonstrate`
-
-## .what
-**demonstrate** is the mechanism that **instantiates demos**: it materializes a concept as a relational treatment that shows how an instance exemplifies that concept.
-
----
-
-## 🔬 definition
-- **mechanism:** the materialization of a concept *as* demo form.
-- **function:** reveals the concept through a chosen instance, making the abstract visible and graspable.
-- **distinction:** articulation describes *what a demo is*; demonstrating performs the *instantiation* of a demo.
-
----
-
-## 📌 examples
-- to demonstrate “walkability,” one presents Portland as the focal instance, relating its sidewalks, mixed-use layout, and transit integration to the broader concept.
-- to demonstrate “empathy,” one spotlights a nurse comforting a patient, relating this specific act of care to the general principle of understanding and sharing another’s feelings.
-
----
-
-## ✨ insight
-**demonstrate** is the bridge between **concept and exemplar**:
-- it is the **mechanism** of showing concepts *in action* through instances.
-- it ensures that demos are not just anecdotes but **systematic materializations** of concept–instance relations.
-
-in knowledge architecture, **demonstrate** sits alongside mechanisms like **articulate** (articles), **catalogize** (catalogs), and **lessonize** (lessons), each materializing concepts in a distinct document mode.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.demonstrate.[lesson].md

@@ -1,49 +0,0 @@
-# 🧩 .brief.lesson: `how to demonstrate a demo`
-
-## .what
-a **demo** is a document that gives a **relational treatment** of a concept: it shows *how an instance exemplifies a concept*.
-this lesson explains how to **demonstrate a demo** — i.e., how to instantiate a demo so the connection between instance and concept is maximally clear.
-
----
-
-## 🎓 steps
-
-1. **select the concept**
-   - identify the abstraction you want to materialize (e.g., “resilience”).
-
-2. **choose a focal instance**
-   - pick a concrete, vivid case (e.g., a tree bending in strong wind).
-   - ensure it is representative enough to reveal the concept.
-
-3. **frame the relation**
-   - state directly how the instance demonstrates the concept.
-   - highlight the relational link (instance → concept).
-
-4. **situate in context**
-   - explain why this instance is a strong example.
-   - connect to broader relevance (domain, application, meaning).
-
-5. **compress articulation**
-   - keep it concise: usually 2–3 paragraphs.
-   - remove noise, emphasize clarity of the instance–concept link.
-
----
-
-## 📌 example: demonstrating a demo of “resilience”
-
-- **concept:** resilience
-- **instance:** a tree bending in strong wind
-- **relation:** the bending tree demonstrates resilience by showing flexibility under force without breaking.
-- **context:** this everyday natural instance captures the broader human/social concept of adapting to stress.
-- **compression:** two short paragraphs clearly tying instance → concept.
-
----
-
-## ✨ insight
-to demonstrate a demo:
-- pick a **clear instance**
-- articulate its **relation to the concept**
-- situate it in **context**
-- keep the link **compressed and clear**
-
-a demo succeeds when the audience can see the **abstract concept made visible** through a single, well-chosen instance.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.lessonize.[article].md

@@ -1,26 +0,0 @@
-# 🧩 .brief.article: `lessonize`
-
-## .what
-**lessonize** is the mechanism that **instantiates lessons**: it materializes a concept as a structured pedagogical treatment that guides learning.
-
----
-
-## 🔬 definition
-- **mechanism:** the materialization of a concept into lesson form.
-- **function:** provides a scaffolded sequence of steps, examples, and practices so the learner can internalize the concept.
-- **distinction:** articulation describes *what a lesson is*; lessonizing performs the *instantiation* of a lesson.
-
----
-
-## 📌 examples
-- to lessonize “gravity,” one designs a sequence moving from dropping an apple → comparing planetary orbits → explaining Newton’s law → practicing with tidal predictions.
-- to lessonize “empathy,” one builds a progression from observing a friend’s feelings → practicing perspective-taking → responding → reflecting on the effect.
-
----
-
-## ✨ insight
-**lessonize** is the bridge between concept and pedagogy:
-- it is the **mechanism** of turning raw content into structured learning.
-- it ensures that lessons are not improvised but **instantiated systematically**.
-
-in knowledge architecture, lessonize sits alongside other mechanisms (e.g., *articulate, catalogize, demonstrate*) as a specific process for **pedagogical materialization**.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.enbrief.2.lessonize.[lesson].md

@@ -1,54 +0,0 @@
-# 🧩 .brief.lesson: `how to lessonize a lesson`
-
-## .what
-a **lesson** is a document that gives a **pedagogical treatment** of a concept: it guides *how the concept is learned and practiced* through structured progression.
-this lesson explains how to **lessonize a lesson** — i.e., how to instantiate a lesson so it effectively scaffolds understanding.
-
----
-
-## 🎓 steps
-
-1. **define the learning goal**
-   - specify what the learner should understand or be able to do at the end.
-   - e.g., “learn how photosynthesis works.”
-
-2. **choose core instances**
-   - gather examples or cases that ground the concept.
-   - ensure variety: simple → complex, familiar → abstract.
-
-3. **sequence the progression**
-   - order steps to move from known → new, concrete → abstract.
-   - each step should build on the previous one.
-
-4. **embed practice and reflection**
-   - include questions, exercises, or thought experiments.
-   - encourage learners to test and reinforce understanding.
-
-5. **compress into a clear arc**
-   - keep the lesson a few paragraphs or steps, not sprawling.
-   - highlight transitions between steps so the flow is obvious.
-
----
-
-## 📌 example: lessonizing a lesson on “photosynthesis”
-
-- **goal:** understand how plants convert sunlight into energy.
-- **instances:** observing a leaf, recalling oxygen release, examining energy diagrams.
-- **sequence:**
-  1. start with observation of leaves and sunlight.
-  2. explain chlorophyll capturing light.
-  3. show the chemical reaction (CO₂ + H₂O → glucose + O₂).
-  4. connect to everyday significance (oxygen supply, food chain).
-- **practice:** sketch the process or explain it in simple terms to a peer.
-
----
-
-## ✨ insight
-to lessonize a lesson:
-- set a **clear goal**
-- select **grounding instances**
-- create a **progression** that builds understanding
-- add **practice and reflection**
-- keep the arc **compressed but complete**
-
-a lesson succeeds when it transforms **instances into a structured pathway**, enabling the learner to grasp and retain the concept.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.kernelize._.[article].md

@@ -1,58 +0,0 @@
-# 🧩 .brief.article: `<kernelize>`
-
-## .what
-**<kernelize>** is the mechanism that extracts 🌱 **doc.kernels** from any 📚 **doc**.
-it reduces unstructured or expansive material into **atomic expressions**, each carrying **one concept**.
-where a 📚 doc may hold many tangled ideas, <kernelize> isolates them into minimal, portable seeds.
-
----
-
-## 🎯 purpose
-- **distill**: strip away noise, phrasing, and redundancy
-- **separate**: untangle multiple ideas into discrete units
-- **stabilize**: preserve the integrity of each concept in its minimal viable form
-- **prepare**: create fertile, portable kernels for use in 🔖 refs, 🪴 briefs, or new 📚 docs
-
----
-
-## ⚙️ properties
-- **one concept only** — every kernel carries exactly one concept
-- **atomic** — irreducible without breaking the idea
-- **fertile** — can grow into larger articulations (briefs, essays, treatises)
-- **portable** — reusable across different contexts and documents
-
----
-
-## 📌 examples
-
-### ⚖️ gravity
-source doc: *“the reason the apple falls is because earth pulls on it with a force — and in fact, any two masses in the universe attract each other.”*
-kernels extracted:
-- 🌱 `earth pulls on the apple`
-- 🌱 `any two masses attract each other`
-
----
-
-### 🎵 music
-source doc: *“music happens when sounds are arranged in rhythm and melody, and harmony is what gives it depth.”*
-kernels extracted:
-- 🌱 `organized sound creates aesthetic experience`
-- 🌱 `rhythm and melody distinguish music from noise`
-- 🌱 `harmony creates depth in music`
-
----
-
-### 🧩 triangle
-source doc: *“a triangle is a polygon with three sides, three angles, and the sum of its angles is 180°.”*
-kernels extracted:
-- 🌱 `a triangle has three sides`
-- 🌱 `a triangle has three angles`
-- 🌱 `the sum of a triangle’s angles is 180°`
-
----
-
-## ✨ insight
-- 📚 docs contain many concepts, often entangled.
-- **<kernelize>** untangles and harvests them into 🌱 kernels.
-- kernels are the **minimal carriers of meaning** — richer than 🔖 refs, smaller than 🪴 briefs.
-- they are the foundation of concept portability, indexing, and recomposition across the document ecosystem.

package/dist/roles/bhrain/briefs/knowledge/kno301.doc.kernelize._.[lesson].md

@@ -1,88 +0,0 @@
-# 🧩 .brief.lesson: `how to <kernelize>`
-
-## 💡 concept
-**<kernelize>** is the practice of extracting 🌱 **doc.kernels** — the atomic, fertile units of concepts — from any 📚 **doc**.
-most docs contain **many concepts**, often mixed together.
-the goal of <kernelize> is to harvest **each concept individually** in its minimal viable form.
-
----
-
-## 🎯 learning goals
-- recognize that a single doc typically contains **multiple concepts**
-- practice isolating and extracting **one kernel per concept**
-- compare kernels to 🔖 refs (pointers) and 🪴 briefs (structured articulations)
-
----
-
-## 🛠️ method
-
-### step 1: scan for concepts
-- read through the 📚 doc (transcript, notes, essay, article).
-- underline every sentence or clause that carries a **distinct idea**.
-
----
-
-### step 2: isolate each idea
-- separate intertwined sentences into discrete conceptual units.
-- treat each idea as a candidate for its own kernel.
-
----
-
-### step 3: reduce to the irreducible
-- rewrite each idea in its **shortest viable form**.
-- test: *if I cut further, does the concept break?*
-- keep only **one concept per kernel**.
-
----
-
-### step 4: declare as kernels
-- format each idea as a 🌱 **doc.kernel**.
-- a single doc may yield a **set of kernels** — one per concept.
-
----
-
-## 📌 practice examples
-
-### ⚖️ gravity (from a lecture transcript)
-> *“so, basically, the reason the apple falls is because earth pulls on it with a force — and actually, any two masses in the universe attract each other, that’s Newton’s big insight.”*
-
-kernels extracted:
-- 🌱 `earth pulls on the apple`
-- 🌱 `any two masses attract each other`
-- 🌱 `Newton identified universal gravitation as a key insight`
-
----
-
-### 🎵 music (from a conversation)
-> *“when you line up sounds in rhythm and melody, suddenly it feels like music instead of just noise. and harmony is what makes it feel rich.”*
-
-kernels extracted:
-- 🌱 `organized sound creates aesthetic experience`
-- 🌱 `rhythm and melody distinguish music from noise`
-- 🌱 `harmony creates richness in music`
-
----
-
-### 🧩 triangle (from a textbook)
-> *“a triangle is defined as a polygon with three sides, three angles, and the sum of its angles equal to 180°.”*
-
-kernels extracted:
-- 🌱 `a triangle has three sides`
-- 🌱 `a triangle has three angles`
-- 🌱 `the sum of a triangle’s angles is 180°`
-
----
-
-## ✨ reflection
-- 📚 docs = soils full of **many concepts** (entangled, verbose, raw).
-- 🔖 refs = labels into concepts (*“gravity”*, *“music”*).
-- 🌱 kernels = harvested seeds, **one per concept**.
-- 🪴 briefs = portable pots, where kernels are transplanted and structured.
-
----
-
-## 🧠 takeaway
-to **<kernelize>** is to **harvest all the concepts from a doc**:
-- extract **each concept separately**
-- reduce it to its **minimal viable form**
-- treat kernels as **fertile seeds** for cataloging, briefing, or hosting in new docs.