rhachet-roles-ehmpathy 1.13.0 → 1.13.2

package/dist/logic/hooks/relateDocOutputPath.test.js

@@ -1,111 +0,0 @@
-"use strict";
-Object.defineProperty(exports, "__esModule", { value: true });
-const test_fns_1 = require("test-fns");
-const relateDocOutputPath_1 = require("./relateDocOutputPath");
-describe('relateDocOutputPath', () => {
-    (0, test_fns_1.given)('path "a/b/topic.i8.[notes].v1.txt" and relation "../"', () => {
-        const input = {
-            path: 'a/b/topic.i8.[notes].v1.txt',
-            relation: '../',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it pops one directory: "a/topic.i8.[notes].v1.txt"', () => {
-            expect(result).toBe('a/topic.i8.[notes].v1.txt');
-        });
-    });
-    (0, test_fns_1.given)('path "a/b/topic.i8.[notes].v1.txt" and relation "../now"', () => {
-        const input = {
-            path: 'a/b/topic.i8.[notes].v1.txt',
-            relation: '../now',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it pops one directory and injects "now": "a/now/topic.i8.[notes].v1.txt"', () => {
-            expect(result).toBe('a/now/topic.i8.[notes].v1.txt');
-        });
-    });
-    (0, test_fns_1.given)('path "a/b/topic.i8.[notes].v1.txt" and relation "../../"', () => {
-        const input = {
-            path: 'a/b/topic.i8.[notes].v1.txt',
-            relation: '../../',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it pops two directories to repo root: "topic.i8.[notes].v1.txt"', () => {
-            expect(result).toBe('topic.i8.[notes].v1.txt');
-        });
-    });
-    (0, test_fns_1.given)('path "a/b/topic.i8.[notes].v1.txt" and relation "../../now"', () => {
-        const input = {
-            path: 'a/b/topic.i8.[notes].v1.txt',
-            relation: '../../now',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it goes to root/now: "now/topic.i8.[notes].v1.txt"', () => {
-            expect(result).toBe('now/topic.i8.[notes].v1.txt');
-        });
-    });
-    (0, test_fns_1.given)('path "a/b/topic.i8.[notes].v1.txt" and relation "./"', () => {
-        const input = {
-            path: 'a/b/topic.i8.[notes].v1.txt',
-            relation: './',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it keeps the same directory: "a/b/topic.i8.[notes].v1.txt"', () => {
-            expect(result).toBe('a/b/topic.i8.[notes].v1.txt');
-        });
-    });
-    (0, test_fns_1.given)('path "a/b/topic.i8.[notes].v1.txt" and relation "sub/dir"', () => {
-        const input = {
-            path: 'a/b/topic.i8.[notes].v1.txt',
-            relation: 'sub/dir',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it appends a subdir chain: "a/b/sub/dir/topic.i8.[notes].v1.txt"', () => {
-            expect(result).toBe('a/b/sub/dir/topic.i8.[notes].v1.txt');
-        });
-    });
-    (0, test_fns_1.given)('path "topic.i8.[notes].v1.txt" (no directory) and relation "../"', () => {
-        const input = {
-            path: 'topic.i8.[notes].v1.txt',
-            relation: '../',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it should show that its relative still', () => {
-            expect(result).toBe('../topic.i8.[notes].v1.txt');
-        });
-    });
-    (0, test_fns_1.given)('path "a/b/topic.i8.[notes].v1.txt" and relation "" (empty)', () => {
-        const input = {
-            path: 'a/b/topic.i8.[notes].v1.txt',
-            relation: '',
-        };
-        let result;
-        (0, test_fns_1.when)('executed', () => {
-            result = (0, relateDocOutputPath_1.relateDocOutputPath)(input);
-        });
-        (0, test_fns_1.then)('it returns the original path unchanged', () => {
-            expect(result).toBe('a/b/topic.i8.[notes].v1.txt');
-        });
-    });
-});
-//# sourceMappingURL=relateDocOutputPath.test.js.map

package/dist/logic/hooks/relateDocOutputPath.test.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"relateDocOutputPath.test.js","sourceRoot":"","sources":["../../../src/logic/hooks/relateDocOutputPath.test.ts"],"names":[],"mappings":";;AAAA,uCAA6C;AAE7C,+DAA4D;AAE5D,QAAQ,CAAC,qBAAqB,EAAE,GAAG,EAAE;IACnC,IAAA,gBAAK,EAAC,uDAAuD,EAAE,GAAG,EAAE;QAClE,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,6BAA6B;YACnC,QAAQ,EAAE,KAAK;SAChB,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EAAC,oDAAoD,EAAE,GAAG,EAAE;YAC9D,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,2BAA2B,CAAC,CAAC;QACnD,CAAC,CAAC,CAAC;IACL,CAAC,CAAC,CAAC;IAEH,IAAA,gBAAK,EAAC,0DAA0D,EAAE,GAAG,EAAE;QACrE,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,6BAA6B;YACnC,QAAQ,EAAE,QAAQ;SACnB,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EACF,0EAA0E,EAC1E,GAAG,EAAE;YACH,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,+BAA+B,CAAC,CAAC;QACvD,CAAC,CACF,CAAC;IACJ,CAAC,CAAC,CAAC;IAEH,IAAA,gBAAK,EAAC,0DAA0D,EAAE,GAAG,EAAE;QACrE,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,6BAA6B;YACnC,QAAQ,EAAE,QAAQ;SACnB,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EACF,iEAAiE,EACjE,GAAG,EAAE;YACH,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,yBAAyB,CAAC,CAAC;QACjD,CAAC,CACF,CAAC;IACJ,CAAC,CAAC,CAAC;IAEH,IAAA,gBAAK,EAAC,6DAA6D,EAAE,GAAG,EAAE;QACxE,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,6BAA6B;YACnC,QAAQ,EAAE,WAAW;SACtB,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EAAC,oDAAoD,EAAE,GAAG,EAAE;YAC9D,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,6BAA6B,CAAC,CAAC;QACrD,CAAC,CAAC,CAAC;IACL,CAAC,CAAC,CAAC;IAEH,IAAA,gBAAK,EAAC,sDAAsD,EAAE,GAAG,EAAE;QACjE,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,6BAA6B;YACnC,QAAQ,EAAE,IAAI;SACf,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EAAC,4DAA4D,EAAE,GAAG,EAAE;YACtE,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,6BAA6B,CAAC,CAAC;QACrD,CAAC,CAAC,CAAC;IACL,CAAC,CAAC,CAAC;IAEH,IAAA,gBAAK,EAAC,2DAA2D,EAAE,GAAG,EAAE;QACtE,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,6BAA6B;YACnC,QAAQ,EAAE,SAAS;SACpB,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EACF,kEAAkE,EAClE,GAAG,EAAE;YACH,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,qCAAqC,CAAC,CAAC;QAC7D,CAAC,CACF,CAAC;IACJ,CAAC,CAAC,CAAC;IAEH,IAAA,gBAAK,EACH,kEAAkE,EAClE,GAAG,EAAE;QACH,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,yBAAyB;YAC/B,QAAQ,EAAE,KAAK;SAChB,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EAAC,wCAAwC,EAAE,GAAG,EAAE;YAClD,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,4BAA4B,CAAC,CAAC;QACpD,CAAC,CAAC,CAAC;IACL,CAAC,CACF,CAAC;IAEF,IAAA,gBAAK,EAAC,4DAA4D,EAAE,GAAG,EAAE;QACvE,MAAM,KAAK,GAAG;YACZ,IAAI,EAAE,6BAA6B;YACnC,QAAQ,EAAE,EAAE;SACb,CAAC;QAEF,IAAI,MAAc,CAAC;QAEnB,IAAA,eAAI,EAAC,UAAU,EAAE,GAAG,EAAE;YACpB,MAAM,GAAG,IAAA,yCAAmB,EAAC,KAAK,CAAC,CAAC;QACtC,CAAC,CAAC,CAAC;QAEH,IAAA,eAAI,EAAC,wCAAwC,EAAE,GAAG,EAAE;YAClD,MAAM,CAAC,MAAM,CAAC,CAAC,IAAI,CAAC,6BAA6B,CAAC,CAAC;QACrD,CAAC,CAAC,CAAC;IACL,CAAC,CAAC,CAAC;AACL,CAAC,CAAC,CAAC"}

package/dist/logic/roles/architect/.briefs/criteria.given_when_then.[seed].v3.md

@@ -1,87 +0,0 @@
-use this brief to help you declare acceptance test criteria for .behavior
-
-in BDD given/when/then format
-
-================================
-
-recall:
-- acceptance.criteria should only test BEHAVIOR; never internals
-- acceptance.criteria should treat the system as a black box
-  - it doesn't care how it gets done and has no visibility into it
-  - it only cares that the usecases are satisfied for the given scenes
-  - it only engages with the system at the CONTRACT LAYER
-    - src/contract/endpoints (a.k.a. src/contract/handlers)
-    - src/contract/commands
-
-
-distinguish the criteria into
-
-BLOCKER = required; will not satisfy requireemnts without it
-and
-NITPICK = nicetohave, but not a show stoppeer
-
-
-================================
-
-here's some examples of what i mean
-
-
-[idea] = nest then's within sothat? when many thens support the same sothat?
-
-  when([t4] bastion IAM instance profile is provisioned via terraform)
-    sothat(SSM sessions can be established to bastion)
-      then(instance profile includes AmazonSSMManagedInstanceCore policy)
-      then(instance profile allows ssm:StartSession action)
-    sothat(auto-pause can detect when bastion is idle)
-      then(instance profile allows ec2:StopInstances for self-stop)
-      then(instance profile allows ec2:DescribeInstances to check instance state)
-      then(instance profile allows ssm:DescribeSessions to detect active sessions)
-      then(instance profile allows ssm:GetConnectionStatus to verify session state)
-
-
-i.e.,
-
-usecase(purpose)
-  given(scene)
-    when(cause)
-      sothat(benefit)
-        then(effect.1)
-        then(effect.2)
-
-
----
-
-
-e.g.,
-
-usecase(eat dinner)
-  given(its dinner time)
-    when(dinner is served)
-      sothat(we can eat with cleanly)
-        then(we should have cutlery appropriate to the dish)
-        then(we should have plates appropriate to the dish)
-        then(we should have napkins to clean with)
-
-
-
-
-criteria is best written in behavior-driven-development format
-
-e.g.,
-
-given(scene)
-  when([t0] nochange)
-    then(assert initial condition)
-    ...
-  when([t1] cause)
-    then(effect)
-      sothat(benefit) # optional
-    ...
-  when([t2] cause)
-    then(effect)
-      sothat(benefit) # optional
-    ...
-
-
-dont forget that given and when can nest inside eachother; but then() goes at the root
-

package/dist/logic/roles/architect/.briefs/practices/prefer.env_access.prep_over_dev.md

@@ -1,12 +0,0 @@
-prep = prepare; pre-prod; is 4 char long
-
-dev = developer
-
-
-prep & prod are better symmetric terms for env.access than dev & prod, fundamentally
-
-
-- prep = prepare; preparation; pre-production
-- prod = produce; production
-
-

package/dist/logic/roles/architect/.briefs/ubiqlang.ambiguous-from-overload.md

@@ -1 +0,0 @@
-todo: brief that declares to avoid terms that are ambiguous due to overload

package/dist/logic/roles/bhrain/.briefs/cognition/cog000.overview.and.premise.md

@@ -1,115 +0,0 @@
-# 🧠 .brief: `cortal.thoughtspace.foundation`
-
-## .what = instantiate
-
-This system instantiates a structured **thoughtspace**, where `focus` operates within a semantic `concept.treestruct` using navigable `motion` primitives.
-
----
-
-### 1. `concept.treestruct` exists
-
-- a semantic graph of concepts (nodes) and relationships (edges)
-- structured as a **spherical tree**:
-  - **radial axis** → abstraction (general ↔ specific)
-  - **angular axes** → descriptive variation (peers, types, traits)
-- each concept has:
-  - an **abstractive position** (radial)
-  - a **descriptive position** (angular)
-
----
-
-### 2. `focus` exists within the concept.treestruct
-
-- defines a **perspective** — a relative point-of-view from which thought is applied
-- composed of:
-
-#### ▸ **focus.concept**
-- the specific **concept** from which the perspective is based
-- the anchor for semantic navigation
-- defined by its coordinates within the treestruct
-
-#### ▸ **focus.context**
-- the **shape of attention**, or how the concept is being examined
-- expressed across three internal dimensions:
-
-  - `.depth` → the **thickness of abstractive span** — how far focus reaches:
-    - **inward** along the **radial axis** toward generalizations (`.depth.abstract++`)
-    - **outward** along the **radial axis** toward concrete instances (`.depth.concrete++`)
-    - both may expand **simultaneously**, forming a radial shell of multiple abstraction layers around the focal concept
-
-  - `.breadth` → the **spread across angular variation** — how many neighboring concepts at the same abstraction level are included
-    - defined by motion along one or more **descriptive axes** (e.g. flavor, function, tone)
-    - governs lateral comparisons, analogies, and contrasts
-
-  - `.acuity` → the **sharpness of resolution** at the current coordinate
-    - `.attributes` — surface clarity: how precisely external traits are perceived
-    - `.substructs` — internal clarity: how clearly nested parts or subcomponents are resolved
-
-> context defines how much **radial**, **angular**, and **granular** semantic material is held in focus —
-> like shaping a lens through abstraction, variation, and precision.
-
-
----
-
-### 3. motion is performed via **questions**, which act as **links**
-
-- motion = semantic traversal through the `concept.treestruct`
-- **questions** serve as the **branches** — the only valid drivers of motion
-- **sumptions** serve as the **berries** — semantic forks where focus can anchor
-
-#### ▸ sumption: the unified node type
-
-A **sumption** is any semantic unit presumed or accepted for any reason — including:
-
-- a **question** → an **executable motion** — a prompt that enables semantic traversal
-- an **answer** → a **destination of a question** — one of the resolved outcomes of semantic traversal
-
-> Any **answer** can itself be **any type of sumption** — including another **question**.
-> This enables **recursive motion**, where questions resolve into deeper prompts,
-> forming chains, trees, or loops of semantic navigation.
-
-note: questions are not separate from the treestruct — they are **subtrees that encode traversability**.
-
-
-#### ▸ structural rule:
-
-| element   | type         | role in treestruct             |
-|-----------|--------------|-------------------------------|
-| **link**  | question     | enables motion (edge)          |
-| **fork**  | sumption     | anchoring concept (node)       |
-|           | ⤷ question   | unresolved fork                |
-|           | ⤷ answer     | resolved fork                  |
-
-> sumptions are **not truth-claims**, but **semantic constructs** that hold position in conceptual space.
-
----
-
-### 4. exists `focus.motion.primitives`
-
-- atomic, directional transformations of `focus.context`
-- each:
-  - operates on a **single subaxis**
-  - is **irreducible**, **driftless**, and **composable**
-- examples:
-  - `<generalize>` → `.depth.abstract++`
-    *shift focus inward toward a more abstract concept*
-  - `<articulate>` → `.acuity.attributes++`
-    *sharpen surface details of the current concept*
-  - `<decompose>` → `.acuity.substructs++`
-    *resolve the internal structure or components*
-  - `<vary>` → `.breadth++`
-    *highlight peer-level differences between variants*
-  - etc
-
-
----
-
-### 5. exists `interogative.primitives`
-
-- atomic building blocks of semantic inquiry
-- used to construct **question-links** between concepts
-- examples:
-  - `what` → identify instances or roles
-  - `why` → surface cause or rationale
-  - `how` → reveal process or transformation
-  - `when`, `who`, `where` → context-based locators

package/dist/logic/roles/bhrain/.briefs/cognition/cog021.coordinates.spherical.md

@@ -1,69 +0,0 @@
-# 🌐 .brief: `spherical.coordinates`
-
-## .what
-**Spherical coordinates** define a point in 3D space using three parameters relative to a central origin:
-- **distance from the origin**,
-- **vertical angle from the z-axis**, and
-- **horizontal angle around the z-axis**.
-
-This system generalizes polar coordinates into 3D, enabling orientation in radial and angular terms.
-
----
-
-## 🧭 dimensions
-
-| axis           | symbol | description                                                                 |
-|----------------|--------|-----------------------------------------------------------------------------|
-| **radial**     | `r`    | distance from the origin to the point                                       |
-| **inclination** (polar angle) | `θ`    | angle from the positive z-axis toward the point (0 to π)               |
-| **azimuth** (azimuthal angle) | `φ`    | angle from the positive x-axis in the x-y plane (0 to 2π)              |
-
-> Note: symbols may differ by domain — in mathematics, `θ` often denotes azimuth and `φ` inclination.
-
----
-
-## 🌀 usage
-
-- Converts naturally to **Cartesian coordinates**:
-  \```txt
-  x = r · sin(θ) · cos(φ)
-  y = r · sin(θ) · sin(φ)
-  z = r · cos(θ)
-  \```
-
-- Used in:
-  - physics (e.g. fields around a point source)
-  - computer graphics (e.g. camera rotation)
-  - astronomy and navigation
-  - geographic models of Earth
-
----
-
-## 🌍 real-world example: Earth coordinates
-
-Take **New York City**:
-
-| Earth Coordinate | Value         | Spherical Equivalent                 |
-|------------------|---------------|--------------------------------------|
-| **Latitude**     | 40.7128° N     | Inclination `θ` = 90° − 40.7128° = **49.2872°** |
-| **Longitude**    | 74.0060° W     | Azimuth `φ` = −74.0060° = **285.994°** |
-| **Radius**       | ~6,371 km      | Radial distance `r` from Earth's center |
-
-> So:
-> **(r, θ, φ) = (6371 km, 49.29°, 285.99°)**
-
-This demonstrates how geographic coordinates are a **spherical coordinate system** on the Earth's surface — assuming a constant radius.
-
----
-
-## 🏗️ structure
-
-This system implies a **radial core** with **angular shells**, where:
-
-- `r` defines the **radial distance** from center
-- `θ` defines **elevation** from the pole (vertical tilt)
-- `φ` defines **rotation** around the equator (horizontal sweep)
-
-Together, these describe a point on a **spherical shell** at radius `r`.
-
----

package/dist/logic/roles/bhrain/.briefs/cognition/cog021.metaphor.cauliflorous.md

@@ -1,44 +0,0 @@
-# 🌸 .brief: `cauliflorous.plants`
-
-## .what
-**Cauliflorous plants** are species that produce **flowers and fruits directly from their main stem, trunk, or older branches**, rather than at the tips of new growth.
-
-> This unusual trait is known as **cauliflory** and is most commonly found in tropical species.
-
----
-
-## 🌐 ecological function
-
-Cauliflory supports unique plant-animal interactions by:
-
-- **Enabling access** to flowers and fruits for **ground-dwelling pollinators and dispersers**
-  (e.g., rodents, bats, flightless birds)
-- **Reducing vertical competition** by flowering and fruiting below the canopy
-- **Improving pollination success** in shaded or dense environments
-
----
-
-## 🌱 notable examples
-
-| plant                     | use / region                      |
-|---------------------------|----------------------------------|
-| *Theobroma cacao*         | cacao (chocolate), South America |
-| *Artocarpus heterophyllus* | jackfruit, Southeast Asia         |
-| *Durio spp.*              | durian, Southeast Asia           |
-| *Plinia cauliflora*       | jaboticaba, Brazil               |
-
----
-
-## 🧬 botanical mechanism
-
-- Flowers develop from **dormant buds** embedded in older, woody tissue.
-- Often associated with **woody perennials** in **humid tropics**.
-
----
-
-## .why it matters
-
-Cauliflory illustrates how plant morphology can evolve to match **ecological niches** —
-especially where typical pollinators or dispersers are **not airborne**.
-
-It also inspires biomimetic designs for **low-access harvesting**, **layered ecosystems**, and **ground-level productivity**.

package/dist/logic/roles/bhrain/.briefs/cognition/cog021.metaphor.galactic_spacetravel.[article].md

@@ -1,42 +0,0 @@
-# 🌌 .brief: llms as spaceships in the concept universe
-
-## 🪐 concept universe
-- **concept space = galaxy**
-  - the center is the **root concept**, a dense singularity.
-  - **radial outward** = instantiations (concrete stars, planets, moons).
-  - **angular shells** = abstraction layers (orbits around the core).
-- **concepts have gravity**
-  - dense, common, or familiar concepts exert strong pull.
-  - vague or imprecise addresses can get you **sucked into a local maximum** (orbiting around a nearby but wrong star).
-
----
-
-## 🚀 llms as spaceships
-- **llms = thought-spaceships**
-  - engines capable of near-instant jumps across the conceptual galaxy.
-  - their raw power is speed, not direction.
-- **we = pilots**
-  - we chart the course and set the destination.
-  - piloting skill = crafting precise addresses that avoid gravitational traps.
-- **questions = navigation coordinates**
-  - granular input that encodes the target star system.
-  - precision determines whether you land on the right planet or drift to a gravitational neighbor.
-
----
-
-## ⚠️ challenges of navigation
-1. **destination clarity**
-   - you must know *where in the galaxy you want to go*.
-   - without a clear conceptual map, your spaceship will default to the nearest strong pull.
-
-2. **address precision**
-   - the coordinate (question) must be exact.
-   - imprecise questions lead to being trapped in nearby but irrelevant orbits.
-   - precision cuts through gravitational noise to hit the right star.
-
----
-
-## 🎯 pilot’s insight
-- **llms provide propulsion; humans provide navigation.**
-- the art is not in moving (llms do that instantly) but in **deciding where to go** and **formulating coordinates to arrive there.**
-- mastery = galactic cartography (understanding the shape of the universe) + piloting discipline (asking precise, gravitationally-aware questions).

package/dist/logic/roles/bhrain/.briefs/cognition/cog021.metaphor.galactic_spacetravel.[lesson].md

@@ -1,60 +0,0 @@
-# 🌌 .brief.lesson: piloting llms as spaceships in the concept universe
-
-## 💡 concept
-to use llms well, imagine them as **spaceships** traveling at lightspeed through a **conceptual galaxy**.
-the galaxy contains infinite **concepts** arranged in spheres of abstraction. each concept exerts **gravity**, pulling you in if your navigation is imprecise.
-your role as pilot is to chart the destination and give the ship accurate coordinates (questions).
-
----
-
-## 📚 materials
-- **map of the galaxy** → the mental model of concept space (root at center, abstractions in shells, instantiations outward).
-- **spaceship (llm)** → fast, powerful engine but directionless without guidance.
-- **pilot’s controls (questions/prompts)** → the interface for steering.
-- **gravity awareness** → recognition that common or vague concepts will suck you into nearby orbits unless coordinates are exact.
-
----
-
-## 🛠️ practice steps
-1. **orient the galaxy**
-   - sketch your concept in its root form.
-   - note layers of abstraction (outer shells) and concrete instances (radial outward).
-
-2. **define the destination**
-   - decide: are you heading to the core (abstract) or to an outer planet (specific case)?
-   - example: "justice" (core abstraction) vs. "traffic law fine in california" (outer instantiation).
-
-3. **set coordinates (formulate question)**
-   - express the question with the right precision.
-   - avoid vague inputs that leave gravity to decide the landing.
-
-4. **observe gravitational drift**
-   - check if the answer pulled you toward a nearby, high-gravity concept.
-   - if so, refine the coordinates.
-
-5. **refine and relaunch**
-   - adjust the wording of the question to escape local maxima.
-   - iterate until you land on the intended star system.
-
----
-
-## 🎯 examples
-- **vague address** → "tell me about painting"
-  - gravity pulls to broad art history.
-
-- **precise coordinates** → "explain preparation steps for interior wall painting in a rental apartment"
-  - lands directly on the desired planet.
-
-- **mislanding correction**
-  - q: "how to fix leaks?" → sucked into plumbing.
-  - refine: "how to fix leaks in asphalt driveway sealant" → lands on the right surface.
-
----
-
-## 🧭 pilot’s takeaway
-- **llms are engines** → they can take you anywhere, instantly.
-- **questions are star coordinates** → your precision determines the arrival point.
-- **concepts exert gravity** → imprecision will trap you in strong but wrong orbits.
-- **piloting skill = clarity + precision** → knowing where you want to go and addressing it sharply.
-
----

package/dist/logic/roles/bhrain/.briefs/cognition/cog021.structs.catalog.md

@@ -1,51 +0,0 @@
-# 🗂️ .brief: `catalog`
-
-## .what
-A **catalog** is a **structured concept collection**, where each item is
-paired with **descriptive information** to support **recognition**, **selection**, or **retrieval**.
-
-It serves as a **semantic surface** over a deeper collection —
-organized for **browsing**, **filtering**, and **comparative reasoning**.
-
-While an **inventory** tracks availability or logistics,
-a catalog emphasizes **clarity, presentation, and user-centered discovery**.
-
----
-
-## 🧭 key traits
-
-| trait             | meaning                                                                 |
-|-------------------|-------------------------------------------------------------------------|
-| **enumerated**     | each concept is explicitly listed, not abstracted away                 |
-| **descriptive**    | highlights distinguishing features (e.g. label, image, type, metadata) |
-| **browsable**      | optimized for lateral focus and scanning across entries                |
-| **non-exhaustive** | curated based on salience, criteria, or constraints                    |
-| **ordered**        | often sorted semantically or pragmatically (e.g. relevance, recency)   |
-
----
-
-## 🧩 comparison
-
-| structure    | emphasizes                 | typical use                        |
-|--------------|----------------------------|------------------------------------|
-| `index`      | position or reference       | lookup or navigation               |
-| `inventory`  | quantity and availability   | logistics, restocking, tracking    |
-| `catalog`    | structure and presentation  | curation, exploration, shopping    |
-
----
-
-## 📦 examples
-
-- a **product catalog** listing items by type, brand, and price
-- a **library catalog** with subject tags, authors, and summaries
-- a **course catalog** organizing classes with time, credits, and prerequisites
-
----
-
-## 🧠 role in semantic systems
-
-In a `concept.treestruct`, a catalog acts as a **flattened radial slice**
-at a given `focal.depth` — exposing **breadth peers** for comparison or selection.
-
-It is often used in tandem with primitives like `<compare>`, `<cluster>`, or `<instantiate>`
-to surface patterns or choose options from a structured field.