rhachet-roles-ehmpathy 1.0.0 → 1.2.0

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>._.[article].frame.colloquial.i2.by_grok.md

@@ -0,0 +1,64 @@
+# 🧩 .brief.article: `demonstrate`
+
+## .what
+**demonstrate** refers to the act of clearly showing or explaining a concept’s essence, structure, or functionality through a tangible instance, often producing a `.brief.demo` artifact to make abstract or complex ideas accessible. In the context of `.brief.demo`, it involves instantiating a concept in a structured Markdown format to reveal its interconnected components, like a tree-like hierarchy, for clear understanding.
+
+---
+
+## 🎯 purpose
+- **clarify** the concept’s core traits, structure, or application by presenting a concrete instance.
+- **showcase** how the concept functions through a specific, relatable example in a `.brief.demo`.
+- **educate** audiences by organizing the concept’s elements into a clear, hierarchical structure.
+- **persuade** readers of the concept’s value by demonstrating its practical or theoretical significance.
+
+---
+
+## 📏 methods of demonstration
+1. **Instantiation in .brief.demo**
+   - Present a concept through a specific instance (e.g., a use case template, a physical scenario) within a `.brief.demo` artifact.
+   - Effective for making abstract or technical concepts tangible, like quantum entanglement via a Bell test.
+
+2. **Structured Explanation**
+   - Use a detailed outline in the `.brief.demo` to explain how the instance embodies the concept’s traits.
+   - Suitable for breaking down complex ideas into clear, interconnected components.
+
+3. **Example-Driven Presentation**
+   - Highlight a single, relatable example to anchor the demonstration, ensuring accessibility.
+   - Ideal for engaging diverse audiences, from novices to experts, with familiar instances.
+
+4. **Hierarchical Organization**
+   - Arrange the demonstration to reflect the concept’s tree-like structure, connecting its elements logically.
+   - Helps reveal the concept’s internal relationships, like branches in a tree, for deeper understanding.
+
+---
+
+## 🔄 when to use
+- When introducing a new concept, such as a technical term or abstract idea, to make it concrete.
+- During educational efforts to clarify complex topics through structured `.brief.demo` artifacts.
+- To communicate system requirements or functionalities, as in software development use cases.
+- When explaining updates or innovations to stakeholders, using clear, instantiated examples.
+
+---
+
+## 📐 examples
+- **Software Development**: Demonstrating a “use case” by presenting a `.brief.demo` for “Booking a Flight on a Travel Website,” using a structured template to show user-system interactions.
+- **Physics Education**: Demonstrating “shear force” with a `.brief.demo` for “Scissors Cutting Paper,” highlighting parallel forces and material deformation.
+- **Cultural Studies**: Demonstrating “tea” via a `.brief.demo` on “Darjeeling Tea,” detailing its production and cultural role.
+- **Scientific Research**: Demonstrating “quantum entanglement” through a `.brief.demo` on a Bell test experiment, showing non-local correlations.
+
+---
+
+## 📚 benefits
+- Enhances understanding by grounding abstract concepts in tangible, relatable instances.
+- Builds credibility through structured, clear `.brief.demo` artifacts that showcase expertise.
+- Encourages engagement by using familiar examples to connect with diverse audiences.
+- Facilitates exploration of a concept’s tree-like structure, revealing its interconnected components.
+
+---
+
+## ⚠️ potential pitfalls
+- Choosing an overly complex instance that obscures the concept instead of clarifying it.
+- Failing to tailor the `.brief.demo` structure to the concept’s nature, reducing its effectiveness.
+- Overloading the artifact with excessive detail, leading to confusion or disengagement.
+
+> A well-executed demonstration via a `.brief.demo` transforms abstract concepts into clear, structured, and engaging insights, bridging theory and application through instantiation.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.[catalog].md

@@ -0,0 +1,106 @@
+# .brief.catalog: `demonstrate variants`
+
+
+\`\`\`
+concept demonstration (demo, genus)
+│
+├── instance
+│   ├── example
+│   │   ↳ question: "what counts as it?"
+│   │   ↳ example: "downtown portland is highly walkable —
+│   │              groceries, schools, and cafes within 10 minutes."
+│   │
+│   ├── counter
+│   │   ↳ question: "what is it not?"
+│   │   ↳ example: "los angeles suburbs where every errand
+│   │              requires a car — this is not walkability."
+│   │
+│   ├── contrast
+│   │   ↳ question: "how is this different from that?"
+│   │   ↳ example: "compare downtown portland (walkable) to
+│   │              houston sprawl (car-dependent)."
+│   │
+│   └── gradation
+│       ↳ question: "how does it vary along a spectrum?"
+│       ↳ example: "low → medium → high walkability across three block patterns."
+│
+├── medium
+│   ├── visual
+│   │   ↳ question: "what does it look like?"
+│   │   ↳ example: "map sketch with a house at the center,
+│   │              icons for grocery, school, café,
+│   │              all within a shaded 10-minute radius."
+│   │
+│   └── emotional
+│       ↳ question: "what does it feel like?"
+│       ↳ example: "the calm of strolling to a café vs the stress of sitting in traffic."
+│
+├── transfer
+│   ├── analogy
+│   │   ↳ question: "what is it like, in structure?"
+│   │   ↳ example: "walkability is like a circulatory system:
+│   │              sidewalks are arteries, intersections are valves,
+│   │              parks are lungs, stores are nutrients."
+│   │
+│   ├── metaphor
+│   │   ↳ question: "what is it, figuratively?"
+│   │   ↳ example: "walkability is oxygen for a city."
+│   │
+│   ├── simile
+│   │   ↳ question: "what is it like, figuratively?"
+│   │   ↳ example: "a walkable neighborhood feels like a living room —
+│   │              everything close, familiar, and reachable."
+│   │
+│   └── allegory
+│       ↳ question: "what story-world can stand in for it?"
+│       ↳ example: "a city without walkability is a kingdom without paths:
+│                  villages isolated, markets starved, citizens trapped.
+│                  when paths connect, culture and trade flow."
+│
+├── sequence
+│   ├── walkthrough
+│   │   ↳ question: "how does it proceed?"
+│   │   ↳ example: "walk from this apartment to the grocery store,
+│   │              noting the sidewalks, crosswalks, and distances."
+│   │
+│   ├── narrative
+│   │   ↳ question: "how does it unfold as lived experience?"
+│   │   ↳ example: "maria leaves her home, strolling past the bakery smells,
+│   │              greeting a neighbor, and reaching the grocery in five minutes."
+│   │
+│   ├── causal
+│   │   ↳ question: "how do inputs lead to outcomes?"
+│   │   ↳ example: "short blocks → more walking → health + economy + climate gains."
+│   │
+│   └── temporal
+│       ↳ question: "how does it change across time?"
+│       ↳ example: "1950 streetcar suburb → 1980 arterial strip → 2025 main street retrofit."
+│
+└── model
+    ├── simulation
+    │   ↳ question: "how would it behave if modeled?"
+    │   ↳ example: "urban planning software shows how
+    │              adding sidewalks shifts daily trips from cars to walking."
+    │
+    ├── prototype
+    │   ↳ question: "what form could it take?"
+    │   ↳ example: "build a model block with wide sidewalks,
+    │              corner cafés, and bike racks to embody walkability."
+    │
+    └── factorization
+        ↳ question: "what are its components?"
+        ↳ example: "proximity, safety, comfort, interest, connectivity as factors of walkability."
+\`\`\`
+
+
+---
+
+## 🎯 notes
+- **five clusters** organize the space of concept-demos:
+  1. **instance** → cases & boundaries
+  2. **medium** → change of representation
+  3. **transfer** → meaning carried across concepts
+  4. **sequence** → unfolding over time
+  5. **model** → embodiment in models/artifacts
+
+- each subtype has a **walkability demo** attached for clarity.

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

@@ -0,0 +1,45 @@
+# .brief.demo: `use case` via `contrast` = `use case vs user journey`
+
+## 💡 concept
+a use case describes how a user interacts with a system to achieve a specific goal, while a user journey maps the broader, often emotional, experience of a user across multiple touchpoints with a product or service.
+
+## ❓ question
+> how does a use case contrast with a user journey?
+
+## 📌 contrast: use case vs user journey
+
+### 📌.📖 what
+
+> what are use cases and user journeys?
+
+- **use case**
+  - focuses on *functional interaction* between user and system.
+  - defines *actors, steps, and system responses* leading to a specific outcome.
+  - *example:* “a customer books a flight on an airline’s website.”
+
+- **user journey**
+  - focuses on *holistic experience* across touchpoints.
+  - includes *motivations, emotions, and pain points* before, during, and after interaction.
+  - *example:* “a traveler researches destinations, compares prices, books a flight, receives updates, travels, and later reviews the airline.”
+
+### 📌.🔍 how
+
+> how does this contrast demonstrate the concept of use case?
+
+- **scope**
+  - a use case is **narrow**, zooming into a single functional interaction.
+  - a user journey is **broad**, mapping multiple interactions across a timeline.
+
+- **focus**
+  - a use case emphasizes **system behavior**: “what happens when the user does X?”
+  - a user journey emphasizes **user experience**: “how does the user feel at each stage?”
+
+- **artifact**
+  - use case outputs are structured step-by-step flows of user + system actions.
+  - user journey outputs are visual maps, storyboards, or timelines showing phases and emotions.
+
+- **example contrast**
+  - **use case:** “customer selects flight → enters details → system confirms booking.”
+  - **user journey:** “customer dreams of vacation → compares airlines → struggles with hidden fees → books → feels reassured by confirmation → experiences anxiety waiting for boarding.”
+
+this contrast clarifies that a **use case is about functionality**, while a **user journey is about experience**. together, they complement each other, but they are not the same.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.counter.[demo].usecase.flyer.by_chargpt.md

@@ -0,0 +1,38 @@
+# .brief.demo: `usecase` via `counter` = `restaurant menu flyer`
+
+## 💡 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 counter-example of a use case?
+
+## 📌 counter-example: restaurant menu flyer
+
+### 📌.📖 what
+
+> what is the restaurant menu flyer?
+
+a printed restaurant menu flyer is a static list of food items and prices distributed for advertising purposes. it provides information but does not describe any user interactions, system responses, or step-by-step goals.
+
+- **static content**
+  - lists meals, prices, and phone number
+  - *example:* a pizza shop flyer with daily specials
+- **no interactive process**
+  - customer may see the flyer, but the flyer itself does not facilitate ordering
+- **no system responses**
+  - the flyer cannot process actions or provide feedback
+- **actors missing**
+  - does not define the roles of customer, staff, or delivery process
+
+### 📌.🔍 how
+
+> how is a restaurant menu flyer a counter-example of a use case?
+
+the menu flyer illustrates what a use case is *not*, because it lacks:
+
+- **interaction**: there is no dynamic exchange between user and system—only one-way information.
+- **steps**: no sequence of actions leading to a goal is described.
+- **actors and responses**: the flyer does not specify participants or their roles, nor does it capture how a system responds to user input.
+- **goal structure**: while the flyer hints at a potential outcome (ordering food), it does not map the process of achieving that outcome.
+
+this counter-example shows that a use case requires **structured interaction** and **defined roles**, not just information or content.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.counter.[demo].walkability.phoenix.by_chargpt.md

@@ -0,0 +1,41 @@
+# .brief.demo: `walkability` via `counter` = `phoenix suburbs`
+
+## 💡 concept
+walkability is the measure of how friendly an area is to walking, determined by the proximity of daily needs, the quality of pedestrian infrastructure, and the safety and comfort of the walking environment.
+
+## ❓ question
+> what is a counter-example of walkability?
+
+## 📌 counter-example: phoenix suburbs
+
+### 📌.📖 what
+
+> what are the phoenix suburbs?
+
+the sprawling suburbs around phoenix, arizona, are characterized by low-density housing, wide arterial roads, and zoning that separates residential areas from commercial and institutional uses. daily needs are typically spread out across miles, accessible primarily by car.
+
+- **long distances to daily needs**
+  - grocery stores, schools, and cafes located far from most homes
+    - *example:* a typical subdivision may require a 15–20 minute drive to reach basic shopping
+- **disconnected infrastructure**
+  - large blocks, wide intersections, and missing sidewalks
+    - *example:* six-lane arterial roads without pedestrian crossings for half a mile
+- **unsafe crossings**
+  - intersections designed for vehicle throughput, not pedestrians
+    - *example:* high-speed right-turn lanes with no pedestrian refuge
+- **weak transit integration**
+  - bus routes are sparse and stops often lack safe walking access
+    - *example:* bus stops located on roads without sidewalks or shelters
+
+### 📌.🔍 how
+
+> how is the phoenix suburban pattern a counter-example of walkability?
+
+phoenix suburbs highlight the absence of walkability through **distance**, **design**, and **dependence**:
+
+- **distance**: residential and commercial areas are so spread out that walking is impractical for daily errands.
+- **design**: streets prioritize car speed and capacity, making walking unpleasant and often dangerous.
+- **dependence**: car ownership becomes a necessity, as walking and transit provide no viable alternative.
+- **comfort and safety**: the harsh desert climate, combined with limited shade and long stretches without sidewalks, further discourages walking.
+
+this counter-example shows that when urban planning prioritizes cars over people, walkability disappears—underscoring why compact, mixed-use, and pedestrian-first design is essential for creating walkable places.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.example.[demo].shear_force.scissors.by_grok.md

@@ -0,0 +1,52 @@
+# 🧩 .brief.demo: `mechanical shear force` via `example` = `scissors`
+
+## 💡 Concept
+
+Mechanical shear force is a type of force that acts parallel to a material’s surface, causing one portion to slide past another, often leading to cutting, deformation, or fracture of the material.
+
+## ❓ Question
+
+> What is an example of mechanical shear force?
+
+## 📌 Example: Scissors Cutting Paper
+
+### 📌.📖 What
+
+> What is scissors cutting paper?
+
+Scissors cutting paper is a common action where two sharp blades slide past each other to slice through a sheet of paper, applying a mechanical force that separates the material. This everyday process, used in households and offices, relies on the precise interaction of blades to achieve a clean cut.
+
+- **Historical Context**
+  - **Invention of Scissors**: Originated around 1500 BCE in ancient Egypt, with modern pivoted scissors refined in the 18th century for precision tasks.
+  - **Evolution of Design**: Advanced from simple metal blades to ergonomic handles and specialized types, like crafting or industrial scissors.
+- **Physical Components**
+  - **Blade Structure**: Consists of two sharp, metal blades pivoted at a central point, allowing them to slide against each other.
+  - **Handle Mechanism**: Ergonomic handles enable the user to apply force, controlling the blades’ movement and pressure.
+  - **Material Interaction**: The blades contact the paper at a small, localized area, focusing the applied force for effective cutting.
+- **Common Applications**
+  - **Household Use**: Employed for tasks like cutting paper for crafts, wrapping, or office work, accessible to all ages.
+  - **Industrial Variants**: Used in larger forms, like shears, for cutting tougher materials in manufacturing or textiles.
+  - **Educational Role**: Taught in schools for art projects, demonstrating basic mechanical principles in action.
+
+### 📌.🔍 How
+
+> How is it an example of mechanical shear force?
+
+Scissors cutting paper exemplifies mechanical shear force by applying parallel forces through sliding blades to sever the paper, demonstrating the concept’s role in material deformation and separation. The process highlights shear force’s characteristics of localized stress, sliding motion, and structural impact in a practical, observable way.
+
+- **Application of Parallel Forces**
+  - **Blade Sliding**: The blades move parallel to each other, exerting opposing forces on the paper’s surface, creating shear stress.
+  - **Localized Contact**: The force concentrates at the point where the blades meet, maximizing shear effect on a small area.
+  - **Force Transmission**: User pressure on the handles transfers directly to the blades, amplifying the shear force applied.
+- **Material Deformation**
+  - **Paper Shearing**: The paper’s fibers are pushed apart as the blades slide, causing the material to split cleanly.
+  - **No Compression**: Unlike crushing, the blades’ action avoids compressing the paper, focusing solely on shear-induced separation.
+  - **Clean Cut**: The result is a smooth edge, showing shear force’s ability to precisely fracture materials.
+- **Mechanical Advantage**
+  - **Lever Action**: The pivot acts as a fulcrum, multiplying the user’s hand force into greater shear force at the blades.
+  - **Blade Angle**: The sharp, angled edges reduce the contact area, increasing shear stress for efficient cutting.
+  - **Design Efficiency**: Ergonomic scissors optimize force transfer, making shear force application intuitive and effective.
+- **Observable Outcomes**
+  - **Visible Separation**: The paper splits visibly as the blades close, directly illustrating shear force’s cutting effect.
+  - **Material Response**: Thin materials like paper yield easily, while thicker ones resist, showing shear force’s dependence on material strength.
+  - **Practical Impact**: The clean cut enables precise tasks, connecting shear force to everyday utility and engineering principles.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.example.[demo].tea.darjeeling.by_grok.md

@@ -0,0 +1,50 @@
+# 🧩 .brief.demo: `tea` via `example` = `darjeeling`
+
+## 💡 Concept
+
+Tea is a beverage made by steeping processed leaves, buds, or twigs of the Camellia sinensis plant in hot water, valued for its diverse flavors, cultural significance, and health benefits.
+
+## ❓ Question
+
+> What is an example of tea?
+
+## 📌 Example: Darjeeling Tea
+
+### 📌.📖 What
+
+> What is Darjeeling tea?
+
+Darjeeling tea is a premium black tea grown in the Darjeeling region of West Bengal, India, renowned for its delicate, muscatel flavor and floral aroma. Often called the “Champagne of teas,” it’s cultivated in high-altitude estates and celebrated for its unique terroir-driven qualities.
+
+- **Historical Context**
+  - **Origins in India**: Introduced in the 19th century by British colonial planters, inspired by Chinese tea cultivation techniques.
+  - **Global Recognition**: Gained international fame for its distinct taste, earning a Geographical Indication (GI) status to protect its authenticity.
+- **Production Characteristics**
+  - **High-Altitude Cultivation**: Grown at elevations of 2,000–7,000 feet in the Himalayan foothills, contributing to its unique flavor profile.
+  - **Seasonal Flushes**: Harvested in distinct seasons (first flush in spring, second flush in summer), each offering different taste notes, from light and floral to robust and fruity.
+- **Cultural Significance**
+  - **Local Tradition**: A cornerstone of Darjeeling’s economy and culture, with tea estates employing thousands and shaping regional identity.
+  - **Global Appeal**: Prized by tea connoisseurs worldwide, often served in high-end tea houses and ceremonies.
+
+### 📌.🔍 How
+
+> How is it an example of tea?
+
+Darjeeling tea exemplifies the concept of tea through its meticulous cultivation and processing from Camellia sinensis, its diverse flavor profiles, and its deep cultural and health-related significance. Its global reputation and versatility in preparation highlight the essence of tea as a beverage and cultural staple.
+
+- **Camellia Sinensis Base**
+  - **Plant Source**: Made from the leaves of the Camellia sinensis plant, aligning with the core definition of true tea.
+  - **Processing Techniques**: Undergoes withering, rolling, oxidation, and drying, typical of black tea production, to develop its signature flavor.
+  - **Varietal Specificity**: Uses the Chinese varietal of Camellia sinensis, adapted to Darjeeling’s unique climate and soil.
+- **Flavor and Aroma Diversity**
+  - **Muscatel Notes**: Known for a distinctive grape-like flavor, especially in second flush teas, showcasing tea’s range of taste profiles.
+  - **Floral Undertones**: First flush teas offer light, floral aromas, appealing to those seeking delicate tea experiences.
+  - **Seasonal Variation**: Different harvests (flushes) provide varied flavors, illustrating tea’s versatility within a single origin.
+- **Cultural Role**
+  - **Social Rituals**: Consumed in afternoon tea settings globally, from British high tea to casual sipping in India, reflecting tea’s social importance.
+  - **Economic Impact**: Supports Darjeeling’s tea estates, employing local communities and reinforcing tea’s role in cultural heritage.
+  - **Ceremonial Use**: Featured in tea tastings and pairings, highlighting tea’s place in refined cultural practices.
+- **Health and Wellness Benefits**
+  - **Antioxidant Properties**: Contains polyphenols, linked to reducing oxidative stress and supporting heart health.
+  - **Caffeine Content**: Provides a mild stimulant effect, offering an energy boost without coffee’s intensity.
+  - **Mental Clarity**: L-theanine promotes relaxation and focus, exemplifying tea’s calming yet invigorating qualities.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.example.[demo].usecase.book_flight.by_grok.md

@@ -0,0 +1,54 @@
+# 🧩 .brief.demo: `use case` via `example` = `booking flight`
+
+## 💡 Concept
+
+A use case describes how a user interacts with a system to achieve a specific goal, detailing actors, steps, and system responses to define functional requirements in software development.
+
+## ❓ Question
+
+> What is an example of a use case?
+
+## 📌 Example: Booking a Flight on a Travel Website
+
+### 📌.📖 What
+
+> What is the use case "booking a flight on a travel website"?
+
+The use case "booking a flight on a travel website" is a structured description of how a traveler uses an online platform like Expedia or Kayak to purchase an airline ticket.
+
+- **Actor**: Traveler (the user seeking to book a flight).
+- **Goal**: To purchase an airline ticket for a chosen destination and date.
+- **Preconditions**: The user has access to the travel website via a web browser or mobile app and a valid payment method.
+- **Main Flow**:
+  1. **User**: Navigates to the website’s homepage and enters departure city, destination, travel dates, and passenger details, then clicks “Search.”
+  2. **System**: Displays a list of available flights with details (airlines, times, prices).
+  3. **User**: Selects a preferred flight and optional extras (e.g., seat selection, baggage).
+  4. **System**: Prompts for passenger details (name, contact info) and payment information.
+  5. **User**: Enters payment details and confirms the booking.
+  6. **System**: Processes payment, books the ticket, and sends a confirmation email with the ticket.
+- **Exceptions**:
+  - **No Flights Available**: If no flights match the criteria, the system displays an error and suggests alternative dates or destinations.
+  - **Payment Failure**: If payment fails, the system notifies the user and prompts re-entry or an alternative payment method.
+
+### 📌.🔍 How
+
+> How is it an example of a use case?
+
+The use case "booking a flight on a travel website" exemplifies a use case by providing a structured description of a traveler’s interaction with a system to achieve a specific goal, capturing user actions, system responses, and edge cases. It serves as a clear blueprint for developers, illustrating how use cases define functional requirements and ensure user-centric system design.
+
+- **Defined Actor and Goal**
+  - **Traveler as Actor**: Specifies the user (traveler) as the primary actor, aligning with the use case’s focus on who interacts with the system.
+  - **Clear Objective**: The goal of purchasing a ticket drives the interaction, a core element of any use case.
+  - **System Role**: The travel website facilitates the goal, acting as the system under consideration.
+- **Structured Interaction Flow**
+  - **Sequential Steps**: Details a clear sequence (search, select, pay), mirroring the step-by-step flow typical of use case descriptions.
+  - **User-System Dialogue**: Alternates between user actions (e.g., entering details) and system responses (e.g., displaying flights), reflecting use case dynamics.
+  - **Preconditions Included**: Specifies requirements like internet access and payment method, setting the stage for the interaction.
+- **Exception Handling**
+  - **Error Scenarios**: Addresses cases like no flights or payment failure, showing how use cases account for alternate paths.
+  - **User Guidance**: System responses (e.g., error messages, prompts) ensure users can navigate issues, a key use case feature.
+  - **Robustness**: Captures edge cases, ensuring the system is designed to handle real-world challenges.
+- **Requirements Specification**
+  - **Functional Needs**: Outlines needs like search functionality and payment processing, guiding developers on system features.
+  - **Security Focus**: Highlights secure payment handling, a critical requirement derived from the use case.
+  - **Stakeholder Clarity**: Provides a clear reference for developers, testers, and designers to align on user needs and system behavior.

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

@@ -0,0 +1,40 @@
+# .brief.demo: `use case` via `example` = `online food delivery`
+
+## 💡 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 an example of a use case?
+
+## 📌 example: online food delivery
+
+### 📌.📖 what
+
+> what is the online food delivery use case?
+
+the online food delivery use case outlines how a customer orders food through a delivery platform (like doordash or uber eats), and how the system responds at each stage to fulfill the request. it represents a common digital interaction where multiple actors (customer, restaurant, courier, system) collaborate to achieve the user’s goal: receiving a meal at home.
+
+- **actors involved**
+  - customer places an order
+  - restaurant receives and prepares food
+  - courier picks up and delivers the order
+  - system coordinates communication and payments
+- **goal**
+  - customer receives desired food at their location in a timely manner
+- **context**
+  - mobile app or website interface, integrated with payment and logistics
+
+### 📌.🔍 how
+
+> how is online food delivery an example of a use case?
+
+it demonstrates a use case by showing the **sequence of interactions**:
+
+1. **customer action**: browses menu, selects food, and confirms order.
+2. **system response**: sends order details to the restaurant, processes payment, provides confirmation to customer.
+3. **restaurant action**: prepares the food and marks it ready.
+4. **system response**: dispatches courier notification and tracks delivery.
+5. **courier action**: picks up order and delivers to customer’s address.
+6. **system response**: updates tracking, confirms delivery, and collects feedback.
+
+this example embodies the concept of a use case by mapping out actors, steps, and goals in a structured way, showing how user intent translates into system-supported outcomes.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.example.[demo].walkability.portland.by_chatgpt.i3.md

@@ -0,0 +1,42 @@
+# .brief.demo: `walkability` via `example` = `downtown portland`
+
+## 💡 concept
+walkability is the measure of how friendly an area is to walking, determined by the proximity of daily needs, the quality of pedestrian infrastructure, and the safety and comfort of the walking environment.
+
+## ❓ question
+> what is an example of walkability?
+
+## 📌 example: downtown portland
+
+### 📌.📖 what
+
+> what is downtown portland?
+
+downtown portland is a central neighborhood in portland, oregon, known for its compact urban grid, accessible public transit, and pedestrian-friendly design. the area integrates commercial, residential, and cultural spaces within short walking distances.
+
+- **daily needs within reach**
+  - groceries, cafes, and schools located within 5–10 minutes by foot
+    - *example:* whole foods and local corner markets
+    - *example:* elementary schools and daycare facilities
+- **continuous walking network**
+  - sidewalks, curb ramps, and bike lanes that form a safe, connected grid
+    - *example:* protected bike lanes on broadway
+- **pedestrian-priority crossings**
+  - crosswalks, countdown signals, and curb extensions
+    - *example:* marked intersections with pedestrian-first light cycles
+- **transit integration**
+  - max light rail, bus, and streetcar stops accessible directly from sidewalks
+    - *example:* pioneer courthouse square transit hub
+
+### 📌.🔍 how
+
+> how is downtown portland an example of walkability?
+
+downtown portland exemplifies walkability because it combines **proximity**, **infrastructure**, and **integration**:
+
+- **proximity**: mixed-use zoning keeps housing, workplaces, shops, and cultural venues close together, reducing reliance on cars.
+- **infrastructure**: the city grid ensures short blocks, frequent intersections, and pedestrian-scale street design that prioritize people on foot.
+- **integration**: public transit connects seamlessly with sidewalks, allowing trips to extend beyond walking range without breaking the pedestrian experience.
+- **safety and comfort**: traffic calming, green streets, and shaded sidewalks create a walking environment that is both secure and inviting.
+
+together, these factors transform downtown portland into a living demonstration of how urban design can encourage walking as the default mode of daily life.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.example.[demo].walkability.portland.by_grok.i2.md

@@ -0,0 +1,49 @@
+# 🧩 .brief.demo: `walkability` via `example` = `portland`
+
+## 💡 Concept
+
+Walkability refers to how friendly an area is to walking, characterized by safe, accessible, and pleasant environments that encourage pedestrian activity, reduce car dependency, and promote community interaction.
+
+## ❓ Question
+*What is an example of walkability?*
+
+## 📌 Example: Portland’s Pearl District
+
+### 📌.📖 What
+
+What is Portland’s Pearl District?
+
+The Pearl District is a vibrant, urban neighborhood in Portland, Oregon, known for its transformation from an industrial area into a cultural hub with art galleries, lofts, and lively public spaces. Once home to warehouses and rail yards, it’s now a model of modern urban living with a focus on community and accessibility.
+
+- **Historical Context**
+  - **Industrial Origins**: Began as a late 19th-century warehouse and rail yard district, redeveloped in the 1990s into a residential and commercial area.
+  - **Urban Renewal**: Old industrial buildings were converted into lofts, galleries, and shops, revitalizing the area into a bustling neighborhood.
+- **Neighborhood Character**
+  - **Cultural Hub**: Features prominent art galleries, boutique shops, and restaurants, drawing artists, residents, and tourists.
+  - **Modern Design**: Combines historic brick buildings with sleek, contemporary architecture in a compact grid layout.
+- **Community Features**
+  - **Public Parks**: Includes Jamison Square and Tanner Springs Park, offering green spaces for recreation and community events.
+  - **Diverse Housing**: Provides high-rise condos, converted lofts, and some affordable housing, fostering a varied resident base.
+
+### 📌.🔍 How
+
+How is it an example of walkability?
+
+The Pearl District exemplifies walkability through its compact, mixed-use design, robust pedestrian infrastructure, and vibrant community spaces that make walking safe, convenient, and enjoyable. Its integration with transit and focus on sustainability further enhance its pedestrian-friendly environment.
+
+- **Mixed-Use Accessibility**
+  - **Proximity of Amenities**: Shops, cafes, galleries, and offices are within a 10–15 minute walk, enabling car-free daily routines.
+  - **Street-Level Engagement**: Ground-floor businesses with outdoor seating create lively, walkable destinations.
+  - **Compact Layout**: Short blocks and a grid pattern minimize walking distances, encouraging pedestrian travel.
+- **Pedestrian-Friendly Infrastructure**
+  - **Safe Sidewalks**: Wide, ADA-compliant sidewalks and frequent crosswalks with countdown timers ensure accessibility and safety.
+  - **Traffic Calming**: Speed bumps and narrowed streets reduce vehicle speeds, prioritizing pedestrian movement.
+  - **Aesthetic Appeal**: Tree-lined streets and public art enhance the walking experience, making it pleasant and inviting.
+- **Transit Integration**
+  - **Streetcar Access**: The Portland Streetcar connects the district to downtown and other areas, supporting car-free mobility.
+  - **Light Rail Proximity**: Nearby MAX light rail stations provide regional access, complementing walking routes.
+  - **Bike Synergy**: Dedicated bike lanes and racks integrate cycling with walking, enhancing multimodal options.
+- **Community and Environmental Benefits**
+  - **Social Connectivity**: Plazas and events like farmers’ markets foster interactions, making walking a community-building activity.
+  - **Sustainability**: Reduced car use lowers emissions, aligning with Portland’s eco-friendly ethos.
+  - **Health Promotion**: Walkable access to amenities encourages physical activity, supporting resident well-being.

package/dist/logic/roles/bhrain/.briefs/librarian.tactics/<demonstrate>.variants.example.[lesson].howto.md

@@ -0,0 +1,28 @@
+# 🧩 .brief.lesson: howto create a .brief.demo via example
+
+## 🎯 Objective
+
+Learn how to create a `.brief.demo`, a concise document that demonstrates a concept through a specific example, with a focus on instantiating the concept in a dedicated “What” section to make it clear and tangible.
+
+## 📋 Steps
+
+1. **Define the Concept Clearly**
+   - Write a brief, one-sentence definition of the concept to set the context for the demonstration.
+   - **Example**: For the concept of a use case, define it as “A use case describes how a user interacts with a system to achieve a goal, detailing actors, steps, and system responses.”
+2. **Choose a Representative Example**
+   - Select a single, concrete example that directly embodies the concept and is relatable to the audience.
+   - **Example**: For shear force, choose “scissors cutting paper” to show parallel forces causing material deformation, a clear and familiar instance.
+3. **Instantiate the Concept in the “What” Section**
+   - Present the example as a direct instance of the concept, using a structure that mirrors its natural form (e.g., a use case template for “Booking a Flight,” a scenario for shear force).
+   - Avoid general descriptions; focus on showing the concept in action.
+   - **Example**: For a use case, present a structured description with Actor (Traveler), Goal (purchase a ticket), Main Flow (search, select, pay), and Exceptions (no flights, payment failure).
+4. **Explain the Connection in a “How” Section**
+   - Detail how the example embodies the concept’s key characteristics, using a structured format like a bulleted list to ensure clarity and depth.
+   - **Example**: For “Booking a Flight,” explain how its structured flow and exception handling align with a use case’s role in defining system requirements.
+
+## 🔑 Key Considerations
+
+- **Instantiation is Key**: The “What” section should always present the example as an instance of the concept (e.g., a use case template, not just a booking process) to directly demonstrate its essence, making the concept tangible.
+- **Keep It Concise**: Avoid verbose outlines or excessive sub-bullets; focus on the example’s core elements to maintain clarity, as seen in the streamlined “Booking a Flight” use case.
+- **Adapt to Concept Type**: Tailor the instantiation to the concept’s nature—use templates for meta-concepts (e.g., use case), scenarios for physical concepts (e.g., shear force), or specific items for tangible concepts (e.g., Darjeeling tea).
+- **Ensure Relatability**: Choose examples that resonate with the audience (e.g., scissors for shear force, a familiar website for booking), ensuring accessibility across technical or abstract concepts.