rhachet-roles-ehmpathy 1.1.0 → 1.2.0

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

@@ -0,0 +1,39 @@
+# 🧩 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

@@ -0,0 +1,48 @@
+# 🧩 .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

@@ -0,0 +1,52 @@
+# 🧩 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

@@ -0,0 +1,40 @@
+# 🧩 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

@@ -0,0 +1,41 @@
+# 🧩 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

@@ -0,0 +1,42 @@
+# 🧩 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

@@ -0,0 +1,42 @@
+# 🧩 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

@@ -0,0 +1,41 @@
+# 🧩 .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

@@ -0,0 +1,50 @@
+# 🧩 .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

@@ -0,0 +1,40 @@
+# 🧩 .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.

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

@@ -0,0 +1,90 @@
+# 🧩 .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

@@ -0,0 +1,64 @@
+# 🧩 .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

@@ -0,0 +1,45 @@
+# 🧩 .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**.