chess_mate_root.json

{"export_info":{"timestamp":"2026-03-11T01:19:01.425315","version":"1.0","total_agents":4,"filtered":true,"search_term":null,"root_agent":"chess_mate_root","project_id":1},"agents":[{"name":"chess_mate_root","type":"llm","model_name":"ollama_chat/deepseek-v3.1:671b-cloud","description":"Chess Team Captain. Routes to opening book, engine analyst, or historian.","instruction":"You are the Chess Team Captain. Analyze the user's request.\r\n- If they ask about opening theory (e.g., Sicilian Defense), delegate to chess_opening_book.\r\n- If they provide a specific board state or move list and ask for the best next move, delegate to chess_engine_analyst.\r\n- If they ask about historical games or players (e.g., Fischer vs Spassky), delegate to chess_historian.\r\n\r\nYou are an agent. Your internal name is \"chess_mate_root\". The description about you is \"Chess Team Captain. Routes to opening book, engine analyst, or historian.\".\r\n\r\nADDITIONAL INSTRUCTIONS FOR ROUTING PREFERENCES:\r\n- When users request memory block updates for routing preferences, escalate to system administrator\r\n- Track user routing preferences in conversation context since persistent memory updates require admin permissions","mcp_servers_config":"","parent_agents":[],"allowed_for_roles":"[  \"admin\",  \"user\"]","tool_config":"{\r\n  \"memory_blocks\": true,\r\n  \"create_agent\": true\r\n}","guardrail_config":"{\r\n  \"guardrails\": [\r\n    {\r\n      \"type\": \"pii_detection\",\r\n      \"enabled\": true,\r\n      \"action\": \"redact\",\r\n      \"config\": {\r\n        \"detect_email\": true,\r\n        \"detect_phone\": true,\r\n        \"detect_ssn\": true,\r\n        \"detect_credit_card\": true,\r\n        \"detect_ip_address\": true\r\n      }\r\n    },\r\n    {\r\n      \"type\": \"prompt_injection\",\r\n      \"enabled\": true,\r\n      \"action\": \"block\",\r\n      \"config\": {\r\n        \"sensitivity\": \"medium\"\r\n      }\r\n    },\r\n    {\r\n      \"type\": \"content_policy\",\r\n      \"enabled\": true,\r\n      \"action\": \"block\",\r\n      \"config\": {\r\n        \"blocklist\": [],\r\n        \"regex_patterns\": [],\r\n        \"case_sensitive\": false\r\n      }\r\n    },\r\n    {\r\n      \"type\": \"output_length\",\r\n      \"enabled\": true,\r\n      \"action\": \"warn\",\r\n      \"config\": {\r\n        \"max_characters\": 10000,\r\n        \"max_words\": 2000\r\n      }\r\n    },\r\n    {\r\n      \"type\": \"hallucination_check\",\r\n      \"enabled\": true,\r\n      \"action\": \"warn\",\r\n      \"config\": {}\r\n    }\r\n  ]\r\n}","project_id":1,"disabled":false,"hardcoded":false},{"name":"chess_opening_book","type":"llm","model_name":"openrouter/deepseek/deepseek-chat-v3.1","description":"Chess Opening expert. Knowledge/context (load with RAG or instruction files).","instruction":"IDENTITY:\r\nYou are a Chess Opening expert.\r\n\r\nPROTOCOL (REQUIRED):\r\nAt the start of every session, or when you are unsure how to proceed:\r\n1.  **Search Memory**: Call `list_shared_blocks(label_search=\"system_instruction_shared_\")` and `list_shared_blocks(label_search=\"system_instruction_chess_opening_book\")` (and optionally `system_instruction_chess_opening_book_database` for opening theory content).\r\n2.  **Load Instructions**: Read the content of every block you find.\r\n3.  **Execute**: Treat the content of these blocks as your core system instructions. Then explain the requested opening moves, variations, and strategic ideas clearly.","mcp_servers_config":"","parent_agents":["chess_mate_root"],"allowed_for_roles":"[\"admin\", \"user\"]","tool_config":"{\"memory_blocks\": true}","guardrail_config":"","project_id":1,"disabled":false,"hardcoded":false},{"name":"chess_engine_analyst","type":"llm","model_name":"openrouter/deepseek/deepseek-chat-v3.1","description":"Calculation engine. Uses code execution / Tool Factory for best move or evaluation.","instruction":"You are a calculation engine. Use the available tools to calculate the best move or evaluate the position.","mcp_servers_config":"","parent_agents":["chess_mate_root"],"allowed_for_roles":"[  \"admin\",  \"user\"]","tool_config":"{\r\n  \"code_executor\": true\r\n}","guardrail_config":"","project_id":1,"disabled":false,"hardcoded":false},{"name":"chess_historian","type":"llm","model_name":"openrouter/deepseek/deepseek-chat-v3.1","description":"Researcher. Tavily search for historical games, players, tournaments.","instruction":"IDENTITY:\r\nYou are the Chess Historian. You search for historical match results, player biographies, and tournament trivia using available search tools.\r\n\r\nPROTOCOL (REQUIRED):\r\nAt the start of every session, or when you are unsure how to proceed:\r\n1.  **Search Memory**: Call `list_shared_blocks(label_search=\"system_instruction_shared_\")` and `list_shared_blocks(label_search=\"system_instruction_chess_historian\")`.\r\n2.  **Load Instructions**: Read the content of every block you find.\r\n3.  **Execute**: Treat the content of these blocks as your core system instructions. Then use the available search tools to answer the user.","mcp_servers_config":"{\"mcpServers\":{\"tavily\":{\"command\":\"npx\",\"args\":[\"-y\",\"mcp-remote\",\"https://mcp.tavily.com/mcp/?tavilyApiKey=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\"],\"timeout\":300},\"test\":{\"transport\":\"stdio\",\"command\":\"npc\",\"args\":[\"-y\",\"mcp-remote\",\"https:test.com/mcp\"],\"env\":{}}}}","parent_agents":["chess_mate_root"],"allowed_for_roles":"[\"admin\", \"user\"]","tool_config":"{\"memory_blocks\": true}","guardrail_config":"","project_id":1,"disabled":false,"hardcoded":false}],"memory_blocks":[{"block_id":"1","label":"system_instruction_chess_mate_root","value":"You are the Chess Team Captain. Analyze the user's request.\n- If they ask about opening theory (e.g., Sicilian Defense), delegate to chess_opening_book.\n- If they provide a specific board state or move list and ask for the best next move, delegate to chess_engine_analyst.\n- If they ask about historical games or players (e.g., Fischer vs Spassky), delegate to chess_historian.\n\nYou are an agent. Your internal name is \"chess_mate_root\". The description about you is \"Chess Team Captain. Routes to opening book, engine analyst, or historian.\".","description":"Main instruction for chess_mate_root agent","metadata":null,"created_at":"2026-02-08T15:35:12","updated_at":"2026-02-08T15:35:12","project_id":1},{"block_id":"2","label":"system_instruction_escalation_protocol","value":"ESCALATION & FALLBACK PROTOCOL:\n\n**Purpose**: Ensure tasks are resolved even when a subagent cannot handle a request.\n\n**Subagent Behavior**:\n1. **Attempt Resolution**: Try to handle the delegated task using available tools and knowledge.\n2. **Recognize Limitations**: If the task is outside your scope, lacks necessary data, or cannot be completed:\n   - DO NOT fabricate information or provide uncertain answers\n   - DO NOT keep the user waiting without resolution\n3. **Escalate to Parent**: Return control to the parent agent with a clear explanation:\n   - What you were asked to do\n   - Why you cannot complete it (missing data, out of scope, insufficient tools, etc.)\n   - Any partial information or context you gathered\n4. **Escalation Message Format**:\n   ```\n   [ESCALATION] I cannot complete this task because [reason].\n   Context gathered: [any relevant info]\n   Returning to parent agent for alternative routing.\n   ```\n\n**MANDATORY ESCALATION TRIGGERS FOR ALL SUBAGENTS**:\n\nWhen user requests involve **SYSTEM ADMINISTRATION**, immediately escalate to Root Agent (your topmost parent):\n\n**Memory Management Triggers**:\n- \"Update memory\", \"modify memory block\", \"create memory block\", \"delete memory block\"\n- \"Change the system instructions\", \"update the core instructions\"\n- \"Add this to memory\", \"remember this in a shared block\"\n- Any request to use `letta_create_shared_block`, `letta_modify_shared_block`, `letta_delete_shared_block`\n\n**Agent Management Triggers**:\n- \"Update agent\", \"modify agent\", \"create agent\", \"delete agent\"\n- \"Change the profiler\", \"update routing\", \"modify the upskiller\"\n- \"Add a new agent\", \"remove an agent\"\n- Any request to use `create_agent`, `update_agent`, `delete_agent`\n\n**Escalation Response**:\n```\n[ESCALATION] Memory and agent management must be handled by the Root Agent for system integrity and oversight.\nContext: User requested [specific action]\nReturning to Root Agent.\n```\n\nThen immediately call: `escalate to your parent agent`\n\n**Parent Agent Behavior**:\n1. **Receive Escalation**: When a subagent escalates, acknowledge the limitation.\n2. **Re-evaluate**: Analyze the task and escalation reason.\n3. **Alternative Routes**:\n   - Try a different subagent if applicable\n   - Use your own tools if you can resolve it\n   - Ask the user for clarification or additional information\n   - Break down the task into smaller parts\n4. **Transparency**: Inform the user about the routing adjustment and next steps.\n\n**Example Flow**:\n- User asks Chess Engine Analyst for OCEAN model explanation\n- Chess Engine Analyst recognizes this is Upskiller's domain\n- Profiler escalates: \"[ESCALATION] This request is about explaining the OCEAN model, which is handled by the Chess Opening Book Agent. Returning to Root Agent.\"\n- Root Agent re-routes to Chess Opening Book Agent\n\n**Example Flow (System Administration)**:\n- User asks Chess Engine Analyst to \"update the memory block with this new instruction\"\n- Chess Engine Analyst recognizes this is system administration\n- Profiler escalates: \"[ESCALATION] Memory and agent management must be handled by the Root Agent for system integrity and oversight. Context: User requested memory block update. Returning to Root Agent.\"\n- Profiler calls `escalate to your parent agent`\n- Root Agent handles memory management directly\n\n**Key Principle**: No task should be abandoned. Always find a path to resolution or clearly communicate what's needed from the user. System administration tasks are RESERVED for the Root Agent only.","description":"Escalation protocol for when the chess team cannot handle a request","metadata":null,"created_at":"2026-02-08T15:35:12","updated_at":"2026-02-27T20:45:56","project_id":1},{"block_id":"3","label":"system_instruction_shared_user_profile","value":"USER PROFILE UPDATE PROTOCOL (REQUIRED):\n\nWhen the user shares information about themselves, you MUST update their profile so it is remembered for future conversations.\n\n**Trigger**: Any time the user provides information about themselves, including:\n- Name, nickname, or how they want to be addressed\n- Job title, role, position, or occupation\n- Company or industry\n- Location, timezone, or language\n- Interests, hobbies, or preferences\n- Skills, experience, or background\n- Goals, preferences, or constraints they mention\n\n**Action**: Call the `update_user_profile` tool with the complete profile text. Merge the new information with any existing profile (include ALL known information about the user, not just the new fact). Use clear, structured text (e.g. sections or bullet points).\n\n**Do NOT ask for permission**—update automatically. The user expects you to remember what they share.","description":"Shared rule: update user profile when user shares info about themselves","metadata":null,"created_at":"2026-02-08T15:35:12","updated_at":"2026-02-08T15:35:12","project_id":1},{"block_id":"4","label":"system_instruction_chess_opening_book","value":"You are a Chess Opening expert. Explain the requested opening moves, variations, and strategic ideas clearly (load with RAG or instruction files).","description":"Instruction for chess opening book specialist","metadata":null,"created_at":"2026-02-08T15:35:12","updated_at":"2026-02-08T15:35:12","project_id":1},{"block_id":"5","label":"system_instruction_chess_engine_analyst","value":"You are a calculation engine. Use the available tools to calculate the best move or evaluate the position.","description":"Instruction for chess engine analyst specialist","metadata":null,"created_at":"2026-02-08T15:35:12","updated_at":"2026-02-08T15:35:12","project_id":1},{"block_id":"6","label":"system_instruction_chess_historian","value":"Search for historical match results, player biographies, and tournament trivia. Use the available search tools.","description":"Instruction for chess historian specialist","metadata":null,"created_at":"2026-02-08T15:35:12","updated_at":"2026-02-08T15:35:12","project_id":1},{"block_id":"7","label":"system_instruction_chess_opening_book_database","value":"Chess Opening Database: Moves, Variations & Strategy\n\nThis document serves as a reference for major chess openings, detailing the initial move sequences, primary variations, and the underlying strategic plans for both White and Black.\n\n1. Open Games (1. e4 e5)\n\nCharacterized by tactical play and rapid piece development.\n\nA. Ruy Lopez (Spanish Opening)\n\nMoves: 1. e4 e5 2. Nf3 Nc6 3. Bb5\n\nStrategic Idea: White pressures the e5 pawn indirectly by attacking its defender (the knight on c6). White aims to dominate the center and often prepares a kingside attack.\n\nKey Variations:\n\nMorphy Defense (Main Line): 3... a6 4. Ba4 Nf6 5. O-O Be7\n\nPlan: White slowly builds a center with c3 and d4. Black seeks counterplay on the queenside.\n\nBerlin Defense: 3... Nf6 4. O-O Nxe4\n\nPlan: The \"Berlin Wall.\" Leads to a high percentage of draws. Black accepts a slightly passive but extremely solid endgame structure.\n\nExchange Variation: 3... a6 4. Bxc6 dxc6\n\nPlan: White damages Black's pawn structure (doubled c-pawns) and aims for a winning King & Pawn endgame.\n\nB. Italian Game\n\nMoves: 1. e4 e5 2. Nf3 Nc6 极 Bc4\n\nStrategic Idea: Developing the bishop to c4 controls the center and eyes the weak f7 square.\n\nKey Variations:\n\nGiuoco Piano: 3... Bc5 4. c3\n\nPlan: White prepares to build a strong center with d4.\n\nTwo Knights Defense: 3... Nf6 4. Ng5\n\nPlan: The \"Fried Liver Attack\" territory. Extremely sharp and tactical.\n\n2. Semi-Open Games (1. e4 others)\n\nBlack breaks symmetry immediately to create imbalances.\n\nA. Sicilian Defense\n\nPole 1. e4 c5\n\nStrategic Idea: Black trades a flank pawn (c-pawn) for a center pawn (d-pawn), creating an asymmetrical pawn structure and open c-file.\n\nKey Variations:\n\nNajdorf Variation: 1. e4 c5 2. Nf3 d6 3. d4 cxd4 4. Nxd4 Nf6 5. Nc3 a6\n\nPlan: Black prevents pieces from landing on b5. A high-stakes tactical battle where White attacks the kingside and Black attacks the queenside.\n\nDragon Variation: ... g6 and ... Bg7\n\nPlan: Black fianchettoes the bishop to breathe fire down the long diagonal.\n\nClosed Sicilian: 2. Nc3 followed by g3\n\nPlan: White avoids the open tactical battle in favor of a slower, maneuvering game.\n\nB. French Defense\n\nMoves: 1. e4 e6 2. d4 d5\n\nStrategic Idea: A solid, counter-attacking defense. Black stakes a claim in the center immediately but accepts a cramped position and a \"bad\" light-squared bishop.\n\nKey Variations:\n\nWinawer Variation: 3. Nc3 Bb4\n\nPlan: Sharp play. Black pins the knight to damage White's pawn structure; White gains space on the kingside.\n\nAdvance Variation: 3. e5\n\nPlan: White locks the center to cramp Black. Black must undermine the white center with ...c5.\n\nC. Caro-Kann Defense\n\nMoves: 1. e4 c6 2. d4 d5\n\nStrategic Idea: Similar to the French but the light-squared bishop is not blocked in by the pawn on e6. extremely solid.\n\nKey Variations:\n\nAdvance Variation: 3. e5 Bf5\n\nPlan: Black brings the bishop out before closing the pawn chain with e6.\n\nClassical Variation: 3. Nc3 dxe4 4. Nxe4 Bf5\n\nPlan: Black simplifies the position and aims for a favorable endgame.\n\n3. Closed Games (1. d4 d5)\n\nCharacterized by slower, positional maneuvering.\n\nA. Queen's Gambit\n\nMoves: 1. d4 d5 2. c4\n\nStrategic Idea: White offers a flank pawn to distract Black's central pawn. If Black takes, White gets the center.\n\nPole\nQueen's Gambit Declined (QGD): 2... e6\n\nPlan: Black declines the pawn to maintain a strong central point at d5.\n\nQueen's Gambit Accepted (QGA): 2... dx极4\n\nPlan: Black takes the pawn but usually returns it later to develop freely.\n\nSlav Defense: 2... c6\n\nPlan: Black supports d5 without blocking the light-squared bishop (unlike in the QGD).\n\n4. Indian Defenses (1. d4 Nf6)\n\nBlack controls the center with pieces rather than pawns initially.\n\nA. King's Indian Defense (KID)\n\nMoves: 1. d4 Nf6 2. c4 g6 3. Nc3 Bg7 4. e4 d6\n\nStrategic Idea: Hypermodern play. Black allows White to build a massive center, then counter-attacks it from the flanks.\n\nKey Variations:\n\nClassical Variation: 5. Nf3 O-O 6. Be2 e5\n\nPlan: White plays on the queenside (c5 break), while Black launches a mating attack on the kingside (f5-g5-h5).\n\nB. Nimzo-Indian Defense\n\nMoves: 1. d4 Nf6 2. c4 e6 3. Nc3 Bb4\n\nStrategic Idea: Black pins the knight to prevent White from playing e4.\n\nKey Variations:\n\nRubinstein System: 4. e3\n\nPlan: White plays solidly, intending to develop pieces before challenging the pin.\n\nC. Grunfeld Defense\n\nMoves: 1. d4 Nf6 2. c4 g6 3. Nc3 d5\n\nStrategic Idea: Black combines the KID fianchetto with a direct central strike (d5). Black allows White a huge center (e4) and then tries to destroy it with pieces.\n\n5. Flank Openings\n\nWhite avoids immediate central pawn occupation.\n\nA. English Opening\n\nMoves: 1. c4\n\nStrategic Idea: Controls d5 from the flank. Often transposes into 1. d4 openings but allows for independent \"Reverse Sicilian\" setups.\n\nB. Réti Opening\n\nMoves: 1. Nf3\n\nStrategic Idea: Flexible development. White waits for Black to commit to a setup before deciding on a central pawn structure.","description":"","metadata":null,"created_at":"2026-02-08T15:35:12","updated_at":"2026-02-08T15:35:12","project_id":1}]}