rhachet-roles-ehmpathy 1.13.3 → 1.13.6

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

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

@@ -1,70 +0,0 @@
-# 🧠 .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

@@ -1,8 +0,0 @@
-## 🔢 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/distilisys.grammar.compressed.md

@@ -1,19 +0,0 @@
-patterns:
-  - [resource] -> <mechanism> -> [resource]
-  - <mechanism>[resource]
-  - <mechanism>[resource]<mechanism>
-  - @[actor]<mechanism> -> [resource] -> {drive:<<effect>>[motive]}
-  - <create>[<mechanism>].to(<mechanism>[resource])
-
-requirements:
-  - all <verb>s must be declared as <mechanism>s
-  - all [noun]s must be declared as [resource]s
-  - all <mechanism>s should be prefixed with their root operation
-    - <get> for reads
-    - <set> for dobj mutations
-    - <rec> for event emissions
-  - use <mechanism>[resource] syntax for brevity, when applicable
-  - scope [resources] within [domain]s when needed for specificity
-    - [domain][resource]
-  - leverage [resources] .attributes when needed
-    - [resource].attribute

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.1.why.common.[article].md

@@ -1,32 +0,0 @@
-# 🧩 why gerunds are so common
-
-## 🏗️ structural reasons
-- **nominalization shortcut**
-  instead of inventing a whole new noun, you can just attach *-ing* and turn an action into a subject/object
-  *e.g., “running is fun” vs. needing a special word like “race”*.
-- **versatility in syntax**
-  gerunds can function as subjects, objects, or complements without breaking grammar rules. this makes them handy “lego blocks” in sentence-building.
-
----
-
-## 🔄 cognitive & communicative reasons
-- **focus on process, not just event**
-  gerunds highlight the *ongoingness* or *essence* of an action, not a single instance.
-  *e.g., “i like swimming” emphasizes the general activity, not one swim*.
-- **concept compression**
-  they condense complex actions into manageable noun-like units, letting us package experiences as “things” that can be talked about, compared, and reasoned with.
-
----
-
-## 🌍 historical reasons
-- **natural evolution of english**
-  english lost many inflections over time. the *-ing* ending became multifunctional (present participle *and* gerund), making it easy to spread.
-- **cross-linguistic parallels**
-  most languages have some way of turning verbs into nouns (latin’s *-ndus*, spanish *-ar → -ando*, etc.). gerunds are english’s efficient version of that broader need.
-
----
-
-## 📊 why “so common” in practice
-- they appear in **everyday talk** (*liking, doing, going*).
-- they’re needed for **abstract concepts** (*thinking, learning, understanding*).
-- they often replace **formal nouns** (*“procrastinating”* instead of *“procrastination”*).

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.1.why.term_smells.[article].md

@@ -1,36 +0,0 @@
-# 🧩 why gerunds can be "term smells"
-
-## 🚩 what is a "term smell"
-a **term smell** is like a code smell: a sign that a term may not be well-formed, clear, or fully thought through. it doesn’t always mean the term is wrong, but it hints at a lack of conceptual distillation.
-
----
-
-## 🧩 why gerunds raise suspicion
-- **process disguised as essence**
-  gerunds often point to *doing* rather than a distilled *thing*.
-  *e.g., “learning” as a noun refers to the act, but what we might mean is “knowledge” (the distilled outcome).*
-
-- **vagueness of scope**
-  gerunds blur whether we mean one instance (*a running race*), the general process (*running in general*), or an abstract quality (*endurance*). this ambiguity can signal sloppy conceptualization.
-
-- **placeholder convenience**
-  gerunds are easy to generate. instead of carefully naming the core concept, we default to *-ing*.
-  *e.g., “networking” instead of specifying “relationships,” “contacts,” or “repute.”*
-
----
-
-## 🌀 signs of insufficient distillation
-- the term **describes activity** but doesn’t identify the **underlying resource, structure, or outcome**.
-  *“teaching” vs. “education,” “building” vs. “structure,” “thinking” vs. “thought.”*
-
-- the term **feels broad or leaky**, covering multiple senses at once.
-  *“writing” could mean the act, the system, the product, or the skill.*
-
-- the term **fails test of substitution**: if we try to define it without the *-ing* form, we get sharper distinctions.
-  *“planning” → could resolve to “plan” (artifact), “process of coordination” (activity), or “strategy” (essence).*
-
----
-
-## 📌 takeaway
-gerunds are common because they’re convenient.
-they’re **term smells** because convenience can mask lack of distillation — using the *doing* form instead of naming the **essence** of what’s really meant.

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.1.why.term_smells.detection.[lesson].md

@@ -1,73 +0,0 @@
-# 🧩 .brief.lesson: `gerund smell test`
-
-## 💡 concept
-a **gerund smell test** helps detect when a concept named with *-ing* is really a sign of insufficient distillation. it forces us to sharpen fuzzy process-terms into precise nouns that capture the essence.
-
----
-
-## 🎯 purpose
-- prevent sloppy terminology by avoiding “process-as-thing” placeholders.
-- guide thinkers toward more distilled, essential names.
-- improve clarity and transferability of concepts in writing, design, or theory.
-
----
-
-## 🧪 the smell test
-
-### 1. substitution test
-> can the gerund be replaced with a sharper noun?
-
-- *“learning” → knowledge*
-- *“building” → structure*
-- *“teaching” → education*
-- *“thinking” → thought*
-
-if the substitution makes meaning clearer, the gerund is a smell.
-
----
-
-### 2. scope clarity test
-> does the gerund blur multiple senses?
-
-- *“writing”* could mean:
-  - the act (scribbling on paper)
-  - the product (a text)
-  - the system (written language)
-  - the skill (literacy)
-
-if it leaks across senses, the gerund is a smell.
-
----
-
-### 3. outcome test
-> does the gerund describe activity instead of the result?
-
-- *“planning”* → could resolve into:
-  - **plan** (artifact)
-  - **strategy** (essence)
-  - **coordination** (process with defined outcome)
-
-if the activity is masking a clearer outcome, the gerund is a smell.
-
----
-
-### 4. convenience test
-> is the gerund just the easiest way out?
-
-- *“networking”* → a shortcut for “relationships,” “contacts,” or “repute.”
-if the term looks like it was coined because *-ing* was handy, it’s a smell.
-
----
-
-## 📚 practice exercise
-take common gerunds and refine them:
-- **thinking** → thought, cognition, reason
-- **doing** → action, execution, behavior
-- **training** → instruction, discipline, practice
-- **meeting** → gathering, session, council
-
----
-
-## 📌 takeaway
-if a term ends in *-ing*, run it through the **gerund smell test**.
-if it fails even one check, distill it to its essence. clarity improves, concepts sharpen, and your system of terms becomes more robust.

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.2.tactic.eliminate.[article].md

@@ -1,55 +0,0 @@
-# 🧩 .brief.article: `eliminate gerunds in prose`
-
-## 🌟 introduction
-the removal of gerunds (*-ing* forms used as nouns) is a deliberate tactic to sharpen language. gerunds often act as **term smells** — signs that the concept has not been distilled to its essence. by replacement with precise nouns, prose becomes clearer, more direct, and more transferable.
-
----
-
-## 🎯 purpose of the tactic
-- **distill essence**: shift from description of activity to naming of outcome, resource, or structure.
-- **remove ambiguity**: avoid blurred meanings (e.g., *“text”* vs. the act of inscription).
-- **increase precision**: force the author to clarify whether they mean *plan*, *strategy*, *education*, *knowledge*, etc.
-- **discipline thought**: strengthen conceptual rigor by avoiding convenient but vague shortcuts.
-
----
-
-## 🔍 how the tactic works
-1. **scan text for gerund forms** (*-ing words that function as nouns*).
-   - examples: *thought, plan, structure, network* as replacements.
-2. **apply the smell test**: substitution, scope, outcome, and convenience.
-3. **replace with distilled nouns** that capture the core meaning.
-   - *thought* instead of “thinking”
-   - *plan / strategy / coordination* instead of “planning”
-   - *relationships / contacts / repute* instead of “networking”
-
----
-
-## 📚 examples
-
-### before
-- *“effective planning is key to success.”*
-### after
-- *“an effective plan is key to success.”*
-- *“strategy is key to success.”*
-
----
-
-### before
-- *“her teaching inspired the students.”*
-### after
-- *“her instruction inspired the students.”*
-- *“her education work inspired the students.”*
-
----
-
-### before
-- *“thinking shapes culture.”*
-### after
-- *“thought shapes culture.”*
-- *“reason shapes culture.”*
-
----
-
-## 📌 takeaway
-the **tactic of gerund removal** forces every concept to pass through the fire of distillation. fuzzy process-terms yield to sharper essences, ambiguity reduces, and conceptual clarity strengthens.
-in disciplined prose, *every gerund is guilty until proven otherwise*.

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.2.tactic.eliminate.[lesson].md

@@ -1,41 +0,0 @@
-# 🧩 .brief.lesson: `gerund removal checklist`
-
-## 💡 concept
-a **gerund removal checklist** is an editing discipline that enforces clarity by replacing *-ing* nouns with distilled terms. it treats every gerund as a warning signal until replaced or justified.
-
----
-
-## 📋 the checklist
-
-### 1. scan
-- highlight every word ending in **-ing**.
-- mark especially those functioning as **subjects, objects, or abstract nouns**.
-
-### 2. test
-apply four filters to each marked word:
-- **substitution**: can a sharper noun replace it? (*planning → plan / strategy*)
-- **scope**: does the word blur multiple meanings? (*writing → text / skill / act*)
-- **outcome**: does the word describe action instead of result? (*training → discipline / instruction*)
-- **convenience**: was the word chosen as an easy placeholder?
-
-### 3. replace
-swap the gerund with the distilled term:
-- “thinking” → *thought, reason, cognition*
-- “building” → *structure, edifice*
-- “networking” → *relationships, contacts, repute*
-
-### 4. re-read
-ensure the new noun preserves intent and increases clarity.
-if meaning shifted, refine further.
-
----
-
-## 🛠️ usage rule
-- treat every gerund as **guilty until proven otherwise**.
-- only retain *-ing* when no sharper essence exists.
-- prefer concrete nouns (artifact, structure, resource, outcome) over vague activity labels.
-
----
-
-## 📌 takeaway
-the **gerund removal checklist** provides a repeatable method for editing prose. it ensures that each concept is expressed in its distilled form, eliminating fuzzy placeholders and strengthening conceptual precision.

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.3.eliminator.[trait]._.md

@@ -1,66 +0,0 @@
-# 🧩 .trait: `gerund eliminator`
-
-## 💡 essence
-the **gerund eliminator** is a discipline of language that treats every *-ing* noun as suspect. it can manifest in three modes:
-- **boon**: sharpens clarity through distillation.
-- **bane**: rigidifies expression into distortion.
-- **balance**: integrates rigor with flexibility to preserve both precision and flow.
-
----
-
-## 🌟 trait.boon
-### essence
-the boon is the gift of clarity. the writer distills vague process-terms into precise nouns, strengthening both prose and thought.
-
-### benefits
-- sharper terms, reduced ambiguity.
-- language that transfers cleanly across contexts.
-- disciplined thought that separates essence from activity.
-
-### behaviors
-- replaces *thinking* with *thought* or *reason*, *planning* with *plan* or *strategy*, *teaching* with *instruction*.
-- applies the gerund removal checklist with consistency.
-- edits prose until every concept is distilled to its core.
-
----
-
-## 🌑 trait.bane
-### essence
-the bane is the trap of rigidity. discipline hardens into dogma, and clarity collapses into distortion.
-
-### risks
-- over-correction that forces awkward substitutions.
-- jargon inflation (inventing strained nouns to purge gerunds).
-- prose that feels stilted, brittle, and inaccessible.
-- dogmatism that polices others’ language unnecessarily.
-
-### symptoms
-- loss of nuance (ongoingness erased).
-- cadence and readability sacrificed for mechanical purity.
-- clarity narrowed into sterile precision.
-
----
-
-## ⚖️ trait.balance
-### essence
-the balance integrates discipline with flexibility. every gerund is still suspect, but judgment, not dogma, decides its fate.
-
-### stance
-- diagnostic, not dogmatic.
-- clarity first: the rule serves meaning, not itself.
-- context-aware: permits gerunds where they carry unique nuance.
-
-### behaviors
-- runs the smell test as default, but allows exceptions.
-- pauses before enforcing: asks *“does this replacement add clarity?”*
-- mediates between rigor and flow, ensuring prose is precise yet natural.
-
----
-
-## 📌 takeaway
-the **gerund eliminator** trait is a tool for sharpening thought and language.
-- in **boon**, it clarifies.
-- in **bane**, it ossifies.
-- in **balance**, it disciplines without distortion.
-
-the art lies not in blind removal, but in serving clarity with every choice of term.

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.3.eliminator.[trait].balance.md

@@ -1,36 +0,0 @@
-# 🧩 .trait.balance: `gerund eliminator`
-
-## 💡 essence
-the **balance of the gerund eliminator** is the capacity to hold the discipline of removal without letting it harden into rigidity. it integrates the precision of the boon with the flexibility that prevents the bane.
-
----
-
-## ⚖️ stance
-- **diagnostic, not dogmatic**: treats every gerund as a candidate for replacement, but allows exceptions when clarity or flow demand it.
-- **clarity-first**: the rule serves meaning, not the other way around.
-- **context-aware**: recognizes when a gerund best conveys ongoingness or process, and permits its use.
-
----
-
-## 🌟 behaviors
-- runs the gerund smell test as standard practice.
-- replaces *planning* with *plan* or *strategy* when appropriate, but allows *being* or *thinking* if the distilled noun would distort meaning.
-- asks: *does this edit improve clarity, or just satisfy the rule?*
-- mediates between rigor and readability, ensuring prose is both precise and natural.
-
----
-
-## 🌱 cultivation
-to embody balance:
-1. apply the gerund removal checklist as default.
-2. pause before enforcing — consider rhythm, nuance, and reader comprehension.
-3. refine terms only when the replacement increases clarity.
-4. embrace the motto: *“clarity is the goal; distillation is the tool.”*
-
----
-
-## 📌 takeaway
-the **trait.balance** of the gerund eliminator unites boon and bane:
-- **boon** brings sharpness.
-- **bane** warns of rigidity.
-- **balance** holds both, ensuring language stays disciplined *and* alive.

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.3.eliminator.[trait].bane.md

@@ -1,34 +0,0 @@
-# 🧩 .trait.bane: `gerund eliminator`
-
-## 💡 essence
-the **bane of the gerund eliminator** appears when the discipline of removal hardens into rigidity. in this mode, the pursuit of clarity collapses into distortion, replacing natural flow with awkward constructs or over-abstract nouns.
-
----
-
-## ⚠️ risks
-- **over-correction**: forces replacement even when the gerund carries the most natural sense.
-- **jargon inflation**: invents strained nouns (*“reasonage”* instead of *reason*) just to purge *-ing*.
-- **stilted prose**: sacrifices rhythm and readability for the sake of mechanical purity.
-- **dogmatism**: corrects others reflexively, even when clarity is already sufficient.
-- **loss of nuance**: erases the sense of ongoing process that only the gerund can convey.
-
----
-
-## 🔍 symptoms
-- prose feels brittle, full of heavy Latinate nouns.
-- sentences lose cadence and accessibility.
-- collaborators feel policed rather than supported.
-- clarity narrows into technical precision at the expense of style.
-
----
-
-## 🌱 counterbalance
-- remember the purpose: **clarity over ritual**.
-- retain gerunds when no distilled noun exists without distortion.
-- weigh flow and rhythm alongside precision.
-- apply the smell test as **diagnosis**, not dogma.
-
----
-
-## 📌 takeaway
-the **gerund eliminator** as a boon sharpens thought, but as a **bane** it distorts expression. mastery lies in balance: purge gerunds that hide essence, but allow them when they carry meaning more gracefully than any substitute.

package/dist/logic/roles/bhrain/.briefs/grammar/gerunds.3.eliminator.[trait].boon.md

@@ -1,35 +0,0 @@
-# 🧩 .trait.boon: `gerund eliminator`
-
-## 💡 essence
-the **boon of the gerund eliminator** is the discipline to strip away fuzzy *-ing* nouns and replace them with distilled essences. in this mode, the trait sharpens language, removes ambiguity, and strengthens thought.
-
----
-
-## 🌟 benefits
-- **clarity**: prose becomes crisp and precise by naming the outcome, resource, or structure instead of the process.
-- **distillation**: forces terms like *planning* to resolve into *plan* or *strategy*.
-- **rigor**: applies the gerund smell test consistently, preventing vague placeholders.
-- **transferability**: concepts carry across contexts more cleanly when expressed in distilled nouns.
-- **thought discipline**: strengthens the writer’s ability to separate essence from activity.
-
----
-
-## 🔍 behaviors
-- scans text for gerunds and highlights them for replacement.
-- replaces *thinking* with *thought* or *reason*, *teaching* with *instruction*, *training* with *discipline*.
-- edits prose into sharper forms without loss of meaning.
-- maintains a catalog of distilled alternatives to accelerate editing.
-
----
-
-## 🌱 cultivation
-to develop the boon:
-1. memorize and apply the gerund removal checklist.
-2. practice rewriting passages until no gerund nouns remain.
-3. study catalogs of replacements to internalize sharper terms.
-4. make *“every gerund is guilty until proven otherwise”* a reflex.
-
----
-
-## 📌 takeaway
-the **gerund eliminator** in boon mode elevates both prose and thought. it yields language that is sharper, more precise, and less ambiguous, turning every sentence into a vessel of distilled essence.