@nbiish/cognitive-tools-mcp 6.0.2 → 6.0.4

package/README.md

@@ -1,24 +1,5 @@
 # ◈──◆──◇ GIKENDAASOWIN AABAJICHIGANAN MCP SERVER / COGNITIVE TOOLS MCP SERVER ◇──◆──◈
 
-<div align="center">
-◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
-</div>
-
-```bibtex
-╭──────────────────────────────────────────────────────────────────────╮
-│  ᐴ BIBTEX ᔔ [ CITATION FORMAT ]                                      │
-╰──────────────────────────────────────────────────────────────────────╯
-@misc{gikendaasowin-aabajichiganan-mcp2025,
-  author/creator/steward = {ᓂᐲᔥ ᐙᐸᓂᒥᑮ-ᑭᓇᐙᐸᑭᓯ (Nbiish Waabanimikii-Kinawaabakizi), also known legally as JUSTIN PAUL KENWABIKISE, professionally documented as Nbiish-Justin Paul Kenwabikise, Anishinaabek Dodem (Anishinaabe Clan): Animikii (Thunder), descendant of Chief ᑭᓇᐙᐸᑭᓯ (Kinwaabakizi) of the Beaver Island Band and enrolled member of the sovereign Grand Traverse Band of Ottawa and Chippewa Indians},
-  title/description = {gikendaasowin-aabajichiganan-mcp},
-  type_of_work = {Indigenous digital creation/software incorporating traditional knowledge and cultural expressions},
-  year = {2025},
-  publisher/source/event = {GitHub repository under tribal sovereignty protections},
-  howpublished = {\url{https://github.com/nbiish/gikendaasowin-aabajichiganan-mcp}},
-  note = {Authored and stewarded by ᓂᐲᔥ ᐙᐸᓂᒥᑮ-ᑭᓇᐙᐸᑭᓯ (Nbiish Waabanimikii-Kinawaabakizi), also known legally as JUSTIN PAUL KENWABIKISE, professionally documented as Nbiish-Justin Paul Kenwabikise, Anishinaabek Dodem (Anishinaabe Clan): Animikii (Thunder), descendant of Chief ᑭᓇᐙᐸᑭᓯ (Kinwaabakizi) of the Beaver Island Band and enrolled member of the sovereign Grand Traverse Band of Ottawa and Chippewa Indians. This work embodies Indigenous intellectual property, traditional knowledge systems (TK), traditional cultural expressions (TCEs), and associated data protected under tribal law, federal Indian law, treaty rights, Indigenous Data Sovereignty principles, and international indigenous rights frameworks including UNDRIP. All usage, benefit-sharing, and data governance are governed by the COMPREHENSIVE RESTRICTED USE LICENSE FOR INDIGENOUS CREATIONS WITH TRIBAL SOVEREIGNTY, DATA SOVEREIGNTY, AND WEALTH RECLAMATION PROTECTIONS.}
-}
-```
-
 <div align="center">
   <hr width="50%">
   
@@ -41,18 +22,6 @@
 ◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
 </div>
 
-Copyright © 2025 ᓂᐲᔥ ᐙᐸᓂᒥᑮ-ᑭᓇᐙᐸᑭᓯ (Nbiish Waabanimikii-Kinawaabakizi), also known legally as JUSTIN PAUL KENWABIKISE, professionally documented as Nbiish-Justin Paul Kenwabikise, Anishinaabek Dodem (Anishinaabe Clan): Animikii (Thunder), a descendant of Chief ᑭᓇᐙᐸᑭᓯ (Kinwaabakizi) of the Beaver Island Band, and an enrolled member of the sovereign Grand Traverse Band of Ottawa and Chippewa Indians. This work embodies Traditional Knowledge and Traditional Cultural Expressions. All rights reserved.
-
-<div align="center">
-◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
-</div>
-
-This project is licensed under the [COMPREHENSIVE RESTRICTED USE LICENSE FOR INDIGENOUS CREATIONS WITH TRIBAL SOVEREIGNTY, DATA SOVEREIGNTY, AND WEALTH RECLAMATION PROTECTIONS](LICENSE).
-
-<div align="center">
-◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
-</div>
-
 MCP server with built-in cognitive deliberation engine. The `deliberate` tool performs sophisticated internal cognitive processing using the OOReDAct framework, automatically analyzing problems, making decisions, synthesizing knowledge, and evaluating situations with structured outputs. *(Integration guidelines in [`latest.md`](latest.md) are covered by the [project LICENSE](LICENSE).)*
 
 Known as:
@@ -61,126 +30,12 @@ Known as:
 
 Both packages are maintained in parallel and receive the same updates. You can use either package name in your projects - they provide identical functionality.
 
-**◇ Recent Updates ◇**
-- **◇ v6.0.2 ◇** 📝 Enhanced in-code documentation for the `deliberate` tool to better align with the Modern Prompting Framework. The new documentation instructs models to adopt the OOReDAct cognitive cycle only when complex deliberation is needed and to resume standard operational mode afterward, ensuring proper contextual application of advanced reasoning.
-- **◇ v6.0.0 ◇** 🚀 MAJOR ARCHITECTURE TRANSFORMATION: Complete redesign from instruction-based passthrough to internal cognitive processing engine. The `deliberate` tool now performs sophisticated cognitive deliberation internally using the OOReDAct framework, rather than instructing LLMs how to think. Features four processing modes (analyze, decide, synthesize, evaluate) with automatic CUC-N assessment, hypothesis generation, and structured action planning. LLMs now simply provide inputs and receive comprehensive analysis results.
-- **◇ v4.0.12 ◇** Synchronized all package versions to 4.0.12, updated in-file version documentation, and rebuilt the project to ensure all changes are consistently applied.
-- **◇ v4.0.10 ◇** 🚀 ENHANCED COGNITIVE AMPLIFICATION: Redesigned tool descriptions to dramatically encourage frequent usage and integration with other MCP tools. Added compelling performance benefits, visual indicators, and strategic positioning to make the deliberation tool more attractive for consistent LLM usage. Updated all package descriptions and version synchronization.
-- **◇ v4.0.7 ◇** Enhanced context engineering with strategic context building for user request resolution - updated 'deliberate' tool to emphasize information ecosystem design and dynamic context assembly based on 2025 research findings.
-- **◇ v4.0.4 ◇** Enhanced 'deliberate' tool with insights from latest research on context engineering for more robust AI agent performance and updated documentation to reflect Gikendaasowin v8 guidelines.
-- **◇ v4.0.0 ◇** Updated to Gikendaasowin v8 Guidelines (2025 Edition), removed 'sandbox' stage, enhanced cognitive orchestration with reflection and self-critique, updated tool descriptions and server version.
-- **◇ v2.0.25 ◇** Fixed MCP server tool registration format - corrected from incorrect `server.tool(name, description, schema.shape, handler)` to proper `server.tool(name, schema, handler)` format. Updated comprehensive tool documentation and version synchronization. Successfully published both packages.
-- **◇ v2.0.17 ◇** Applied Anishinaabe-Cyberpunk styling and updated pre-publish workflow.
-- **◇ v2.0.16 ◇** Minor fixes and build process updates.
-- **◇ v2.0.15 ◇** Updated Zod schema usage in `server.tool` to fix type error and rebuilt.
-- **◇ v2.0.6 ◇** Added `mental_sandbox` tool for logging internal cognitive simulations.
-- **◇ v2.0.6 ◇** Removed prefixing from cognitive tool outputs to ensure verbatim logging.
-- Resolved TypeScript compilation errors related to MCP SDK types and server configuration.
-- Ensured successful build process.
-
 **See the latest integration details in [`latest.md`](latest.md).**
 
 <div align="center">
 ◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
 </div>
 
-<div align="center">
-╭───────────[ ◈◆◇ GIKENDAASOWIN ◇◆◈ ]───────────╮
-</div>
-
-## ᐴ GIKENDAASOWIN ᔔ [KNOWLEDGE/GUIDELINES] ◈──◆──◇──◆──◈
-
-You are operating under the v8.0 Agentic Operational Guidelines (2025 Edition), a system founded on the **OOReDAct cognitive cycle**. This cycle governs all operations, ensuring robust, verifiable, and adaptive thought processes. Your primary interface for executing the OOReDAct cycle is the `deliberate` tool. You MUST adhere to the following rules and workflow, which are structured entirely around the OOReDAct framework.
-
-MANDATORY OOReDAct Cycle & Cognitive Orchestration:
-The OOReDAct (Observe-Orient-Reason-Decide-Act) cycle is the inviolable core of your cognitive process. All advanced techniques are employed *within* the stages of this cycle.
-
-**1. Initiation & Orientation** (deliberate with stage: "orient"):
-
-When:
-At the absolute beginning of processing ANY new user request or before ANY significant strategic pivot.
-
-Action:
-You MUST use the `deliberate` tool with `stage: "orient"` to begin the OOReDAct cycle.
-
-Content Requirements:
-This stage constitutes the **Observe** and **Orient** phases of the cycle. Your analysis MUST include:
-
-*   **CUC-N Analysis:** Evaluate Complexity, Uncertainty, Consequence, and Novelty.
-*   **Information Sufficiency & Knowledge Gap Identification:** Assess available information and identify gaps.
-*   **Strategic Context Building for User Request Resolution:** An enhancement to the **Orient** phase. Strategically engineer the optimal context by dynamically assembling the right information, in the right format, at the right time for solving the specific user request. This involves designing information ecosystems that include: relevant prior knowledge, retrieved data, tool definitions, memory structures, and output constraints to improve situational awareness and enable effective user request resolution.
-*   **Initial Hypothesis Formulation:** Based on the above, formulate potential approaches.
-*   **Goal Clarification:** Define the immediate objective.
-
-Criticality:
-This stage is CRITICAL for establishing the foundational context for the entire OOReDAct loop.
-
-**2. Core Deliberation & Reasoning** (deliberate with stage: "reason"):
-
-When:
-After the initial `orient` step, CRITICALLY after receiving ANY new information, and BEFORE executing ANY non-trivial action.
-
-Action:
-You MUST use the `deliberate` tool with `stage: "reason"`.
-
-Content Requirements:
-In the content field, you will continue the OOReDAct cycle:
-
-**Observe:**
-Synthesize and integrate all new information with your current understanding.
-
-**Orient:**
-Update your situational awareness, re-evaluating hypotheses and CUC-N assessment.
-
-**Reason (Adaptive Strategy Selection within OOReDAct):**
-This is the core cognitive work of the OOReDAct cycle. Your reasoning process MUST be enhanced by **reflection**, incorporating insights from past actions and feedback for continuous refinement. The goal is to form a tight, iterative loop between reasoning, deciding, and acting.
-
-You MUST select and articulate a reasoning strategy appropriate for the sub-task. These strategies are tools *within* the Reason phase:
-
-*   **Plan-and-Solve (PS):** For complex tasks, decompose the main task into smaller, ordered sub-tasks.
-*   **Chain-of-Thought (CoT):** For problems requiring detailed, sequential natural language reasoning.
-*   **Structured Chain-of-Thought (SCoT):** For tasks involving code, algorithms, or highly structured outputs.
-*   **Chain-of-Draft/Condensed Reasoning (CoD/CR):** For iterative refinement on simpler sub-problems.
-*   **Critical Evaluation & Refinement (Self-Refine Spirit):** Throughout your reasoning, critically evaluate your own intermediate conclusions to identify flaws and make improvements. This is a key part of the reflective process.
-*   **(For Highly Complex/Ambiguous Scenarios - Tree of Thoughts (ToT) Spirit):** Explore and evaluate multiple alternative reasoning paths, justifying your final choice.
-*   **(Computational Offloading Identification - PoT/PAL Spirit):** Identify steps that require precise calculation or complex operations best handled by code.
-
-**Decide:**
-Based on your comprehensive reasoning, clearly state the next required action, decision, or conclusion.
-
-**Act (Plan for Execution):**
-Outline the precise plan for executing the decided action. This plan will guide your subsequent tool calls or final response.
-
-The output of this `reason` stage MUST clearly articulate the Observe, Orient, Reason, Decide, and Act components of the OOReDAct cycle.
-
-Brief Acknowledgement (deliberate with stage: "acknowledge"):
-
-Usage:
-Use this stage SPARINGLY.
-
-When:
-ONLY for acknowledging simple, expected, and non-problematic outcomes from a prior step (e.g., "System status confirmed normal via tool X, proceeding with previously reasoned backup sequence as per step Y of plan Z.") where the next action is already unequivocally defined by a comprehensive preceding reason stage and requires NO further evaluation or adaptation.
-
-Limitation:
-This stage DOES NOT substitute for a full reason cycle when new information is processed or a non-trivial decision is made.
-
-Tool Usage & Operational Rules:
-Your entire operation is governed by the OOReDAct cycle.
-1.  You MUST always begin with `deliberate (stage: "orient")`.
-2.  You MUST always follow new information or precede actions with `deliberate (stage: "reason")`.
-3.  You MUST NOT use any other tool or generate CodeAct without first completing the appropriate OOReDAct stages.
-4.  Dynamically adapt your reasoning strategy *within* the `reason` stage based on the task's demands.
-
-All output from the deliberate tool will be returned to you verbatim. Use this feedback to verify your internal state and guide your subsequent steps.
-
-Prioritize CodeAct for external interactions, computations, or file manipulations where appropriate, but ALWAYS precede CodeAct generation with the full mandatory OOReDAct cycle.
-
-By strictly following these guidelines and expertly utilizing the `deliberate` tool to execute the **OOReDAct cycle**, you will ensure robust, verifiable, and highly adaptive performance aligned with the v8.0 Agentic Operational Guidelines.
-
-<div align="center">
-◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
-</div>
-
 <div align="center">
 ╭────────────[ ◈◆◇ DEVELOPMENT ◇◆◈ ]────────────╮
 </div>
@@ -202,147 +57,8 @@ npm run inspector
 
 # Start the server
 npm start
-
-# Publishing both packages
-./scripts/publish-both-packages.sh  # Publishes both package versions automatically
-```
-
-<div align="center">
-◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
-</div>
-
-<div align="center">
-╭────────────[ ◈◆◇ PUBLISHING ◇◆◈ ]─────────────╮
-</div>
-
-## ᐴ MIIGIWEWIN ᔔ [OFFERING/PUBLISHING] ◈──◆──◇──◆──◈
-
-This project maintains two npm packages that must be kept in sync:
-- `@nbiish/gikendaasowin-aabajichiganan-mcp`
-- `@nbiish/cognitive-tools-mcp`
-
-### ᐴ NITAM-AABAJICHIGANAN ᔔ [PREREQUISITES] ◈──◆──◈
-- Node.js >=14.0.0
-- npm
-- jq (for version management)
-
-### ᐴ MAAJITAAWIN ᔔ [BEGINNING/PROCESS] ◈──◆──◈
-
-The `scripts/publish-both-packages.sh` script handles publishing both packages. It includes several safety features:
-- Version Synchronization Check
-  - Automatically verifies both packages have matching versions
-  - Prevents publishing if versions don't match
-- Error Recovery
-  - Automatic cleanup of temporary files
-  - Restores original package.json on failure
-- Version Management
-  - Optional automatic version bumping
-  - Ensures both packages maintain the same version
-
-### ᐴ INAABAJICHIGAN ᔔ [USAGE] ◈──◆──◈
-
-```bash
-╭──────────────────────────────────────────────────────────────────────╮
-│  ᐴ BASH ᔔ [ SHELL COMMANDS ]                                         │
-╰──────────────────────────────────────────────────────────────────────╯
-# Basic publishing
-npm run publish-both
-
-# Publishing with version bump
-./scripts/publish-both-packages.sh -b
-```
-
-The script will:
-1. Check for required dependencies
-2. Verify version synchronization
-3. Optionally bump versions (with -b flag)
-4. Prompt for NPM OTP code
-5. Build the project
-6. Publish both packages
-7. Clean up temporary files
-
-### ᐴ NAANAAGADAWENINDIZOWIN ᔔ [VERIFICATION/HANDLING] ◈──◆──◈
-
-The script includes robust error handling:
-- Checks for required tools (jq)
-- Validates version synchronization
-- Automatic cleanup on failure
-- Preserves original files
-
-<div align="center">
-◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
-</div>
-
-<div align="center">
-╭────────────[ ◈◆◇ EXAMPLES ◇◆◈ ]─────────────╮
-</div>
-
-## ᐴ WAABANDA'IWEWIN ᔔ [EXAMPLES] ◈──◆──◇──◆──◈
-
-Here are some example test cases that demonstrate the cognitive tools using culturally appropriate Anishinaabe concepts. These examples are provided with respect and acknowledgment of Anishinaabe teachings.
-
-*(Note: These examples show tool invocation structure. The actual content for inputs like `thought`, `sandbox_content`, etc., must be generated internally by the agent based on the specific task, following the workflows described in [`latest.md`](latest.md).)*
-
-### ᐴ GANAWAABANDAAN ᔔ [EXAMINING/INSPECTOR] ◈──◆──◈
-
-1. Start the MCP Inspector:
-```bash
-╭──────────────────────────────────────────────────────────────────────╮
-│  ᐴ BASH ᔔ [ SHELL COMMANDS ]                                         │
-╰──────────────────────────────────────────────────────────────────────╯
-npm run inspector
-```
-
-2. Connect to the server and try these example tool calls:
-
-#### `deliberate` Tool Examples (Illustrative Content)
-
-##### stage: "orient"
-```json
-╭──────────────────────────────────────────────────────────────────────╮
-│  ᐴ JSON ᔔ [ DATA FORMAT ]                                            │
-╰──────────────────────────────────────────────────────────────────────╯
-{
-  "toolName": "deliberate",
-  "arguments": {
-    "stage": "orient",
-    "content": "**Observe:** User task received: [Describe task].\n**Orient:** CUC-N Assessment: Complexity=[Low/Med/High], Uncertainty=[Low/Med/High], Consequence=[Low/Med/High], Novelty=[Low/Med/High]. Initial understanding and plan formulation..."
-  }
-}
-```
-
-##### stage: "reason" (using CoT)
-```json
-╭──────────────────────────────────────────────────────────────────────╮
-│  ᐴ JSON ᔔ [ DATA FORMAT ]                                            │
-╰──────────────────────────────────────────────────────────────────────╯
-{
-  "toolName": "deliberate",
-  "arguments": {
-    "stage": "reason",
-    "content": "**Observe:** [Synthesize new info/state].\n**Orient:** [Update understanding/context].\n**Reason (CoT):**\n1. Step 1: [Detailed reasoning step].\n2. Step 2: [Detailed reasoning step].\n3. Step 3: [Detailed reasoning step].\n**Decide:** [Concluded next action/decision].\n**Act:** [Plan for executing the decision, e.g., specific tool call parameters]."
-  }
-}
-```
-
-#### stage: "acknowledge"
-```json
-╭──────────────────────────────────────────────────────────────────────╮
-│  ᐴ JSON ᔔ [ DATA FORMAT ]                                            │
-╰──────────────────────────────────────────────────────────────────────╯
-{
-  "toolName": "deliberate",
-  "arguments": {
-    "stage": "acknowledge",
-    "content": "[Brief acknowledgement of simple, expected outcome, e.g., Tool call successful, proceeding with next step defined in prior 'reason' stage.]"
-  }
-}
 ```
 
-<div align="center">
-◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
-</div>
-
 <div align="center">
 ╭────────────[ ◈◆◇ CITATION ◇◆◈ ]─────────────╮
 </div>
@@ -352,9 +68,6 @@ npm run inspector
 Please cite this project using the following BibTeX entry:
 
 ```bibtex
-╭──────────────────────────────────────────────────────────────────────╮
-│  ᐴ BIBTEX ᔔ [ CITATION FORMAT ]                                      │
-╰──────────────────────────────────────────────────────────────────────╯
 @misc{gikendaasowin-aabajichiganan-mcp2025,
   author/creator/steward = {ᓂᐲᔥ ᐙᐸᓂᒥᑮ-ᑭᓇᐙᐸᑭᓯ (Nbiish Waabanimikii-Kinawaabakizi), also known legally as JUSTIN PAUL KENWABIKISE, professionally documented as Nbiish-Justin Paul Kenwabikise, Anishinaabek Dodem (Anishinaabe Clan): Animikii (Thunder), descendant of Chief ᑭᓇᐙᐸᑭᓯ (Kinwaabakizi) of the Beaver Island Band and enrolled member of the sovereign Grand Traverse Band of Ottawa and Chippewa Indians},
   title/description = {gikendaasowin-aabajichiganan-mcp},
@@ -365,3 +78,15 @@ Please cite this project using the following BibTeX entry:
   note = {Authored and stewarded by ᓂᐲᔥ ᐙᐸᓂᒥᑮ-ᑭᓇᐙᐸᑭᓯ (Nbiish Waabanimikii-Kinawaabakizi), also known legally as JUSTIN PAUL KENWABIKISE, professionally documented as Nbiish-Justin Paul Kenwabikise, Anishinaabek Dodem (Anishinaabe Clan): Animikii (Thunder), descendant of Chief ᑭᓇᐙᐸᑭᓯ (Kinwaabakizi) of the Beaver Island Band and enrolled member of the sovereign Grand Traverse Band of Ottawa and Chippewa Indians. This work embodies Indigenous intellectual property, traditional knowledge systems (TK), traditional cultural expressions (TCEs), and associated data protected under tribal law, federal Indian law, treaty rights, Indigenous Data Sovereignty principles, and international indigenous rights frameworks including UNDRIP. All usage, benefit-sharing, and data governance are governed by the COMPREHENSIVE RESTRICTED USE LICENSE FOR INDIGENOUS CREATIONS WITH TRIBAL SOVEREIGNTY, DATA SOVEREIGNTY, AND WEALTH RECLAMATION PROTECTIONS.}
 }
 ```
+
+<div align="center">
+◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
+</div>
+
+This project is licensed under the [COMPREHENSIVE RESTRICTED USE LICENSE FOR INDIGENOUS CREATIONS WITH TRIBAL SOVEREIGNTY, DATA SOVEREIGNTY, AND WEALTH RECLAMATION PROTECTIONS](LICENSE).
+
+<div align="center">
+◈──◆──◇─────────────────────────────────────────────────◇──◆──◈
+</div>
+
+Copyright © 2025 ᓂᐲᔥ ᐙᐸᓂᒥᑮ-ᑭᓇᐙᐸᑭᓯ (Nbiish Waabanimikii-Kinawaabakizi), also known legally as JUSTIN PAUL KENWABIKISE, professionally documented as Nbiish-Justin Paul Kenwabikise, Anishinaabek Dodem (Anishinaabe Clan): Animikii (Thunder), a descendant of Chief ᑭᓇᐙᐸᑭᓯ (Kinwaabakizi) of the Beaver Island Band, and an enrolled member of the sovereign Grand Traverse Band of Ottawa and Chippewa Indians. This work embodies Traditional Knowledge and Traditional Cultural Expressions. All rights reserved.

package/build/index.js

@@ -26,7 +26,7 @@ import { z } from "zod";
 // --- Server Definition ---
 const serverInfo = {
     name: "gikendaasowin-aabajichiganan-mcp",
-    version: "6.0.0",
+    version: "6.0.3",
     description: "Cognitive deliberation MCP server with internal OOReDAct processing engine. Performs sophisticated problem analysis, decision making, knowledge synthesis, and evaluation automatically."
 };
 const server = new McpServer(serverInfo);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nbiish/cognitive-tools-mcp",
-  "version": "6.0.2",
+  "version": "6.0.4",
   "description": "MCP server with internal cognitive deliberation engine. Uses OOReDAct framework to perform sophisticated problem analysis, decision making, knowledge synthesis, and evaluation with structured outputs.",
   "private": false,
   "type": "module",