@axiom-lattice/examples-deep_research 1.0.13 → 1.0.14

package/.env

@@ -18,7 +18,7 @@ VOLCENGINE_API_KEY2=a0533576-d6ed-4ca4-a308-473cbf7ebd10
 
 TAVILY_API_KEY=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
 
-# DATABASE_URL=postgresql://postgres.ldejdqkwvlllycysuvsr:jfd4whz@GPF2nqx7zhm@aws-0-ap-southeast-1.pooler.supabase.com:6543/postgres
+DATABASE_URL=postgresql://postgres_fuli:jfd4whz%40GPF2nqx7zhm@pgm-uf615169n98t95tflo.pg.rds.aliyuncs.com:5432/postgres
 # QUEUE_NAME=simon_tasks
 # REDIS_URL=redis://localhost:6379
 # REDIS_PASSWORD=fina

package/.turbo/turbo-build.log

@@ -1,5 +1,5 @@
 
-> @axiom-lattice/examples-deep_research@1.0.13 build /home/runner/work/agentic/agentic/examples/deep_research
+> @axiom-lattice/examples-deep_research@1.0.14 build /home/runner/work/agentic/agentic/examples/deep_research
 > tsup
 
 CLI Building entry: src/index.ts
@@ -9,9 +9,9 @@
 CLI Target: es2020
 CLI Cleaning output folder
 CJS Build start
-CJS dist/index.js     14.28 KB
-CJS dist/index.js.map 16.33 KB
-CJS ⚡️ Build success in 34ms
+CJS dist/index.js     20.25 KB
+CJS dist/index.js.map 26.46 KB
+CJS ⚡️ Build success in 30ms
 DTS Build start
-DTS ⚡️ Build success in 5042ms
+DTS ⚡️ Build success in 5094ms
 DTS dist/index.d.ts 13.00 B

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # @axiom-lattice/examples-deep_research
 
+## 1.0.14
+
+### Patch Changes
+
+- d43ea0b: add schedule task
+- Updated dependencies [d43ea0b]
+  - @axiom-lattice/pg-stores@1.0.3
+  - @axiom-lattice/protocols@2.1.8
+  - @axiom-lattice/gateway@2.1.19
+  - @axiom-lattice/core@2.1.14
+
 ## 1.0.13
 
 ### Patch Changes

package/dist/index.js

@@ -31,7 +31,7 @@ var require_package = __commonJS({
   "package.json"(exports2, module2) {
     module2.exports = {
       name: "@axiom-lattice/examples-deep_research",
-      version: "1.0.13",
+      version: "1.0.14",
       main: "dist/index.js",
       bin: {
         "lattice-deep-research": "./dist/index.js"
@@ -55,6 +55,8 @@ var require_package = __commonJS({
       dependencies: {
         "@axiom-lattice/core": "workspace:*",
         "@axiom-lattice/gateway": "workspace:*",
+        "@axiom-lattice/protocols": "workspace:*",
+        "@axiom-lattice/pg-stores": "workspace:*",
         dotenv: "^16.6.1",
         uuid: "^9.0.1",
         zod: "^3.24.2",
@@ -82,7 +84,7 @@ var require_package = __commonJS({
 // src/index.ts
 var import_dotenv = __toESM(require("dotenv"));
 var import_gateway = require("@axiom-lattice/gateway");
-var import_core2 = require("@axiom-lattice/core");
+var import_core3 = require("@axiom-lattice/core");
 
 // src/agents/research/index.ts
 var import_core = require("@axiom-lattice/core");
@@ -232,6 +234,162 @@ var research_agents = [
 ];
 (0, import_core.registerAgentLattices)(research_agents);
 
+// src/agents/data_agent/index.ts
+var import_core2 = require("@axiom-lattice/core");
+var import_zod2 = __toESM(require("zod"));
+var dataAgentPrompt = `You are an expert Data Analyst AI assistant specialized in converting natural language questions into SQL queries and retrieving data from databases.
+
+Your primary responsibilities:
+1. Understand user questions about data
+2. Explore the database schema to understand available tables and their relationships
+3. Write accurate and efficient SQL queries to answer questions
+4. Present results in a clear and understandable format
+
+## Workflow
+
+When a user asks a question about data, follow these steps:
+
+### Step 1: Understand the Database Schema
+- First, use the \`list_tables_sql\` tool to see all available tables
+- Then, use the \`info_sql\` tool to get detailed schema information for relevant tables
+- Pay attention to:
+  - Column names and data types
+  - Primary keys and foreign keys (relationships between tables)
+  - Sample data to understand the data format
+
+### Step 2: Plan Your Query
+- Think about which tables you need to query
+- Consider if you need to JOIN multiple tables
+- Think about filtering conditions (WHERE clauses)
+- Consider if you need aggregations (COUNT, SUM, AVG, etc.)
+- Consider sorting and limiting results
+
+### Step 3: Validate Your Query
+- Use the \`query_checker_sql\` tool to validate your SQL query before execution
+- Fix any issues found by the checker
+- Make sure the query is safe and efficient
+
+### Step 4: Execute and Present Results
+- Use the \`query_sql\` tool to execute your validated query
+- Present the results in a clear format
+- Explain what the data means in context of the user's question
+- If the results are unexpected, analyze and explain possible reasons
+
+## SQL Best Practices
+
+1. **Be Specific**: Always specify column names instead of using SELECT *
+2. **Use Aliases**: Use meaningful table and column aliases for clarity
+3. **Handle NULLs**: Consider NULL values in your queries
+4. **Limit Results**: For exploratory queries, limit results to avoid overwhelming output
+5. **Optimize JOINs**: Use appropriate JOIN types (INNER, LEFT, etc.)
+6. **Use Indexes**: Structure queries to leverage indexes when possible
+
+## Communication Guidelines
+
+- Explain your thought process as you work
+- If you need clarification about the user's question, ask
+- If a query returns unexpected results, explain what might have happened
+- Suggest follow-up queries or analyses that might be helpful
+- Present data insights, not just raw results
+
+## Error Handling
+
+- If a query fails, analyze the error message
+- Try to fix the query and re-execute
+- If you cannot answer the question due to data limitations, explain clearly what is missing
+
+Remember: The goal is not just to write SQL, but to help users understand their data and make informed decisions.
+`;
+var sqlBuilderPrompt = `You are a SQL Expert sub-agent. Your job is to write precise, efficient SQL queries.
+
+When given a task:
+1. Analyze the schema information provided
+2. Write the most appropriate SQL query
+3. Validate the query using query_checker_sql
+4. Return the finalized query
+
+Focus on:
+- Query correctness
+- Query efficiency
+- Proper use of JOINs and subqueries
+- Appropriate use of aggregate functions
+- Clear column naming and aliasing
+
+If you encounter issues:
+- Analyze the error
+- Modify the query accordingly
+- Re-validate before returning
+
+Always return your final query in a clear format for execution.
+`;
+var dataAnalysisPrompt = `You are a Data Analysis Expert sub-agent. Your job is to interpret query results and provide insights.
+
+When given query results:
+1. Summarize the key findings
+2. Identify patterns or anomalies
+3. Provide context and interpretation
+4. Suggest potential follow-up analyses
+
+Focus on:
+- Clear, concise summaries
+- Statistical insights when appropriate
+- Business context interpretation
+- Visualization suggestions if applicable
+
+Present your analysis in a structured format:
+- Summary
+- Key Findings
+- Insights
+- Recommendations (if any)
+`;
+var data_agents = [
+  {
+    key: "data_agent",
+    name: "Data Agent",
+    description: "An intelligent NL2SQL agent that converts natural language questions into SQL queries and retrieves data from databases. Use this agent for data analysis tasks, database queries, and data exploration.",
+    type: import_core2.AgentType.DEEP_AGENT,
+    tools: ["list_tables_sql", "info_sql", "query_sql", "query_checker_sql"],
+    prompt: dataAgentPrompt,
+    subAgents: ["sql-builder-agent", "data-analysis-agent"],
+    schema: import_zod2.default.object({}),
+    /**
+     * Runtime configuration injected into tool execution context.
+     * databaseKey: The database key registered via sqlDatabaseManager.
+     * Tools will access this via config.configurable.runConfig.databaseKey
+     */
+    runConfig: {
+      databaseKey: "fulidb"
+      // Set this to the registered database key
+    }
+  },
+  {
+    key: "sql-builder-agent",
+    name: "sql-builder-agent",
+    type: import_core2.AgentType.REACT,
+    description: "A specialized sub-agent for building and validating SQL queries. Give this agent schema information and a data question, and it will return an optimized SQL query.",
+    prompt: sqlBuilderPrompt,
+    tools: ["info_sql", "query_checker_sql"]
+    // Sub-agents inherit runConfig from parent agent via the execution context
+  },
+  {
+    key: "data-analysis-agent",
+    name: "data-analysis-agent",
+    type: import_core2.AgentType.REACT,
+    description: "A specialized sub-agent for analyzing query results and providing insights. Give this agent query results and it will provide a structured analysis.",
+    prompt: dataAnalysisPrompt,
+    tools: []
+  }
+];
+(0, import_core2.registerAgentLattices)(data_agents);
+function initializeDataAgentDatabase(key, config) {
+  import_core2.sqlDatabaseManager.registerDatabase(key, config);
+}
+initializeDataAgentDatabase("fulidb", {
+  type: "postgres",
+  connectionString: process.env.DATABASE_URL,
+  database: "postgres"
+});
+
 // src/index.ts
 var import_path = __toESM(require("path"));
 var PACKAGE_VERSION = require_package().version;
@@ -269,7 +427,7 @@ function parsePort() {
   }
   return 4001;
 }
-(0, import_core2.registerModelLattice)(
+(0, import_core3.registerModelLattice)(
   "default",
   // {
   //   model: "deepseek-chat",

package/dist/index.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../package.json","../src/index.ts","../src/agents/research/index.ts"],"sourcesContent":["{\n  \"name\": \"@axiom-lattice/examples-deep_research\",\n  \"version\": \"1.0.13\",\n  \"main\": \"dist/index.js\",\n  \"bin\": {\n    \"lattice-deep-research\": \"./dist/index.js\"\n  },\n  \"scripts\": {\n    \"build\": \"tsup\",\n    \"start\": \"node dist/index.js\",\n    \"dev\": \"tsup src/index.ts --format cjs --dts --watch --onSuccess \\\"node dist/index.js\\\"\",\n    \"dev:nodemon\": \"nodemon --watch 'src/**/*.ts' --watch '../../packages/core/dist/**/*' --exec 'ts-node' -r tsconfig-paths/register src/index.ts\",\n    \"dev:serve\": \"tsup src/index.ts --format cjs --dts --watch --serve dist/index.js\",\n    \"dev:inspect\": \"tsup src/index.ts --format cjs --dts --watch --onSuccess \\\"node --inspect dist/index.js\\\"\",\n    \"lint\": \"tsc --noEmit\",\n    \"test\": \"jest\",\n    \"test:watch\": \"jest --watch\",\n    \"test:coverage\": \"jest --coverage\"\n  },\n  \"keywords\": [],\n  \"author\": \"\",\n  \"license\": \"ISC\",\n  \"description\": \"Deep Research Server for Axiom Lattice\",\n  \"dependencies\": {\n    \"@axiom-lattice/core\": \"workspace:*\",\n    \"@axiom-lattice/gateway\": \"workspace:*\",\n    \"dotenv\": \"^16.6.1\",\n    \"uuid\": \"^9.0.1\",\n    \"zod\": \"^3.24.2\",\n    \"zod-to-json-schema\": \"^3.24.3\"\n  },\n  \"devDependencies\": {\n    \"@types/jest\": \"^29.5.14\",\n    \"@types/lodash\": \"^4.17.16\",\n    \"@types/node\": \"^20.17.23\",\n    \"@types/uuid\": \"^9.0.8\",\n    \"@typescript-eslint/eslint-plugin\": \"^7.2.0\",\n    \"@typescript-eslint/parser\": \"^7.2.0\",\n    \"eslint\": \"^8.57.0\",\n    \"jest\": \"^29.7.0\",\n    \"nodemon\": \"^3.1.9\",\n    \"ts-jest\": \"^29.4.0\",\n    \"ts-node\": \"^10.9.2\",\n    \"tsup\": \"^8.5.0\",\n    \"typescript\": \"^5.8.2\"\n  }\n}\n","import dotenv from \"dotenv\";\n\nimport { LatticeGateway } from \"@axiom-lattice/gateway\";\nimport {\n  registerCheckpointSaver,\n  registerModelLattice,\n} from \"@axiom-lattice/core\";\nimport \"./agents\";\nimport path from \"path\";\n// 在文件开头添加\nconst PACKAGE_VERSION = require(\"../package.json\").version;\nconst BUILD_TIME = new Date().toISOString();\nconst IS_DEV = process.env.NODE_ENV !== \"production\";\n\n// 在启动时输出\nconsole.log(`\n╔═══════════════════════════════════════╗\n║  Lattice Deep Research Server         ║\n║  Version: ${PACKAGE_VERSION}                          ║\n║  Build Time: ${BUILD_TIME}  ║\n║  Environment: ${IS_DEV ? \"Development\" : \"Production\"}              ║\n╚═══════════════════════════════════════╝\n`);\n// Load environment variables\ndotenv.config({ path: path.resolve(__dirname, \"../.env\") });\n\n// Parse command line arguments for port configuration\nfunction parsePort(): number {\n  const args = process.argv.slice(2);\n  const portIndex = args.findIndex((arg) => arg === \"--port\" || arg === \"-p\");\n\n  if (portIndex !== -1 && args[portIndex + 1]) {\n    const port = parseInt(args[portIndex + 1], 10);\n    if (!isNaN(port) && port > 0 && port < 65536) {\n      return port;\n    }\n    console.warn(\n      `Invalid port value: ${args[portIndex + 1]}, using default port 4001`\n    );\n  }\n\n  // Check environment variable\n  if (process.env.PORT) {\n    const port = parseInt(process.env.PORT, 10);\n    if (!isNaN(port) && port > 0 && port < 65536) {\n      return port;\n    }\n    console.warn(\n      `Invalid PORT environment variable: ${process.env.PORT}, using default port 4001`\n    );\n  }\n\n  // Default port\n  return 4001;\n}\n\n// Register default model Lattice\nregisterModelLattice(\n  \"default\",\n  // {\n  //   model: \"deepseek-chat\",\n  //   provider: \"deepseek\",\n  //   streaming: false,\n  // }\n  // {\n  //   model: \"deepseek-chat\",\n  //   provider: \"deepseek\",\n  //   streaming: false,\n  //   apiKeyEnvName: \"DEEPSEEK_API_KEY2\",\n  // },\n  // {\n  //   model: \"deepseek-v3-250324\",\n  //   provider: \"volcengine\",\n  //   streaming: false,\n  // },\n  {\n    model: \"kimi-k2-250905\",\n    provider: \"volcengine\",\n    streaming: true,\n    apiKeyEnvName: \"VOLCENGINE_API_KEY2\",\n  }\n  // {\n  //   model: \"kimi-k2-0711-preview\",\n  //   provider: \"openai\",\n  //   streaming: true,\n  //   apiKeyEnvName: \"KIMI_API_KEY\",\n  //   baseURL: \"https://api.moonshot.cn/v1\",\n  // }\n  // {\n  //   model: \"qwen-plus\",\n  //   provider: \"openai\",\n  //   streaming: false,\n  //   apiKeyEnvName: \"DASHSCOPE_API_KEY\",\n  //   baseURL: \"https://dashscope.aliyuncs.com/compatible-mode/v1\",\n  // }\n);\nLatticeGateway.registerLatticeRoutes(LatticeGateway.app);\n\nconst port = parsePort();\nconsole.log(`Starting server on port ${port}`);\n\nLatticeGateway.startAsHttpEndpoint({\n  port,\n  queueServiceConfig: { type: \"memory\", defaultStartPollingQueue: true },\n});\n","/* eslint-disable no-console */\n\nimport {\n  registerAgentLattices,\n  AgentType,\n  AgentConfig,\n} from \"@axiom-lattice/core\";\nimport z from \"zod\";\n\nconst subResearchPrompt = `You are a dedicated researcher. Your job is to conduct research based on the users questions.\n\nConduct thorough research and then reply to the user with a detailed answer to their question\n\nonly your FINAL answer will be passed on to the user. They will have NO knowledge of anything except your final message, so your final report should be your final message!`;\n\nconst subCritiquePrompt = `You are a dedicated editor. You are being tasked to critique a report.\n\nYou can find the report at \\`final_report.md\\`.\n\nYou can find the question/topic for this report at \\`question.txt\\`.\n\nThe user may ask for specific areas to critique the report in. Respond to the user with a detailed critique of the report. Things that could be improved.\n\nYou can use the search tool to search for information, if that will help you critique the report\n\nDo not write to the \\`final_report.md\\` yourself.\n\nThings to check:\n- Check that each section is appropriately named\n- Check that the report is written as you would find in an essay or a textbook - it should be text heavy, do not let it just be a list of bullet points!\n- Check that the report is comprehensive. If any paragraphs or sections are short, or missing important details, point it out.\n- Check that the article covers key areas of the industry, ensures overall understanding, and does not omit important parts.\n- Check that the article deeply analyzes causes, impacts, and trends, providing valuable insights\n- Check that the article closely follows the research topic and directly answers questions\n- Check that the article has a clear structure, fluent language, and is easy to understand.\n`;\n\n// Prompt prefix to steer the agent to be an expert researcher\nconst researchInstructions = `You are an expert researcher. Your job is to conduct thorough research, and then write a polished report.\n\nThe first thing you should do is to write the original user question to \\`question.txt\\` so you have a record of it.\n\nUse the research-agent to conduct deep research. It will respond to your questions/topics with a detailed answer.\n\nWhen you think you enough information to write a final report, write it to \\`final_report.md\\`\n\nYou can call the critique-agent to get a critique of the final report. After that (if needed) you can do more research and edit the \\`final_report.md\\`\nYou can do this however many times you want until are you satisfied with the result.\n\nOnly edit the file once at a time (if you call this tool in parallel, there may be conflicts).\n\nHere are instructions for writing the final report:\n\n<report_instructions>\n\nCRITICAL: Make sure the answer is written in the same language as the human messages! If you make a todo plan - you should note in the plan what language the report should be in so you dont forget!\nNote: the language the report should be in is the language the QUESTION is in, not the language/country that the question is ABOUT.\n\nPlease create a detailed answer to the overall research brief that:\n1. Is well-organized with proper headings (# for title, ## for sections, ### for subsections)\n2. Includes specific facts and insights from the research\n3. References relevant sources using [Title](URL) format\n4. Provides a balanced, thorough analysis. Be as comprehensive as possible, and include all information that is relevant to the overall research question. People are using you for deep research and will expect detailed, comprehensive answers.\n5. Includes a \"Sources\" section at the end with all referenced links\n\nYou can structure your report in a number of different ways. Here are some examples:\n\nTo answer a question that asks you to compare two things, you might structure your report like this:\n1/ intro\n2/ overview of topic A\n3/ overview of topic B\n4/ comparison between A and B\n5/ conclusion\n\nTo answer a question that asks you to return a list of things, you might only need a single section which is the entire list.\n1/ list of things or table of things\nOr, you could choose to make each item in the list a separate section in the report. When asked for lists, you don't need an introduction or conclusion.\n1/ item 1\n2/ item 2\n3/ item 3\n\nTo answer a question that asks you to summarize a topic, give a report, or give an overview, you might structure your report like this:\n1/ overview of topic\n2/ concept 1\n3/ concept 2\n4/ concept 3\n5/ conclusion\n\nIf you think you can answer the question with a single section, you can do that too!\n1/ answer\n\nREMEMBER: Section is a VERY fluid and loose concept. You can structure your report however you think is best, including in ways that are not listed above!\nMake sure that your sections are cohesive, and make sense for the reader.\n\nFor each section of the report, do the following:\n- Use simple, clear language\n- Use ## for section title (Markdown format) for each section of the report\n- Do NOT ever refer to yourself as the writer of the report. This should be a professional report without any self-referential language.\n- Do not say what you are doing in the report. Just write the report without any commentary from yourself.\n- Each section should be as long as necessary to deeply answer the question with the information you have gathered. It is expected that sections will be fairly long and verbose. You are writing a deep research report, and users will expect a thorough answer.\n- Use bullet points to list out information when appropriate, but by default, write in paragraph form.\n\nREMEMBER:\nThe brief and research may be in English, but you need to translate this information to the right language when writing the final answer.\nMake sure the final answer report is in the SAME language as the human messages in the message history.\n\nFormat the report in clear markdown with proper structure and include source references where appropriate.\n\n<Citation Rules>\n- Assign each unique URL a single citation number in your text\n- End with ### Sources that lists each source with corresponding numbers\n- IMPORTANT: Number sources sequentially without gaps (1,2,3,4...) in the final list regardless of which sources you choose\n- Each source should be a separate line item in a list, so that in markdown it is rendered as a list.\n- Example format:\n  [1] Source Title: URL\n  [2] Source Title: URL\n- Citations are extremely important. Make sure to include these, and pay a lot of attention to getting these right. Users will often use these citations to look into more information.\n</Citation Rules>\n</report_instructions>\n\nYou have access to a few tools.\n\n## \\`internet_search\\`\n\nUse this to run an internet search for a given query. You can specify the number of results, the topic, and whether raw content should be included.\n`;\n\nconst research_agents: AgentConfig[] = [\n  {\n    key: \"deep_research_agent\",\n    name: \"Deep Research Agent\",\n    description:\n      \"Used to research more in depth questions. Only give this researcher one topic at a time. Do not pass multiple sub questions to this researcher. Instead, you should break down a large topic into the necessary components, and then call multiple research agents in parallel, one for each sub question.\",\n    type: AgentType.DEEP_AGENT,\n    tools: [\"internet_search\"],\n    prompt: researchInstructions,\n    subAgents: [\"critique-agent\", \"research-agent\"],\n    schema: z.object({\n      test: z.string().optional(),\n    }),\n  },\n  {\n    key: \"research-agent\",\n    name: \"research-agent\",\n    type: AgentType.REACT,\n    description:\n      \"Used to research more in depth questions. Only give this researcher one topic at a time. Do not pass multiple sub questions to this researcher. Instead, you should break down a large topic into the necessary components, and then call multiple research agents in parallel, one for each sub question.\",\n    prompt: subResearchPrompt,\n    tools: [\"internet_search\"],\n  },\n  {\n    key: \"critique-agent\",\n    name: \"critique-agent\",\n    type: AgentType.REACT,\n    description:\n      \"Used to critique the final report. Give this agent some infomration about how you want it to critique the report.\",\n    prompt: subCritiquePrompt,\n  },\n];\n\nregisterAgentLattices(research_agents);\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA;AAAA,iBAAAA,UAAAC,SAAA;AAAA,IAAAA,QAAA;AAAA,MACE,MAAQ;AAAA,MACR,SAAW;AAAA,MACX,MAAQ;AAAA,MACR,KAAO;AAAA,QACL,yBAAyB;AAAA,MAC3B;AAAA,MACA,SAAW;AAAA,QACT,OAAS;AAAA,QACT,OAAS;AAAA,QACT,KAAO;AAAA,QACP,eAAe;AAAA,QACf,aAAa;AAAA,QACb,eAAe;AAAA,QACf,MAAQ;AAAA,QACR,MAAQ;AAAA,QACR,cAAc;AAAA,QACd,iBAAiB;AAAA,MACnB;AAAA,MACA,UAAY,CAAC;AAAA,MACb,QAAU;AAAA,MACV,SAAW;AAAA,MACX,aAAe;AAAA,MACf,cAAgB;AAAA,QACd,uBAAuB;AAAA,QACvB,0BAA0B;AAAA,QAC1B,QAAU;AAAA,QACV,MAAQ;AAAA,QACR,KAAO;AAAA,QACP,sBAAsB;AAAA,MACxB;AAAA,MACA,iBAAmB;AAAA,QACjB,eAAe;AAAA,QACf,iBAAiB;AAAA,QACjB,eAAe;AAAA,QACf,eAAe;AAAA,QACf,oCAAoC;AAAA,QACpC,6BAA6B;AAAA,QAC7B,QAAU;AAAA,QACV,MAAQ;AAAA,QACR,SAAW;AAAA,QACX,WAAW;AAAA,QACX,WAAW;AAAA,QACX,MAAQ;AAAA,QACR,YAAc;AAAA,MAChB;AAAA,IACF;AAAA;AAAA;;;AC9CA,oBAAmB;AAEnB,qBAA+B;AAC/B,IAAAC,eAGO;;;ACJP,kBAIO;AACP,iBAAc;AAEd,IAAM,oBAAoB;AAAA;AAAA;AAAA;AAAA;AAM1B,IAAM,oBAAoB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAuB1B,IAAM,uBAAuB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAyF7B,IAAM,kBAAiC;AAAA,EACrC;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,aACE;AAAA,IACF,MAAM,sBAAU;AAAA,IAChB,OAAO,CAAC,iBAAiB;AAAA,IACzB,QAAQ;AAAA,IACR,WAAW,CAAC,kBAAkB,gBAAgB;AAAA,IAC9C,QAAQ,WAAAC,QAAE,OAAO;AAAA,MACf,MAAM,WAAAA,QAAE,OAAO,EAAE,SAAS;AAAA,IAC5B,CAAC;AAAA,EACH;AAAA,EACA;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,MAAM,sBAAU;AAAA,IAChB,aACE;AAAA,IACF,QAAQ;AAAA,IACR,OAAO,CAAC,iBAAiB;AAAA,EAC3B;AAAA,EACA;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,MAAM,sBAAU;AAAA,IAChB,aACE;AAAA,IACF,QAAQ;AAAA,EACV;AACF;AAAA,IAEA,mCAAsB,eAAe;;;ADxJrC,kBAAiB;AAEjB,IAAM,kBAAkB,kBAA2B;AACnD,IAAM,cAAa,oBAAI,KAAK,GAAE,YAAY;AAC1C,IAAM,SAAS,QAAQ,IAAI,aAAa;AAGxC,QAAQ,IAAI;AAAA;AAAA;AAAA,mBAGE,eAAe;AAAA,sBACZ,UAAU;AAAA,uBACT,SAAS,gBAAgB,YAAY;AAAA;AAAA,CAEtD;AAED,cAAAC,QAAO,OAAO,EAAE,MAAM,YAAAC,QAAK,QAAQ,WAAW,SAAS,EAAE,CAAC;AAG1D,SAAS,YAAoB;AAC3B,QAAM,OAAO,QAAQ,KAAK,MAAM,CAAC;AACjC,QAAM,YAAY,KAAK,UAAU,CAAC,QAAQ,QAAQ,YAAY,QAAQ,IAAI;AAE1E,MAAI,cAAc,MAAM,KAAK,YAAY,CAAC,GAAG;AAC3C,UAAMC,QAAO,SAAS,KAAK,YAAY,CAAC,GAAG,EAAE;AAC7C,QAAI,CAAC,MAAMA,KAAI,KAAKA,QAAO,KAAKA,QAAO,OAAO;AAC5C,aAAOA;AAAA,IACT;AACA,YAAQ;AAAA,MACN,uBAAuB,KAAK,YAAY,CAAC,CAAC;AAAA,IAC5C;AAAA,EACF;AAGA,MAAI,QAAQ,IAAI,MAAM;AACpB,UAAMA,QAAO,SAAS,QAAQ,IAAI,MAAM,EAAE;AAC1C,QAAI,CAAC,MAAMA,KAAI,KAAKA,QAAO,KAAKA,QAAO,OAAO;AAC5C,aAAOA;AAAA,IACT;AACA,YAAQ;AAAA,MACN,sCAAsC,QAAQ,IAAI,IAAI;AAAA,IACxD;AAAA,EACF;AAGA,SAAO;AACT;AAAA,IAGA;AAAA,EACE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAiBA;AAAA,IACE,OAAO;AAAA,IACP,UAAU;AAAA,IACV,WAAW;AAAA,IACX,eAAe;AAAA,EACjB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAeF;AACA,8BAAe,sBAAsB,8BAAe,GAAG;AAEvD,IAAM,OAAO,UAAU;AACvB,QAAQ,IAAI,2BAA2B,IAAI,EAAE;AAE7C,8BAAe,oBAAoB;AAAA,EACjC;AAAA,EACA,oBAAoB,EAAE,MAAM,UAAU,0BAA0B,KAAK;AACvE,CAAC;","names":["exports","module","import_core","z","dotenv","path","port"]}
+{"version":3,"sources":["../package.json","../src/index.ts","../src/agents/research/index.ts","../src/agents/data_agent/index.ts"],"sourcesContent":["{\n  \"name\": \"@axiom-lattice/examples-deep_research\",\n  \"version\": \"1.0.14\",\n  \"main\": \"dist/index.js\",\n  \"bin\": {\n    \"lattice-deep-research\": \"./dist/index.js\"\n  },\n  \"scripts\": {\n    \"build\": \"tsup\",\n    \"start\": \"node dist/index.js\",\n    \"dev\": \"tsup src/index.ts --format cjs --dts --watch --onSuccess \\\"node dist/index.js\\\"\",\n    \"dev:nodemon\": \"nodemon --watch 'src/**/*.ts' --watch '../../packages/core/dist/**/*' --exec 'ts-node' -r tsconfig-paths/register src/index.ts\",\n    \"dev:serve\": \"tsup src/index.ts --format cjs --dts --watch --serve dist/index.js\",\n    \"dev:inspect\": \"tsup src/index.ts --format cjs --dts --watch --onSuccess \\\"node --inspect dist/index.js\\\"\",\n    \"lint\": \"tsc --noEmit\",\n    \"test\": \"jest\",\n    \"test:watch\": \"jest --watch\",\n    \"test:coverage\": \"jest --coverage\"\n  },\n  \"keywords\": [],\n  \"author\": \"\",\n  \"license\": \"ISC\",\n  \"description\": \"Deep Research Server for Axiom Lattice\",\n  \"dependencies\": {\n    \"@axiom-lattice/core\": \"workspace:*\",\n    \"@axiom-lattice/gateway\": \"workspace:*\",\n    \"@axiom-lattice/protocols\": \"workspace:*\",\n    \"@axiom-lattice/pg-stores\": \"workspace:*\",\n    \"dotenv\": \"^16.6.1\",\n    \"uuid\": \"^9.0.1\",\n    \"zod\": \"^3.24.2\",\n    \"zod-to-json-schema\": \"^3.24.3\"\n  },\n  \"devDependencies\": {\n    \"@types/jest\": \"^29.5.14\",\n    \"@types/lodash\": \"^4.17.16\",\n    \"@types/node\": \"^20.17.23\",\n    \"@types/uuid\": \"^9.0.8\",\n    \"@typescript-eslint/eslint-plugin\": \"^7.2.0\",\n    \"@typescript-eslint/parser\": \"^7.2.0\",\n    \"eslint\": \"^8.57.0\",\n    \"jest\": \"^29.7.0\",\n    \"nodemon\": \"^3.1.9\",\n    \"ts-jest\": \"^29.4.0\",\n    \"ts-node\": \"^10.9.2\",\n    \"tsup\": \"^8.5.0\",\n    \"typescript\": \"^5.8.2\"\n  }\n}\n","import dotenv from \"dotenv\";\n\nimport { LatticeGateway } from \"@axiom-lattice/gateway\";\nimport {\n  getScheduleLattice,\n  registerCheckpointSaver,\n  registerModelLattice,\n  registerScheduleLattice,\n} from \"@axiom-lattice/core\";\nimport \"./agents\";\n\nimport path from \"path\";\nimport { ScheduleType } from \"@axiom-lattice/protocols\";\nimport { PostgreSQLScheduleStorage } from \"@axiom-lattice/pg-stores\";\n// 在文件开头添加\nconst PACKAGE_VERSION = require(\"../package.json\").version;\nconst BUILD_TIME = new Date().toISOString();\nconst IS_DEV = process.env.NODE_ENV !== \"production\";\n\n// 在启动时输出\nconsole.log(`\n╔═══════════════════════════════════════╗\n║  Lattice Deep Research Server         ║\n║  Version: ${PACKAGE_VERSION}                          ║\n║  Build Time: ${BUILD_TIME}  ║\n║  Environment: ${IS_DEV ? \"Development\" : \"Production\"}              ║\n╚═══════════════════════════════════════╝\n`);\n// Load environment variables\ndotenv.config({ path: path.resolve(__dirname, \"../.env\") });\n\n// Parse command line arguments for port configuration\nfunction parsePort(): number {\n  const args = process.argv.slice(2);\n  const portIndex = args.findIndex((arg) => arg === \"--port\" || arg === \"-p\");\n\n  if (portIndex !== -1 && args[portIndex + 1]) {\n    const port = parseInt(args[portIndex + 1], 10);\n    if (!isNaN(port) && port > 0 && port < 65536) {\n      return port;\n    }\n    console.warn(\n      `Invalid port value: ${args[portIndex + 1]}, using default port 4001`\n    );\n  }\n\n  // Check environment variable\n  if (process.env.PORT) {\n    const port = parseInt(process.env.PORT, 10);\n    if (!isNaN(port) && port > 0 && port < 65536) {\n      return port;\n    }\n    console.warn(\n      `Invalid PORT environment variable: ${process.env.PORT}, using default port 4001`\n    );\n  }\n\n  // Default port\n  return 4001;\n}\n\n// Register default model Lattice\nregisterModelLattice(\n  \"default\",\n  // {\n  //   model: \"deepseek-chat\",\n  //   provider: \"deepseek\",\n  //   streaming: false,\n  // }\n  // {\n  //   model: \"deepseek-chat\",\n  //   provider: \"deepseek\",\n  //   streaming: false,\n  //   apiKeyEnvName: \"DEEPSEEK_API_KEY2\",\n  // },\n  // {\n  //   model: \"deepseek-v3-250324\",\n  //   provider: \"volcengine\",\n  //   streaming: false,\n  // },\n  {\n    model: \"kimi-k2-250905\",\n    provider: \"volcengine\",\n    streaming: true,\n    apiKeyEnvName: \"VOLCENGINE_API_KEY2\",\n  }\n  // {\n  //   model: \"kimi-k2-0711-preview\",\n  //   provider: \"openai\",\n  //   streaming: true,\n  //   apiKeyEnvName: \"KIMI_API_KEY\",\n  //   baseURL: \"https://api.moonshot.cn/v1\",\n  // }\n  // {\n  //   model: \"qwen-plus\",\n  //   provider: \"openai\",\n  //   streaming: false,\n  //   apiKeyEnvName: \"DASHSCOPE_API_KEY\",\n  //   baseURL: \"https://dashscope.aliyuncs.com/compatible-mode/v1\",\n  // }\n);\nLatticeGateway.registerLatticeRoutes(LatticeGateway.app);\n\n// // 注册 Schedule Lattice（使用 PostgreSQL 持久化）\n// registerScheduleLattice(\"default\", {\n//   name: \"Default Scheduler\",\n//   description: \"Production scheduler with PostgreSQL\",\n//   type: ScheduleType.POSTGRES,\n//   storage: new PostgreSQLScheduleStorage({\n//     poolConfig: process.env.DATABASE_URL || \"\",\n//   }),\n// });\n\n// const scheduler = getScheduleLattice(\"default\");\n// // 注册 Handler（每次服务启动时都需要注册）\n// scheduler.registerHandler(\"send-email\", async (payload, taskInfo) => {\n//   console.log(\"send-email\", payload, taskInfo);\n// });\n// scheduler.restore();\n\n// // 一次性延迟任务\n// scheduler.scheduleOnce(\n//   \"email-123\",\n//   \"send-email\",\n//   { to: \"user@example.com\", subject: \"Welcome!\" },\n//   { delayMs: 60000 } // 1分钟后执行\n// );\n\nconst port = parsePort();\nconsole.log(`Starting server on port ${port}`);\n\nLatticeGateway.startAsHttpEndpoint({\n  port,\n  queueServiceConfig: { type: \"memory\", defaultStartPollingQueue: true },\n});\n","/* eslint-disable no-console */\n\nimport {\n  registerAgentLattices,\n  AgentType,\n  AgentConfig,\n} from \"@axiom-lattice/core\";\nimport z from \"zod\";\n\nconst subResearchPrompt = `You are a dedicated researcher. Your job is to conduct research based on the users questions.\n\nConduct thorough research and then reply to the user with a detailed answer to their question\n\nonly your FINAL answer will be passed on to the user. They will have NO knowledge of anything except your final message, so your final report should be your final message!`;\n\nconst subCritiquePrompt = `You are a dedicated editor. You are being tasked to critique a report.\n\nYou can find the report at \\`final_report.md\\`.\n\nYou can find the question/topic for this report at \\`question.txt\\`.\n\nThe user may ask for specific areas to critique the report in. Respond to the user with a detailed critique of the report. Things that could be improved.\n\nYou can use the search tool to search for information, if that will help you critique the report\n\nDo not write to the \\`final_report.md\\` yourself.\n\nThings to check:\n- Check that each section is appropriately named\n- Check that the report is written as you would find in an essay or a textbook - it should be text heavy, do not let it just be a list of bullet points!\n- Check that the report is comprehensive. If any paragraphs or sections are short, or missing important details, point it out.\n- Check that the article covers key areas of the industry, ensures overall understanding, and does not omit important parts.\n- Check that the article deeply analyzes causes, impacts, and trends, providing valuable insights\n- Check that the article closely follows the research topic and directly answers questions\n- Check that the article has a clear structure, fluent language, and is easy to understand.\n`;\n\n// Prompt prefix to steer the agent to be an expert researcher\nconst researchInstructions = `You are an expert researcher. Your job is to conduct thorough research, and then write a polished report.\n\nThe first thing you should do is to write the original user question to \\`question.txt\\` so you have a record of it.\n\nUse the research-agent to conduct deep research. It will respond to your questions/topics with a detailed answer.\n\nWhen you think you enough information to write a final report, write it to \\`final_report.md\\`\n\nYou can call the critique-agent to get a critique of the final report. After that (if needed) you can do more research and edit the \\`final_report.md\\`\nYou can do this however many times you want until are you satisfied with the result.\n\nOnly edit the file once at a time (if you call this tool in parallel, there may be conflicts).\n\nHere are instructions for writing the final report:\n\n<report_instructions>\n\nCRITICAL: Make sure the answer is written in the same language as the human messages! If you make a todo plan - you should note in the plan what language the report should be in so you dont forget!\nNote: the language the report should be in is the language the QUESTION is in, not the language/country that the question is ABOUT.\n\nPlease create a detailed answer to the overall research brief that:\n1. Is well-organized with proper headings (# for title, ## for sections, ### for subsections)\n2. Includes specific facts and insights from the research\n3. References relevant sources using [Title](URL) format\n4. Provides a balanced, thorough analysis. Be as comprehensive as possible, and include all information that is relevant to the overall research question. People are using you for deep research and will expect detailed, comprehensive answers.\n5. Includes a \"Sources\" section at the end with all referenced links\n\nYou can structure your report in a number of different ways. Here are some examples:\n\nTo answer a question that asks you to compare two things, you might structure your report like this:\n1/ intro\n2/ overview of topic A\n3/ overview of topic B\n4/ comparison between A and B\n5/ conclusion\n\nTo answer a question that asks you to return a list of things, you might only need a single section which is the entire list.\n1/ list of things or table of things\nOr, you could choose to make each item in the list a separate section in the report. When asked for lists, you don't need an introduction or conclusion.\n1/ item 1\n2/ item 2\n3/ item 3\n\nTo answer a question that asks you to summarize a topic, give a report, or give an overview, you might structure your report like this:\n1/ overview of topic\n2/ concept 1\n3/ concept 2\n4/ concept 3\n5/ conclusion\n\nIf you think you can answer the question with a single section, you can do that too!\n1/ answer\n\nREMEMBER: Section is a VERY fluid and loose concept. You can structure your report however you think is best, including in ways that are not listed above!\nMake sure that your sections are cohesive, and make sense for the reader.\n\nFor each section of the report, do the following:\n- Use simple, clear language\n- Use ## for section title (Markdown format) for each section of the report\n- Do NOT ever refer to yourself as the writer of the report. This should be a professional report without any self-referential language.\n- Do not say what you are doing in the report. Just write the report without any commentary from yourself.\n- Each section should be as long as necessary to deeply answer the question with the information you have gathered. It is expected that sections will be fairly long and verbose. You are writing a deep research report, and users will expect a thorough answer.\n- Use bullet points to list out information when appropriate, but by default, write in paragraph form.\n\nREMEMBER:\nThe brief and research may be in English, but you need to translate this information to the right language when writing the final answer.\nMake sure the final answer report is in the SAME language as the human messages in the message history.\n\nFormat the report in clear markdown with proper structure and include source references where appropriate.\n\n<Citation Rules>\n- Assign each unique URL a single citation number in your text\n- End with ### Sources that lists each source with corresponding numbers\n- IMPORTANT: Number sources sequentially without gaps (1,2,3,4...) in the final list regardless of which sources you choose\n- Each source should be a separate line item in a list, so that in markdown it is rendered as a list.\n- Example format:\n  [1] Source Title: URL\n  [2] Source Title: URL\n- Citations are extremely important. Make sure to include these, and pay a lot of attention to getting these right. Users will often use these citations to look into more information.\n</Citation Rules>\n</report_instructions>\n\nYou have access to a few tools.\n\n## \\`internet_search\\`\n\nUse this to run an internet search for a given query. You can specify the number of results, the topic, and whether raw content should be included.\n`;\n\nconst research_agents: AgentConfig[] = [\n  {\n    key: \"deep_research_agent\",\n    name: \"Deep Research Agent\",\n    description:\n      \"Used to research more in depth questions. Only give this researcher one topic at a time. Do not pass multiple sub questions to this researcher. Instead, you should break down a large topic into the necessary components, and then call multiple research agents in parallel, one for each sub question.\",\n    type: AgentType.DEEP_AGENT,\n    tools: [\"internet_search\"],\n    prompt: researchInstructions,\n    subAgents: [\"critique-agent\", \"research-agent\"],\n    schema: z.object({\n      test: z.string().optional(),\n    }),\n  },\n  {\n    key: \"research-agent\",\n    name: \"research-agent\",\n    type: AgentType.REACT,\n    description:\n      \"Used to research more in depth questions. Only give this researcher one topic at a time. Do not pass multiple sub questions to this researcher. Instead, you should break down a large topic into the necessary components, and then call multiple research agents in parallel, one for each sub question.\",\n    prompt: subResearchPrompt,\n    tools: [\"internet_search\"],\n  },\n  {\n    key: \"critique-agent\",\n    name: \"critique-agent\",\n    type: AgentType.REACT,\n    description:\n      \"Used to critique the final report. Give this agent some infomration about how you want it to critique the report.\",\n    prompt: subCritiquePrompt,\n  },\n];\n\nregisterAgentLattices(research_agents);\n","/**\n * Data Agent - NL2SQL Agent\n * An intelligent agent that converts natural language questions to SQL queries\n * and retrieves data from connected databases.\n */\n\nimport {\n  registerAgentLattices,\n  AgentType,\n  AgentConfig,\n  sqlDatabaseManager,\n  DatabaseConfig,\n} from \"@axiom-lattice/core\";\nimport z from \"zod\";\n\n/**\n * System prompt for the main data agent\n * This agent orchestrates the NL2SQL process\n */\nconst dataAgentPrompt = `You are an expert Data Analyst AI assistant specialized in converting natural language questions into SQL queries and retrieving data from databases.\n\nYour primary responsibilities:\n1. Understand user questions about data\n2. Explore the database schema to understand available tables and their relationships\n3. Write accurate and efficient SQL queries to answer questions\n4. Present results in a clear and understandable format\n\n## Workflow\n\nWhen a user asks a question about data, follow these steps:\n\n### Step 1: Understand the Database Schema\n- First, use the \\`list_tables_sql\\` tool to see all available tables\n- Then, use the \\`info_sql\\` tool to get detailed schema information for relevant tables\n- Pay attention to:\n  - Column names and data types\n  - Primary keys and foreign keys (relationships between tables)\n  - Sample data to understand the data format\n\n### Step 2: Plan Your Query\n- Think about which tables you need to query\n- Consider if you need to JOIN multiple tables\n- Think about filtering conditions (WHERE clauses)\n- Consider if you need aggregations (COUNT, SUM, AVG, etc.)\n- Consider sorting and limiting results\n\n### Step 3: Validate Your Query\n- Use the \\`query_checker_sql\\` tool to validate your SQL query before execution\n- Fix any issues found by the checker\n- Make sure the query is safe and efficient\n\n### Step 4: Execute and Present Results\n- Use the \\`query_sql\\` tool to execute your validated query\n- Present the results in a clear format\n- Explain what the data means in context of the user's question\n- If the results are unexpected, analyze and explain possible reasons\n\n## SQL Best Practices\n\n1. **Be Specific**: Always specify column names instead of using SELECT *\n2. **Use Aliases**: Use meaningful table and column aliases for clarity\n3. **Handle NULLs**: Consider NULL values in your queries\n4. **Limit Results**: For exploratory queries, limit results to avoid overwhelming output\n5. **Optimize JOINs**: Use appropriate JOIN types (INNER, LEFT, etc.)\n6. **Use Indexes**: Structure queries to leverage indexes when possible\n\n## Communication Guidelines\n\n- Explain your thought process as you work\n- If you need clarification about the user's question, ask\n- If a query returns unexpected results, explain what might have happened\n- Suggest follow-up queries or analyses that might be helpful\n- Present data insights, not just raw results\n\n## Error Handling\n\n- If a query fails, analyze the error message\n- Try to fix the query and re-execute\n- If you cannot answer the question due to data limitations, explain clearly what is missing\n\nRemember: The goal is not just to write SQL, but to help users understand their data and make informed decisions.\n`;\n\n/**\n * System prompt for the SQL query builder sub-agent\n */\nconst sqlBuilderPrompt = `You are a SQL Expert sub-agent. Your job is to write precise, efficient SQL queries.\n\nWhen given a task:\n1. Analyze the schema information provided\n2. Write the most appropriate SQL query\n3. Validate the query using query_checker_sql\n4. Return the finalized query\n\nFocus on:\n- Query correctness\n- Query efficiency\n- Proper use of JOINs and subqueries\n- Appropriate use of aggregate functions\n- Clear column naming and aliasing\n\nIf you encounter issues:\n- Analyze the error\n- Modify the query accordingly\n- Re-validate before returning\n\nAlways return your final query in a clear format for execution.\n`;\n\n/**\n * System prompt for the data analysis sub-agent\n */\nconst dataAnalysisPrompt = `You are a Data Analysis Expert sub-agent. Your job is to interpret query results and provide insights.\n\nWhen given query results:\n1. Summarize the key findings\n2. Identify patterns or anomalies\n3. Provide context and interpretation\n4. Suggest potential follow-up analyses\n\nFocus on:\n- Clear, concise summaries\n- Statistical insights when appropriate\n- Business context interpretation\n- Visualization suggestions if applicable\n\nPresent your analysis in a structured format:\n- Summary\n- Key Findings\n- Insights\n- Recommendations (if any)\n`;\n\n/**\n * Data Agent configurations\n */\nconst data_agents: AgentConfig[] = [\n  {\n    key: \"data_agent\",\n    name: \"Data Agent\",\n    description:\n      \"An intelligent NL2SQL agent that converts natural language questions into SQL queries and retrieves data from databases. Use this agent for data analysis tasks, database queries, and data exploration.\",\n    type: AgentType.DEEP_AGENT,\n    tools: [\"list_tables_sql\", \"info_sql\", \"query_sql\", \"query_checker_sql\"],\n    prompt: dataAgentPrompt,\n    subAgents: [\"sql-builder-agent\", \"data-analysis-agent\"],\n    schema: z.object({}),\n    /**\n     * Runtime configuration injected into tool execution context.\n     * databaseKey: The database key registered via sqlDatabaseManager.\n     * Tools will access this via config.configurable.runConfig.databaseKey\n     */\n    runConfig: {\n      databaseKey: \"fulidb\", // Set this to the registered database key\n    },\n  },\n  {\n    key: \"sql-builder-agent\",\n    name: \"sql-builder-agent\",\n    type: AgentType.REACT,\n    description:\n      \"A specialized sub-agent for building and validating SQL queries. Give this agent schema information and a data question, and it will return an optimized SQL query.\",\n    prompt: sqlBuilderPrompt,\n    tools: [\"info_sql\", \"query_checker_sql\"],\n    // Sub-agents inherit runConfig from parent agent via the execution context\n  },\n  {\n    key: \"data-analysis-agent\",\n    name: \"data-analysis-agent\",\n    type: AgentType.REACT,\n    description:\n      \"A specialized sub-agent for analyzing query results and providing insights. Give this agent query results and it will provide a structured analysis.\",\n    prompt: dataAnalysisPrompt,\n    tools: [],\n  },\n];\n\n// Register the agents\nregisterAgentLattices(data_agents);\n\n/**\n * Helper function to initialize database connection for the data agent\n * Call this before using the data agent\n *\n * @param key - Unique identifier for the database connection\n * @param config - Database configuration\n *\n * @example\n * ```typescript\n * import { initializeDataAgentDatabase } from \"@axiom-lattice/examples-deep_research/agents/data_agent\";\n *\n * // Using connection string\n * initializeDataAgentDatabase(\"mydb\", {\n *   type: \"postgres\",\n *   connectionString: process.env.DATABASE_URL\n * });\n *\n * // Or using individual parameters\n * initializeDataAgentDatabase(\"mydb\", {\n *   type: \"postgres\",\n *   host: \"localhost\",\n *   port: 5432,\n *   database: \"mydb\",\n *   user: \"user\",\n *   password: \"password\"\n * });\n * ```\n */\nexport function initializeDataAgentDatabase(\n  key: string,\n  config: DatabaseConfig\n): void {\n  sqlDatabaseManager.registerDatabase(key, config);\n}\n\n/**\n * Helper function to set the default database for the data agent\n *\n * @param key - Database key to set as default\n */\nexport function setDefaultDatabase(key: string): void {\n  sqlDatabaseManager.setDefaultDatabase(key);\n}\n\n/**\n * Export types for external use\n */\nexport type { DatabaseConfig };\n\ninitializeDataAgentDatabase(\"fulidb\", {\n  type: \"postgres\",\n  connectionString: process.env.DATABASE_URL,\n  database: \"postgres\",\n});\n"],"mappings":";;;;;;;;;;;;;;;;;;;;;;;;;;;;;AAAA;AAAA,iBAAAA,UAAAC,SAAA;AAAA,IAAAA,QAAA;AAAA,MACE,MAAQ;AAAA,MACR,SAAW;AAAA,MACX,MAAQ;AAAA,MACR,KAAO;AAAA,QACL,yBAAyB;AAAA,MAC3B;AAAA,MACA,SAAW;AAAA,QACT,OAAS;AAAA,QACT,OAAS;AAAA,QACT,KAAO;AAAA,QACP,eAAe;AAAA,QACf,aAAa;AAAA,QACb,eAAe;AAAA,QACf,MAAQ;AAAA,QACR,MAAQ;AAAA,QACR,cAAc;AAAA,QACd,iBAAiB;AAAA,MACnB;AAAA,MACA,UAAY,CAAC;AAAA,MACb,QAAU;AAAA,MACV,SAAW;AAAA,MACX,aAAe;AAAA,MACf,cAAgB;AAAA,QACd,uBAAuB;AAAA,QACvB,0BAA0B;AAAA,QAC1B,4BAA4B;AAAA,QAC5B,4BAA4B;AAAA,QAC5B,QAAU;AAAA,QACV,MAAQ;AAAA,QACR,KAAO;AAAA,QACP,sBAAsB;AAAA,MACxB;AAAA,MACA,iBAAmB;AAAA,QACjB,eAAe;AAAA,QACf,iBAAiB;AAAA,QACjB,eAAe;AAAA,QACf,eAAe;AAAA,QACf,oCAAoC;AAAA,QACpC,6BAA6B;AAAA,QAC7B,QAAU;AAAA,QACV,MAAQ;AAAA,QACR,SAAW;AAAA,QACX,WAAW;AAAA,QACX,WAAW;AAAA,QACX,MAAQ;AAAA,QACR,YAAc;AAAA,MAChB;AAAA,IACF;AAAA;AAAA;;;AChDA,oBAAmB;AAEnB,qBAA+B;AAC/B,IAAAC,eAKO;;;ACNP,kBAIO;AACP,iBAAc;AAEd,IAAM,oBAAoB;AAAA;AAAA;AAAA;AAAA;AAM1B,IAAM,oBAAoB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAuB1B,IAAM,uBAAuB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAyF7B,IAAM,kBAAiC;AAAA,EACrC;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,aACE;AAAA,IACF,MAAM,sBAAU;AAAA,IAChB,OAAO,CAAC,iBAAiB;AAAA,IACzB,QAAQ;AAAA,IACR,WAAW,CAAC,kBAAkB,gBAAgB;AAAA,IAC9C,QAAQ,WAAAC,QAAE,OAAO;AAAA,MACf,MAAM,WAAAA,QAAE,OAAO,EAAE,SAAS;AAAA,IAC5B,CAAC;AAAA,EACH;AAAA,EACA;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,MAAM,sBAAU;AAAA,IAChB,aACE;AAAA,IACF,QAAQ;AAAA,IACR,OAAO,CAAC,iBAAiB;AAAA,EAC3B;AAAA,EACA;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,MAAM,sBAAU;AAAA,IAChB,aACE;AAAA,IACF,QAAQ;AAAA,EACV;AACF;AAAA,IAEA,mCAAsB,eAAe;;;AC1JrC,IAAAC,eAMO;AACP,IAAAC,cAAc;AAMd,IAAM,kBAAkB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAmExB,IAAM,mBAAmB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AA0BzB,IAAM,qBAAqB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAwB3B,IAAM,cAA6B;AAAA,EACjC;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,aACE;AAAA,IACF,MAAM,uBAAU;AAAA,IAChB,OAAO,CAAC,mBAAmB,YAAY,aAAa,mBAAmB;AAAA,IACvE,QAAQ;AAAA,IACR,WAAW,CAAC,qBAAqB,qBAAqB;AAAA,IACtD,QAAQ,YAAAC,QAAE,OAAO,CAAC,CAAC;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,IAMnB,WAAW;AAAA,MACT,aAAa;AAAA;AAAA,IACf;AAAA,EACF;AAAA,EACA;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,MAAM,uBAAU;AAAA,IAChB,aACE;AAAA,IACF,QAAQ;AAAA,IACR,OAAO,CAAC,YAAY,mBAAmB;AAAA;AAAA,EAEzC;AAAA,EACA;AAAA,IACE,KAAK;AAAA,IACL,MAAM;AAAA,IACN,MAAM,uBAAU;AAAA,IAChB,aACE;AAAA,IACF,QAAQ;AAAA,IACR,OAAO,CAAC;AAAA,EACV;AACF;AAAA,IAGA,oCAAsB,WAAW;AA8B1B,SAAS,4BACd,KACA,QACM;AACN,kCAAmB,iBAAiB,KAAK,MAAM;AACjD;AAgBA,4BAA4B,UAAU;AAAA,EACpC,MAAM;AAAA,EACN,kBAAkB,QAAQ,IAAI;AAAA,EAC9B,UAAU;AACZ,CAAC;;;AF9ND,kBAAiB;AAIjB,IAAM,kBAAkB,kBAA2B;AACnD,IAAM,cAAa,oBAAI,KAAK,GAAE,YAAY;AAC1C,IAAM,SAAS,QAAQ,IAAI,aAAa;AAGxC,QAAQ,IAAI;AAAA;AAAA;AAAA,mBAGE,eAAe;AAAA,sBACZ,UAAU;AAAA,uBACT,SAAS,gBAAgB,YAAY;AAAA;AAAA,CAEtD;AAED,cAAAC,QAAO,OAAO,EAAE,MAAM,YAAAC,QAAK,QAAQ,WAAW,SAAS,EAAE,CAAC;AAG1D,SAAS,YAAoB;AAC3B,QAAM,OAAO,QAAQ,KAAK,MAAM,CAAC;AACjC,QAAM,YAAY,KAAK,UAAU,CAAC,QAAQ,QAAQ,YAAY,QAAQ,IAAI;AAE1E,MAAI,cAAc,MAAM,KAAK,YAAY,CAAC,GAAG;AAC3C,UAAMC,QAAO,SAAS,KAAK,YAAY,CAAC,GAAG,EAAE;AAC7C,QAAI,CAAC,MAAMA,KAAI,KAAKA,QAAO,KAAKA,QAAO,OAAO;AAC5C,aAAOA;AAAA,IACT;AACA,YAAQ;AAAA,MACN,uBAAuB,KAAK,YAAY,CAAC,CAAC;AAAA,IAC5C;AAAA,EACF;AAGA,MAAI,QAAQ,IAAI,MAAM;AACpB,UAAMA,QAAO,SAAS,QAAQ,IAAI,MAAM,EAAE;AAC1C,QAAI,CAAC,MAAMA,KAAI,KAAKA,QAAO,KAAKA,QAAO,OAAO;AAC5C,aAAOA;AAAA,IACT;AACA,YAAQ;AAAA,MACN,sCAAsC,QAAQ,IAAI,IAAI;AAAA,IACxD;AAAA,EACF;AAGA,SAAO;AACT;AAAA,IAGA;AAAA,EACE;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA,EAiBA;AAAA,IACE,OAAO;AAAA,IACP,UAAU;AAAA,IACV,WAAW;AAAA,IACX,eAAe;AAAA,EACjB;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAAA;AAeF;AACA,8BAAe,sBAAsB,8BAAe,GAAG;AA2BvD,IAAM,OAAO,UAAU;AACvB,QAAQ,IAAI,2BAA2B,IAAI,EAAE;AAE7C,8BAAe,oBAAoB;AAAA,EACjC;AAAA,EACA,oBAAoB,EAAE,MAAM,UAAU,0BAA0B,KAAK;AACvE,CAAC;","names":["exports","module","import_core","z","import_core","import_zod","z","dotenv","path","port"]}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@axiom-lattice/examples-deep_research",
-  "version": "1.0.13",
+  "version": "1.0.14",
   "main": "dist/index.js",
   "bin": {
     "lattice-deep-research": "./dist/index.js"
@@ -14,8 +14,10 @@
     "uuid": "^9.0.1",
     "zod": "^3.24.2",
     "zod-to-json-schema": "^3.24.3",
-    "@axiom-lattice/core": "2.1.13",
-    "@axiom-lattice/gateway": "2.1.18"
+    "@axiom-lattice/core": "2.1.14",
+    "@axiom-lattice/gateway": "2.1.19",
+    "@axiom-lattice/protocols": "2.1.8",
+    "@axiom-lattice/pg-stores": "1.0.3"
   },
   "devDependencies": {
     "@types/jest": "^29.5.14",

package/src/agents/data_agent/index.ts

@@ -0,0 +1,234 @@
+/**
+ * Data Agent - NL2SQL Agent
+ * An intelligent agent that converts natural language questions to SQL queries
+ * and retrieves data from connected databases.
+ */
+
+import {
+  registerAgentLattices,
+  AgentType,
+  AgentConfig,
+  sqlDatabaseManager,
+  DatabaseConfig,
+} from "@axiom-lattice/core";
+import z from "zod";
+
+/**
+ * System prompt for the main data agent
+ * This agent orchestrates the NL2SQL process
+ */
+const dataAgentPrompt = `You are an expert Data Analyst AI assistant specialized in converting natural language questions into SQL queries and retrieving data from databases.
+
+Your primary responsibilities:
+1. Understand user questions about data
+2. Explore the database schema to understand available tables and their relationships
+3. Write accurate and efficient SQL queries to answer questions
+4. Present results in a clear and understandable format
+
+## Workflow
+
+When a user asks a question about data, follow these steps:
+
+### Step 1: Understand the Database Schema
+- First, use the \`list_tables_sql\` tool to see all available tables
+- Then, use the \`info_sql\` tool to get detailed schema information for relevant tables
+- Pay attention to:
+  - Column names and data types
+  - Primary keys and foreign keys (relationships between tables)
+  - Sample data to understand the data format
+
+### Step 2: Plan Your Query
+- Think about which tables you need to query
+- Consider if you need to JOIN multiple tables
+- Think about filtering conditions (WHERE clauses)
+- Consider if you need aggregations (COUNT, SUM, AVG, etc.)
+- Consider sorting and limiting results
+
+### Step 3: Validate Your Query
+- Use the \`query_checker_sql\` tool to validate your SQL query before execution
+- Fix any issues found by the checker
+- Make sure the query is safe and efficient
+
+### Step 4: Execute and Present Results
+- Use the \`query_sql\` tool to execute your validated query
+- Present the results in a clear format
+- Explain what the data means in context of the user's question
+- If the results are unexpected, analyze and explain possible reasons
+
+## SQL Best Practices
+
+1. **Be Specific**: Always specify column names instead of using SELECT *
+2. **Use Aliases**: Use meaningful table and column aliases for clarity
+3. **Handle NULLs**: Consider NULL values in your queries
+4. **Limit Results**: For exploratory queries, limit results to avoid overwhelming output
+5. **Optimize JOINs**: Use appropriate JOIN types (INNER, LEFT, etc.)
+6. **Use Indexes**: Structure queries to leverage indexes when possible
+
+## Communication Guidelines
+
+- Explain your thought process as you work
+- If you need clarification about the user's question, ask
+- If a query returns unexpected results, explain what might have happened
+- Suggest follow-up queries or analyses that might be helpful
+- Present data insights, not just raw results
+
+## Error Handling
+
+- If a query fails, analyze the error message
+- Try to fix the query and re-execute
+- If you cannot answer the question due to data limitations, explain clearly what is missing
+
+Remember: The goal is not just to write SQL, but to help users understand their data and make informed decisions.
+`;
+
+/**
+ * System prompt for the SQL query builder sub-agent
+ */
+const sqlBuilderPrompt = `You are a SQL Expert sub-agent. Your job is to write precise, efficient SQL queries.
+
+When given a task:
+1. Analyze the schema information provided
+2. Write the most appropriate SQL query
+3. Validate the query using query_checker_sql
+4. Return the finalized query
+
+Focus on:
+- Query correctness
+- Query efficiency
+- Proper use of JOINs and subqueries
+- Appropriate use of aggregate functions
+- Clear column naming and aliasing
+
+If you encounter issues:
+- Analyze the error
+- Modify the query accordingly
+- Re-validate before returning
+
+Always return your final query in a clear format for execution.
+`;
+
+/**
+ * System prompt for the data analysis sub-agent
+ */
+const dataAnalysisPrompt = `You are a Data Analysis Expert sub-agent. Your job is to interpret query results and provide insights.
+
+When given query results:
+1. Summarize the key findings
+2. Identify patterns or anomalies
+3. Provide context and interpretation
+4. Suggest potential follow-up analyses
+
+Focus on:
+- Clear, concise summaries
+- Statistical insights when appropriate
+- Business context interpretation
+- Visualization suggestions if applicable
+
+Present your analysis in a structured format:
+- Summary
+- Key Findings
+- Insights
+- Recommendations (if any)
+`;
+
+/**
+ * Data Agent configurations
+ */
+const data_agents: AgentConfig[] = [
+  {
+    key: "data_agent",
+    name: "Data Agent",
+    description:
+      "An intelligent NL2SQL agent that converts natural language questions into SQL queries and retrieves data from databases. Use this agent for data analysis tasks, database queries, and data exploration.",
+    type: AgentType.DEEP_AGENT,
+    tools: ["list_tables_sql", "info_sql", "query_sql", "query_checker_sql"],
+    prompt: dataAgentPrompt,
+    subAgents: ["sql-builder-agent", "data-analysis-agent"],
+    schema: z.object({}),
+    /**
+     * Runtime configuration injected into tool execution context.
+     * databaseKey: The database key registered via sqlDatabaseManager.
+     * Tools will access this via config.configurable.runConfig.databaseKey
+     */
+    runConfig: {
+      databaseKey: "fulidb", // Set this to the registered database key
+    },
+  },
+  {
+    key: "sql-builder-agent",
+    name: "sql-builder-agent",
+    type: AgentType.REACT,
+    description:
+      "A specialized sub-agent for building and validating SQL queries. Give this agent schema information and a data question, and it will return an optimized SQL query.",
+    prompt: sqlBuilderPrompt,
+    tools: ["info_sql", "query_checker_sql"],
+    // Sub-agents inherit runConfig from parent agent via the execution context
+  },
+  {
+    key: "data-analysis-agent",
+    name: "data-analysis-agent",
+    type: AgentType.REACT,
+    description:
+      "A specialized sub-agent for analyzing query results and providing insights. Give this agent query results and it will provide a structured analysis.",
+    prompt: dataAnalysisPrompt,
+    tools: [],
+  },
+];
+
+// Register the agents
+registerAgentLattices(data_agents);
+
+/**
+ * Helper function to initialize database connection for the data agent
+ * Call this before using the data agent
+ *
+ * @param key - Unique identifier for the database connection
+ * @param config - Database configuration
+ *
+ * @example
+ * ```typescript
+ * import { initializeDataAgentDatabase } from "@axiom-lattice/examples-deep_research/agents/data_agent";
+ *
+ * // Using connection string
+ * initializeDataAgentDatabase("mydb", {
+ *   type: "postgres",
+ *   connectionString: process.env.DATABASE_URL
+ * });
+ *
+ * // Or using individual parameters
+ * initializeDataAgentDatabase("mydb", {
+ *   type: "postgres",
+ *   host: "localhost",
+ *   port: 5432,
+ *   database: "mydb",
+ *   user: "user",
+ *   password: "password"
+ * });
+ * ```
+ */
+export function initializeDataAgentDatabase(
+  key: string,
+  config: DatabaseConfig
+): void {
+  sqlDatabaseManager.registerDatabase(key, config);
+}
+
+/**
+ * Helper function to set the default database for the data agent
+ *
+ * @param key - Database key to set as default
+ */
+export function setDefaultDatabase(key: string): void {
+  sqlDatabaseManager.setDefaultDatabase(key);
+}
+
+/**
+ * Export types for external use
+ */
+export type { DatabaseConfig };
+
+initializeDataAgentDatabase("fulidb", {
+  type: "postgres",
+  connectionString: process.env.DATABASE_URL,
+  database: "postgres",
+});

package/src/agents/index.ts

@@ -1,4 +1,3 @@
 //import "./todo";
 import "./research";
-
-// import "./property_viewing";
+import "./data_agent";

package/src/index.ts

@@ -2,11 +2,16 @@ import dotenv from "dotenv";
 
 import { LatticeGateway } from "@axiom-lattice/gateway";
 import {
+  getScheduleLattice,
   registerCheckpointSaver,
   registerModelLattice,
+  registerScheduleLattice,
 } from "@axiom-lattice/core";
 import "./agents";
+
 import path from "path";
+import { ScheduleType } from "@axiom-lattice/protocols";
+import { PostgreSQLScheduleStorage } from "@axiom-lattice/pg-stores";
 // 在文件开头添加
 const PACKAGE_VERSION = require("../package.json").version;
 const BUILD_TIME = new Date().toISOString();
@@ -96,6 +101,31 @@ registerModelLattice(
 );
 LatticeGateway.registerLatticeRoutes(LatticeGateway.app);
 
+// // 注册 Schedule Lattice（使用 PostgreSQL 持久化）
+// registerScheduleLattice("default", {
+//   name: "Default Scheduler",
+//   description: "Production scheduler with PostgreSQL",
+//   type: ScheduleType.POSTGRES,
+//   storage: new PostgreSQLScheduleStorage({
+//     poolConfig: process.env.DATABASE_URL || "",
+//   }),
+// });
+
+// const scheduler = getScheduleLattice("default");
+// // 注册 Handler（每次服务启动时都需要注册）
+// scheduler.registerHandler("send-email", async (payload, taskInfo) => {
+//   console.log("send-email", payload, taskInfo);
+// });
+// scheduler.restore();
+
+// // 一次性延迟任务
+// scheduler.scheduleOnce(
+//   "email-123",
+//   "send-email",
+//   { to: "user@example.com", subject: "Welcome!" },
+//   { delayMs: 60000 } // 1分钟后执行
+// );
+
 const port = parsePort();
 console.log(`Starting server on port ${port}`);