rhachet-roles-ehmpathy 1.13.3 → 1.13.6

package/dist/logic/roles/bhrain/.briefs/knowledge/kno101.primitives.1.ontology.[article].frame.docs_as_materializations.md

@@ -1,63 +0,0 @@
-# 🧩 .brief: `instances, documents, concepts`
-
-## .what
-knowledge rests on three interdependent layers:
-- **instances** (atoms of data/experience)
-- **documents** (materializations built on instances)
-- **concepts** (patterns/relationships in reality)
-
----
-
-## 🔬 structure
-
-### 1. instances = atoms
-- the irreducible substrate: data, events, cases, specimens
-- raw, concrete, concept-neutral until organized
-
-### 2. documents = materializations
-- organized arrangements of instances that **make concepts visible**
-- treatments:
-  - **article = definitional**
-  - **catalog = organizational**
-  - **demo = relational**
-  - **lesson = pedagogical**
-
-### 3. concepts = patterns in reality
-- abstract structures that exist independent of documentation
-- revealed, not created, by documents
-- persist across contexts, even if differently expressed
-
----
-
-## 🔗 relationship
-
-\`\`\`
-concepts (patterns in reality)
-    ↓ materialized via
-documents (organized arrangements of instances)
-    ↓ grounded in
-instances (atoms of raw data/experience)
-\`\`\`
-
----
-
-## 📌 examples
-
-- **gravity**
-  - concept: a real principle of nature
-  - documents: Newton’s *Principia* (article/lesson)
-  - instances: apples falling, orbits, tides
-
-- **leadership**
-  - concept: a relational pattern in human groups
-  - documents: biographies, case studies, management guides
-  - instances: specific leader actions, group decisions
-
----
-
-## ✨ insight
-- **instances** = evidentiary base
-- **documents** = concept-detection and transmission devices
-- **concepts** = pre-existing patterns that documents reveal
-
-knowledge emerges in practice not because concepts are invented, but because documents **make them perceptible** by arranging instances.

package/dist/logic/roles/bhrain/.briefs/knowledge/kno101.primitives.1.ontology.[article].frame.docs_as_references.md

@@ -1,45 +0,0 @@
-# 🧩 .brief: `instances, documents, concepts as observations, references, referents`
-
-## .what
-knowledge can be framed as a triad of **observations, references, and referents**:
-- 🔹 **instances = observations**
-- 📑 **documents = references**
-- 🌐 **concepts = referents**
-
-this alignment highlights how knowledge flows: from what is observed, to how it is referenced, to what those references ultimately point to in reality.
-
----
-
-## 🔬 structure
-
-### 🔹 instances = observations
-- raw particulars: data points, events, cases, specimens
-- directly perceived or recorded
-- evidentiary substrate for knowledge
-
-### 📑 documents = references
-- organized forms that point to and frame observations
-- articles, catalogs, demos, lessons
-- mediate between what is observed and what is real by structuring references
-
-### 🌐 concepts = referents
-- real patterns, structures, or principles in reality
-- exist independently of observation or documentation
-- what references (documents) ultimately point toward
-
----
-
-## 📌 example: gravity
-
-- **observations (instances):** apples falling, planets orbiting, tides shifting
-- **references (documents):** Newton’s *Principia*, astronomical tables, physics lessons
-- **referent (concept):** the real force/pattern of gravitational attraction
-
----
-
-## ✨ insight
-- 🔹 **observations** give us the data of experience
-- 📑 **references** organize those observations for transmission
-- 🌐 **referents** are the real-world structures those references aim at
-
-documents are thus **structured references**: they do not create concepts but link observations to the pre-existing referents those observations disclose.

package/dist/logic/roles/bhrain/.briefs/knowledge/kno101.primitives.2.rel.many_to_many.[article].md

@@ -1,37 +0,0 @@
-# 🧩 instances, documents, and multiple concepts
-
-## 1. instances are polyvalent
-- the same set of raw observations can support different patterns.
-- instances do not “belong” to one concept — they remain neutral evidence until organized.
-
----
-
-## 2. documents frame the pattern
-- **articles**: arrange the same events into different narratives (e.g., “progress” vs. “conflict”).
-- **catalogs**: classify the same items by different principles (e.g., “evolutionary lineage” vs. “ecological role”).
-- **demos**: show the same behavior as “leadership” in one framing, or as “manipulation” in another.
-- **lessons**: use the same experiments to teach “gravity” in physics, or “scientific method” in education.
-
----
-
-## 3. concepts coexist
-- multiple concepts can be validly materialized from the same evidentiary base.
-- what changes is the **treatment**: the way instances are arranged into a document.
-
----
-
-## 🔗 example
-
-**instances:** events of the French Revolution (1789–1799)
-
-- **concept = revolution** → article: “the nature of political revolutions”
-- **concept = progress** → lesson: “steps toward modern democracy”
-- **concept = conflict** → demo: “case study of class struggle”
-- **concept = human nature** → catalog: “patterns of collective behavior under stress”
-
----
-
-## ✨ insight
-- **instances are concept-neutral** until organized.
-- **documents are concept-detection and transmission devices** that surface different concepts from the same raw material.
-- explains why different disciplines (history, sociology, economics) can study the same dataset and yield distinct conceptual insights.

package/dist/logic/roles/bhrain/.briefs/knowledge/kno101.primitives.3.instances.[article].md

@@ -1,39 +0,0 @@
-# 🧩 instances (atoms)
-
-## .what
-**instances** are the irreducible substrate of knowledge — the raw, concrete elements of experience, observation, or data.
-
-They are the *things themselves*, not yet arranged or interpreted.
-
----
-
-## 🔬 characteristics
-- **atomic** → cannot be further reduced without losing identity
-- **concrete** → tied to specific time, place, or occurrence
-- **neutral** → not bound to any single concept until organized in a document
-- **repeatable** → can be referenced, collected, or measured
-
----
-
-## 🧷 forms of instances
-- **data points** → a recorded temperature, a survey response, a transaction
-- **events** → a protest, a business meeting, a thunderstorm
-- **cases** → an individual patient’s condition, a lawsuit, a project outcome
-- **specimens** → a biological sample, a rock in geology, an artifact in archaeology
-
-> note: these clusters are not exhaustive, but demonstrative
-
----
-
-## 📌 examples
-- a single apple falling from a tree (event)
-- one lab measurement of blood pressure (data point)
-- a specific court ruling (case)
-- a fossil in a museum drawer (specimen)
-
----
-
-## ✨ role
-- **foundation:** supply the evidentiary grounding for all knowledge work
-- **versatility:** the same set of instances can underlie multiple concepts, depending on arrangement
-- **dependency:** without instances, documents cannot materialize concepts

package/dist/logic/roles/bhrain/.briefs/knowledge/kno101.primitives.4.documents.[article].md

@@ -1,37 +0,0 @@
-# 🧩 documents (concept materializations)
-
-## .what
-**documents** are structured arrangements of instances that **materialize a concept** — making it visible, graspable, and transmissible.
-
-They do not create concepts, but reveal and communicate them by curating how instances are selected, ordered, and framed.
-
----
-
-## 🔬 characteristics
-- **constructive** → transform raw instances into recognizable patterns
-- **mediating** → bridge between abstract concept and concrete instances
-- **varied** → different treatments (definitional, organizational, relational, pedagogical)
-- **persistent** → stabilize knowledge so it can be shared across time and space
-
----
-
-## 🧷 forms of documents
-- **articles** → definitional treatment (what a concept *is*)
-- **catalogs** → organizational treatment (how it *varies/relates*)
-- **demos** → relational treatment (how an *instance exemplifies* it)
-- **lessons** → pedagogical treatment (how it can be *learned*)
-
----
-
-## 📌 examples
-- *Principia Mathematica* (article/lesson) materializing the concept of **gravity**
-- a biological taxonomy chart (catalog) materializing the concept of **species differentiation**
-- a video case study (demo) materializing the concept of **leadership in practice**
-- a tutorial sequence (lesson) materializing the concept of **computer programming**
-
----
-
-## ✨ role
-- **materializers:** reveal pre-existing concepts through organization of instances
-- **detectors:** detect patterns implicit in reality by framing evidence
-- **transmitters:** make concepts communicable across audiences and generations

package/dist/logic/roles/bhrain/.briefs/knowledge/kno101.primitives.5.concepts.[article].md

@@ -1,39 +0,0 @@
-# 🧩 concepts (patterns in reality)
-
-## .what
-**concepts** are the abstract structures — patterns, relationships, or principles — that exist in reality independent of documentation.
-
-They are the *meaning-bearing forms* discoverable in the fabric of events, behaviors, and phenomena.
-
----
-
-## 🔬 characteristics
-- **ontic** → exist whether or not they are recognized or documented
-- **structural** → defined by relationships among instances, not by any single instance
-- **stable** → persist across contexts, even if expressed differently
-- **pluralizable** → the same instances can materialize multiple concepts, depending on arrangement
-
----
-
-## 🧷 forms of concepts
-- **physical principles** → gravity, inertia, thermodynamics
-- **social patterns** → leadership, cooperation, conflict
-- **biological relationships** → evolution, symbiosis, adaptation
-- **abstract structures** → number, symmetry, causality
-
-> note: these clusters are not exhaustive, but demonstrative
-
----
-
-## 📌 examples
-- **gravity**: the real force/pattern that governs attraction of masses
-- **leadership**: the relational dynamic observable in human groups
-- **symbiosis**: a biological relationship between species
-- **justice**: a normative structure in social life
-
----
-
-## ✨ role
-- **existence:** independent of human recognition, concepts are “out there” in reality
-- **discoverability:** documents make them perceptible by organizing instances
-- **transmissibility:** once materialized in documents, concepts can be shared, taught, and critiqued

package/dist/logic/roles/bhrain/.briefs/knowledge/kno201.documents._.[article].md

@@ -1,48 +0,0 @@
-# 🧩 .brief: `documents as vehicles of concept materialization`
-
-## .what
-**documents** are structured vehicles that materialize concepts by arranging instances into communicable form.
-they are not the origin of concepts — which exist as real patterns in reality — but the **means by which those patterns are detected, revealed, and transmitted**.
-
----
-
-## 🔗 relation to knowledge
-
-- 🔹 **instances** = atoms, the raw substrate (events, data, specimens)
-- 📑 **documents** = arrangements of instances that materialize concepts
-- 🌐 **concepts** = patterns and relationships in reality, made perceptible through documents
-
-\`\`\`
-concepts (patterns in reality)
-    ↓ materialized via
-documents (organized arrangements of instances)
-    ↓ grounded in
-instances (atoms of raw data/experience)
-\`\`\`
-
-documents sit in the middle layer: they **leverage instances to reveal concepts**.
-
----
-
-## 📖 archetypes of documents
-
-documents take on distinct **treatment modes**, each shaping how concepts are materialized:
-
-- 📖 **article — definitional**: clarifies *what a concept is* (e.g., Newton’s *Principia* → gravity)
-- 🗂️ **catalog — organizational**: maps *how instances or sub-concepts relate* (e.g., periodic table → elements)
-- 🎬 **demo — relational**: shows *how an instance exemplifies a concept* (e.g., Portland → walkability)
-- 🎓 **lesson — pedagogical**: guides *how a concept is learned and practiced* (e.g., Euclid’s *Elements* → geometry)
-
----
-
-## ✨ insight
-- documents are **concept-materialization devices**, not concept-creation devices
-- they are the **bridge**: grounding abstract structures in concrete instances
-- multiple documents can materialize the same concept differently, and the same set of instances can support multiple concepts depending on arrangement
-
-**in the architecture of knowledge:**
-- 🔹 instances supply the *evidence*
-- 📑 documents supply the *form*
-- 🌐 concepts supply the *structure of reality*
-
-together, they form a triad where documents are the **active medium of transmission and detection**.

package/dist/logic/roles/bhrain/.briefs/knowledge/kno201.documents._.[catalog].md

@@ -1,52 +0,0 @@
-# 🧩 comparative catalog of document archetypes
-
-## 📊 compressed overview
-
-| **archetype** | **what** |
-|---------------|----------|
-| 📖 **article**   | defines *what a concept is* |
-| 🗂️ **catalog**   | organizes *how concepts/instances relate* |
-| 🎬 **demo**      | exemplifies *how an instance shows a concept* |
-| 🎓 **lesson**    | teaches *how a concept is learned/practiced* |
-
----
-
-## 📖 1. article — definitional
-**what:** clarifies *what a concept is* through explanation and boundary-setting
-**forms:** encyclopedia entries, research papers, essays, reference guides
-**examples:** Newton’s *Principia* (gravity), Wikipedia (photosynthesis), journal article (cognitive bias)
-**role:** define, anchor, transmit shared meaning
-
----
-
-## 🗂️ 2. catalog — organizational
-**what:** maps *how instances or sub-concepts relate* within a system
-**forms:** taxonomies, dictionaries, encyclopedias, databases, ontologies
-**examples:** Linnaeus’ *Systema Naturae* (species), periodic table (elements), Roget’s Thesaurus (language)
-**role:** organize, map, stabilize reference
-
----
-
-## 🎬 3. demo — relational
-**what:** shows *how a specific instance exemplifies a concept*
-**forms:** case studies, simulations, narratives, worked examples, performances
-**examples:** Portland (walkability), Ferrari F1-75 (racecar), clinical case (disease), role-play (conflict resolution)
-**role:** reveal, bridge instance → concept, transmit intuitively
-
----
-
-## 🎓 4. lesson — pedagogical
-**what:** guides *how a concept is learned and practiced* via structured sequences
-**forms:** textbooks, curricula, tutorials, workshops, training manuals
-**examples:** Euclid’s *Elements* (geometry), coding tutorial (loops), biology chapter (cell division), first-aid manual
-**role:** teach, scaffold, transmit across generations
-
----
-
-## ✨ insight
-- 📖 **articles define**
-- 🗂️ **catalogs organize**
-- 🎬 **demos exemplify**
-- 🎓 **lessons teach**
-
-each archetype materializes concepts from instances with a distinct treatment style, together forming a complementary system of knowledge.

package/dist/logic/roles/bhrain/.briefs/knowledge/kno201.documents.articles.[article].md

@@ -1,40 +0,0 @@
-# 🧩 documents.article (definitional treatment)
-
-## .what
-an **article** is a document form that provides a **definitional treatment** of a concept.
-its role is to **articulate what a concept is** by organizing instances into explanatory, expository text.
-
-articles do not invent the concept — they **materialize it** by clarifying boundaries, meaning, and context.
-
----
-
-## 🔬 characteristics
-- **definitional** → establishes “what it is”
-- **expository** → conveys through structured explanation
-- **boundary-setting** → distinguishes the concept from related ideas
-- **persistent** → stabilizes a shared understanding across readers
-
----
-
-## 🧷 forms of articles
-> note: these clusters are not exhaustive, but demonstrative
-
-- **encyclopedia entries** → concise, standardized definitions
-- **research papers** → formal articulation supported by evidence
-- **essays** → interpretive, argumentative treatments
-- **reference guides** → practical summaries clarifying use
-
----
-
-## 📌 examples
-- Newton’s *Principia* articulating the concept of **gravity**
-- Aristotle’s *Poetics* defining the concept of **tragedy**
-- a Wikipedia page explaining **photosynthesis**
-- a journal article clarifying the concept of **cognitive bias**
-
----
-
-## ✨ role
-- **clarify** → provide stable definitions and interpretations
-- **anchor** → establish a conceptual reference point for other documents
-- **transmit** → enable shared understanding across communities and generations

package/dist/logic/roles/bhrain/.briefs/knowledge/kno201.documents.catalogs.[article].md

@@ -1,41 +0,0 @@
-# 🧩 documents.catalog (organizational treatment)
-
-## .what
-a **catalog** is a document form that provides an **organizational treatment** of a concept.
-its role is to **arrange how instances or sub-concepts relate within a system**, revealing structure, variety, and interconnections.
-
-catalogs do not invent the concept — they **materialize it** by mapping its organization across instances.
-
----
-
-## 🔬 characteristics
-- **systematic** → emphasizes order, grouping, classification
-- **relational** → shows how parts connect within a whole
-- **comprehensive** (aspirational) → strives for completeness of coverage
-- **reference-oriented** → designed for lookup, navigation, comparison
-
----
-
-## 🧷 forms of catalogs
-> note: these clusters are not exhaustive, but demonstrative
-
-- **taxonomies** → hierarchical classifications (e.g., Linnaean species system)
-- **dictionaries** → lexical mappings of language
-- **encyclopedias** → organized bodies of reference knowledge
-- **databases** → structured collections for retrieval and analysis
-- **ontologies** → conceptual maps of domains
-
----
-
-## 📌 examples
-- Carl Linnaeus’ *Systema Naturae* cataloging **species differentiation**
-- Roget’s *Thesaurus* cataloging **semantic relationships** in language
-- the *Periodic Table* cataloging **elements by properties**
-- a product database cataloging **inventory items**
-
----
-
-## ✨ role
-- **organize** → reveal structure, categories, and relationships
-- **map** → provide overviews of domains of knowledge
-- **stabilize** → act as authoritative references across communities

package/dist/logic/roles/bhrain/.briefs/knowledge/kno201.documents.demos.[article].md

@@ -1,42 +0,0 @@
-# 🧩 documents.demo (relational treatment)
-
-## .what
-a **demo** is a document form that provides a **relational treatment** of a concept.
-its role is to **show how a particular instance exemplifies a concept**, making the abstract tangible through lived or observable cases.
-
-demos do not create the concept — they **materialize it** by spotlighting the link between instance and concept.
-
----
-
-## 🔬 characteristics
-- **exemplificatory** → highlights “this is how *that* shows *this*”
-- **concrete** → rooted in specific cases, narratives, or simulations
-- **relational** → frames the connection between instance and concept
-- **illustrative** → emphasizes visibility and graspability over abstraction
-
----
-
-## 🧷 forms of demos
-> note: these clusters are not exhaustive, but demonstrative
-
-- **case studies** → detailed instances exemplifying a concept in practice
-- **simulations** → modeled scenarios demonstrating principles
-- **narratives** → stories or dialogues that embody concepts
-- **worked examples** → step-by-step demonstrations of how a concept applies
-- **videos / performances** → live or recorded enactments of concepts in action
-
----
-
-## 📌 examples
-- Portland as a demo of **walkability**
-- the Ferrari F1-75 as a demo of a **racecar**
-- a clinical case study as a demo of **disease presentation**
-- a worked math example as a demo of **algebraic principles**
-- a role-play video as a demo of **conflict resolution**
-
----
-
-## ✨ role
-- **reveal** → make abstract concepts perceivable through concrete exemplars
-- **bridge** → connect the rawness of instances with the abstraction of concepts
-- **transmit** → enable intuitive grasp by showing, not just telling

package/dist/logic/roles/bhrain/.briefs/knowledge/kno201.documents.lessons.[article].md

@@ -1,42 +0,0 @@
-# 🧩 documents.lesson (pedagogical treatment)
-
-## .what
-a **lesson** is a document form that provides a **pedagogical treatment** of a concept.
-its role is to **guide how a concept is learned and practiced**, sequencing instances and explanations into a structured path of understanding.
-
-lessons do not create the concept — they **materialize it** by arranging knowledge for comprehension, retention, and skill-building.
-
----
-
-## 🔬 characteristics
-- **instructional** → oriented toward teaching and learning
-- **sequenced** → organizes material step by step, building progressively
-- **scaffolded** → supports learners with examples, exercises, and reinforcement
-- **transformative** → aims to change the learner’s state of knowledge or ability
-
----
-
-## 🧷 forms of lessons
-> note: these clusters are not exhaustive, but demonstrative
-
-- **textbooks** → structured expositions covering domains systematically
-- **curricula** → multi-lesson frameworks guiding progression over time
-- **tutorials** → stepwise guides for practical skills or concepts
-- **workshops / exercises** → interactive sessions with application focus
-- **training manuals** → prescriptive guides for applied contexts
-
----
-
-## 📌 examples
-- Euclid’s *Elements* as a lesson in **geometry**
-- a programming tutorial teaching **loops and conditionals**
-- a biology textbook chapter on **cell division**
-- a curriculum on **civic education** in schools
-- a workshop manual for **first aid procedures**
-
----
-
-## ✨ role
-- **teach** → enable learners to internalize concepts through structured progression
-- **scaffold** → support comprehension with examples, practice, and review
-- **transmit** → pass concepts across generations and communities in durable form

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

@@ -1,41 +0,0 @@
-# 🧩 .brief: `documents.refs (minimal references)`
-
-## .what
-**refs** are a type of document at the most minimal scale.
-they function as **direct pointers to concepts** — often just a word, phrase, or short sentence.
-unlike longer documents, they do not develop, explain, or organize; they simply **reference**.
-
----
-
-## 🔬 characteristics
-- **minimal** → the smallest possible form of a document
-- **indexical** → serve to point toward a concept without elaboration
-- **atomic** → can be embedded within larger documents as building blocks
-- **dependent** → rely on context (shared language, prior knowledge) to be meaningful
-
----
-
-## 🧷 forms of refs
-> note: not exhaustive, but demonstrative
-
-- **single words** → “gravity,” “justice,” “walkability”
-- **short phrases** → “social contract,” “supply and demand”
-- **sentence-pointers** → “see Newton on planetary motion,” “refer to Portland as an example”
-- **labels / tags** → category names, hashtags, keywords
-
----
-
-## 📌 examples
-- the term **“photosynthesis”** pointing to the concept of energy conversion in plants
-- the word **“democracy”** referencing the concept of collective governance
-- a tag like **#leadership** indexing content about the social concept of leadership
-- a margin note: *“cf. Euclid, Book I”*
-
----
-
-## ✨ role
-- **name** → provide handles for concepts so they can be referenced in discourse
-- **index** → act as entry points into larger bodies of knowledge
-- **embed** → function as the basic building blocks within more expansive documents
-
-refs are thus the **minimal mode of documents**: pure reference without expansion, anchoring the link between language and concepts.

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

@@ -1,50 +0,0 @@
-# 🧩 .brief: `doc.kernel`
-
-## .what
-a **doc.kernel** is the **atomic variant of a document**.
-it carries exactly **one concept**, expressed in its **minimal viable form**.
-a kernel is not a pointer (like a ref), nor a structured articulation (like a brief) — it is the smallest **fertile expression** of a concept, portable across contexts.
-
----
-
-## 🎯 purpose
-- **seed** a concept for recomposition, growth, or articulation
-- preserve integrity of a single idea while stripping away excess context
-- provide a unit small enough to combine, cluster, or transplant into new docs
-
----
-
-## ⚙️ properties
-- **atomic** — cannot be reduced further without losing the concept
-- **fertile** — can grow into a brief, article, or larger doc
-- **portable** — independent of its original doc; reusable elsewhere
-- **focused** — always represents *one and only one* concept
-
----
-
-## 🔄 relation to other variants
-- 🔖 **doc.ref** = *points* to a concept, but carries no content
-- 🌱 **doc.kernel** = *seeds* a concept in its minimal expression
-- 🪴 **doc.brief** = *carries* one or more concepts in structured, compressed form
-- 📚 **doc** = *hosts* concepts at any scale, compression unspecified
-
----
-
-## 📌 examples
-
-### ⚖️ gravity
-- 🌱 **doc.kernel:** `masses attract one another`
-
-### 🎵 music
-- 🌱 **doc.kernel:** `organized sound creates aesthetic or emotional experience`
-
-### 🧩 triangle
-- 🌱 **doc.kernel:** `a triangle has three sides`
-
----
-
-## ✨ insight
-a **doc.kernel** is the **seed-unit of conceptual materialization**:
-- smaller than a brief, richer than a ref.
-- designed for portability, recomposition, and growth.
-- the foundation of the compression axis — the **irreducible carriers of meaning** inside the doc ecosystem.

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

@@ -1,40 +0,0 @@
-# 🧩 .brief: `documents.briefs (compressed references)`
-
-## .what
-**briefs** are a type of document that provide **compressed, high-density articulation** of a concept.
-they sit between minimal references (🔖 refs) and expansive documents, guaranteeing **at least a few paragraphs** of structured content with **maximum signal and minimum noise**.
-
----
-
-## 🔬 characteristics
-- **compressed** → distill essential meaning without redundancy
-- **structured** → organized into clear sections for readability
-- **length-anchored** → never too short (≥ a few paragraphs), but intentionally concise
-- **treatment-flexible** → can take the form of article, catalog, demo, or lesson
-
----
-
-## 🧷 forms of briefs
-> note: not exhaustive, but demonstrative
-
-- **brief.article** → compressed definitional treatment
-- **brief.catalog** → compressed organizational mapping
-- **brief.demo** → compressed instance-to-concept exemplification
-- **brief.lesson** → compressed pedagogical sequence
-
----
-
-## 📌 examples
-- a 3-paragraph **brief.article** on **leadership** defining the concept clearly
-- a **brief.catalog** listing and explaining three main types of **volcanoes**
-- a **brief.demo** showing Portland as an instance of **walkability**
-- a **brief.lesson** on **supply and demand** with a short guided example
-
----
-
-## ✨ role
-- **distill** → cut away noise, leaving only essential articulation
-- **transmit** → offer quick but thorough grasp of a concept
-- **standardize** → provide a reliable format for compressed knowledge work
-
-briefs are the **high-efficiency mode of documents**: not minimal pointers, but maximally compact treatments that balance depth with brevity.