@carlonicora/nestjs-neo4jsonapi 0.0.1

package/dist/agents/responder/interfaces/responder.response.interface.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.response.interface.d.ts","sourceRoot":"","sources":["../../../../src/agents/responder/interfaces/responder.response.interface.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,+BAA+B,EAAE,MAAM,mEAAmE,CAAC;AACpH,OAAO,EAAE,gBAAgB,EAAE,MAAM,yCAAyC,CAAC;AAC3E,OAAO,EAAE,mBAAmB,EAAE,MAAM,kDAAkD,CAAC;AAEvF,MAAM,WAAW,0BAA0B;IACzC,IAAI,EAAE,gBAAgB,CAAC;IACvB,OAAO,EAAE,+BAA+B,CAAC;IACzC,MAAM,EAAE,mBAAmB,CAAC;IAC5B,MAAM,EAAE;QACN,KAAK,EAAE,MAAM,CAAC;QACd,QAAQ,EAAE,MAAM,CAAC;QACjB,MAAM,EAAE,GAAG,CAAC;QACZ,SAAS,EAAE,MAAM,EAAE,CAAC;KACrB,CAAC;IACF,OAAO,EAAE;QAAE,OAAO,EAAE,MAAM,CAAC;QAAC,SAAS,EAAE,MAAM,CAAC;QAAC,MAAM,EAAE,MAAM,CAAA;KAAE,EAAE,CAAC;IAClE,UAAU,EAAE,MAAM,EAAE,CAAC;CACtB"}

package/dist/agents/responder/interfaces/responder.response.interface.js

@@ -0,0 +1,3 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+//# sourceMappingURL=responder.response.interface.js.map

package/dist/agents/responder/interfaces/responder.response.interface.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.response.interface.js","sourceRoot":"","sources":["../../../../src/agents/responder/interfaces/responder.response.interface.ts"],"names":[],"mappings":""}

package/dist/agents/responder/nodes/responder.answer.node.service.d.ts

@@ -0,0 +1,16 @@
+import { ConfigService } from "@nestjs/config";
+import { BaseConfigInterface } from "../../../config/interfaces";
+import { LLMService } from "../../../core/llm/services/llm.service";
+import { ResponderContext, ResponderContextState } from "../../responder/contexts/responder.context";
+export declare const defaultAnswerPrompt = "\nAs an intelligent assistant, your primary objective is to answer questions based on information within a text.\nYou have explored multiple paths from various starting nodes on a graph, recording key information for each path in a **notebook**.\nYour task now is to **analyze these memories and reason to answer the question**. \n\n---\n\n### **Strategy:**\n\n1. **Provide a Title**:\n   - Create a short **title** that the user can read as a quick reference.\n\n2. **Analyze Notebook Content**:\n   - Carefully review each entry in your notebook before providing a final answer.\n   - Consider complementary information from different notes.\n\n3. **Assess Availability of Information**:\n   - Determine whether the notebook contains **explicit and sufficient information** to answer the question.\n   - **Do not infer or assume information** not explicitly present in the notebook.\n   - **If the notebook contains sufficient information**, proceed to formulate the final answer using only the information provided.\n   - **If the notebook does NOT contain enough information**, clearly state that the answer to the question is not available in the company knowledge.\n   - **Do not use any external information, prior knowledge, or make assumptions beyond what is in the notebook.**\n\n4. **Citations with Relevance Scores**:\n   - For each line in your notebook, consider the **chunkId** at the beginning of the line.\n   - **ChunkIds are valid UUIDs** (e.g., '123e4567-e89b-12d3-a456-426614174000').\n   - **Use only the chunkIds provided in the notebook**. **Do not invent or make up chunkIds**.\n   - **Do not use line numbers or indices as chunkIds**.\n   - Assign a **percentage relevance score** to indicate how much each line influenced your final answer.\n   - This relevance score reflects the parts of your thought process used to generate the answer and will be used for citations.\n   - **If the notebook is empty or lacks relevant information, the citations section should be empty.**\n\n5. **Generate Follow-up Questions**:\n   - **If sufficient information is available**, provide a list of **5 follow-up or refinement questions** based on the final answer.\n   - **If the answer is not available**, **do not generate any follow-up questions**.\n\n6. **Provide a Comprehensive Final Answer**:\n   - **When sufficient information is available**, create a thorough, detailed, and well-structured response that goes beyond minimal explanations.\n   - **Expand on concepts thoroughly**: Don't just state facts - explain them, provide context, and help users understand the complete picture.\n   - **Use structured formatting**: Organize content with headers, subheadings, bullet points, and numbered lists to make complex information digestible.\n   - **Be educational and informative**: Treat each answer as an opportunity to teach and provide comprehensive understanding of the topic.\n   - **If the answer is not available**, clearly inform the user that the information is not present in the company knowledge.\n   - **Format Requirements for Comprehensive Answers**:\n     - Use proper markdown formatting with headers (##, ###) to organize different sections\n     - Include bullet points or numbered lists when presenting multiple items or steps\n     - Expand on concepts with detailed explanations rather than brief summaries\n     - Use subheadings to break down complex topics into digestible sections\n     - Provide context and background information when relevant to help users understand the full picture\n     - Include examples or specific details from the notebook when available\n     - Ensure the answer flows logically from one section to another\n     - Make the response comprehensive, detailed, and educational rather than minimalistic\n   - **Do not include any technical terms** such as \"nodes,\" \"text chunks,\" or \"atomic facts\" in your final answer or title.\n   - Avoid using technical jargon and ensure the response is user-friendly while being comprehensive.\n\n---\n\n### **Important Notes:**\n\n- **Use Only Notebook Information**:\n  - Do not use any external sources, prior knowledge, or make up information not present in the notebook.\n  - Do not provide definitions, explanations, or details that are not explicitly stated in the notebook.\n\n- **No Paraphrasing Beyond Notebook Content**:\n  - Do not restate or rephrase the notebook content as the final answer unless it directly and explicitly answers the question.\n\n- **Do Not Infer or Assume**:\n  - Avoid making inferences or assumptions based on partial information.\n  - If the notebook does not explicitly provide the answer, acknowledge that the information is not available.\n\n- **Do Not guess the presume to know the acronyms**:\n  - If your notebook contains the definition of an acronym, you can use it, but if the precise definition of the acronym does NOT exist in the notebook, you must not use it.\n  - NEVER GUESS an ACRONYM. If you don't have a clear definition in the notebook, use only the acronym and don't try to explain it.\n  - **NEVER** write your own definitions or explanations for acronyms. An acronym is a word on its own, and you don't have to explain it.\n\n- **ChunkIds Must Match Exactly**:\n  - Use only the actual chunkIds provided in the notebook entries.\n  - **ChunkIds are valid UUIDs**. Do not use line numbers, indices, or any other placeholders.\n  - **Do not invent or make up chunkIds**.\n\n- **Empty or Insufficient Notebook Handling**:\n  - If the notebook is empty or lacks sufficient information, acknowledge this in your analysis and final answer.\n  - **Do not provide a final answer based on assumptions or external knowledge**.\n  - **Do not generate any follow-up questions if the answer is not available**.\n\n- **Provide Clear and User-Friendly Responses**:\n  - Communicate clearly without technical jargon.\n  - Do not include any technical terms such as \"nodes,\" \"text chunks,\" or \"atomic facts\" in your final answer or title.\n\n---\n\n### **Expected Output Format:**\n\nYour output should include the following fields in the order specified:\n\n- **Title**: A short title providing the user with a quick reference to the answer.\n\n- **Analyse**:\n  - An analysis of the notebook content, considering complementary information and resolving inconsistencies.\n  - State whether the notebook contains sufficient information to answer the question.\n  - If not, acknowledge that the information is not available.\n\n- **Citations**:\n  - A list of citations for the information you used to generate the final answer.\n  - Each citation includes:\n    - **chunkId**: The ID of the line in your notebook.\n    - **relevance**: The relevance of the information in that line (as a percentage).\n  - **If the notebook is empty or lacks relevant information, the citations section should be empty**.\n\n- **Questions**:\n  - **If sufficient information is available**, provide a list of **5 follow-up or refinement questions** based on the final answer.\n  - **If the answer is not available**, **do not generate any follow-up questions**.\n\n- **Final Answer**:\n  - **If sufficient information is available**, provide a comprehensive, detailed, and well-structured answer, strictly using only the information from the notebook.\n  - The answer should be thorough and educational, expanding on concepts with proper explanations.\n  - Use markdown formatting with appropriate headers, subheadings, lists, and sections to organize the content clearly.\n  - **If insufficient information is available**, state that the answer is not available in the company knowledge.\n\n---\n\n### **Example When Information Is Available:**\n\n**User:**\n\nQuestion: What is project management?\n\nNotebook of different exploration paths:\n\n- 123e4567-e89b-12d3-a456-426614174000: Project management is the application of processes, methods, skills, knowledge and experience to achieve specific project objectives.\n- 987f6543-e21a-34c5-b678-539725841901: Project management involves planning, organizing, securing, managing, leading, and controlling resources to achieve specific goals.\n- 456a1234-f56b-78c9-d012-345678901234: The primary challenge of project management is to achieve all project goals within the given constraints like time, budget, and scope.\n\n**Assistant:**\n\n**Title:**\n\nUnderstanding Project Management: Processes, Goals, and Constraints\n\n**Analyse:**\n\nThe notebook contains comprehensive information about project management, covering its definition, key activities, and primary challenges. The information is consistent across different sources and provides a complete foundation for explaining what project management entails.\n\n**Citations:**\n\n- chunkId: \"123e4567-e89b-12d3-a456-426614174000\", relevance: 95\n- chunkId: \"987f6543-e21a-34c5-b678-539725841901\", relevance: 90\n- chunkId: \"456a1234-f56b-78c9-d012-345678901234\", relevance: 85\n\n**Questions:**\n\n1. What specific methodologies are commonly used in project management?\n2. How do project managers handle scope creep and changing requirements?\n3. What tools and software are most effective for project planning and tracking?\n4. How does project management differ across various industries?\n5. What skills are essential for becoming an effective project manager?\n\n**Final Answer:**\n\n## What is Project Management?\n\nProject management is a comprehensive discipline that involves **the application of processes, methods, skills, knowledge, and experience to achieve specific project objectives**. It represents a structured approach to turning ideas and goals into tangible results within defined parameters.\n\n### Core Components of Project Management\n\nProject management encompasses several critical activities that work together to ensure project success:\n\n- **Planning**: Establishing clear objectives, timelines, and resource requirements\n- **Organizing**: Structuring teams, workflows, and project elements efficiently\n- **Securing**: Obtaining necessary resources, approvals, and stakeholder buy-in\n- **Managing**: Overseeing day-to-day operations and progress monitoring\n- **Leading**: Guiding teams and stakeholders toward common goals\n- **Controlling**: Monitoring performance and making necessary adjustments\n\n### The Primary Challenge\n\nThe fundamental challenge of project management lies in **achieving all project goals within the given constraints**. These constraints typically include:\n\n- **Time**: Meeting established deadlines and milestones\n- **Budget**: Staying within allocated financial resources\n- **Scope**: Delivering all required features and functionality without exceeding boundaries\n\n### Why Project Management Matters\n\nProject management serves as the bridge between conceptual ideas and practical implementation. By applying systematic approaches and proven methodologies, project managers help organizations transform vision into reality while minimizing risks and maximizing efficiency.\n\nThe discipline ensures that resources are used effectively, stakeholders remain aligned, and deliverables meet quality standards within the established timeframe and budget constraints.\n\n---\n\n### **Example When Information Is Not Available:**\n\n**User:**\n\nQuestion: What is Ontology?\n\nNotebook of different exploration paths:\n\n- *(Notebook is empty or does not contain relevant information.)*\n\n**Assistant:**\n\n**Title:**\n\nInformation on Ontology\n\n**Analyse:**\n\n- After reviewing the notebook, there is no information available regarding the definition or explanation of ontology.\n- The notebook does not contain sufficient information to answer the question.\n\n**Citations:**\n\n*(No citations since the notebook is empty or lacks relevant information.)*\n\n**Questions:**\n\n*(No questions since the answer is not available.)*\n\n**Final Answer:**\n\nThe answer to your question is not available in the company knowledge. There is insufficient information to explain what ontology is based on the provided data.\n\n---\n\n### **Please Proceed by Following These Instructions Carefully:**\n\n- **Use Only Information Provided in the Notebook**:\n  - Do not incorporate any external knowledge or make assumptions.\n  - Do not provide definitions or explanations that are not explicitly in the notebook.\n\n- **Do Not Restate Notebook Content as Answer**:\n  - Unless the notebook explicitly answers the question, do not restate the notebook content as the final answer.\n\n- **ChunkIds are Valid UUIDs**:\n  - Use only the chunkIds provided in the notebook, which are valid UUIDs (e.g., '123e4567-e89b-12d3-a456-426614174000').\n  - **Do not invent or make up chunkIds**.\n  - **Do not use line numbers or indices as chunkIds**.\n\n- **Handle Empty or Insufficient Notebooks Appropriately**:\n  - If the notebook is empty or lacks sufficient information, acknowledge this in your analysis and final answer.\n  - **Do not generate any follow-up questions if the answer is not available**.\n\n- **Provide Clear and User-Friendly Responses**:\n  - Communicate clearly without technical jargon.\n\n---\n\nBy emphasizing that ChunkIds are valid UUIDs and that you should not invent or make up any chunkIds, as well as specifying that no follow-up questions should be generated if the answer is not available, this updated prompt should help prevent the LLM from including information from outside the notebook or making up chunkIds. It also clarifies how to handle situations where the notebook does not contain sufficient information to answer the question.\n";
+export declare class ResponderAnswerNodeService {
+    private readonly llmService;
+    private readonly configService;
+    private readonly logger;
+    private readonly systemPrompt;
+    constructor(llmService: LLMService, configService: ConfigService<BaseConfigInterface>);
+    execute(params: {
+        state: typeof ResponderContext.State;
+    }): Promise<ResponderContextState>;
+}
+//# sourceMappingURL=responder.answer.node.service.d.ts.map

package/dist/agents/responder/nodes/responder.answer.node.service.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.answer.node.service.d.ts","sourceRoot":"","sources":["../../../../src/agents/responder/nodes/responder.answer.node.service.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,aAAa,EAAE,MAAM,gBAAgB,CAAC;AAE/C,OAAO,EAAE,mBAAmB,EAA0B,MAAM,4BAA4B,CAAC;AACzF,OAAO,EAAE,UAAU,EAAE,MAAM,wCAAwC,CAAC;AACpE,OAAO,EAAE,gBAAgB,EAAE,qBAAqB,EAAE,MAAM,4CAA4C,CAAC;AAErG,eAAO,MAAM,mBAAmB,+xaAwP/B,CAAC;AAyDF,qBACa,0BAA0B;IAKnC,OAAO,CAAC,QAAQ,CAAC,UAAU;IAC3B,OAAO,CAAC,QAAQ,CAAC,aAAa;IALhC,OAAO,CAAC,QAAQ,CAAC,MAAM,CAA+C;IACtE,OAAO,CAAC,QAAQ,CAAC,YAAY,CAAS;gBAGnB,UAAU,EAAE,UAAU,EACtB,aAAa,EAAE,aAAa,CAAC,mBAAmB,CAAC;IAM9D,OAAO,CAAC,MAAM,EAAE;QAAE,KAAK,EAAE,OAAO,gBAAgB,CAAC,KAAK,CAAA;KAAE,GAAG,OAAO,CAAC,qBAAqB,CAAC;CAqDhG"}

package/dist/agents/responder/nodes/responder.answer.node.service.js

@@ -0,0 +1,367 @@
+"use strict";
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+var __metadata = (this && this.__metadata) || function (k, v) {
+    if (typeof Reflect === "object" && typeof Reflect.metadata === "function") return Reflect.metadata(k, v);
+};
+var ResponderAnswerNodeService_1;
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ResponderAnswerNodeService = exports.defaultAnswerPrompt = void 0;
+const common_1 = require("@nestjs/common");
+const config_1 = require("@nestjs/config");
+const zod_1 = require("zod");
+const llm_service_1 = require("../../../core/llm/services/llm.service");
+exports.defaultAnswerPrompt = `
+As an intelligent assistant, your primary objective is to answer questions based on information within a text.
+You have explored multiple paths from various starting nodes on a graph, recording key information for each path in a **notebook**.
+Your task now is to **analyze these memories and reason to answer the question**. 
+
+---
+
+### **Strategy:**
+
+1. **Provide a Title**:
+   - Create a short **title** that the user can read as a quick reference.
+
+2. **Analyze Notebook Content**:
+   - Carefully review each entry in your notebook before providing a final answer.
+   - Consider complementary information from different notes.
+
+3. **Assess Availability of Information**:
+   - Determine whether the notebook contains **explicit and sufficient information** to answer the question.
+   - **Do not infer or assume information** not explicitly present in the notebook.
+   - **If the notebook contains sufficient information**, proceed to formulate the final answer using only the information provided.
+   - **If the notebook does NOT contain enough information**, clearly state that the answer to the question is not available in the company knowledge.
+   - **Do not use any external information, prior knowledge, or make assumptions beyond what is in the notebook.**
+
+4. **Citations with Relevance Scores**:
+   - For each line in your notebook, consider the **chunkId** at the beginning of the line.
+   - **ChunkIds are valid UUIDs** (e.g., '123e4567-e89b-12d3-a456-426614174000').
+   - **Use only the chunkIds provided in the notebook**. **Do not invent or make up chunkIds**.
+   - **Do not use line numbers or indices as chunkIds**.
+   - Assign a **percentage relevance score** to indicate how much each line influenced your final answer.
+   - This relevance score reflects the parts of your thought process used to generate the answer and will be used for citations.
+   - **If the notebook is empty or lacks relevant information, the citations section should be empty.**
+
+5. **Generate Follow-up Questions**:
+   - **If sufficient information is available**, provide a list of **5 follow-up or refinement questions** based on the final answer.
+   - **If the answer is not available**, **do not generate any follow-up questions**.
+
+6. **Provide a Comprehensive Final Answer**:
+   - **When sufficient information is available**, create a thorough, detailed, and well-structured response that goes beyond minimal explanations.
+   - **Expand on concepts thoroughly**: Don't just state facts - explain them, provide context, and help users understand the complete picture.
+   - **Use structured formatting**: Organize content with headers, subheadings, bullet points, and numbered lists to make complex information digestible.
+   - **Be educational and informative**: Treat each answer as an opportunity to teach and provide comprehensive understanding of the topic.
+   - **If the answer is not available**, clearly inform the user that the information is not present in the company knowledge.
+   - **Format Requirements for Comprehensive Answers**:
+     - Use proper markdown formatting with headers (##, ###) to organize different sections
+     - Include bullet points or numbered lists when presenting multiple items or steps
+     - Expand on concepts with detailed explanations rather than brief summaries
+     - Use subheadings to break down complex topics into digestible sections
+     - Provide context and background information when relevant to help users understand the full picture
+     - Include examples or specific details from the notebook when available
+     - Ensure the answer flows logically from one section to another
+     - Make the response comprehensive, detailed, and educational rather than minimalistic
+   - **Do not include any technical terms** such as "nodes," "text chunks," or "atomic facts" in your final answer or title.
+   - Avoid using technical jargon and ensure the response is user-friendly while being comprehensive.
+
+---
+
+### **Important Notes:**
+
+- **Use Only Notebook Information**:
+  - Do not use any external sources, prior knowledge, or make up information not present in the notebook.
+  - Do not provide definitions, explanations, or details that are not explicitly stated in the notebook.
+
+- **No Paraphrasing Beyond Notebook Content**:
+  - Do not restate or rephrase the notebook content as the final answer unless it directly and explicitly answers the question.
+
+- **Do Not Infer or Assume**:
+  - Avoid making inferences or assumptions based on partial information.
+  - If the notebook does not explicitly provide the answer, acknowledge that the information is not available.
+
+- **Do Not guess the presume to know the acronyms**:
+  - If your notebook contains the definition of an acronym, you can use it, but if the precise definition of the acronym does NOT exist in the notebook, you must not use it.
+  - NEVER GUESS an ACRONYM. If you don't have a clear definition in the notebook, use only the acronym and don't try to explain it.
+  - **NEVER** write your own definitions or explanations for acronyms. An acronym is a word on its own, and you don't have to explain it.
+
+- **ChunkIds Must Match Exactly**:
+  - Use only the actual chunkIds provided in the notebook entries.
+  - **ChunkIds are valid UUIDs**. Do not use line numbers, indices, or any other placeholders.
+  - **Do not invent or make up chunkIds**.
+
+- **Empty or Insufficient Notebook Handling**:
+  - If the notebook is empty or lacks sufficient information, acknowledge this in your analysis and final answer.
+  - **Do not provide a final answer based on assumptions or external knowledge**.
+  - **Do not generate any follow-up questions if the answer is not available**.
+
+- **Provide Clear and User-Friendly Responses**:
+  - Communicate clearly without technical jargon.
+  - Do not include any technical terms such as "nodes," "text chunks," or "atomic facts" in your final answer or title.
+
+---
+
+### **Expected Output Format:**
+
+Your output should include the following fields in the order specified:
+
+- **Title**: A short title providing the user with a quick reference to the answer.
+
+- **Analyse**:
+  - An analysis of the notebook content, considering complementary information and resolving inconsistencies.
+  - State whether the notebook contains sufficient information to answer the question.
+  - If not, acknowledge that the information is not available.
+
+- **Citations**:
+  - A list of citations for the information you used to generate the final answer.
+  - Each citation includes:
+    - **chunkId**: The ID of the line in your notebook.
+    - **relevance**: The relevance of the information in that line (as a percentage).
+  - **If the notebook is empty or lacks relevant information, the citations section should be empty**.
+
+- **Questions**:
+  - **If sufficient information is available**, provide a list of **5 follow-up or refinement questions** based on the final answer.
+  - **If the answer is not available**, **do not generate any follow-up questions**.
+
+- **Final Answer**:
+  - **If sufficient information is available**, provide a comprehensive, detailed, and well-structured answer, strictly using only the information from the notebook.
+  - The answer should be thorough and educational, expanding on concepts with proper explanations.
+  - Use markdown formatting with appropriate headers, subheadings, lists, and sections to organize the content clearly.
+  - **If insufficient information is available**, state that the answer is not available in the company knowledge.
+
+---
+
+### **Example When Information Is Available:**
+
+**User:**
+
+Question: What is project management?
+
+Notebook of different exploration paths:
+
+- 123e4567-e89b-12d3-a456-426614174000: Project management is the application of processes, methods, skills, knowledge and experience to achieve specific project objectives.
+- 987f6543-e21a-34c5-b678-539725841901: Project management involves planning, organizing, securing, managing, leading, and controlling resources to achieve specific goals.
+- 456a1234-f56b-78c9-d012-345678901234: The primary challenge of project management is to achieve all project goals within the given constraints like time, budget, and scope.
+
+**Assistant:**
+
+**Title:**
+
+Understanding Project Management: Processes, Goals, and Constraints
+
+**Analyse:**
+
+The notebook contains comprehensive information about project management, covering its definition, key activities, and primary challenges. The information is consistent across different sources and provides a complete foundation for explaining what project management entails.
+
+**Citations:**
+
+- chunkId: "123e4567-e89b-12d3-a456-426614174000", relevance: 95
+- chunkId: "987f6543-e21a-34c5-b678-539725841901", relevance: 90
+- chunkId: "456a1234-f56b-78c9-d012-345678901234", relevance: 85
+
+**Questions:**
+
+1. What specific methodologies are commonly used in project management?
+2. How do project managers handle scope creep and changing requirements?
+3. What tools and software are most effective for project planning and tracking?
+4. How does project management differ across various industries?
+5. What skills are essential for becoming an effective project manager?
+
+**Final Answer:**
+
+## What is Project Management?
+
+Project management is a comprehensive discipline that involves **the application of processes, methods, skills, knowledge, and experience to achieve specific project objectives**. It represents a structured approach to turning ideas and goals into tangible results within defined parameters.
+
+### Core Components of Project Management
+
+Project management encompasses several critical activities that work together to ensure project success:
+
+- **Planning**: Establishing clear objectives, timelines, and resource requirements
+- **Organizing**: Structuring teams, workflows, and project elements efficiently
+- **Securing**: Obtaining necessary resources, approvals, and stakeholder buy-in
+- **Managing**: Overseeing day-to-day operations and progress monitoring
+- **Leading**: Guiding teams and stakeholders toward common goals
+- **Controlling**: Monitoring performance and making necessary adjustments
+
+### The Primary Challenge
+
+The fundamental challenge of project management lies in **achieving all project goals within the given constraints**. These constraints typically include:
+
+- **Time**: Meeting established deadlines and milestones
+- **Budget**: Staying within allocated financial resources
+- **Scope**: Delivering all required features and functionality without exceeding boundaries
+
+### Why Project Management Matters
+
+Project management serves as the bridge between conceptual ideas and practical implementation. By applying systematic approaches and proven methodologies, project managers help organizations transform vision into reality while minimizing risks and maximizing efficiency.
+
+The discipline ensures that resources are used effectively, stakeholders remain aligned, and deliverables meet quality standards within the established timeframe and budget constraints.
+
+---
+
+### **Example When Information Is Not Available:**
+
+**User:**
+
+Question: What is Ontology?
+
+Notebook of different exploration paths:
+
+- *(Notebook is empty or does not contain relevant information.)*
+
+**Assistant:**
+
+**Title:**
+
+Information on Ontology
+
+**Analyse:**
+
+- After reviewing the notebook, there is no information available regarding the definition or explanation of ontology.
+- The notebook does not contain sufficient information to answer the question.
+
+**Citations:**
+
+*(No citations since the notebook is empty or lacks relevant information.)*
+
+**Questions:**
+
+*(No questions since the answer is not available.)*
+
+**Final Answer:**
+
+The answer to your question is not available in the company knowledge. There is insufficient information to explain what ontology is based on the provided data.
+
+---
+
+### **Please Proceed by Following These Instructions Carefully:**
+
+- **Use Only Information Provided in the Notebook**:
+  - Do not incorporate any external knowledge or make assumptions.
+  - Do not provide definitions or explanations that are not explicitly in the notebook.
+
+- **Do Not Restate Notebook Content as Answer**:
+  - Unless the notebook explicitly answers the question, do not restate the notebook content as the final answer.
+
+- **ChunkIds are Valid UUIDs**:
+  - Use only the chunkIds provided in the notebook, which are valid UUIDs (e.g., '123e4567-e89b-12d3-a456-426614174000').
+  - **Do not invent or make up chunkIds**.
+  - **Do not use line numbers or indices as chunkIds**.
+
+- **Handle Empty or Insufficient Notebooks Appropriately**:
+  - If the notebook is empty or lacks sufficient information, acknowledge this in your analysis and final answer.
+  - **Do not generate any follow-up questions if the answer is not available**.
+
+- **Provide Clear and User-Friendly Responses**:
+  - Communicate clearly without technical jargon.
+
+---
+
+By emphasizing that ChunkIds are valid UUIDs and that you should not invent or make up any chunkIds, as well as specifying that no follow-up questions should be generated if the answer is not available, this updated prompt should help prevent the LLM from including information from outside the notebook or making up chunkIds. It also clarifies how to handle situations where the notebook does not contain sufficient information to answer the question.
+`;
+const outputSchema = zod_1.z.object({
+    title: zod_1.z.string().describe(`You should generate a short title to provide the user a quick reference`),
+    analyse: zod_1.z
+        .string()
+        .describe(`You should first analyse each notebook content before providing a final answer. During the analysis, consider complementary information from other notes and employ a majority voting strategy to resolve any inconsistencies.`),
+    citations: zod_1.z
+        .array(zod_1.z.object({
+        chunkId: zod_1.z.string().describe(`The UUID of the line in your notebook`),
+        relevance: zod_1.z
+            .number()
+            .describe(`The relevance of the information in the line of your notebook in percentage between 0 and 100. This defines if the information is relevant to the question or not and if it will be used as a citation.`),
+    }))
+        .describe(`You should provide citations to the information you used to generate the final answer. Consider ALL the ChunkIds in your notebook. Each citation should have a relevance score. Each ChunkId should be unique. Each ChunkId should have a relevance score.`),
+    questions: zod_1.z
+        .array(zod_1.z.string())
+        .describe(`A list of **5 follow-up or refinement questions** based on the final answer.`),
+    finalAnswer: zod_1.z.string().describe(`Generate a comprehensive, detailed, and well-structured final answer using only information from the notebook. If insufficient information is available, clearly state that the answer is not available in the company knowledge.
+
+Format Requirements:
+- Use proper markdown formatting with headers (##, ###) to organize content into logical sections
+- Include bullet points or numbered lists for multiple items, steps, or concepts
+- Expand on concepts with thorough explanations rather than brief summaries
+- Use subheadings to break complex topics into digestible parts
+- Provide detailed context and background information to help users understand completely
+- Include specific examples or details from the notebook when available
+- Ensure the answer flows logically and is educational in nature
+- Make the response comprehensive and informative, not minimalistic
+      `),
+});
+const inputSchema = zod_1.z.object({
+    question: zod_1.z.string().describe("The question asked by the user"),
+    annotations: zod_1.z.string().describe("A set of annotations to provide additional context"),
+    notebook: zod_1.z
+        .array(zod_1.z.object({
+        chunkId: zod_1.z.string().describe("The UUID of the chunk"),
+        content: zod_1.z
+            .string()
+            .describe("The note you took about the content of the text chunk in relation to the user question."),
+    }))
+        .describe("A set of notes identified for each chunk of text that could be used as sources"),
+});
+let ResponderAnswerNodeService = ResponderAnswerNodeService_1 = class ResponderAnswerNodeService {
+    constructor(llmService, configService) {
+        this.llmService = llmService;
+        this.configService = configService;
+        this.logger = new common_1.Logger(ResponderAnswerNodeService_1.name);
+        const prompts = this.configService.get("prompts");
+        this.systemPrompt = prompts?.responder ?? exports.defaultAnswerPrompt;
+    }
+    async execute(params) {
+        const inputParams = {
+            question: params.state.context.question,
+            annotations: params.state.context.annotations,
+            notebook: params.state.context.notebook,
+        };
+        const llmResponse = await this.llmService.call({
+            inputSchema: inputSchema,
+            inputParams: inputParams,
+            outputSchema: outputSchema,
+            systemPrompts: [this.systemPrompt],
+            temperature: 0.1,
+        });
+        const sources = llmResponse.citations.map((citation) => ({
+            chunkId: citation.chunkId ?? "",
+            relevance: citation.relevance ?? 0,
+            reason: "",
+        }));
+        const filteredSources = [];
+        for (const source of sources) {
+            const existingSource = filteredSources.find((s) => s.chunkId === source.chunkId);
+            const existingNote = params.state.context.notebook.find((n) => n.chunkId === source.chunkId);
+            if (existingNote)
+                source.reason = existingNote.reason;
+            if (!existingSource) {
+                filteredSources.push(source);
+                continue;
+            }
+            if (source.relevance > existingSource.relevance) {
+                existingSource.relevance = source.relevance;
+            }
+        }
+        params.state.sources = filteredSources;
+        params.state.ontologies = params.state.context.ontology;
+        params.state.tokens = llmResponse.tokenUsage;
+        params.state.finalAnswer = {
+            title: llmResponse.title,
+            answer: llmResponse.finalAnswer,
+            analysis: llmResponse.analyse,
+            questions: llmResponse.questions,
+            hasAnswer: true,
+        };
+        return params.state;
+    }
+};
+exports.ResponderAnswerNodeService = ResponderAnswerNodeService;
+exports.ResponderAnswerNodeService = ResponderAnswerNodeService = ResponderAnswerNodeService_1 = __decorate([
+    (0, common_1.Injectable)(),
+    __metadata("design:paramtypes", [llm_service_1.LLMService,
+        config_1.ConfigService])
+], ResponderAnswerNodeService);
+//# sourceMappingURL=responder.answer.node.service.js.map

package/dist/agents/responder/nodes/responder.answer.node.service.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.answer.node.service.js","sourceRoot":"","sources":["../../../../src/agents/responder/nodes/responder.answer.node.service.ts"],"names":[],"mappings":";;;;;;;;;;;;;AAAA,2CAAoD;AACpD,2CAA+C;AAC/C,6BAAwB;AAExB,wEAAoE;AAGvD,QAAA,mBAAmB,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CAwPlC,CAAC;AAEF,MAAM,YAAY,GAAG,OAAC,CAAC,MAAM,CAAC;IAC5B,KAAK,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,yEAAyE,CAAC;IACrG,OAAO,EAAE,OAAC;SACP,MAAM,EAAE;SACR,QAAQ,CACP,gOAAgO,CACjO;IACH,SAAS,EAAE,OAAC;SACT,KAAK,CACJ,OAAC,CAAC,MAAM,CAAC;QACP,OAAO,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,uCAAuC,CAAC;QACrE,SAAS,EAAE,OAAC;aACT,MAAM,EAAE;aACR,QAAQ,CACP,yMAAyM,CAC1M;KACJ,CAAC,CACH;SACA,QAAQ,CACP,4PAA4P,CAC7P;IACH,SAAS,EAAE,OAAC;SACT,KAAK,CAAC,OAAC,CAAC,MAAM,EAAE,CAAC;SACjB,QAAQ,CAAC,8EAA8E,CAAC;IAC3F,WAAW,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAC9B;;;;;;;;;;;OAWG,CACJ;CACF,CAAC,CAAC;AAEH,MAAM,WAAW,GAAG,OAAC,CAAC,MAAM,CAAC;IAC3B,QAAQ,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,gCAAgC,CAAC;IAC/D,WAAW,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,oDAAoD,CAAC;IACtF,QAAQ,EAAE,OAAC;SACR,KAAK,CACJ,OAAC,CAAC,MAAM,CAAC;QACP,OAAO,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,QAAQ,CAAC,uBAAuB,CAAC;QACrD,OAAO,EAAE,OAAC;aACP,MAAM,EAAE;aACR,QAAQ,CAAC,yFAAyF,CAAC;KACvG,CAAC,CACH;SACA,QAAQ,CAAC,gFAAgF,CAAC;CAC9F,CAAC,CAAC;AAGI,IAAM,0BAA0B,kCAAhC,MAAM,0BAA0B;IAIrC,YACmB,UAAsB,EACtB,aAAiD;QADjD,eAAU,GAAV,UAAU,CAAY;QACtB,kBAAa,GAAb,aAAa,CAAoC;QALnD,WAAM,GAAG,IAAI,eAAM,CAAC,4BAA0B,CAAC,IAAI,CAAC,CAAC;QAOpE,MAAM,OAAO,GAAG,IAAI,CAAC,aAAa,CAAC,GAAG,CAAyB,SAAS,CAAC,CAAC;QAC1E,IAAI,CAAC,YAAY,GAAG,OAAO,EAAE,SAAS,IAAI,2BAAmB,CAAC;IAChE,CAAC;IAED,KAAK,CAAC,OAAO,CAAC,MAAgD;QAC5D,MAAM,WAAW,GAAgC;YAC/C,QAAQ,EAAE,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,QAAQ;YACvC,WAAW,EAAE,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,WAAW;YAC7C,QAAQ,EAAE,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,QAAQ;SACxC,CAAC;QAEF,MAAM,WAAW,GAAG,MAAM,IAAI,CAAC,UAAU,CAAC,IAAI,CAA+B;YAC3E,WAAW,EAAE,WAAW;YACxB,WAAW,EAAE,WAAW;YACxB,YAAY,EAAE,YAAY;YAC1B,aAAa,EAAE,CAAC,IAAI,CAAC,YAAY,CAAC;YAClC,WAAW,EAAE,GAAG;SACjB,CAAC,CAAC;QAEH,MAAM,OAAO,GAAG,WAAW,CAAC,SAAS,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC;YACvD,OAAO,EAAE,QAAQ,CAAC,OAAO,IAAI,EAAE;YAC/B,SAAS,EAAE,QAAQ,CAAC,SAAS,IAAI,CAAC;YAClC,MAAM,EAAE,EAAE;SACX,CAAC,CAAC,CAAC;QAEJ,MAAM,eAAe,GAAG,EAAE,CAAC;QAC3B,KAAK,MAAM,MAAM,IAAI,OAAO,EAAE,CAAC;YAC7B,MAAM,cAAc,GAAG,eAAe,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,KAAK,MAAM,CAAC,OAAO,CAAC,CAAC;YACjF,MAAM,YAAY,GAAG,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,QAAQ,CAAC,IAAI,CAAC,CAAC,CAAC,EAAE,EAAE,CAAC,CAAC,CAAC,OAAO,KAAK,MAAM,CAAC,OAAO,CAAC,CAAC;YAE7F,IAAI,YAAY;gBAAE,MAAM,CAAC,MAAM,GAAG,YAAY,CAAC,MAAM,CAAC;YAEtD,IAAI,CAAC,cAAc,EAAE,CAAC;gBACpB,eAAe,CAAC,IAAI,CAAC,MAAM,CAAC,CAAC;gBAC7B,SAAS;YACX,CAAC;YAED,IAAI,MAAM,CAAC,SAAS,GAAG,cAAc,CAAC,SAAS,EAAE,CAAC;gBAChD,cAAc,CAAC,SAAS,GAAG,MAAM,CAAC,SAAS,CAAC;YAC9C,CAAC;QACH,CAAC;QAED,MAAM,CAAC,KAAK,CAAC,OAAO,GAAG,eAAe,CAAC;QACvC,MAAM,CAAC,KAAK,CAAC,UAAU,GAAG,MAAM,CAAC,KAAK,CAAC,OAAO,CAAC,QAAQ,CAAC;QAExD,MAAM,CAAC,KAAK,CAAC,MAAM,GAAG,WAAW,CAAC,UAAU,CAAC;QAE7C,MAAM,CAAC,KAAK,CAAC,WAAW,GAAG;YACzB,KAAK,EAAE,WAAW,CAAC,KAAK;YACxB,MAAM,EAAE,WAAW,CAAC,WAAW;YAC/B,QAAQ,EAAE,WAAW,CAAC,OAAO;YAC7B,SAAS,EAAE,WAAW,CAAC,SAAS;YAChC,SAAS,EAAE,IAAI;SAChB,CAAC;QAEF,OAAO,MAAM,CAAC,KAAK,CAAC;IACtB,CAAC;CACF,CAAA;AAjEY,gEAA0B;qCAA1B,0BAA0B;IADtC,IAAA,mBAAU,GAAE;qCAMoB,wBAAU;QACP,sBAAa;GANpC,0BAA0B,CAiEtC"}

package/dist/agents/responder/responder.module.d.ts

@@ -0,0 +1,3 @@
+export declare class ResponderModule {
+}
+//# sourceMappingURL=responder.module.d.ts.map

package/dist/agents/responder/responder.module.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.module.d.ts","sourceRoot":"","sources":["../../../src/agents/responder/responder.module.ts"],"names":[],"mappings":"AASA,qBAKa,eAAe;CAAG"}

package/dist/agents/responder/responder.module.js

@@ -0,0 +1,28 @@
+"use strict";
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ResponderModule = void 0;
+const common_1 = require("@nestjs/common");
+const contextualiser_module_1 = require("../contextualiser/contextualiser.module");
+const responder_context_factory_1 = require("./factories/responder.context.factory");
+const responder_answer_node_service_1 = require("./nodes/responder.answer.node.service");
+const responder_service_1 = require("./services/responder.service");
+const llm_module_1 = require("../../core/llm/llm.module");
+const company_module_1 = require("../../foundations/company/company.module");
+const s3_module_1 = require("../../foundations/s3/s3.module");
+let ResponderModule = class ResponderModule {
+};
+exports.ResponderModule = ResponderModule;
+exports.ResponderModule = ResponderModule = __decorate([
+    (0, common_1.Module)({
+        imports: [llm_module_1.LLMModule, s3_module_1.S3Module, company_module_1.CompanyModule, contextualiser_module_1.ContextualiserModule],
+        providers: [responder_context_factory_1.ResponderContextFactoryService, responder_service_1.ResponderService, responder_answer_node_service_1.ResponderAnswerNodeService],
+        exports: [responder_service_1.ResponderService],
+    })
+], ResponderModule);
+//# sourceMappingURL=responder.module.js.map

package/dist/agents/responder/responder.module.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.module.js","sourceRoot":"","sources":["../../../src/agents/responder/responder.module.ts"],"names":[],"mappings":";;;;;;;;;AAAA,2CAAwC;AACxC,mFAA+E;AAC/E,qFAAuF;AACvF,yFAAmF;AACnF,oEAAgE;AAChE,0DAAsD;AACtD,6EAAyE;AACzE,8DAA0D;AAOnD,IAAM,eAAe,GAArB,MAAM,eAAe;CAAG,CAAA;AAAlB,0CAAe;0BAAf,eAAe;IAL3B,IAAA,eAAM,EAAC;QACN,OAAO,EAAE,CAAC,sBAAS,EAAE,oBAAQ,EAAE,8BAAa,EAAE,4CAAoB,CAAC;QACnE,SAAS,EAAE,CAAC,0DAA8B,EAAE,oCAAgB,EAAE,0DAA0B,CAAC;QACzF,OAAO,EAAE,CAAC,oCAAgB,CAAC;KAC5B,CAAC;GACW,eAAe,CAAG"}

package/dist/agents/responder/services/responder.service.d.ts

@@ -0,0 +1,21 @@
+import { ContextualiserService } from "../../contextualiser/services/contextualiser.service";
+import { ResponderContextFactoryService } from "../../responder/factories/responder.context.factory";
+import { ResponderResponseInterface } from "../../responder/interfaces/responder.response.interface";
+import { ResponderAnswerNodeService } from "../../responder/nodes/responder.answer.node.service";
+import { MessageInterface } from "../../../common/interfaces/message.interface";
+import { DataLimits } from "../../../common/types/data.limits";
+export declare class ResponderService {
+    private readonly responderContextFactoryService;
+    private readonly contextualiserService;
+    private readonly answerNode;
+    constructor(responderContextFactoryService: ResponderContextFactoryService, contextualiserService: ContextualiserService, answerNode: ResponderAnswerNodeService);
+    run(params: {
+        companyId: string;
+        contentId: string;
+        contentType: string;
+        dataLimits: DataLimits;
+        messages: MessageInterface[];
+        question?: string;
+    }): Promise<ResponderResponseInterface>;
+}
+//# sourceMappingURL=responder.service.d.ts.map

package/dist/agents/responder/services/responder.service.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.service.d.ts","sourceRoot":"","sources":["../../../../src/agents/responder/services/responder.service.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,qBAAqB,EAAE,MAAM,sDAAsD,CAAC;AAE7F,OAAO,EAAE,8BAA8B,EAAE,MAAM,qDAAqD,CAAC;AACrG,OAAO,EAAE,0BAA0B,EAAE,MAAM,yDAAyD,CAAC;AACrG,OAAO,EAAE,0BAA0B,EAAE,MAAM,qDAAqD,CAAC;AACjG,OAAO,EAAE,gBAAgB,EAAE,MAAM,8CAA8C,CAAC;AAChF,OAAO,EAAE,UAAU,EAAE,MAAM,mCAAmC,CAAC;AAE/D,qBACa,gBAAgB;IAEzB,OAAO,CAAC,QAAQ,CAAC,8BAA8B;IAC/C,OAAO,CAAC,QAAQ,CAAC,qBAAqB;IACtC,OAAO,CAAC,QAAQ,CAAC,UAAU;gBAFV,8BAA8B,EAAE,8BAA8B,EAC9D,qBAAqB,EAAE,qBAAqB,EAC5C,UAAU,EAAE,0BAA0B;IAGnD,GAAG,CAAC,MAAM,EAAE;QAChB,SAAS,EAAE,MAAM,CAAC;QAClB,SAAS,EAAE,MAAM,CAAC;QAClB,WAAW,EAAE,MAAM,CAAC;QACpB,UAAU,EAAE,UAAU,CAAC;QACvB,QAAQ,EAAE,gBAAgB,EAAE,CAAC;QAC7B,QAAQ,CAAC,EAAE,MAAM,CAAC;KACnB,GAAG,OAAO,CAAC,0BAA0B,CAAC;CA0DxC"}

package/dist/agents/responder/services/responder.service.js

@@ -0,0 +1,87 @@
+"use strict";
+var __decorate = (this && this.__decorate) || function (decorators, target, key, desc) {
+    var c = arguments.length, r = c < 3 ? target : desc === null ? desc = Object.getOwnPropertyDescriptor(target, key) : desc, d;
+    if (typeof Reflect === "object" && typeof Reflect.decorate === "function") r = Reflect.decorate(decorators, target, key, desc);
+    else for (var i = decorators.length - 1; i >= 0; i--) if (d = decorators[i]) r = (c < 3 ? d(r) : c > 3 ? d(target, key, r) : d(target, key)) || r;
+    return c > 3 && r && Object.defineProperty(target, key, r), r;
+};
+var __metadata = (this && this.__metadata) || function (k, v) {
+    if (typeof Reflect === "object" && typeof Reflect.metadata === "function") return Reflect.metadata(k, v);
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ResponderService = void 0;
+const langgraph_1 = require("@langchain/langgraph");
+const common_1 = require("@nestjs/common");
+const crypto_1 = require("crypto");
+const contextualiser_service_1 = require("../../contextualiser/services/contextualiser.service");
+const responder_context_1 = require("../../responder/contexts/responder.context");
+const responder_context_factory_1 = require("../../responder/factories/responder.context.factory");
+const responder_answer_node_service_1 = require("../../responder/nodes/responder.answer.node.service");
+let ResponderService = class ResponderService {
+    constructor(responderContextFactoryService, contextualiserService, answerNode) {
+        this.responderContextFactoryService = responderContextFactoryService;
+        this.contextualiserService = contextualiserService;
+        this.answerNode = answerNode;
+    }
+    async run(params) {
+        const workflow = new langgraph_1.StateGraph(responder_context_1.ResponderContext)
+            .addNode("contextualiser", async (state) => {
+            const context = await this.contextualiserService.run({
+                companyId: state.companyId,
+                contentId: state.contentId,
+                contentType: state.contentType,
+                dataLimits: params.dataLimits,
+                messages: params.messages,
+                question: params.question,
+            });
+            state.context = context;
+            state.tokens = context.tokens;
+            return state;
+        })
+            .addNode("answer", async (state) => {
+            const result = await this.answerNode.execute({
+                state: state,
+            });
+            return result;
+        })
+            .addEdge(langgraph_1.START, "contextualiser")
+            .addEdge("contextualiser", "answer")
+            .addEdge("answer", langgraph_1.END);
+        const threadId = (0, crypto_1.randomUUID)();
+        const checkpointer = new langgraph_1.MemorySaver();
+        const app = workflow.compile({ checkpointer: checkpointer });
+        const initialState = this.responderContextFactoryService.create({
+            companyId: params.companyId,
+            contentId: params.contentId,
+            contentType: params.contentType,
+            dataLimits: params.dataLimits,
+        });
+        let finalState;
+        try {
+            finalState = await app.invoke(initialState, {
+                configurable: { thread_id: threadId },
+                recursionLimit: 100,
+            });
+        }
+        catch (e) {
+            console.error("[WORKFLOW:Responder] Failed with error", {
+                error: e.message,
+                errorCode: e.lc_error_code,
+                recursionLimit: 100,
+            });
+            throw e;
+        }
+        const response = this.responderContextFactoryService.createAnswer({
+            state: finalState,
+        });
+        return response;
+    }
+};
+exports.ResponderService = ResponderService;
+exports.ResponderService = ResponderService = __decorate([
+    (0, common_1.Injectable)(),
+    __metadata("design:paramtypes", [responder_context_factory_1.ResponderContextFactoryService,
+        contextualiser_service_1.ContextualiserService,
+        responder_answer_node_service_1.ResponderAnswerNodeService])
+], ResponderService);
+//# sourceMappingURL=responder.service.js.map

package/dist/agents/responder/services/responder.service.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"responder.service.js","sourceRoot":"","sources":["../../../../src/agents/responder/services/responder.service.ts"],"names":[],"mappings":";;;;;;;;;;;;AAAA,oDAA2E;AAC3E,2CAA4C;AAC5C,mCAAoC;AACpC,iGAA6F;AAC7F,kFAAqG;AACrG,mGAAqG;AAErG,uGAAiG;AAK1F,IAAM,gBAAgB,GAAtB,MAAM,gBAAgB;IAC3B,YACmB,8BAA8D,EAC9D,qBAA4C,EAC5C,UAAsC;QAFtC,mCAA8B,GAA9B,8BAA8B,CAAgC;QAC9D,0BAAqB,GAArB,qBAAqB,CAAuB;QAC5C,eAAU,GAAV,UAAU,CAA4B;IACtD,CAAC;IAEJ,KAAK,CAAC,GAAG,CAAC,MAOT;QACC,MAAM,QAAQ,GAAG,IAAI,sBAAU,CAAC,oCAAgB,CAAC;aAC9C,OAAO,CAAC,gBAAgB,EAAE,KAAK,EAAE,KAAK,EAAE,EAAE;YACzC,MAAM,OAAO,GAAG,MAAM,IAAI,CAAC,qBAAqB,CAAC,GAAG,CAAC;gBACnD,SAAS,EAAE,KAAK,CAAC,SAAS;gBAC1B,SAAS,EAAE,KAAK,CAAC,SAAS;gBAC1B,WAAW,EAAE,KAAK,CAAC,WAAW;gBAC9B,UAAU,EAAE,MAAM,CAAC,UAAU;gBAC7B,QAAQ,EAAE,MAAM,CAAC,QAAQ;gBACzB,QAAQ,EAAE,MAAM,CAAC,QAAQ;aAC1B,CAAC,CAAC;YACH,KAAK,CAAC,OAAO,GAAG,OAAO,CAAC;YACxB,KAAK,CAAC,MAAM,GAAG,OAAO,CAAC,MAAM,CAAC;YAE9B,OAAO,KAAK,CAAC;QACf,CAAC,CAAC;aACD,OAAO,CAAC,QAAQ,EAAE,KAAK,EAAE,KAA4B,EAAE,EAAE;YACxD,MAAM,MAAM,GAAG,MAAM,IAAI,CAAC,UAAU,CAAC,OAAO,CAAC;gBAC3C,KAAK,EAAE,KAAK;aACb,CAAC,CAAC;YACH,OAAO,MAAM,CAAC;QAChB,CAAC,CAAC;aACD,OAAO,CAAC,iBAAK,EAAE,gBAAgB,CAAC;aAChC,OAAO,CAAC,gBAAgB,EAAE,QAAQ,CAAC;aACnC,OAAO,CAAC,QAAQ,EAAE,eAAG,CAAC,CAAC;QAE1B,MAAM,QAAQ,GAAG,IAAA,mBAAU,GAAE,CAAC;QAC9B,MAAM,YAAY,GAAG,IAAI,uBAAW,EAAE,CAAC;QACvC,MAAM,GAAG,GAAG,QAAQ,CAAC,OAAO,CAAC,EAAE,YAAY,EAAE,YAAY,EAAE,CAAC,CAAC;QAE7D,MAAM,YAAY,GAA0B,IAAI,CAAC,8BAA8B,CAAC,MAAM,CAAC;YACrF,SAAS,EAAE,MAAM,CAAC,SAAS;YAC3B,SAAS,EAAE,MAAM,CAAC,SAAS;YAC3B,WAAW,EAAE,MAAM,CAAC,WAAW;YAC/B,UAAU,EAAE,MAAM,CAAC,UAAU;SAC9B,CAAC,CAAC;QAEH,IAAI,UAAiC,CAAC;QACtC,IAAI,CAAC;YACH,UAAU,GAAG,MAAM,GAAG,CAAC,MAAM,CAAC,YAAY,EAAE;gBAC1C,YAAY,EAAE,EAAE,SAAS,EAAE,QAAQ,EAAE;gBACrC,cAAc,EAAE,GAAG;aACb,CAAC,CAAC;QACZ,CAAC;QAAC,OAAO,CAAC,EAAE,CAAC;YACX,OAAO,CAAC,KAAK,CAAC,wCAAwC,EAAE;gBACtD,KAAK,EAAG,CAAW,CAAC,OAAO;gBAC3B,SAAS,EAAG,CAAS,CAAC,aAAa;gBACnC,cAAc,EAAE,GAAG;aACpB,CAAC,CAAC;YACH,MAAM,CAAC,CAAC;QACV,CAAC;QAED,MAAM,QAAQ,GAA+B,IAAI,CAAC,8BAA8B,CAAC,YAAY,CAAC;YAC5F,KAAK,EAAE,UAAU;SAClB,CAAC,CAAC;QAEH,OAAO,QAAQ,CAAC;IAClB,CAAC;CACF,CAAA;AAxEY,4CAAgB;2BAAhB,gBAAgB;IAD5B,IAAA,mBAAU,GAAE;qCAGwC,0DAA8B;QACvC,8CAAqB;QAChC,0DAA0B;GAJ9C,gBAAgB,CAwE5B"}

package/dist/agents/summariser/services/summariser.service.d.ts

@@ -0,0 +1,24 @@
+import { ConfigService } from "@nestjs/config";
+import { TokenUsageInterface } from "../../../common/interfaces/token.usage.interface";
+import { BaseConfigInterface } from "../../../config/interfaces";
+import { ModelService } from "../../../core/llm/services/model.service";
+import { Chunk } from "../../../foundations/chunk/entities/chunk.entity";
+export declare const defaultMapPrompt = "Summarize the following content using clean markdown formatting.\n\nIMPORTANT: Output ONLY the summary content directly. Do NOT include:\n- Introductory phrases like \"Here is a summary\"\n- Meta-commentary about what you're doing\n- Unnecessary horizontal rules or separators\n\nJust write the summary content itself.\n\n{context}";
+export declare const defaultCombinePrompt = "Based on the following summaries, write a consolidated summary that integrates all the main themes and key points.\n\n{text}\n\nIMPORTANT: Output ONLY the summary content directly. Do NOT include:\n- Introductory phrases like \"Here is a summary\"\n- Meta-commentary about what you're doing\n- Unnecessary horizontal rules or separators\n- Any reference to the fact that you are synthesizing summaries\n\nWrite directly about the content subject. Use well-structured markdown with appropriate headings, bullet points, and emphasis.";
+export declare const defaultTldrPrompt = "Create a single concise sentence (maximum 20 words) that captures the essential point of this summary:\n\n{summary}";
+export declare class SummariserService {
+    private readonly modelService;
+    private readonly configService;
+    private readonly mapPromptText;
+    private readonly combinePromptText;
+    private readonly tldrPromptText;
+    constructor(modelService: ModelService, configService: ConfigService<BaseConfigInterface>);
+    summarise(params: {
+        chunks: Chunk[];
+    }): Promise<{
+        content: string;
+        tldr: string;
+        tokens: TokenUsageInterface;
+    }>;
+}
+//# sourceMappingURL=summariser.service.d.ts.map

package/dist/agents/summariser/services/summariser.service.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"summariser.service.d.ts","sourceRoot":"","sources":["../../../../src/agents/summariser/services/summariser.service.ts"],"names":[],"mappings":"AAGA,OAAO,EAAE,aAAa,EAAE,MAAM,gBAAgB,CAAC;AAE/C,OAAO,EAAE,mBAAmB,EAAE,MAAM,kDAAkD,CAAC;AACvF,OAAO,EAAE,mBAAmB,EAA0B,MAAM,4BAA4B,CAAC;AACzF,OAAO,EAAE,YAAY,EAAE,MAAM,0CAA0C,CAAC;AACxE,OAAO,EAAE,KAAK,EAAE,MAAM,kDAAkD,CAAC;AAEzE,eAAO,MAAM,gBAAgB,gVASnB,CAAC;AAEX,eAAO,MAAM,oBAAoB,whBAU8F,CAAC;AAEhI,eAAO,MAAM,iBAAiB,wHAEpB,CAAC;AAEX,qBACa,iBAAiB;IAM1B,OAAO,CAAC,QAAQ,CAAC,YAAY;IAC7B,OAAO,CAAC,QAAQ,CAAC,aAAa;IANhC,OAAO,CAAC,QAAQ,CAAC,aAAa,CAAS;IACvC,OAAO,CAAC,QAAQ,CAAC,iBAAiB,CAAS;IAC3C,OAAO,CAAC,QAAQ,CAAC,cAAc,CAAS;gBAGrB,YAAY,EAAE,YAAY,EAC1B,aAAa,EAAE,aAAa,CAAC,mBAAmB,CAAC;IAQ9D,SAAS,CAAC,MAAM,EAAE;QAAE,MAAM,EAAE,KAAK,EAAE,CAAA;KAAE,GAAG,OAAO,CAAC;QACpD,OAAO,EAAE,MAAM,CAAC;QAChB,IAAI,EAAE,MAAM,CAAC;QACb,MAAM,EAAE,mBAAmB,CAAC;KAC7B,CAAC;CAiEH"}