rhachet-roles-ehmpathy 1.0.0 → 1.2.0

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.example.structure.[article].i2.md

@@ -0,0 +1,73 @@
+# 🧩 .brief.article: `recommended structure of .brief.demo via example`
+
+## 🌟 introduction
+
+a `.brief.demo` is a streamlined, example-driven document designed to illustrate a concept by presenting a specific instance of it in a structured markdown format. by recommending a standardized structure with a focus on instantiating the concept, it ensures clarity, engagement, and adaptability for diverse audiences, from students to professionals.
+
+## 📚 the core components
+
+the `.brief.demo` follows a logical progression to build understanding step by step.
+
+### 1. concept definition (💡)
+a concise, one-sentence definition of the concept, setting the foundation without overwhelming the reader. it acts as the entry point, ensuring everyone starts on the same page.
+
+- **purpose**: define the concept succinctly, avoiding jargon where possible.
+
+### 2. guiding question (❓)
+a block-quoted question focuses the demo on a specific inquiry, typically:
+`> what is an example of [concept]?`
+
+- **purpose**: to create curiosity and direct attention to the example’s role in answering the query.
+
+### 3. example presentation (📌)
+this is the heart of the `.brief.demo`, introducing the chosen example and breaking it into two subsections: **what** and **how**.
+
+#### 📌.📖 what
+instantiates the concept by presenting the example in its most representative form. the structure used here is imagined to best fit the concept being demonstrated.
+
+**purpose**: to make the concept tangible rather than abstract.
+
+#### 📌.🔍 how
+explains how the instantiated example embodies the concept. the structure of this explanation is also imagined to best fit the concept.
+
+**purpose**: to provide depth and analysis, linking the instance back to the definition in a systematic way.
+
+### 4. placeholder example of `.brief.demo` structure
+
+\`\`\`markdown
+# 🧩 .brief.demo: `[concept]` via `example` = `[example]`
+
+## 💡 concept
+[brief definition of the concept]
+
+## ❓ question
+> what is an example of [concept]?
+
+## 📌 example: [example title]
+
+### 📌.📖 what
+
+> What is [specific example of the concept]?
+
+[brief introduction to the example]
+
+[structured instantiation imagined to fit the concept]
+
+### 📌.🔍 how
+
+> How is it an example of [concept]?
+
+[brief explanation of how it embodies the concept]
+
+[structured explanation imagined to fit the concept]
+\`\`\`
+
+## ✅ benefits and adaptability
+
+the `.brief.demo` structure excels in its adaptability:
+
+- **clarity through instantiation**: the “what” section transforms abstractions into concrete, example-driven forms.
+- **depth without overload**: the “how” section provides analysis through whatever framing best matches the concept, ensuring precision without unnecessary bulk.
+- **versatility across domains**: whether scientific, technical, social, or abstract, the structure adapts by letting the instance shape its own presentation.
+
+this makes `.brief.demo` a powerful tool for education, documentation, and knowledge sharing, consistently delivering clear and engaging concept demonstrations.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.narrative.[demo].usecase.order_online.by_chatgpt.md

@@ -0,0 +1,34 @@
+# .brief.demo: `use case` via `narrative` = `ordering dinner on an app`
+
+## 💡 concept
+a use case describes how a user interacts with a system to achieve a specific goal, detailing the steps, actors, and system responses involved in the interaction.
+
+## ❓ question
+> what is a narrative example of a use case?
+
+## 📌 narrative: ordering dinner on an app
+
+### 📌.📖 what
+
+> what is the story of ordering dinner on an app?
+
+emma has just finished a long day at work and doesn’t feel like cooking. she opens her favorite food delivery app on her phone, browses local restaurants, and chooses a thai place she likes. after customizing her pad thai with no peanuts, she taps “order now.”
+
+- the **system** processes her payment and confirms the order.
+- the **restaurant** receives the request and begins cooking.
+- a **courier** is assigned and notified through the app.
+- emma gets real-time updates and watches the courier’s location as the delivery approaches.
+- finally, the courier rings her doorbell and hands her dinner, just as the app marks the order complete.
+
+### 📌.🔍 how
+
+> how does this narrative embody a use case?
+
+this narrative demonstrates a use case because it shows:
+
+- **actors**: emma (customer), the app (system), the restaurant, and the courier.
+- **goal**: emma’s objective of getting a meal delivered.
+- **steps**: the sequence of interactions—from browsing and ordering to cooking, delivery, and confirmation.
+- **system responses**: payment processing, status updates, and delivery tracking that support each step.
+
+by telling a story from the user’s perspective, the narrative highlights the flow of interactions that define a use case, making the abstract concept tangible and relatable.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.walkthrough.[demo].usecase.book_online.by_chatgpt.md

@@ -0,0 +1,47 @@
+# .brief.demo: `use case` via `walkthrough` = `booking a hotel room online`
+
+## 💡 concept
+a use case describes how a user interacts with a system to achieve a specific goal, detailing the steps, actors, and system responses involved in the interaction.
+
+## ❓ question
+> what is a walkthrough example of a use case?
+
+## 📌 walkthrough: booking a hotel room online
+
+### 📌.📖 what
+
+> what is the walkthrough of booking a hotel room?
+
+a customer wants to reserve a hotel stay through a booking website. this walkthrough guides step by step through the interaction from start to finish.
+
+1. **open system**
+   - user navigates to the hotel booking website.
+   - *system response:* homepage loads with search bar.
+2. **search hotels**
+   - user enters destination, dates, and guest count.
+   - *system response:* list of available hotels appears.
+3. **select hotel**
+   - user browses and chooses a hotel.
+   - *system response:* details page shows amenities, price, and photos.
+4. **choose room**
+   - user selects a room type.
+   - *system response:* room availability and price confirmed.
+5. **enter details**
+   - user provides guest information and payment method.
+   - *system response:* form validates input and displays order summary.
+6. **confirm booking**
+   - user clicks “book now.”
+   - *system response:* confirmation page with reservation number and email receipt.
+
+### 📌.🔍 how
+
+> how is this a walkthrough of a use case?
+
+this walkthrough shows the **structured sequence** of steps and responses:
+
+- **actors**: user and system are clearly identified at each stage.
+- **goal orientation**: every step moves toward the outcome—successfully booking a room.
+- **interaction clarity**: system responses are paired with user actions, demonstrating the back-and-forth flow.
+- **step-by-step detail**: breaking the process into checkpoints makes the use case easy to follow and replicate.
+
+the walkthrough method highlights the **procedural nature** of a use case, showing how user actions trigger system behavior until the goal is achieved.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/[brief].verbiage.outline.over.narrative.md

@@ -0,0 +1,55 @@
+# 🧩 .brief: `brief.article.format.outline`
+
+## .what
+**`brief.article.format.outline`** specifies the preference for writing **[brief][article]**s in **outline format** rather than paragraph format,
+in order to **maximize signal-to-noise ratio** — ensuring the reader receives the **most relevant information** with the **least distraction**.
+
+---
+
+## 🎯 purpose
+- prioritize **information density** over narrative flow
+- enable **rapid scanning** and **selective focus** on relevant points
+- minimize **filler language**, rhetorical padding, and connective prose that dilute clarity
+
+---
+
+## 📐 rationale
+### 1. higher signal density
+- each point stands alone, stripped to its essential statement
+- no dependency on surrounding sentences for meaning
+
+### 2. lower cognitive noise
+- reduced verbal clutter, fewer transitions
+- visual separation between concepts lowers mental parsing cost
+
+### 3. faster scanning & retrieval
+- indentation and bullet hierarchy serve as immediate visual anchors
+- enables “jump-to-point” reading without loss of context
+
+### 4. explicit structure
+- hierarchy is visible, not inferred
+- easier to map relationships between concepts at a glance
+
+---
+
+## 🔍 comparison
+| factor                  | outline format  | paragraph format |
+|-------------------------|----------------|------------------|
+| signal density          | **high**       | medium           |
+| noise suppression       | **strong**     | weaker           |
+| scan speed              | **fast**       | slower           |
+| structure visibility    | **explicit**   | implicit         |
+| nuance capacity         | lower          | higher           |
+
+---
+
+## 🛠 usage guidance
+- default to outline format for all `[brief][article]`s
+- use paragraph sub-sections **only** when nuance or rhetorical flow is essential
+- keep bullet points **single-idea only**; avoid compound sentences in bullets
+
+---
+
+## 📎 note
+this preference is **format-level**, not **content-level** — it shapes **presentation**, not **what is included**.
+the core content of a [brief] remains the same regardless of format; the outline format simply transmits it **more cleanly and quickly**.

package/dist/logic/roles/bhrain/.briefs/physics/optics.focal.acuity.md

@@ -0,0 +1,77 @@
+# .brief: focal.acuity
+
+## what
+
+**focal.acuity** refers to the **fineness of structure** that can be resolved **at the focal plane** — the geometric surface where optical focus is sharpest. It represents the **resolving power** of the system in the region of maximum clarity.
+
+---
+
+## why
+
+While **focal.depth** determines *how much* of the scene appears in focus, **focal.acuity** determines *how sharply* the focal plane itself is rendered.
+
+It is essential for:
+- Capturing fine textures and edge contrast
+- Supporting high-resolution imaging
+- Achieving clinical clarity in product, macro, and technical photography
+
+---
+
+## governed by
+
+### 🔬 Diffraction-limited resolution
+
+blur_diameter = d = 2.44 * λ * N
+=> focal.acuity ∝ 1 / d
+=> focal.acuity ∝ 1 / N
+
+```\`\`
+focal.acuity ∝ 1 / N
+\`\```
+
+where:
+- d = diffraction blur diameter
+- lambda = wavelength of light (e.g. 550 nm for green)
+- N = aperture (f-number)
+
+> focal.acuity **decreases** (detail coarsens) with:
+> - smaller aperture (larger f-number)
+> - longer wavelengths (e.g. redder light)
+
+---
+
+## key behaviors
+
+| Adjustment                   | Effect on focal.acuity        |
+|------------------------------|-------------------------------|
+| Larger aperture (↓ f-number) | increases it (sharper detail) |
+| Smaller aperture (↑ f-number)| decreases it (diffraction blur) |
+| Shorter wavelength           | increases it (sharper edges)  |
+| Better optics/sensor         | improves overall acuity       |
+
+---
+
+## creative usage
+
+- **High focal.acuity** (e.g. f/2.8–f/5.6):
+  - Yields crisp microtexture and high subject clarity
+  - Ideal for macro, studio, and product photography
+
+- **Reduced focal.acuity** (e.g. f/16–f/22):
+  - Acceptable in landscape or documentary work
+  - Used when prioritizing depth over precision
+
+---
+
+## limitations
+
+- **focal.acuity** is fundamentally limited by diffraction at small apertures
+- Increasing acuity reduces **focal.depth**, unless distance is increased
+- Post-processing cannot restore detail beyond optical resolution
+
+---
+
+## metaphorical phrasing
+
+> **focal.acuity** is how finely your lens can **etch the truth** onto the focal plane
+> It defines the **maximum clarity** achievable in the region of perfect focus

package/dist/logic/roles/bhrain/.briefs/physics/optics.focal.breadth.md

@@ -0,0 +1,74 @@
+# .brief: focal.breadth
+
+## what
+
+**focal.breadth** refers to the **field of view** (FoV) — the angular or spatial extent of the scene captured by the lens. It defines *how much* of the world is included in the frame, horizontally, vertically, and diagonally.
+
+The term "breadth" is used here as a conceptual synonym for FoV: a lens’s **focal.breadth** determines the spatial span visible at any moment of focus.
+
+---
+
+## why
+
+**focal.breadth** governs spatial inclusion:
+- Wide breadth = broader context, more environment, less magnification
+- Narrow breadth = tighter crop, more subject isolation, stronger compression
+
+This impacts:
+- **Composition and storytelling**
+- **Spatial relationships** (e.g. background flattening)
+- **Perceptual distance** between foreground and background elements
+
+---
+
+## governed by
+
+### 📐 Lens-to-sensor geometry
+
+\`\`\`
+focal.breadth ∝ k₁ / f
+\`\`\`
+
+Where:
+- `k₁` = `sensor_size` = physical diagonal of the camera sensor
+- `f` = `focal_length` = optical focal length of the lens
+
+> Shorter focal lengths → **wider breadth**
+> Longer focal lengths → **narrower breadth**
+
+---
+
+## key behaviors
+
+| Adjustment             | Effect on focal.breadth         |
+|------------------------|----------------------------------|
+| Decrease focal length  | expands breadth (wide angle)     |
+| Increase focal length  | narrows breadth (telephoto)      |
+| Crop sensor vs full-frame | reduces breadth (less of scene) |
+
+---
+
+## creative usage
+
+- **Wide focal.breadth** (e.g. 24mm):
+  - Landscape, architecture, immersive scenes
+  - Emphasizes environment over subject
+
+- **Narrow focal.breadth** (e.g. 85mm+):
+  - Portraits, wildlife, compressed compositions
+  - Emphasizes subject, de-emphasizes context
+
+---
+
+## limitations
+
+- Very wide breadths may introduce distortion at frame edges
+- Very narrow breadths reduce spatial awareness and require greater stability
+- Breadth must be balanced with focal.acuity and focal.depth to maintain clarity across the frame
+
+---
+
+## metaphorical phrasing
+
+> **focal.breadth** is your **window onto the world**
+> It defines *how wide the camera can see* — the lateral span of your visual attention.

package/dist/logic/roles/bhrain/.briefs/physics/optics.focal.depth.md

@@ -0,0 +1,77 @@
+# .brief: focal.depth
+
+## what
+
+**focal.depth** refers to the **range of object distances** in front of and behind the focal plane that appear **acceptably sharp**. It defines the "thickness" of the focus zone surrounding the point of perfect sharpness.
+
+---
+
+## why
+
+While **focal.acuity** describes *how sharply* the focal plane is rendered, **focal.depth** describes *how far that sharpness extends*. It's critical for:
+
+- Keeping entire subjects or scenes acceptably in focus
+- Managing viewer attention and spatial context
+- Balancing artistic isolation with technical clarity
+
+---
+
+## governed by
+
+### 📐 Depth of field (approximate)
+
+```\`\`
+focal.depth ≈ (2 * N * c * focal.distance²) / f²
+\`\```
+
+where
+- `N` = aperture (f-number)
+- `c` = circle of confusion (maximum acceptable blur)
+- `focal.distance` = subject distance (from lens to focal plane)
+- `f` = focal length, a fn of `focal.breadth`
+
+simplified
+- assume `c = d = 2.44 * λ * N`, a diffraction-limited system
+- deref `f ∝ k₁ / focal.breadth`, by definition
+
+```\`\`
+focal.depth ∝ N² × focal.distance² × focal.breadth²
+\`\```
+
+---
+
+## key behaviors
+
+| Adjustment                   | Effect on focal.depth         |
+|------------------------------|-------------------------------|
+| Smaller aperture (↑ f-number)| increases it (more in focus)  |
+| Larger aperture (↓ f-number) | decreases it (shallower zone) |
+| Farther focus distance       | increases it nonlinearly      |
+| Closer focus distance        | decreases it rapidly          |
+
+---
+
+## creative usage
+
+- **Shallow focal.depth** (e.g. f/1.4):
+  - Isolates subject from background
+  - Ideal for portraits and cinematic shots
+
+- **Deep focal.depth** (e.g. f/16):
+  - Maintains clarity across space
+  - Used in landscapes, architecture, documentation
+
+---
+
+## limitations
+
+- Increasing focal.depth via smaller apertures introduces **diffraction**, reducing **focal.acuity**
+- Getting more depth often requires stepping farther away
+- Focal.depth depends on the lens, aperture, and subject distance — not just focus point
+
+---
+
+## metaphorical phrasing
+
+> **focal.depth** is the **breadth** of your clarity
+> It defines how far sharpness can **reach** across space, extending from the focal plane outward

package/dist/logic/roles/bhrain/.briefs/physics/optics.focal.distance.md

@@ -0,0 +1,92 @@
+# .brief: focal.distance
+
+## what
+
+**focal.distance** refers to the **distance from the lens to the focal plane** — the exact location in space where the subject is brought into geometric focus.
+
+---
+
+## why
+
+While **focal.acuity** defines *how finely* the focal plane is rendered, and **focal.depth** defines *how far* sharpness extends around it, **focal.distance** defines *where* that clarity is placed in the scene.
+
+It controls:
+- Subject framing and spatial scale
+- The perceived compression of background and foreground
+- The sensitivity of focus and blur relationships in space
+
+---
+
+## governed by
+
+### 📐 Thin lens equation
+
+```\`\`
+1/f = 1/focal.distance + 1/image_distance
+\`\```
+
+This determines **where** the focal plane sits for a given lens.
+
+---
+
+### 🔧 How aperture interacts — via depth of field
+
+The **relationship between aperture and focal.distance** emerges through the depth of field equation:
+
+```\`\`
+focal.depth ≈ (2 * N * c * focal.distance²) / f²
+\`\```
+
+where
+- `N` = aperture (f-number)
+- `c` = circle of confusion (maximum acceptable blur)
+- `focal.distance` = subject distance (from lens to focal plane)
+- `f` = focal length, a fn of `focal.breadth`
+
+simplified
+- assume `c = d = 2.44 * λ * N`, a diffraction-limited system
+- deref `f ∝ k₁ / focal.breadth`, by definition
+
+```\`\`
+focal.depth ∝ N² × focal.distance² × focal.breadth²
+\`\```
+
+---
+
+## key behaviors
+
+| Adjustment               | Effect on focal.distance           |
+|--------------------------|------------------------------------|
+| Physically moving closer | decreases it                       |
+| Stepping farther back    | increases it                       |
+| Using wider aperture     | makes the system more sensitive to small changes in focal.distance |
+| Using smaller aperture   | tolerates more deviation from exact distance |
+
+---
+
+## creative usage
+
+- **Close focal.distance**:
+  - Emphasizes subject
+  - Increases blur and isolation
+  - Requires precision
+
+- **Far focal.distance**:
+  - Expands depth
+  - Stabilizes scene-wide focus
+  - Suits landscapes, architecture, and static subjects
+
+---
+
+## limitations
+
+- Very close distances drastically reduce focal.depth
+- Large apertures require extremely accurate focusing at short distances
+- Focal.distance interacts with both lens choice and aperture behavior
+
+---
+
+## metaphorical phrasing
+
+> **focal.distance** is your **placement of intent** — it marks where clarity lands.
+> The closer it lies, the tighter your tolerance must be; the farther it stretches, the more generous the depth becomes.

package/dist/logic/roles/bhrain/.briefs/physics/optics.focal.tradeoffs.md

@@ -0,0 +1,107 @@
+# .brief: focal.tradeoffs
+
+## what
+
+**focal.tradeoffs** describe the physical constraint that links:
+
+- **focal.acuity** — the fineness of detail resolvable **at the focal plane**
+- **focal.breadth** — the angular or spatial extent of the field of view (FoV)
+- **focal.distance** — the distance **from the lens to the focal plane**
+- **focal.depth** — the range of distances **around the focal plane** that remain acceptably sharp
+
+These four factors are coupled by the geometry of light: changing one requires compensating adjustments to at least one of the others. The relationship models the inescapable tradeoffs in all optical focus systems.
+
+---
+
+## equation
+
+Assuming constant sensor size and fixed circle of confusion:
+
+\`\`\`ts
+// given
+focal.depth ∝ N² × focal.distance² × focal.breadth²
+focal.acuity ∝ 1 / N
+
+// then
+N ∝ 1 / focal.acuity
+focal.depth ∝ (1 / focal.acuity)² × focal.distance² × focal.breadth²
+focal.depth ∝ focal.distance² × focal.breadth² / focal.acuity²
+
+// therefore
+focal.acuity² × focal.depth ∝ focal.distance² × focal.breadth²
+\`\`\`
+
+---
+
+## key relationship
+
+\`\`\`
+focal.acuity² × focal.depth ∝ focal.distance² × focal.breadth²
+\`\`\`
+
+> You can only maximize two at a time — the other two must yield.
+
+---
+
+## variable meanings
+
+- **focal.acuity** — how finely your lens resolves detail at the point of focus
+- **focal.breadth** — how wide your frame sees (field of view)
+- **focal.depth** — how far the focus zone stretches through space
+- **focal.distance** — how close or far the focal plane is set
+
+---
+
+## tradeoff matrix
+
+| Want to increase…     | Compensate by…                                   |
+|------------------------|--------------------------------------------------|
+| **focal.acuity** ↑     | decrease depth ↓, step back ↑, narrow breadth ↓ |
+| **focal.breadth** ↑    | reduce acuity ↓, step back ↑, flatten depth ↓   |
+| **focal.depth** ↑      | reduce acuity ↓, step back ↑, compress breadth ↓|
+| **focal.distance** ↓   | reduce depth ↓, increase acuity ↑, narrow breadth ↓ |
+
+---
+
+## verbal examples
+
+- want **finer details**? (focal.acuity++)
+- then, either
+  - step back (focal.distance++)
+  - collapse depth (focal.depth--)
+  - crop field of view (focal.breadth--)
+
+- want a **wider scene**? (focal.breadth++)
+- then, either
+  - reduce acuity (focal.acuity--)
+  - step back (focal.distance++)
+  - tolerate shallow depth (focal.depth--)
+
+- want **deeper focus**? (focal.depth++)
+- then, either
+  - reduce acuity (focal.acuity--)
+  - step back (focal.distance++)
+  - narrow scene (focal.breadth--)
+
+- want to get **closer**? (focal.distance--)
+- then, either
+  - reduce depth (focal.depth--)
+  - increase sharpness (focal.acuity++)
+  - narrow scene (focal.breadth--)
+
+---
+
+## best practice zone
+
+For full-frame photography:
+
+- Aperture: f/5.6 to f/8
+- Distance: 2–5 meters
+- Focal length: 35mm–85mm (moderate breadth)
+
+This keeps the optical balance manageable:
+
+- **focal.acuity**: avoids diffraction or aberration
+- **focal.breadth**: flexible for framing
+- **focal.depth**: useful for subject layering
+- **focal.distance**: compositional stability

package/dist/logic/roles/bhrain/.briefs/terms.motive.intent.goal.md

@@ -0,0 +1,46 @@
+🔥 [motive] — an internal pressure or desire
+.what = the underlying reason the actor wants anything at all
+
+.form = emotional, value-driven, often implicit
+
+.examples:
+[motive] = avoid failure
+[motive] = gain respect
+[motive] = feel in control
+
+---
+
+🎯 [intent] — a chosen next action
+.what = a specific thing the actor plans to do next
+
+.form = short-term, actionable, verb-shaped
+
+.examples:
+[intent] = schedule a call
+[intent] = submit proposal
+[intent] = clean the garage
+
+---
+
+🥅 [goal] — a desired future state
+.what = a future outcome the actor wants to reach
+
+.form = long-term, state-shaped, noun/condition
+
+.examples:
+[goal] = get more customers
+[goal] = have a clean house
+[goal] = win the bid
+
+---
+
+🧠 mental model
+[motive] = source of pressure
+[goal] = destination
+[intent] = chosen step toward it
+
+- `[motive]` fuels the journey
+- `[goal]` gives it direction
+- `[intent]` initiates motion
+
+> every `[intent]` serves a `[goal]`, and every `[goal]` is backed by a `[motive]` — but these are not always visible on the surface.