rhachet-roles-bhrain 0.1.0 → 0.2.0

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:29:19.551Z.f4d48288c7f7b0b2.md

@@ -1,43 +0,0 @@
-# 🧩 .brief: `perspective on <catalogize> as a tactic`
-
-## .what
-**`<catalogize>`** is a tactic designed to systematically organize a wide array of concepts into a coherent structure or system. It aims to identify, classify, and relate distinct concepts within a given scope, providing clarity and facilitating understanding through structured representation.
-
----
-
-## 🎯 core perspective
-`<catalogize>` has parallels with the tactic known as **`<diverge>`**, particularly in its ability to handle diverse concepts. However, while **`<diverge>`** seeks to generate concepts expansively and without immediate structure, `<catalogize>` benefits from leveraging pre-diverged content to focus on the task of organizing and classifying these ideas effectively.
-
-> 🧩 Diverging first provides a rich dataset for `<catalogize>` to work with, enhancing the quality and scope of the cataloging process.
-
----
-
-## ⚙️ operational insight
-- **similarity to `<diverge>`**:
-  - both can zero shot concepts, initiating from nothing to create content.
-  - both aim to cover a wide range of concepts, albeit with different end goals.
-  
-- **difference from `<diverge>`**:
-  - `<diverge>` focuses on ideation, while `<catalogize>` focuses on organization.
-  - `<catalogize>` benefits from having pre-diverged outputs as the focus.concept, allowing it to allocate cognitive resources towards effective cataloging rather than ideation.
-
-- **best practice**:
-  - ideally, one uses **`<diverge>`** initially to ensure a broad and diverse set of concepts, then employs `<catalogize>` to impose structure and order.
-
----
-
-## 📐 strategic use
-- Initialization: `<diverge>` generates a wide-ranging set of concepts.
-- Progression: Leveraged **divergent outputs** as focus.concept for `<catalogize>`.
-- Convergence: `<catalogize>` filters, categorizes, and arranges these into a meaningful, structured framework.
-
----
-
-## 🎯 benefits
-- **Efficiency**: By separating the divergent and cataloging phases, you conserve mental energy and optimize the capacity of each tactic.
-- **Comprehensiveness**: Ensures a thorough exploration of the concept space prior to imposing a structure.
-- **Clarity**: Results in a refined, organized output that enhances understanding of complex ideas.
-
-> Adopting this approach means `<catalogize>` doesn't waste compute on generating, but focuses on delivering a structured and meaningful catalog.
-
----

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:31:05.482Z.875d98d92fe452d1.md

@@ -1,46 +0,0 @@
-# 🧩 .brief: `perspective on <catalogize> as a tactic`
-
-## .what
-**`<catalogize>`** is a tactic designed to systematically organize a wide array of concepts into a coherent structure or system. It aims to identify, classify, and relate distinct concepts within a given scope, providing clarity and facilitating understanding through structured representation.
-
----
-
-## 🎯 core perspective
-`<catalogize>` has parallels with the tactic known as **`<diverge>`**, particularly in its ability to handle diverse concepts. However, while **`<diverge>`** seeks to generate concepts expansively and without immediate structure, `<catalogize>` benefits from leveraging pre-diverged content to focus on the task of organizing and classifying these ideas effectively.
-
-> 🧩 Diverging first provides a rich dataset for `<catalogize>` to work with, enhancing the quality and scope of the cataloging process.
-
----
-
-## ⚙️ operational insight
-- **similarity to `<diverge>`**:
-  - both can zero shot concepts, initiating from nothing to create content.
-  - both aim to cover a wide range of concepts, albeit with different end goals.
-
-- **difference from `<diverge>`**:
-  - `<diverge>` focuses on ideation, while `<catalogize>` focuses on organization.
-  - `<catalogize>` benefits from having pre-diverged outputs in the focus.concept, allowing it to allocate cognitive resources towards effective cataloging rather than ideation.
-
-- **optimization hypothesis**:
-  - with pre-diverged outputs, `<catalogize>` saves LLM compute for cataloging activities, enhancing efficiency and depth without spending resources on divergence.
-
-- **best practice**:
-  - ideally, one uses **`<diverge>`** initially to ensure a broad and diverse set of concepts, then employs `<catalogize>` to impose structure and order.
-
----
-
-## 📐 strategic use
-- Initialization: `<diverge>` generates a wide-ranging set of concepts.
-- Progression: Leveraged **divergent outputs** in focus.concept for `<catalogize>`.
-- Convergence: `<catalogize>` filters, categorizes, and arranges these into a meaningful, structured framework.
-
----
-
-## 🎯 benefits
-- **Efficiency**: By separating the divergent and cataloging phases, you conserve mental energy and optimize the capacity of each tactic.
-- **Comprehensiveness**: Ensures a thorough exploration of the concept space prior to imposing a structure.
-- **Clarity**: Results in a refined, organized output that enhances understanding of complex ideas.
-
-> Adopting this approach means `<catalogize>` doesn't waste compute on generating, but focuses on delivering a structured and meaningful catalog.
-
----

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.concept.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.context.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2.md.goal.md

@@ -1,10 +0,0 @@
-
-
-articulate a brief on a perspective.
-
-specifically, a perspective about a tactic called <catalogize>. (dont declare a brief on catalogize, only the perspective)
-
-the perspective is that 
-
-<catalogize> is similar to diverge since it can zero shot concepts, but it is often helpful to diverge in advance and pass the results as part of the focus.concept so that catalogize can leverage it and save its compute for the actual catalogization instead
-

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.concept.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.context.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].md.goal.md

@@ -1,4 +0,0 @@
-
-
-articulate a brief which describes the PERSPECTIVE that <catalogize> is similar to diverge since it can zero shot concepts, but it is often helpful to diverge in advance and pass the results as part of the focus.concept so that catalogize can leverage it and save its compute for the actual catalogization instead
-

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical/2025-08-19T05:18:27.266Z.f1bb2e1f049133a5.md

@@ -1,64 +0,0 @@
-# 🧩 .brief: `demonstrate`
-
-## .what
-**demonstrate** refers to the act of clearly showing or explaining how something works, highlighting its features, processes, or effects. It involves presenting a concept or an action in a manner that is understandable and convincing, often through examples, illustrations, or practical applications.
-
----
-
-## 🎯 purpose
-- **clarify** the functionality, features, or value of a concept or product.
-- **showcase** abilities or outcomes through practical examples or simulations.
-- **educate** an audience by providing a detailed explanation or display.
-- **persuade** others by effectively communicating advantages or benefits.
-
----
-
-## 📏 methods of demonstration
-1. **Visual demonstrations**
-   - Use of images, animations, or videos.
-   - Effective for conveying complex ideas quickly and engagingly.
-
-2. **Verbal explanations**
-   - Clear, concise, and well-structured descriptions.
-   - Suitable for situations where visual aids are impractical.
-
-3. **Hands-on demonstrations**
-   - Interactive methods where participants engage directly with the material.
-   - Ideal for workshops, labs, or real-time presentations.
-
-4. **Examples and case studies**
-   - Presentation of real-world scenarios or success stories.
-   - Helps audiences relate to and understand practical applications.
-
----
-
-## 🔄 when to use
-- When introducing a new concept or product.
-- During educational sessions or workshops.
-- To support a sales pitch or marketing effort.
-- When changes or updates to existing systems need to be communicated clearly.
-
----
-
-## 📐 examples
-- **Product launches**: Demonstrating new features or capabilities of a product to potential customers or investors.
-- **Educational settings**: Teachers demonstrating a scientific experiment to students for better understanding.
-- **Training sessions**: A coach or trainer demonstrating a technique or skill for learners to emulate.
-- **Presentations**: A speaker using slides and live demos to highlight key points.
-
----
-
-## 📚 benefits
-- Enhances understanding and retention of information.
-- Builds credibility and confidence in the presenter or product.
-- Encourages engagement and interaction from the audience.
-- Serves as a valuable tool for persuasion by providing evidence and clarity.
-
----
-
-## ⚠️ potential pitfalls
-- Overcomplicating the presentation leading to confusion.
-- Failing to engage the audience or adapt to their level of understanding.
-- Technical failures in demonstrations relying heavily on equipment or software.
-
-> A well-executed demonstration bridges the gap between theoretical concepts and practical application, making abstract ideas tangible and actionable.

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template/2025-08-19T05:21:27.536Z.05c9744a2208309b.md

@@ -1,74 +0,0 @@
-# 🧩 .brief: `demonstrate`
-
-## .what
-
-To **demonstrate** is to clearly and effectively show or prove a concept, process, or phenomenon through evidence, examples, or experiments. It involves a structured presentation or execution that enables an audience to gain understanding or insight.
-
----
-
-## 🎯 purpose
-
-- to provide **clear evidence** or **example** of how something works or functions
-- to make abstract concepts more **tangible** and **understandable**
-- to **validate or prove** a hypothesis or concept through observable means
-
----
-
-## 📐 attributes
-
-- **clarity:** demonstrations should be easy to follow and understand
-- **relevance:** aligned with the audience's level of knowledge and interest
-- **effectiveness:** ability to convey the intended message or concept efficiently
-- **engagement:** actively involves the audience or observers, making the concept memorable
-
----
-
-## 🛠️ methods
-
-1. **prepare**
-   - define the objective and key points to demonstrate
-   - gather necessary materials or tools
-
-2. **execute**
-   - follow a logical sequence
-   - use visual aids, examples, or analogies
-
-3. **validate**
-   - invite questions or feedback
-   - ensure comprehension and gather proof of understanding
-
-4. **refine**
-   - improve clarity and effectiveness based on feedback
-   - adjust as needed for different audiences or contexts
-
----
-
-## 📦 examples
-
-- **scientific experiments:** demonstrating principles of physics
-- **software demos:** showing features and functionality
-- **training sessions:** illustrating procedures or skills
-- **marketing presentations:** demonstrating product benefits
-
----
-
-## ⚖️ tradeoffs
-
-- **too detailed:** may overwhelm and lose the audience's interest
-- **too simple:** may not fully convey the complexity or significance
-- **context-specific:** requires tailoring to different audiences or settings to ensure effectiveness
-
----
-
-## 🔁 integration
-
-- use demonstrations to complement lectures and presentations by providing practical examples
-- integrate into user manuals and guides for more effective teaching and learning
-
---- 
-
-## 💡 tips
-
-- keep the audience engaged through interactive elements
-- use simple, clear language and visual aids
-- test the demonstration beforehand to ensure smooth delivery

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.concept.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.context.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.goal.md

@@ -1,6 +0,0 @@
-
-brief on <demonstrate>
-
-produces [briefs] which demonstrate some [concept]
-
-

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.concept.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.context.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>._.[article].frame.tactical.md.goal.md

@@ -1,6 +0,0 @@
-
-brief on <demonstrate>
-
-produces [briefs] which demonstrate some [concept]
-
-

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog]/2025-08-19T05:33:41.302Z.78d520797f9769bd.md

@@ -1,68 +0,0 @@
-# 🧩 .brief.catalog: `demonstration.tactics`
-
-## .what
-a **catalog of tactics** for applying demonstrations effectively to articulate and make sense of concepts, processes, or systems. these tactics guide how to display or elucidate elements to clarify understanding or showcase utility.
-
----
-
-## 🛠 tactics
-
-### 1. **visual demonstration**
-- employs images, animations, or videos to convey the essence of a concept.
-- ideal for quickly and engagingly explaining complex ideas.
-
----
-
-### 2. **verbal explanation**
-- delivers clear, structured descriptions suitable for settings where visuals can't be used.
-
----
-
-### 3. **hands-on interaction**
-- involves participants directly for experiential learning, best used in workshops or labs.
-
----
-
-### 4. **use of examples and case studies**
-- presents real-world scenarios or success stories for relatable and practical understanding.
-
----
-
-### 5. **step-by-step walkthrough**
-- breaks down a process into successive steps, useful for tasks requiring precision or sequence.
-
----
-
-### 6. **simulation and role-play**
-- mimics real-life situations to test concepts and gauge reactions or understanding in a controlled environment.
-
----
-
-### 7. **analogies and metaphors**
-- leverages relatable comparisons to simplify and clarify complex concepts.
-
----
-
-### 8. **live demonstrations**
-- conducts demonstrations in real-time, allowing for immediate feedback and adjustments.
-
----
-
-## 🔄 usage
-- choose tactics based on audience, content complexity, and context.
-- combine multiple tactics to enhance engagement and clarity.
-- adjust tactics to fit different learning styles and preferences.
-
----
-
-## 🎯 why it works
-- promotes active engagement and understanding.
-- aids retention by providing practical, relatable anchors.
-- bridges theory to practice through visible and tangible examples.
-
----
-
-## 💡 notes
-- consider audience size and setting when choosing a tactic.
-- ensure technical readiness for any tools or materials required.
-- always follow-up demonstrations with Q&A for added clarity and understanding.

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.concept.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.context.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<demonstrate>.tactics.[catalog].md.goal.md

@@ -1,6 +0,0 @@
-
-
-articulate a .brief.catalog
-
-on different tactics of demonstration
-

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:42:52.441Z.9b5920a5f2286358.md

@@ -1 +0,0 @@
-add the contract section, like <diverge> has 

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:45:56.905Z.c41b7ee6c012dca7.md

@@ -1 +0,0 @@
-add examples

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.feedback/2025-08-17T23:46:26.625Z.550b8cabb776137d.md

@@ -1 +0,0 @@
-illustrate the examples

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-17T23:39:04.903Z.1dbacaa56e249af8.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-17T23:40:21.876Z.1dbacaa56e249af8.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-17T23:45:04.183Z.1dbacaa56e249af8.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-17T23:39:04.904Z.20883c047b5b3927.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-17T23:40:21.877Z.20883c047b5b3927.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-17T23:45:04.183Z.20883c047b5b3927.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:39:04.900Z.f214cfb2b02fab75.md

@@ -1,3 +0,0 @@
-
-articulate what the thought process of <cluster> is
-

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:40:21.875Z.f214cfb2b02fab75.md

@@ -1,3 +0,0 @@
-
-articulate what the thought process of <cluster> is
-

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<cluster>._.[article].frame.tactical.md.goal/2025-08-17T23:45:04.181Z.f214cfb2b02fab75.md

@@ -1,3 +0,0 @@
-
-articulate what the thought process of <cluster> is
-

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.concept/2025-08-18T05:06:49.996Z.1dbacaa56e249af8.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.2.md.foci.ponder.que.context/2025-08-18T05:06:49.997Z.20883c047b5b3927.md

@@ -1,12 +0,0 @@
-[
-  "what concept.dimensions are important to articulate for this specific goal?",
-  "which <articulate>.tactics would help most for this goal?",
-  "what granularity should it be articulated to?",
-  "who is this for?",
-  "why do they care?",
-  "where will this be used?",
-  "when is this relevant?",
-  "what constraints exist?",
-  "what is the setting or situation for this concept?",
-  "what related concepts or materials already exist in this context?"
-]

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.2.md.goal/2025-08-18T05:06:49.995Z.528e7ccdbef5d0cb.md

@@ -1,3 +0,0 @@
-
-articulate what the thought process of <triage> is
-

package/dist/roles/thinker/briefs/thinker.tactics/.rhachet/.rhachet/<triage>._.[article].frame.tactical.3.md.foci.ponder.que.concept/2025-08-18T05:07:30.952Z.1dbacaa56e249af8.md

@@ -1,13 +0,0 @@
-[
-  "what exactly am I articulating?",
-  "what is the goal of this articulation?",
-  "what is the core message or takeaway?",
-  "what level of acuity is needed?",
-  "what gaps must be addressed?",
-  "what qualities or attributes must be surfaced?",
-  "what scope boundaries should be maintained?",
-  "what misconceptions should be addressed?",
-  "what sub-points or dimensions does it naturally break into?",
-  "what terms or concepts must be defined for clarity?",
-  "what real-world examples or analogies will anchor it?"
-]