rhachet-roles-ehmpathy 1.1.0 → 1.2.0

package/dist/logic/roles/bhrain/.briefs/cognition/cog501.cortal.assemblylang.2.composites.zoom.md

@@ -0,0 +1,127 @@
+# 🔎 .brief: `cortal.execution.assemblylang.zoom`
+
+## .what
+
+`<zoom>` is a **composite assemblylang operation**
+used to reshape **`focus.context`** by applying a structured sequence of:
+
+- `<think>` — to process or generate detail
+- `<recall>` — to retrieve supporting memory or context
+- `<steer>` — to navigate to concept-adjacent resources
+
+It adjusts **how attention is configured**, not just **what is in focus** —
+enabling deliberate expansion or contraction of **depth**, **breadth**, **acuity**, or blends of all three.
+
+---
+
+## 🧭 directional forms
+
+| form              | effect                              |
+|-------------------|--------------------------------------|
+| `<zoom><in>`      | increase contextual richness         |
+| `<zoom><out>`     | decrease contextual load or scope    |
+
+→ both forms operate **within or near the current `focus.concept`**,
+and update **`focus.context`** as their primary target.
+
+---
+
+## 🧩 axes of zooming
+
+Each zoom may declare one or more **focus dimensions** or subaxes via `.via(...)`:
+
+\`\`\`ts
+<zoom><in>.via("attributes")        // enrich trait resolution
+<zoom><out>.via("depth")            // abstract away from specifics
+<zoom><in>.via("substructs", "depth") // composite focus sharpening
+\`\`\`
+
+| axis            | zoom in effect                      | zoom out effect                        |
+|------------------|--------------------------------------|------------------------------------------|
+| `attributes`     | `<articulate>`                      | `<compress>`                             |
+| `substructs`     | `<decompose>`                       | `<encompose>`                            |
+| `depth`          | `<instantiate>`                     | `<generalize>`                           |
+| `breadth`        | `<shift>` / `<fanout>`              | `<rotate>` / `<invert>` / prune peers    |
+
+---
+
+## 🔧 zoom as composite coreop
+
+Unlike primitive coreops, `<zoom>`:
+
+- **has no fixed form** — it is always a composed chain
+- **is defined by purpose** — modulate attention shape
+- **may include multiple coreops** in sequence or parallel
+
+---
+
+## 🧠 example: single-axis zoom in
+
+\`\`\`ts
+<zoom><in>.via("substructs") = [
+  <recall>("known parts"),
+  <think>(<decompose>)
+]
+\`\`\`
+
+---
+
+## 🧠 example: multi-axis zoom out
+
+\`\`\`ts
+<zoom><out>.via("breadth", "depth") = [
+  <recall>("sibling concepts"),
+  <think>(<generalize>),
+  <steer>(<fanout>)
+]
+\`\`\`
+
+---
+
+## 🛠️ use cases
+
+| scenario                          | zoom form                       |
+|-----------------------------------|----------------------------------|
+| examine the internal structure    | `<zoom><in>.via("substructs")`   |
+| find similar alternatives         | `<zoom><out>.via("breadth")`     |
+| simplify framing and focus        | `<zoom><out>.via("attributes")`  |
+| generate specific variants        | `<zoom><in>.via("depth")`        |
+| design from multiple dimensions   | `<zoom><in>.via("depth", "attributes", "substructs")` |
+
+---
+
+## 🔄 relation to other coreops
+
+| op         | acts on          | motion pattern | context reshaping |
+|------------|------------------|----------------|--------------------|
+| `<steer>`  | `focus.concept`  | procedural     | indirectly         |
+| `<think>`  | `focus.*`        | local          | ✅ yes             |
+| `<recall>` | memory/interface | static or indirect | ✅ yes        |
+| **`<zoom>`**   | `focus.context`  | composite       | ✅ **primary**     |
+
+---
+
+## 🔁 runtime & devtime support
+
+Like `<think>`, `<zoom>` can be:
+
+- **executed dynamically** inside `<steer>` or `<choice>` blocks
+- **precompiled** into `<steer>` routes to pre-shape context before key steps
+
+---
+
+## 📌 metaphor
+
+> `<zoom>` is like turning the **lens dial** of your semantic focus —
+> it widens, sharpens, simplifies, or recasts your cognitive beam.
+
+---
+
+## 🔁 related briefs
+
+- [`cortal.focus`](./cortal.focus.md)
+- [`focus.motion.primitives`](./focus.motion.primitives.md)
+- [`cortal.execution.instructionset`](./instructionset.md)
+- [`cortal.execution.assemblylang.steer`](./assemblylang.steer.md)
+- [`cortal.execution.assemblylang.think`](./assemblylang.think.md)
+- [`cortal.execution.assemblylang.recall`](./assemblylang.recall.md)

package/dist/logic/roles/bhrain/.briefs/cognition/cog501.cortal.assemblylang.3.catalogs.md

@@ -0,0 +1,107 @@
+# 📚 .brief: `cortal.catalogs`
+
+## .what
+
+`cortal.catalogs` are **structured repositories of reusable cognition** —
+collections of **semantic tools** that support fast, interpretable reasoning without starting from scratch.
+
+There are two main kinds:
+
+1. **question catalogs** → reusable **motion vectors**
+2. **assembly catalogs** → reusable **thought sequences**
+
+> catalogs capture **well-shaped recipes** —
+> high-quality, repeatable semantic moves.
+
+---
+
+## ❓ 1. question catalogs
+
+A **question** is a **motion vector** through concept space.
+A **question catalog** collects **reusable semantic maneuvers**, each defined only by:
+
+- **motion.vector** → what kind of semantic motion it performs
+- **motion.usecases** → when and why this motion is useful
+
+### example entries:
+
+| question                                 | motion.vector                 | motion.usecases                   |
+|------------------------------------------|--------------------------------|------------------------------------|
+| `what caused this?`                      | `.depth++`                    | causal diagnosis                   |
+| `what are alternatives?`                 | `.breadth++`                  | option generation                  |
+| `how is this composed?`                  | `.acuity.substruct++`         | structural decomposition           |
+| `what’s missing?`                        | `.acuity.attribute++`         | completeness / gap-finding         |
+| `is this still true?`                    | `.context.refresh`            | contextual verification            |
+
+> 📍 questions **do not define context or concept** —
+> they are **pure motion vectors**, reusable anywhere.
+
+---
+
+## 🛠️ 2. assembly catalogs
+
+An **assembly** is a **compiled thought sequence** —
+a stepwise **atomic chain** built from primitives like `<steer>`, `<think>`, and `<recall>`.
+
+An **assembly catalog** collects common **reasonage workflows**
+that can be reused, adapted, or parameterized.
+
+### example entries:
+
+#### 🧠 diagnosis loop
+
+\`\`\`ts
+<route>([
+  ask("what failed?"),
+  <think>(<decompose>[system]),
+  ask("what caused this part to fail?"),
+  <recall>(<save>("hypothesis"))
+])
+\`\`\`
+
+#### 🎯 selection flow
+
+\`\`\`ts
+<route>([
+  ask("what are the options?"),
+  <fanout>[[option]],
+  <compare>[[option]] → [criteria],
+  ask("which is most viable?"),
+  <choice>({...})
+])
+\`\`\`
+
+> assemblies are **semantic macros** — reusable atomic chains of thought
+
+---
+
+## 🔁 reuse vs scratch
+
+| method         | advantage                                |
+|----------------|-------------------------------------------|
+| from scratch   | custom-tailored, cognitively expensive    |
+| from catalog   | efficient, proven, semantically smooth    |
+
+> 🧠 good catalogs let you **plug in your content**
+> without reinventing the flow.
+
+---
+
+## 🧩 catalog roles
+
+| kind       | unit           | function                            |
+|------------|----------------|-------------------------------------|
+| `question` | motion vector  | semantic traversal pattern          |
+| `assembly` | atomic chain   | procedural thought sequence         |
+
+---
+
+## 🔁 related briefs
+
+- [`questions`](./questions.md)
+- [`cortal.assemblylang.primitives`](./cortal.assemblylang.primitives.md)
+- [`cortal.execution.instructionset`](./instructionset.md)
+- [`cortal.assembly.grammar`](./cortal.assembly.grammar.md)
+- [`focus.motion.primitives`](./focus.motion.primitives.md)
+
+---

package/dist/logic/roles/bhrain/.briefs/cognition/cog501.cortal.assemblylang.3.grammar.md

@@ -0,0 +1,124 @@
+# 🧩 .brief: `cortal.assembly.grammar`
+
+## .what
+
+`cortal.assembly.grammar` defines how **execution primitives** and **conceptual references**
+combine into flat, **stepwise semantic expressions**.
+
+It provides a low-level syntax for:
+
+- executing primitives (`<steer>`, `<think>`, `<recall>`)
+- referencing semantic units (`[X]`, `[[X]]`)
+- expressing flat operations that yield either **single or pooled** outputs
+
+> expressions are always **one level deep** — atomic, interpretable, and
+> suitable for line-by-line execution or inspection.
+
+---
+
+## 🧠 expression structure
+
+Each instruction uses this flat format:
+
+\`\`\`ts
+<operation>[input] → [output]
+\`\`\`
+
+- `<operation>`: one of the core execution primitives or motion commands
+- `[input]`: a **singular** resource
+- `[[input]]`: a **plural** resource (a pool)
+- `[output]`: result of the operation, may also be singular or plural
+
+> both **input** and **output** may be pools (`[[X]]`) or single items (`[X]`)
+
+---
+
+## 📦 resource forms
+
+| form         | meaning                                 |
+|--------------|------------------------------------------|
+| `[X]`        | a **singular resource** (concept)        |
+| `[[X]]`      | a **plural resource** (pool of concepts) |
+| `[Class]`    | abstract type or category                |
+| `[example]`  | instance of a class                      |
+
+Examples:
+
+\`\`\`ts
+<compare>[[fruit]] → [axis]
+<gather>[[claim]] → [[evidence]]
+<imagine>[Tool] → [[tool]]
+\`\`\`
+
+> `[[X]]` = pool
+> `[X]` = single concept
+
+---
+
+## 🧪 example: class to instance pool
+
+\`\`\`ts
+<imagine>[Threat] → [[threat]]
+\`\`\`
+
+- `[Threat]` is a class
+- `[[threat]]` is a **pool** of generated examples
+- `<imagine>` returns **many plausible manifestations**, not one
+
+---
+
+## 🧠 roles in the grammar
+
+| element       | role                          | example                  |
+|---------------|-------------------------------|---------------------------|
+| `<op>`        | execution primitive            | `<decompose>`, `<save>`   |
+| `[X]`         | singular operand               | `[banana]`, `[Tool]`      |
+| `[[X]]`       | plural operand                 | `[[fruit]]`, `[[idea]]`   |
+| `→`           | yields                         | motion result             |
+| `[Y]`         | singular output                | `[axis]`, `[knife]`       |
+| `[[Y]]`       | plural output                  | `[[tool]]`, `[[claim]]`   |
+| `"label"`     | memory reference               | `"draft"`, `"goal"`       |
+
+---
+
+## 📏 grammar rules
+
+- ❌ **No nesting:**
+  \`\`\`ts
+  <compress>(<decompose>[X])    // ❌ invalid
+  \`\`\`
+
+- ✅ **Use chaining instead:**
+  \`\`\`ts
+  <decompose>[bike] → [parts]
+  <compress>[parts] → [summary]
+  \`\`\`
+
+- ✅ **Use memory for state passing:**
+  \`\`\`ts
+  <save>("bike")
+  <load>("bike") → [bike]
+  \`\`\`
+
+---
+
+## 🧩 grammar patterns
+
+| pattern                             | purpose                                |
+|-------------------------------------|----------------------------------------|
+| `<imagine>[Class] → [[examples]]`   | generate a pool of concept instances   |
+| `<compare>[[peers]] → [axis]`       | extract trait from a set               |
+| `<steer>[goal]`                     | change focal anchor                    |
+| `<recall>(<save>["label"])`         | persist semantic state                 |
+
+---
+
+## 🔁 related briefs
+
+- [`cortal.assemblylang.primitives`](./cortal.assemblylang.primitives.md)
+- [`focus.motion.primitives`](./focus.motion.primitives.md)
+- [`cortal.focus`](./cortal.focus.md)
+- [`questions`](./questions.md)
+- [`concept.treestruct`](./concept.treestruct.md)
+
+---

package/dist/logic/roles/bhrain/.briefs/cognition/inflight/concept.vs.idea.md

@@ -0,0 +1,70 @@
+# 🧠 .brief: [idea]
+
+## .what
+
+An **idea** is a **focused**, **motivated**, and **activatable** unit of thought.
+
+It emerges when a **concept** is embedded within a **context** (forming a **focus**),
+and is shaped by an underlying **motive** — a reason for existing.
+Ideas are **usable**: they can be tested, developed, shared, or acted upon.
+
+> `idea = focus + motive + activation potential`
+> where `focus = concept + context`
+
+---
+
+## 🧩 traits
+
+| trait            | description                                                 |
+|------------------|-------------------------------------------------------------|
+| **focused**       | grounded in a [concept] and framed by a [context]           |
+| **motivated**     | held for a reason — such as curiosity, need, or strategy    |
+| **activatable**   | can produce consequences — through thought or action        |
+
+---
+
+## 🌱 subtypes of [idea]
+
+Grouped by **motive**:
+
+### ▸ directive — aims to guide action
+
+| subtype     | description                             | example                        |
+|-------------|-----------------------------------------|--------------------------------|
+| **proposal** | meant to be adopted or tested          | “let’s support dark mode”      |
+| **suggestion** | soft or optional version of proposal | “maybe group by category?”     |
+| **plan**     | structured into steps or phases        | “step 1: gather feedback...”   |
+| **vision**   | aspirational, long-range form          | “instant onboarding for all”   |
+
+---
+
+### ▸ evaluative — seeks to assess or assert truth
+
+| subtype        | description                             | example                              |
+|----------------|-----------------------------------------|--------------------------------------|
+| **opinion**     | subjective evaluation                  | “this feels clunky”                  |
+| **assumption**  | unverified working belief              | “users read the text”                |
+| **hypothesis**  | falsifiable prediction or explanation  | “fewer fields = more signups”        |
+| **belief**      | durable conviction                     | “privacy is a human right”           |
+
+---
+
+### ▸ generative — explores, reveals, or reframes
+
+| subtype        | description                              | example                                |
+|----------------|------------------------------------------|----------------------------------------|
+| **imagination** | exploratory, unconstrained creation      | “what if buildings floated?”           |
+| **insight**     | crystallized understanding               | “the issue is the checkout loop”       |
+| **reframe**     | shifts interpretation or perspective     | “this isn’t failure — it’s feedback”   |
+
+---
+
+## 🧭 summary structure
+
+\`\`\`txt
+[idea]
+  = [focus] + [motive] + activation potential
+  = ([concept] + [context]) + why + usability
+\`\`\`
+
+Ideas are **living units of meaning** — carried with purpose and ready to move.

package/dist/logic/roles/bhrain/.briefs/cognition/inflight/core.concept.adjectives.md

@@ -0,0 +1,8 @@
+## 🔢 catalog: minimal-building-block adjectives
+
+| term         | scope emphasis                     | scale emphasis               | connotation                               | best fit when… |
+|--------------|------------------------------------|-------------------------------|--------------------------------------------|----------------|
+| **elemental**| universal, appears in every domain | not necessarily smallest      | poetic, natural forces, ever-present       | you want to stress that it’s *everywhere* and *essential* |
+| **primitive**| baseline for a system              | smallest defined in that system | technical, formal, structural             | you want to stress *irreducible* in a technical sense |
+| **atomic**   | indivisible                        | absolute smallest possible    | physics/metaphor of atoms, granular        | you want to stress *cannot be split without losing identity* |
+| **fundamental**| core requirement                  | can be large or small         | formal, serious, sometimes abstract        | you want to stress *underlying importance*, not size |

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

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

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

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

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

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