rhachet-roles-ehmpathy 1.13.0 → 1.13.2

package/dist/logic/roles/designer/outlineVision/stepOutlineVision.template.md

@@ -1,47 +0,0 @@
-@[designer]<outline><vision> for [desire]
-
----
-
-.intent
-- clarify the **core intent** of the desired system or product
-- define the **irreducible constraints** that must be respected
-- surface the **essential shape** implied by the intent
-- identify **open space** — parts left intentionally flexible or undecided
-
----
-
-.format
-\`\`\`md
-# 🎯 intent
-- {short summary of what the system is trying to make possible}
-
-# 📏 constraints
-- {things this system must respect — e.g., must run as CLI, must not leak domain logic}
-
-# 🧩 implied shape
-- [resource] — {core object this system revolves around}
-- <mechanism> — {core transformation it must enable}
-- {driver} — {why this system is needed now}
-
-# 🔮 open space
-- {what’s not yet decided — interface, delivery method, structure, etc.}
-\`\`\`
-
----
-
-.ask =
-\`\`\`md
-$.rhachet{desire}
-\`\`\`
-
-.inflight? =
-\`\`\`md
-$.rhachet{inflight}
-\`\`\`
-
-.feedback? =
-\`\`\`md
-$.rhachet{feedback}
-\`\`\`
-
-.output = a distilled vision summary with core intent, constraints, implied shape, and open space; if inflight provided, respond to the feedback

package/dist/logic/roles/ecologist/.briefs/.readme.md

@@ -1,17 +0,0 @@
-these are the briefs that are relevant to the ecologist role
-
-.scratch has inflight and deprecated briefs
-
-directories group briefs by relevance
-
-root may also have some ungrouped ones
-
----
-
-look for ._.summary.md briefs for compressed representations
-
----
-
-we try and declare briefs as if they were courses in college
-
-it's a pattern ghia imagined, and has a good parallel, as our aim is to distill as informative and useful of a brief as possible -> distill lessons

package/dist/logic/roles/ecologist/.briefs/distilisys/sys101.distilisys.grammar.md

@@ -1,221 +0,0 @@
-.tactic = lang:distilisys
-
-.what = a minimal, visual language for declaring system behavior using `[resource]`, `<mechanism>`, and `{driver}`
-
-.where:
-  - used to express systems across domains (ecologies, economies, software, architecture, law, etc)
-  - intended as a **canonical, long-term representation** of system behavior
-  - enables fast comprehension and accurate knowledge transfer across roles
-  - bridges business modeling with technical implementation
-
-.why:
-  - distills system complexity into simple, legible steps
-  - reveals system **structure**, **pressure**, and **purpose** in one flow
-  - prevents bloated diagrams and code-first traps
-  - centers every system on motive (`{driver}`), not just structure (`[resource]`)
-  - provides a visual grammar for tracing behavior, loops, and leverage
-
----
-
-## 🧬 distilisys grammar
-
-> a complete system is composed of three structural units:
-> `[resource]`, `<mechanism>`, and `{driver}` — linked via arrow flows (`->`)
-
----
-
-### 🔤 syntax reference
-
-
-| unit           | role in system                       | allowed values / structure                            | examples                                              |
-|----------------|--------------------------------------|-------------------------------------------------------|-------------------------------------------------------|
-| `[resource]`   | observable noun or state             | any domain-grounded, visible quantity                 | [time], [status], [paperRoll], [lead], [invoiceDraft] |
-| `<mechanism>`  | atomic verb or procedure             | any named transformation (must be unambiguous)        | <rest>, <run>, <cache>, <pressAndDry>, <assignCrew>   |
-| `<<effect>>`   | motive impact on a resource          | one of `<<gain>>`, `<<drop>>`, `<<save>>`, `<<lift>>` | <<gain>>[chance], <<drop>>[threat]                    |
-| `{driver}`     | pressure or motive signal            | one of four canonical forms *(see below)*             | {+incentive:<<save>>[time]}, {-headwind:[friction]}   |
-
-
----
-
-### 📌 valid `{driver}` forms
-
-motive pressure must take one of these four structures:
-
-| form              | meaning                                 | example                                      |
-|-------------------|-----------------------------------------|----------------------------------------------|
-| `{+incentive}`    | actor is pulled toward a `[chance]`     | `[actor]{+incentive:<<save>>[time]}`         |
-| `{-decentive}`    | actor is pushed away from a `[threat]`  | `[actor]{-decentive:<<drop>>[health]}`       |
-| `{+tailwind}`     | environment helps progress              | `[season]{+tailwind:<<gain>>[demand]}`       |
-| `{-headwind}`     | environment hurts progress              | `[policy]{-headwind:<<gain>>[growth]}`       |
-
-📌 each `{driver}` optionally names the `<<effect>>[resource]` it acts on.
-see `ecologist.brief: motive grammar` for deeper structure.
-
----
-
-### 🔁 routes, choices, and cycles
-
-- use `->` to show transformation:
-  ```text
-  [pulp] -> <bleach> -> [refinedPulp]
-  ```
-
-- use `?` to mark optional paths:
-  ```text
-  [pulp] -> <bleach>? -> [refinedPulp]
-  ```
-
-- use `// 🔁` to mark loops:
-  ```text
-  [jobBooked]   // 🔁 cycle
-  ```
-
----
-
-### ♻️ cycles
-
-- **cycles dominate long-term system behavior**
-  - they drive reinforcement, depletion, habituation, and resilience
-  - without cycles, systems are static or short-lived
-- examples include flywheels, feedback loops, starvation spirals, compounding growth, decay chains
-- always **model cycles explicitly** — they reveal the true engine of the system
-- mark the return edge with a `<<gain>>` or `<<drop>>` to show its **motive impact**, when applicable
-- cycles aren’t just features — they are the **core structure** of persistence, collapse, and change
-
-
----
-
-### ♻️ actorfull vs actorless systems
-
-distilisys can model both actorfull and actorless systems
-
----
-
-#### 🧍 actorfull systems
-systems where behavior is shaped by **actors with motive**
-→ use **motive grammar** to trace transformation + pressure
-
-```text
-<mechanism> → <<effect>>[resource] → <<gain>>[chance]
-<mechanism> → <<effect>>[resource] → <<drop>>[threat]
-```
-
-- shows not just **what changes**, but **why it matters**
-- used for ecosystems, businesses, organisms, social behavior
-
----
-
-#### ⚙️ actorless systems
-systems that run without motive or agency
-→ trace only transformations of [resource] via <mechanism>
-
-```text
-[resource] → <mechanism> → [resource]
-```
-
-- sufficient for:
-  - physical processes (e.g. circuits, fluid flow)
-  - deterministic systems
-  - mechanistic pipelines
-
-> 📌 motive grammar is optional — used only when actors and outcomes shape system flow
-
-
----
-
-### ✔️ guidance
-
-- start with the `{driver}` → what pressure triggers this system?
-- define entry `[resource]` and final `[resource]` states
-- describe each `<mechanism>` step clearly and precisely
-- always show what `[resource]` is affected and what is returned
-- tag **cycles** and **optional paths** explicitly
-- **avoid generic terms** like `[user]`, `<processData>`, `<sync>`, use ubiqlang
-
----
-
-### 🧪 examples
-
-.positive:
-```sys
-@[neighbor]<getLawnCareApt>
-=
-    [lawn]
-    -> @[neighbor]<getLawnState>
-    -> [lawn].looks=poor
-
-    -> @[neighbor]<getLawnCareQuotes>
-    -> [quoteList]
-
-    -> @[neighbor]<choosePro>
-    -> [jobBooked]
-
-      => [neighbor]{+incentive:[status]++:keepUpWithJoneses}
-      => [platform]{+incentive:[trust]++:fromProviders}
-      => [platform]{+incentive:[money]++:transactionFee}
-```
-
-```sys
-@[provider]<winLawnCareSubscription>
-=
-    @[neighbor]<getLawnCareApt>
-    -> [jobBooked]
-
-    -> @[pro]<acceptJob>
-    -> @[pro]<doTheWork>
-    -> [lawn].looks=great
-
-    -> @[neighbor]<leaveReview>
-    -> [review]
-
-    -> @[platform]<updateProReputation>
-    -> [pro].rating++
-
-    -> @[platform]<promptRebooking>
-    -> @[neighbor]<bookFollowup>
-    -> [jobBooked]   // 🔁 cycle
-
-      => [pro]{+incentive:[money]++:jobPayout}
-      => [pro]{+incentive:[trust]++:goodReview}
-      => [neighbor]{+incentive:[safety]++:sameProSameQuality}
-      => [platform]{+incentive:[retention]++:repeatBooking}
-```
-
-.negative:
-- `<processData>` → unclear mechanism
-- `[user]` → too generic
-- `<sync>` → ambiguous meaning across contexts
-- `{driver}` omitted → unclear system purpose
-
----
-
-.recommendations:
-  - every system should begin and end with `[resource]`
-  - use `<mechanism>` for every transformation
-  - include a `{driver}` to express motive
-  - embed motive grammar inline (`<<effect>>[resource]`)
-  - mark cycles explicitly (`// 🔁`)
-  - reference `ubiqlang` to name domain terms clearly
-
----
-
-### 📚 extension: `motive.grammar`
-
-> motive.grammar is a formal extension of distilisys.grammar
-> — used when actor behavior and motivational dynamics must be made explicit.
-
-it introduces:
-- `[chance]` and `[threat]` as motive targets
-- `<<effect>>[resource]` grammar to explain pressure
-- semantic distinctions like `<<gain>>`, `<<drop>>`, `<<save>>`, and `<<lift>>`
-- actor-based drivers like `{+incentive:<<save>>[time]}`
-
-📌 use `motive.grammar` when you need to model **why** actors act, not just **how** systems operate.
-
----
-
-.related:
-  - tactic: `lang:ubiqlang`
-  - brief: `ecologist.brief: motive grammar`
-  - brief: `ecologist.brief: motive horizon`
-  - brief: `ecologist.brief: motive polarity`

package/dist/logic/roles/ecologist/.briefs/distilisys/sys201.actor.motive._.summary.md

@@ -1,82 +0,0 @@
-# 🧭 ecologist.actor.motive primitives
-
-these primitives define how actors relate to paths, pressure, and loss over time.
-
----
-
-## ⌛ 1. reversibility & entropy
-
-- **reversibility** = how much future [option]ality is preserved after a [choice]
-- **entropy** = the collapse of future [option]s following irreversible [choice]
-  → entropy rises as [choice]s foreclose paths
-  → reversibility slows entropic loss
-
----
-
-## 🎲 2. option, chance, choice
-
-- **option** = could
-- **chance** = should
-- **choice** = will
-
-\`\`\`text
-chance = option × motive
-choice = chance × decision
-\`\`\`
-
-- **option** defines what’s available
-- **chance** defines what’s relevant
-- **choice** defines what’s committed
-
----
-
-## ⚠️ 3. chance.motive.polarity, threat
-
-- [chance] can carry **positive** or **negative** motive polarity
-  → pulls the actor toward, or pushes them away
-
-- a **[threat]** is a [chance] with **decentive motive**
-  → [chance].motive = {-decentive}
-
-- threats still follow the [chance] structure
-  → they are possible futures, just ones the actor is **driven to avoid**
-
-\`\`\`text
-threat = [chance].motive={decentive}
-       = option × motive={decentive}
-\`\`\`
-
----
-
-## 🧭 4. motive horizon: why actors act
-
-- all actions aim to:
-  - **<<gain>>[chance]** → expand attractive futures
-  - **<<drop>>[threat]** → eliminate repulsive ones
-
-- [time], [energy], [status], etc. are not motives themselves — they are **levers** to shift [chance] or [threat]
-
-\`\`\`text
-mechanism → <<effect>>[resource] → <<gain>>[chance]
-mechanism → <<effect>>[resource] → <<drop>>[threat]
-\`\`\`
-
-📌 intelligence = managing levers to maximize [chance], minimize [threat]
-
----
-
-## 🧠 5. motive grammar: distilisys + actor motive
-
-- extends `distilisys:grammar` by adding **motive force** to system flows
-
-- every action flows from:
-  - `<mechanism>` → <<effect>>[resource] → <<gain>>[chance]
-  - `<mechanism>` → <<effect>>[resource] → <<drop>>[threat]
-
-- `{driver}` adds pressure context:
-  - `{+incentive}`, `{-decentive}` → actor-driven
-  - `{+tailwind}`, `{-headwind}` → environment-driven
-
-- `[resource]` only matters when it shifts exposure to [chance] or [threat]
-
-📌 motive grammar = distilisys + reason to act

package/dist/logic/roles/ecologist/.briefs/distilisys/sys201.actor.motive.p1.reversibility.entropy.md

@@ -1,39 +0,0 @@
-## ♻️ ecologist.brief: reversibility and entropy
-
-> this brief defines how **reversibility** interacts with **entropy** in ecological and decision-making systems.
-> it explains why reversible choices preserve agency — and why irreversible ones accelerate loss.
-
----
-
-### 🔁 reversibility
-a **reversible choice** is one whose consequences can be undone or altered
-it preserves optionality and keeps future paths open
-
-an **irreversible choice** consumes resources, alters the environment, or forecloses prior options
-it commits the actor to a narrowed future
-
----
-
-### 🌀 entropy
-entropy measures the system’s **disorder**, **uncertainty**, or **loss of recoverability**
-it tends to increase over time — especially through irreversible actions
-
----
-
-### ⛓️ relationship
-
-- **reversibility resists entropy**
-  reversible choices delay commitment and preserve order
-  → more paths stay accessible
-
-- **irreversibility increases entropy**
-  irreversible choices lock in change, close options, and increase system disorder
-  → fewer future paths remain
-
----
-
-### 🧠 ecological implication
-- actors tend to **prefer reversible choices under uncertainty**
-  → to **buffer against entropic loss**
-  → to preserve **future agency** in evolving environments
-

package/dist/logic/roles/ecologist/.briefs/distilisys/sys201.actor.motive.p2.option.chance.choice.md

@@ -1,140 +0,0 @@
-## 🧭 ecologist.brief: option vs chance vs choice
-
-> these three terms describe how actors relate to possible paths.
-> each plays a distinct role in motive grammar:
-> - **option** defines availability
-> - **chance** adds motive
-> - **choice** commits to action
-
----
-
-### 🛣️ option
-a path the actor *could* take
-neutral — no preference, pressure, or motive required
-
----
-
-### 🎯 chance
-a path the actor is *driven* to take
-an option made salient by motive — not yet taken, but charged with relevance
-
-→ `chance = option × motive`
-
-*note: [chance] is a synonym for [opportunity]*
-
----
-
-### 🗳️ choice
-a path the actor *commits* to take
-it turns potential into action
-
-→ `choice = chance × decision`
-
-#### ⌛ reversibility and entropy
-
-- **reversible choices** preserve optionality
-  → paths remain open; entropy stays low
-  _ex: briefly probing a foraging site_
-
-- **irreversible choices** consume or foreclose options
-  → future paths collapse; entropy rises
-  _ex: attacking a predator, migrating, mating_
-
-> reversibility measures how much **future agency** is preserved
-> irreversible choices accelerate **entropic decay**
-> reversibility is how actors **buffer against commitment risk**
-
----
-
-### 🔁 progression
-
-\`\`\`md
-option
-  ↓ × motive
-chance
-  ↓ × decision
-choice
-\`\`\`
-
----
-
-### 🔁 pattern
-
-- **option** = could
-- **chance** = should
-- **choice** = will
-
----
-
-### 🧪 summary
-
-| term   | definition                      | identity          |
-|--------|---------------------------------|-------------------|
-| option | a possible path                 | —                 |
-| chance | a motivated option              | option × motive   |
-| choice | a committed path                | chance × decision |
-
----
-
-## 🧪 examples: option vs chance vs choice
-
----
-
-### 1. 🐦 bird sees two berry bushes
-
-- **option**:
-  - [option.1] = bush.1 with 5 berries
-  - [option.2] = bush.2 with 3–10 berries (uncertain yield)
-
-- **chance**:
-  - [chance.1] = <<gain>>[berries] ×5 → <<gain>>[energy], <<gain>>[nutrients]
-  - [chance.2] = <<gain>>[berries] ×3–10 → same drivers, higher upside
-
-- **choice**:
-  commits to [chance.2] — starts with bush.2
-  - reasoning: higher yield may meet need in one stop
-  - fallback remains if yield is low
-
-- ⌛ **reversibility**:
-  - initially reversible (can switch bushes)
-  - becomes irreversible once berries are consumed → entropy ↑
-
----
-
-### 2. 🧑 human choosing a job offer
-
-- **option**:
-  - [option.1] = local company (stable, low growth)
-  - [option.2] = startup (high risk, high upside)
-
-- **chance**:
-  - [chance.1] = <<gain>>[income], <<drop>>[risk]
-  - [chance.2] = <<gain>>[equity], <<lift>>[future potential], <<gain>>[experience]
-
-- **choice**:
-  commits to [chance.2] — accepts startup offer
-  - reasoning: aligns with ambition and growth motive
-
-- ⌛ **reversibility**:
-  - partially reversible (can leave job), but
-  - opportunity cost and sunk effort accumulate → entropy ↑
-
----
-
-### 3. 🐘 elephant approaches waterholes
-
-- **option**:
-  - [option.1] = nearby, crowded waterhole
-  - [option.2] = distant, quieter waterhole
-
-- **chance**:
-  - [chance.1] = <<gain>>[water] quickly, but risk <<drop>>[access]
-  - [chance.2] = <<gain>>[water], <<lift>>[safety], <<drop>>[conflict], at cost of <<drop>>[time]
-
-- **choice**:
-  commits to [chance.2] — takes the distant route
-  - reasoning: safer, more reliable, fewer competitors
-
-- ⌛ **reversibility**:
-  - mostly irreversible — once underway, less useful to retreat
-  - travel cost and risk compound → entropy ↑

package/dist/logic/roles/ecologist/.briefs/distilisys/sys201.actor.motive.p3.chance.motive.polarity.threat.md

@@ -1,72 +0,0 @@
-## 🧭 ecologist.brief: motive polarity
-
-> all behavior is driven by motive — but not all motive attracts.
-> motive can pull actors toward outcomes (**incentives**) or push them away (**decentives**).
-> this polarity applies to [chance] — possible futures with motivational force.
-
----
-
-### 🧲 incentive
-a **positive motive** — pulls the actor toward a future
-→ drives **approach behavior**
-
-- examples:
-  - food → <<gain>>[energy]
-  - mate → <<gain>>[reproductive chance]
-  - shelter → <<drop>>[exposure]
-
----
-
-### 🧲 decentive _(preferred term)_
-a **negative motive** — pushes the actor away from a future
-→ drives **avoidance behavior**
-
-> 📌 a decentive is still a motive — not its absence
-> it creates urgency, direction, and action — just in reverse
-
-- examples:
-  - predator → <<drop>>[life], <<drop>>[agency]
-  - fire → <<drop>>[resource]
-  - toxin → <<drop>>[health]
-
----
-
-### ⚖️ polarity applied to [chance]
-
-> **[chance] = [option] × motive**
-> polarity determines whether the actor is driven *toward* or *away*
-
----
-
-#### ⚠️ [threat]
-a **negatively motivated [chance]** — a possible future the actor is driven to avoid
-
-→ `threat = chance.motive = {-decentive}`
-
-- a threat is still a [chance] — it might happen
-- what distinguishes it is that the actor wants to avoid it; a **push-away** motive polarity
-
-this includes:
-- **[risk]** — the [chance].probability of this [threat]
-- **[pain]** — the [chance].outcome of this [threat]
-
-> 📌 [risk] and [pain] are specific to [threat]s,
-> but their structure — `chance.probability` and `chance.outcome` — applies to all [chance]s
-
----
-
-### 🧪 summary
-
-| concept      | what it is                         | motive polarity  | behavior it drives   |
-|--------------|------------------------------------|------------------|----------------------|
-| [chance]     | possible outcome with motive       | + or –           | approach or avoid    |
-| [threat]     | chance with decentive motive       | –                | avoidance            |
-| [magnet]     | chance with incentive motive       | +                | approach             |
-| incentive    | motive that attracts               | +                | approach             |
-| decentive    | motive that repels                 | –                | avoidance            |
-
----
-
-📌 prefer **decentive** over *disincentive*
-→ it is morphologically parallel to *incentive*
-→ and fits cleanly into the grammar of [chance].motive