rhachet-roles-bhrain 0.1.0 → 0.1.1

package/package.json

@@ -2,7 +2,7 @@
   "name": "rhachet-roles-bhrain",
   "author": "ehmpathy",
   "description": "reliable thought concept navigation roles, briefs, and skills, via rhachet",
-  "version": "0.1.0",
+  "version": "0.1.1",
   "repository": "ehmpathy/rhachet-roles-bhrain",
   "homepage": "https://github.com/ehmpathy/rhachet-roles-bhrain",
   "keywords": [
@@ -18,6 +18,39 @@
   "files": [
     "/dist"
   ],
+  "scripts": {
+    "build:ts": "tsc -p ./tsconfig.build.json",
+    "commit:with-cli": "npx cz",
+    "fix:format:biome": "biome check --write",
+    "fix:format": "npm run fix:format:biome",
+    "fix:lint": "biome check --write",
+    "fix": "npm run fix:format && npm run fix:lint",
+    "build:clean": "rm dist/ -rf",
+    "build:compile": "tsc -p ./tsconfig.build.json && tsc-alias -p ./tsconfig.build.json",
+    "build:complete": "rsync -a --prune-empty-dirs --include='*/' --exclude='**/.route/**' --exclude='**/.scratch/**' --exclude='**/.behavior/**' --exclude='**/*.test.sh' --include='**/*.template.md' --include='**/briefs/**/*.md' --include='**/briefs/*.md' --include='**/skills/**/*.sh' --include='**/skills/*.sh' --include='**/skills/**/*.jsonc' --include='**/skills/*.jsonc' --exclude='*' src/ dist/",
+    "build": "npm run build:clean && npm run build:compile && npm run build:complete --if-present",
+    "test:commits": "LAST_TAG=$(git describe --tags --abbrev=0 @^ 2> /dev/null || git rev-list --max-parents=0 HEAD) && npx commitlint --from $LAST_TAG --to HEAD --verbose",
+    "test:types": "tsc -p ./tsconfig.json --noEmit",
+    "test:format": "npm run test:format:biome",
+    "test:lint:deps": "npx depcheck -c ./.depcheckrc.yml",
+    "test:integration:hold": "jest -c ./jest.integration.config.ts --forceExit --verbose --passWithNoTests $([ -z $THOROUGH ] && echo '--changedSince=main')",
+    "test:lint:biome": "biome check --diagnostic-level=error",
+    "test:lint:biome:all": "biome check",
+    "test:lint": "npm run test:lint:biome && npm run test:lint:deps",
+    "test:unit": "jest -c ./jest.unit.config.ts --forceExit --verbose --passWithNoTests $([ -z $THOROUGH ] && echo '--changedSince=main') $([ -n $RESNAP ] && echo '--updateSnapshot')",
+    "test:integration": "echo 'todo: release'",
+    "test:acceptance:locally": "npm run build && LOCALLY=true jest -c ./jest.acceptance.config.ts --forceExit --verbose --runInBand --passWithNoTests $([ -n $RESNAP ] && echo '--updateSnapshot')",
+    "test": "npm run test:commits && npm run test:types && npm run test:format && npm run test:lint && npm run test:unit && npm run test:integration && npm run test:acceptance:locally",
+    "test:acceptance": "npm run build && jest -c ./jest.acceptance.config.ts --forceExit --verbose --runInBand --passWithNoTests $([ -n $RESNAP ] && echo '--updateSnapshot')",
+    "prepush": "npm run test && npm run build",
+    "prepublish": "npm run build",
+    "preversion": "npm run prepush",
+    "postversion": "git push origin HEAD --tags --no-verify",
+    "prepare:husky": "husky install && chmod ug+x .husky/*",
+    "prepare": "if [ -e .git ] && [ -z $CI ]; then npm run prepare:husky && npm run prepare:rhachet; fi",
+    "test:format:biome": "biome format",
+    "prepare:rhachet": "rhachet init && rhachet roles link --role mechanic && rhachet roles init --role mechanic"
+  },
   "dependencies": {
     "@ehmpathy/as-command": "1.0.3",
     "@ehmpathy/uni-time": "1.8.1",
@@ -27,7 +60,6 @@
     "helpful-errors": "1.5.3",
     "inquirer": "12.7.0",
     "openai": "5.8.2",
-    "rhachet": "1.13.11",
     "rhachet-artifact": "1.0.0",
     "rhachet-artifact-git": "1.1.0",
     "serde-fns": "1.2.0",
@@ -55,8 +87,8 @@
     "esbuild-register": "3.6.0",
     "husky": "8.0.3",
     "jest": "30.2.0",
-    "rhachet": "1.13.11",
-    "rhachet-roles-ehmpathy": "1.15.12",
+    "rhachet": "1.15.0",
+    "rhachet-roles-ehmpathy": "1.15.14",
     "test-fns": "1.6.0",
     "tsc-alias": "1.8.10",
     "tsx": "4.20.6",
@@ -69,36 +101,5 @@
       "path": "./node_modules/cz-conventional-changelog"
     }
   },
-  "scripts": {
-    "build:ts": "tsc -p ./tsconfig.build.json",
-    "commit:with-cli": "npx cz",
-    "fix:format:biome": "biome check --write",
-    "fix:format": "npm run fix:format:biome",
-    "fix:lint": "biome check --write",
-    "fix": "npm run fix:format && npm run fix:lint",
-    "build:clean": "rm dist/ -rf",
-    "build:compile": "tsc -p ./tsconfig.build.json && tsc-alias -p ./tsconfig.build.json",
-    "build:complete": "rsync -a --prune-empty-dirs --include='*/' --exclude='**/.route/**' --exclude='**/.scratch/**' --exclude='**/.behavior/**' --exclude='**/*.test.sh' --include='**/*.template.md' --include='**/briefs/**/*.md' --include='**/briefs/*.md' --include='**/skills/**/*.sh' --include='**/skills/*.sh' --include='**/skills/**/*.jsonc' --include='**/skills/*.jsonc' --exclude='*' src/ dist/",
-    "build": "npm run build:clean && npm run build:compile && npm run build:complete --if-present",
-    "test:commits": "LAST_TAG=$(git describe --tags --abbrev=0 @^ 2> /dev/null || git rev-list --max-parents=0 HEAD) && npx commitlint --from $LAST_TAG --to HEAD --verbose",
-    "test:types": "tsc -p ./tsconfig.json --noEmit",
-    "test:format": "npm run test:format:biome",
-    "test:lint:deps": "npx depcheck -c ./.depcheckrc.yml",
-    "test:integration:hold": "jest -c ./jest.integration.config.ts --forceExit --verbose --passWithNoTests $([ -z $THOROUGH ] && echo '--changedSince=main')",
-    "test:lint:biome": "biome check --diagnostic-level=error",
-    "test:lint:biome:all": "biome check",
-    "test:lint": "npm run test:lint:biome && npm run test:lint:deps",
-    "test:unit": "jest -c ./jest.unit.config.ts --forceExit --verbose --passWithNoTests $([ -z $THOROUGH ] && echo '--changedSince=main') $([ -n $RESNAP ] && echo '--updateSnapshot')",
-    "test:integration": "echo 'todo: release'",
-    "test:acceptance:locally": "npm run build && LOCALLY=true jest -c ./jest.acceptance.config.ts --forceExit --verbose --runInBand --passWithNoTests $([ -n $RESNAP ] && echo '--updateSnapshot')",
-    "test": "npm run test:commits && npm run test:types && npm run test:format && npm run test:lint && npm run test:unit && npm run test:integration && npm run test:acceptance:locally",
-    "test:acceptance": "npm run build && jest -c ./jest.acceptance.config.ts --forceExit --verbose --runInBand --passWithNoTests $([ -n $RESNAP ] && echo '--updateSnapshot')",
-    "prepush": "npm run test && npm run build",
-    "prepublish": "npm run build",
-    "preversion": "npm run prepush",
-    "postversion": "git push origin HEAD --tags --no-verify",
-    "prepare:husky": "husky install && chmod ug+x .husky/*",
-    "test:format:biome": "biome format",
-    "prepare:rhachet": "rhachet init && rhachet roles link --role mechanic && .agent/repo=ehmpathy/role=mechanic/skills/.skills/init.claude.sh"
-  }
-}
+  "packageManager": "pnpm@10.24.0"
+}

package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.foci.ponder.que.concept/2025-08-28T02:43:27.729Z.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/librarian.context/.rhachet/.rhachet/term.referent.foci.ponder.que.context/2025-08-28T02:43:27.729Z.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/librarian.context/.rhachet/.rhachet/term.referent.goal/2025-08-28T02:43:27.728Z.b1869db890614951.md

@@ -1,3 +0,0 @@
-
-articulate the term referent
-

package/dist/roles/thinker/briefs/librarian.context/.rhachet/.rhachet/term.referent.md.foci.ponder.que.concept/2025-08-28T02:44:23.033Z.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/librarian.context/.rhachet/.rhachet/term.referent.md.foci.ponder.que.context/2025-08-28T02:44:23.033Z.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/librarian.context/.rhachet/.rhachet/term.referent.md.goal/2025-08-28T02:44:23.031Z.852c92045a674148.md

@@ -1,4 +0,0 @@
-
-
-define the term 'referent'
-

package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent/2025-08-28T02:44:30.724Z.2f5896cb587117da.md

@@ -1,44 +0,0 @@
-# 🧩 .brief: `referent`
-
-## .what
-A **referent** is the specific entity in the world that a linguistic term or expression refers to or names. It is the actual object, concept, or entity that is designated by a word, phrase, or symbol within a particular context.
-
----
-
-## 🎯 purpose
-- **clarify meaning**: distinguishing between a word (signifier) and what it signifies in reality.
-- **enhance communication**: ensures that communicative intent is aligned with the actual subject matter.
-- **support logical reasoning**: crucial in semantics, philosophy, and linguistics for analyzing meaning.
-
----
-
-## 🧭 relation to language
-- **linguistic sign**: comprises both the signifier (e.g., word) and the referent (e.g., object or concept).
-- **denotation**: focuses on the direct association between linguistic terms and their referents.
-
----
-
-## 📚 examples
-- The word **"apple"** as a term may have various referents: a fruit, a tree, depending on context.
-- The name **"Paris"** can refer to the French capital or the mythological character, depending on usage.
-
----
-
-## 📍 usage in fields
-- **Linguistics**: Studies how language refers to objects and ideas.
-- **Philosophy**: Explores issues of reference, meaning, and existence.
-- **Artificial Intelligence**: Utilizes referents to enable understanding and manipulation of language.
-
----
-
-## ❗ important distinctions
-- **Referent vs. Meaning**: 'Meaning' encompasses more than the referent, including connotations and cultural contexts.
-- **Referent vs. Reference**: 'Reference' is the act or process of referring; the referent is the object itself.
-
----
-
-## 🛠 usage guidance
-- Specify context for clarity, as some words can have multiple or ambiguous referents.
-- Be aware of context shifts that might change referents (e.g., metaphors, jokes).
-
----

package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.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.context/.rhachet/term.referent.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.context/.rhachet/term.referent.goal.md

@@ -1,3 +0,0 @@
-
-articulate the term referent
-

package/dist/roles/thinker/briefs/librarian.context/.rhachet/term.referent.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.context/.rhachet/term.referent.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.context/.rhachet/term.referent.md.goal.md

@@ -1,4 +0,0 @@
-
-
-define the term 'referent'
-

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

@@ -1 +0,0 @@
-specifically use the terms zeroshot concepts and focus.concept

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.feedback/2025-08-19T05:30:52.866Z.c1ad1fe6df73a851.md

@@ -1 +0,0 @@
-explicitly reference the hypothesis with diverge r outputs in the context, we save llm.compute for catalogization, rather than  divergence

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.concept/2025-08-19T05:27:55.753Z.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/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.foci.ponder.que.context/2025-08-19T05:27:55.754Z.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/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].i2.md.goal/2025-08-19T05:27:55.751Z.c8232988c046d948.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/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.concept/2025-08-19T05:26:12.617Z.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/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].md.foci.ponder.que.context/2025-08-19T05:26:12.617Z.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/librarian.tactics/.rhachet/.rhachet/<catalogize>.vs_diverge.[article].md.goal/2025-08-19T05:26:12.615Z.68cf5d37ff5abc75.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/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.concept/2025-08-19T05:21:17.678Z.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/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.foci.ponder.que.context/2025-08-19T05:21:17.679Z.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/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.i3.via_rhachet.with_template.md.goal/2025-08-19T05:21:17.676Z.b35533aecf461c68.md

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

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.concept/2025-08-19T05:18:01.113Z.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/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.md.foci.ponder.que.context/2025-08-19T05:18:01.115Z.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/librarian.tactics/.rhachet/.rhachet/<demonstrate>._.[article].frame.tactical.md.goal/2025-08-19T05:18:01.112Z.b35533aecf461c68.md

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

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.concept/2025-08-19T05:33:21.987Z.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/librarian.tactics/.rhachet/.rhachet/<demonstrate>.tactics.[catalog].md.foci.ponder.que.context/2025-08-19T05:33:21.988Z.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/librarian.tactics/.rhachet/.rhachet/<demonstrate>.tactics.[catalog].md.goal/2025-08-19T05:33:21.985Z.1f3884998db3b338.md

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

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article]/2025-08-19T05:26:25.275Z.8a56710c0bb0b7f5.md

@@ -1,62 +0,0 @@
-# 🧩 .brief: `catalogize perspective and divergence`
-
-## .what
-
-`<catalogize>` is a focus.motion primitive for organizing and generating a structured catalog of concepts or entities. It operates by systematically exploring and mapping distinct aspects or components of the core concept, producing a comprehensive and organized output.
-
----
-
-## 🎯 purpose
-
-- organize concepts into a coherent, navigable structure
-- reveal hidden patterns or relationships among concepts
-- provide a detailed overview or inventory of related elements
-
----
-
-## 🌿 relation to divergence
-
-- **similarity with `<diverge>`:** both expand a core concept to surface variations and alternatives.
-- **difference from `<diverge>`:** `<catalogize>` focuses on organizing the expanded output, while `<diverge>` focuses on generating diverse possibilities.
-
-> `<diverge>` proposes; `<catalogize>` organizes and solidifies the proposition into a catalog.
-
----
-
-## 📜 method
-
-1. **preparation**
-   - Optional: Perform `<diverge>` to gather a wide array of possibilities related to the core concept.
-   
-2. **focus configuration**
-   - Input: Define the `focus.concept` to set the scope and anchor of the catalogization.
-   
-3. **execute catalogize**
-   - Structure: Categorize components of the concept by grouping them into logical categories or lists.
-   - Label: Assign labels or tags to segments for clarity and easy reference.
-   
-4. **finalize**
-   - Verification: Ensure all important components are included and well-organized.
-   - Optimization: Refine the structure for clarity and ease of navigation.
-
----
-
-## 💬 in practice
-
-Using `<catalogize>` after `<diverge>` enhances efficiency. By preparing a diverse array of concept variations in advance, `<catalogize>` can focus more on organizing and detailed catalog construction, rather than generating raw content. 
-
----
-
-## 🧠 examples
-
-### Scenario: Product Feature Catalog
-- **Input:** Outputs from `<diverge>` including various feature ideas.
-- **Use `<catalogize>` to:**
-  - Group features into functionality categories (e.g., "User Experience," "Security," "Performance").
-  - Create an inventory of planned features for development teams and stakeholders.
-
-### Scenario: Research Findings Catalog
-- **Input:** Data points and hypotheses from your research.
-- **Use `<catalogize>` to:**
-  - Organize findings into thematic areas or trends.
-  - Label each area with key insights or questions for further exploration.

package/dist/roles/thinker/briefs/librarian.tactics/.rhachet/<catalogize>.vs_diverge.[article].i2/2025-08-19T05:28:06.500Z.30e7bf815db7709b.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 start from scratch and create something from nothing.
-  - 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, 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: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.
-
----