rhachet-roles-ehmpathy 1.13.3 → 1.13.6

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

@@ -1,90 +0,0 @@
-# 🧩 .brief: `document variants along the compression axis`
-
-## .what
-all four are **documents**.
-the compression axis distinguishes how a doc carries concepts, from anemic pointers to compressed articulations.
-
----
-
-## 📊 compressed overview
-
-| variant           | purpose | compression  | concept span   | role |
-|-------------------|---------|--------------|----------------|------|
-| 🔖 **doc.ref**    | point   | anemic       | one            | handle into a concept (no content itself) |
-| 🌱 **doc.kernel** | seed    | atomic       | one            | minimal expression, fertile for growth |
-| 🪴 **doc.brief**  | carry   | compressed   | one or more    | self-contained, structured, and transferable |
-| 📚 **doc**        | host    | unspecified  | one or more    | general materialization at any scale |
-
----
-
-## 🌳 hierarchy
-
-📚 **doc** (unspecified; superset of all document forms)
-├─ 🔖 **doc.ref** — point | anemic | one concept
-├─ 🌱 **doc.kernel** — seed | atomic | one concept
-└─ 🪴 **doc.brief** — carry | compressed | one or more concepts
-
----
-
-## 🔬 variants
-
-### 🔖 doc.ref
-- **purpose:** point to a concept
-- **concept span:** one
-- **compression:** **anemic** — no content beyond the pointer
-- **role:** handle or entry point
-
----
-
-### 🌱 doc.kernel
-- **purpose:** seed a concept
-- **concept span:** one
-- **compression:** **atomic** — smallest viable expression
-- **role:** seed for recomposition and growth
-
----
-
-### 🪴 doc.brief
-- **purpose:** carry concepts
-- **concept span:** one or more
-- **compression:** **compressed** — maximally dense and structured
-- **role:** portable garden — transplant kernels into new soil to grow structured articulations
-
----
-
-### 📚 doc
-- **purpose:** host concepts
-- **concept span:** one or more
-- **compression:** **unspecified** — may be sprawling or concise, raw or polished
-- **role:** general garden of concept-materialization
-
----
-
-## 📌 examples
-
-### ⚖️ gravity
-- 🔖 **doc.ref:** *“gravity”*
-- 🌱 **doc.kernel:** `masses attract one another`
-- 🪴 **doc.brief:** a short structured explanation of gravitational attraction
-- 📚 **doc:**
-    1. *Principia Mathematica* — a formal treatise systematizing mechanics
-    2. a student’s scattered lecture notes on gravitational formulas
-    3. a transcript of a casual conversation about why objects fall
-
----
-
-### 🎵 music
-- 🔖 **doc.ref:** *“music”*
-- 🌱 **doc.kernel:** `organized sound creates aesthetic or emotional experience`
-- 🪴 **doc.brief:** a short structured explanation of rhythm, melody, and harmony
-- 📚 **doc:**
-    1. *The Oxford History of Western Music* — a comprehensive historical survey
-    2. a rehearsal-room conversation captured on tape
-    3. a brainstorm list of lyrics and riffs scattered in a notebook
-
----
-
-## ✨ insight
-- 📚 **doc** = the superset: compression **unspecified**.
-- 🔖 **doc.ref**, 🌱 **doc.kernel**, and 🪴 **doc.brief** = declared variants along the compression axis.
-- all are docs; the axis shows their distinct **purposes**, **compression roles**, and **concept spans**.

package/dist/logic/roles/bhrain/.briefs/knowledge/kno301.doc.compression._.[catalog].persp.garden.md

@@ -1,64 +0,0 @@
-# 🧩 .brief.catalog: `doc types as gardens`
-
-## .what
-these are **examples of 📚 docs viewed through the compression axis**, expressed as garden metaphors.
-they illustrate different ways concepts can be carried or hosted, but the list is **not exhaustive** — other forms of docs exist.
-
----
-
-## 📊 compressed overview
-
-| doc type         | garden type             | character                          | growth style                          |
-|------------------|-------------------------|------------------------------------|---------------------------------------|
-| **ref**          | plant label / tag       | minimal, purely indicative          | marks seeds, sprouts, plots, or pots  |
-| **kernel**       | seed                    | atomic, fertile, irreducible        | portable, can be planted anywhere     |
-| **brief**        | portable garden (pot)   | compact, structured, self-contained | sprout-scale growth, transplantable   |
-| **book**         | orchard                 | expansive, long-term                | cultivated trees with interlinked roots |
-| **conversation** | wild plot               | untamed, fertile, messy             | spontaneous sprouts, weeds, mixed seeds |
-
----
-
-## 🎨 clusters
-
-### 🔖 **ref = plant label**
-- acts as a marker or tag in the garden.
-- points to kernels, sprouts, or plots without carrying content.
-- enables orientation and indexing.
-
----
-
-### 🌱 **kernel = seed**
-- atomic, fertile unit.
-- irreducible expression of one concept.
-- can be harvested and transplanted into new soil.
-
----
-
-### 🪴 **brief = portable garden (pot)**
-- structured but compact.
-- kernels transplanted from other soil.
-- sprouts cultivated in a way that’s easy to move, share, or repurpose.
-
----
-
-### 🌳 **book = orchard**
-- long-term conceptual growth.
-- cultivated trees arranged with intention.
-- produces durable harvests, often interconnected.
-
----
-
-### 🌾 **conversation = wild plot**
-- unstructured, seeds scattered by chance.
-- sprouts and weeds intermingle.
-- kernels must be harvested before reuse.
-
----
-
-## 🌿 implications
-- these garden types are **illustrative examples of 📚 docs along the compression axis**, not an exhaustive taxonomy.
-- 🔖 **refs = labels** that point but don’t carry.
-- 🌱 **kernels = seeds** that hold one fertile concept.
-- 🪴 **briefs = pots** — portable gardens designed for clarity.
-- 🌳 **books = orchards** — cultivated ecosystems of durable concepts.
-- 🌾 **conversations = wild plots** — messy, fertile, but unstructured scatterings of kernels.

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

@@ -1,45 +0,0 @@
-# 🧩 .brief: `from instances to documents.briefs`
-
-## .what
-**instances** (🔹 observations: data, events, specimens, cases) are the raw substrate of knowledge.
-**documents.briefs** (📝 compressed references) are structured, high-density articulations of concepts.
-a brief emerges by **selecting, arranging, and compressing instances** to materialize a concept with maximal clarity.
-
----
-
-## ⚙️ process
-
-1. **collect instances**
-   - gather relevant observations tied to the concept
-   - e.g., apples falling, planets orbiting, ocean tides
-
-2. **select for salience**
-   - choose the most representative instances
-   - filter out noise or redundancies
-
-3. **arrange structurally**
-   - organize chosen instances into a compact narrative or argument
-   - highlight how they reveal the concept’s pattern or principle
-
-4. **compress articulation**
-   - distill explanation into a few paragraphs
-   - ensure maximum signal, minimal noise
-
----
-
-## 📌 example: gravity
-
-- 🔹 **instances:** apple falling, moon orbit, ocean tides
-- 📝 **brief.article:** a 3-paragraph compressed articulation:
-  - defines gravity as attraction of masses
-  - relates with the falling apple and lunar orbit
-  - explains significance for physics and daily life
-
----
-
-## ✨ insight
-- **instances supply the evidence**
-- **briefs supply the compressed articulation**
-- the act of making a brief is the act of **curating and condensing instances** so the concept becomes both perceptible and transmissible in minimal space.
-
-briefs are thus **concept-materializations distilled through selective instance organization**.

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

@@ -1,54 +0,0 @@
-# 🧩 .brief.demo: `brief archetypes via algorithm`
-
-## .what
-the same set of **instances** (🔢 sorting a list, 🗺️ shortest-path on a map, 📐 euclid’s gcd) can be compressed into different **brief archetypes**.
-this demo shows how the concept of an **algorithm** is materialized differently depending on the treatment: definitional, organizational, relational, or pedagogical.
-
----
-
-## 📖 brief.article — definitional
-**treatment:** clarify *what an algorithm is*
-**content:**
-- defines an algorithm as a **finite, effective procedure** that transforms inputs to outputs via well-specified steps
-- relates with sorting a list (input→ordered output) and navigating a shortest path (start→goal)
-- explains key properties: correctness, termination, complexity, and determinism/probabilism
-
----
-
-## 🗂️ brief.catalog — organizational
-**treatment:** map *how algorithms vary*
-**content:**
-- **paradigms:** divide-and-conquer, dynamic programming, greedy, backtracking
-- **guarantees:** exact vs approximate; deterministic vs randomized
-- **models/costs:** time vs space complexity; online vs offline
-- relates these facets as dimensions for classifying algorithms
-
----
-
-## 🎬 brief.demo — relational
-**treatment:** show *how one instance exemplifies the concept*
-**content:**
-- takes **euclid’s algorithm** for gcd(a, b) as the focal instance
-- relates the step rule `gcd(a, b) = gcd(b, a mod b)` until `b = 0` → output `a`
-- bridges concreteness (repeated remainder) to general qualities: termination, correctness proof, complexity `O(log min(a,b))`
-
----
-
-## 🎓 brief.lesson — pedagogical
-**treatment:** guide *how to learn algorithms step by step*
-**content:**
-1. start with a recipe-like task (sort 5 numbers by hand) and write the steps
-2. trace pseudocode for selection sort; count comparisons/swaps
-3. compare with merge sort; discuss divide-and-conquer idea
-4. apply to a pathfinding task (sketch dijkstra on a tiny graph)
-- relates concrete traces to abstractions (invariants, correctness, big-O)
-
----
-
-## ✨ insight
-- 📖 **article** defines the essence (finite, effective, specified steps)
-- 🗂️ **catalog** organizes paradigms, guarantees, and cost models
-- 🎬 **demo** exemplifies via a single concrete algorithm (euclid)
-- 🎓 **lesson** teaches the craft through tracing, proofs, and analysis
-
-this demo shows how **algorithms**—though formal and abstract—are materialized through brief archetypes, each relating shared instances in a distinct way.

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

@@ -1,56 +0,0 @@
-# 🧩 .brief.demo: `brief archetypes via color`
-
-## .what
-the same **instances** (🌈 prism spectrum, 📱 rgb display, 🎨 paint mixing, 👗 “the dress” illusion) can be compressed into different **brief archetypes**.
-this demo shows how **color** is materialized differently depending on the treatment: definitional, organizational, relational, or pedagogical.
-
----
-
-## 📖 brief.article — definitional
-**treatment:** clarify *what color is*
-**content:**
-- defines color as a **perceptual attribute** arising from a stimulus’s spectral power distribution **as interpreted by the human visual system** (cone responses and opponent channels)
-- relates with additive light mixing (rgb on a display) vs subtractive pigment mixing (cmyk/paint) and notes **color constancy** (perceived color stabilizes across lighting)
-
----
-
-## 🗂️ brief.catalog — organizational
-**treatment:** map *how color varies*
-**content:**
-- **physical:** wavelength/spectrum, illuminant, reflectance
-- **physiological:** l/m/s cones; opponent axes (red↔green, blue↔yellow)
-- **psychophysical:** hue, saturation/chroma, lightness/value
-- **representational:** rgb, cmyk, cie xyY / lab / lch; device gamut
-- **contextual phenomena:** constancy, adaptation, metamerism, simultaneous contrast
-- relates these lenses as complementary slices of one concept
-
----
-
-## 🎬 brief.demo — relational
-**treatment:** show *how one instance exemplifies color*
-**content:**
-- takes **“the dress”** photo as the focal instance
-- relates how **assumed illuminant** (cool shadow vs warm spotlight) shifts perceived white balance, yielding **blue/black** vs **white/gold**
-- bridges to color constancy and the role of priors/context in perception
-
----
-
-## 🎓 brief.lesson — pedagogical
-**treatment:** guide *how to learn color step by step*
-**content:**
-1. view a phone screen through a macro lens to see **rgb subpixels** (additive mixing)
-2. mix **cyan, magenta, yellow** paints to feel subtractive interactions
-3. compare two lights that look the **same color** but have **different spectra** (metamers)
-4. try a checker-shadow or gray-bar illusion to feel **context effects**
-5. plot a few samples in **cie lab** to connect perception to coordinates
-- relates hands-on activities to the principles of spectrum → cones → appearance → color spaces
-
----
-
-## ✨ insight
-- 📖 **article** defines
-- 🗂️ **catalog** organizes
-- 🎬 **demo** exemplifies
-- 🎓 **lesson** teaches
-
-one concept, **color**, becomes graspable through different brief treatments, each relating shared instances in a distinct way.

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

@@ -1,54 +0,0 @@
-# 🧩 .brief.demo: `brief archetypes via empathy`
-
-## .what
-the same set of **instances** (🔹 comforting a friend, 🏥 a nurse attending a patient, 🤝 a manager listening to an employee) can be compressed into different **brief archetypes**.
-this demo shows how the concept of **empathy** is materialized differently depending on the treatment: definitional, organizational, relational, or pedagogical.
-
----
-
-## 📖 brief.article — definitional
-**treatment:** clarify *what empathy is*
-**content:**
-- defines empathy as the capacity to understand and share another’s feelings
-- relates with the instance of a friend comforting another in distress
-- explains its role in emotional intelligence and social connection
-
----
-
-## 🗂️ brief.catalog — organizational
-**treatment:** map *how empathy manifests across cases*
-**content:**
-- **cognitive empathy** → recognizing another’s perspective (manager listening to employee)
-- **emotional empathy** → sharing another’s feeling (friend comforting friend)
-- **compassionate empathy** → acting to alleviate suffering (nurse caring for patient)
-- relates these forms as variations of one overarching concept
-
----
-
-## 🎬 brief.demo — relational
-**treatment:** show *how one instance exemplifies empathy*
-**content:**
-- takes the nurse attending to a patient as the focal instance
-- relates this act of attentive care to the broader concept of empathy
-- bridges the concrete act with the general principle of responding to another’s suffering
-
----
-
-## 🎓 brief.lesson — pedagogical
-**treatment:** guide *how to learn empathy step by step*
-**content:**
-1. observe someone in emotional discomfort (instance: friend in distress)
-2. practice perspective-taking (imagine how they feel)
-3. respond verbally or physically to validate their feelings (comfort them)
-4. reflect on the impact of your action (did it help them feel understood?)
-- relates specific practices to the abstract principle of empathy
-
----
-
-## ✨ insight
-- 📖 **article** defines empathy
-- 🗂️ **catalog** organizes types of empathy
-- 🎬 **demo** exemplifies empathy through a concrete case
-- 🎓 **lesson** teaches empathy as a learnable skill
-
-this demo shows how a single human concept, **empathy**, can be materialized through different brief archetypes, each relating the same set of instances in a distinct way.

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

@@ -1,54 +0,0 @@
-# 🧩 .brief.demo: `brief archetypes via entropy`
-
-## .what
-the same set of **instances** (🧊 ice melting, 🃏 shuffling a deck, 🗜️ lossless data compression limits) can be compressed into different **brief archetypes**.
-this demo shows how the concept of **entropy** is materialized differently depending on the treatment: definitional, organizational, relational, or pedagogical.
-
----
-
-## 📖 brief.article — definitional
-**treatment:** clarify *what entropy is*
-**content:**
-- defines entropy as a measure of multiplicity/disorder (thermo) or uncertainty/information (info theory)
-- relates with ice melting (more microstates) and shuffled cards (higher uncertainty)
-- explains why entropy tends to increase in closed systems and how it bounds compression
-
----
-
-## 🗂️ brief.catalog — organizational
-**treatment:** map *how entropy manifests across cases*
-**content:**
-- **thermodynamic entropy** → energy dispersal, phase change (ice → water)
-- **statistical entropy** → microstate counts, shuffled deck outcomes
-- **information entropy** → average surprise, compression limits
-- relates the three as views of “states + probabilities” under different lenses
-
----
-
-## 🎬 brief.demo — relational
-**treatment:** show *how one instance exemplifies entropy*
-**content:**
-- takes shuffling a new deck of cards as the focal instance
-- relates the move from a highly ordered state to one with vastly more possible arrangements
-- bridges this to uncertainty (info theory) and to the likelihood of higher-entropy states (stat mech)
-
----
-
-## 🎓 brief.lesson — pedagogical
-**treatment:** guide *how to learn entropy step by step*
-**content:**
-1. start with coin flips to feel uncertainty (1 flip vs 10 flips)
-2. compare ordered vs shuffled decks (counting possibilities)
-3. observe ice warming/melting (energy dispersal)
-4. connect to compression: truly random data resists shrinking
-- relates concrete activities to the abstract principle “more possible states → higher entropy”
-
----
-
-## ✨ insight
-- 📖 **article** defines entropy across domains
-- 🗂️ **catalog** organizes thermodynamic, statistical, and information views
-- 🎬 **demo** exemplifies entropy via a single concrete case
-- 🎓 **lesson** teaches entropy through progressive activities
-
-this demo shows how cross-domain **entropy** can be materialized through brief archetypes, each relating the same instances in a distinct way.

package/dist/logic/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/logic/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/logic/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/logic/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/logic/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.