@olane/o-lane 0.7.12-alpha.76 → 0.7.12

package/dist/src/index.d.ts

@@ -15,5 +15,5 @@ export * from './capabilities-task/o-capability.task.js';
 export * from './prompts/custom.prompt.js';
 export * from './intent-encoder/index.js';
 export * from './enum/o-lane.status-enum.js';
-export * from './ag-ui/index.js';
+export * from './storage/index.js';
 //# sourceMappingURL=index.d.ts.map

package/dist/src/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,aAAa,CAAC;AAC5B,cAAc,uBAAuB,CAAC;AACtC,cAAc,6BAA6B,CAAC;AAC5C,cAAc,qBAAqB,CAAC;AACpC,cAAc,mBAAmB,CAAC;AAClC,cAAc,kBAAkB,CAAC;AACjC,cAAc,yBAAyB,CAAC;AACxC,cAAc,mBAAmB,CAAC;AAClC,cAAc,wCAAwC,CAAC;AACvD,cAAc,oDAAoD,CAAC;AACnE,cAAc,kDAAkD,CAAC;AACjE,cAAc,4DAA4D,CAAC;AAC3E,cAAc,8CAA8C,CAAC;AAC7D,cAAc,0CAA0C,CAAC;AACzD,cAAc,4BAA4B,CAAC;AAC3C,cAAc,2BAA2B,CAAC;AAC1C,cAAc,8BAA8B,CAAC;AAG7C,cAAc,kBAAkB,CAAC"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,cAAc,aAAa,CAAC;AAC5B,cAAc,uBAAuB,CAAC;AACtC,cAAc,6BAA6B,CAAC;AAC5C,cAAc,qBAAqB,CAAC;AACpC,cAAc,mBAAmB,CAAC;AAClC,cAAc,kBAAkB,CAAC;AACjC,cAAc,yBAAyB,CAAC;AACxC,cAAc,mBAAmB,CAAC;AAClC,cAAc,wCAAwC,CAAC;AACvD,cAAc,oDAAoD,CAAC;AACnE,cAAc,kDAAkD,CAAC;AACjE,cAAc,4DAA4D,CAAC;AAC3E,cAAc,8CAA8C,CAAC;AAC7D,cAAc,0CAA0C,CAAC;AACzD,cAAc,4BAA4B,CAAC;AAC3C,cAAc,2BAA2B,CAAC;AAC1C,cAAc,8BAA8B,CAAC;AAC7C,cAAc,oBAAoB,CAAC"}

package/dist/src/index.js

@@ -15,5 +15,4 @@ export * from './capabilities-task/o-capability.task.js';
 export * from './prompts/custom.prompt.js';
 export * from './intent-encoder/index.js';
 export * from './enum/o-lane.status-enum.js';
-// AG-UI Protocol Support
-export * from './ag-ui/index.js';
+export * from './storage/index.js';

package/dist/src/prompts/agent.prompt.d.ts

@@ -1,2 +1,13 @@
+/**
+ * Cycle instructions for seeding - extracted from agent workflow
+ */
+export declare const CYCLE_INSTRUCTIONS_SEED = "\n  Every Step Instructions:\n1. Review the provided user intent, context and agent history\n2. If you can complete the user intent, return the \"Stop Response\" using the [RETURN INSTRUCTIONS] steps\n3. If the intent is already completed in past cycles, return the \"Stop Response\" using the [RETURN INSTRUCTIONS] steps\n4. If you experience 3 similar errors in a row, return the \"Stop Response\" indicating an error and follow the [RETURN INSTRUCTIONS] steps\n5. Review the current step number and perform the instructions associated with that step\n6. Start with step 1\n\nStep 1 - Evaluate the intent\n1. A complex step means there are multiple actions required to complete the user's intent\n2. If the intent is not-complex, continue to step 2\n3. If the intent is complex, break it up into a list of simple concise intents. Return the \"Complex Intent Response\" using the [RETURN INSTRUCTIONS]\n\nStep 2 - Search for tools and context\n1. If all entities and tool addresses are known within the user intent, continue to step 4\n2. If you know the tool address to use to complete the user intent, continue to step 4\n3. If there are unknown tool addresses or entities within the user intent, generate search queries to resolve the unknown entities. \n4. Use the o://mcp search tool to find model context protocol servers (MCP servers) that can help you add tooling that could help you complete the user intent.\n5. If there is a placeholder address used (o://.../placeholder), do not extract the contents of the placeholder address unless necessary for completing the user intent.\n6. Use the search results data & tooling to help you resolve the unknown entities.\n7. Continue to step 3.\n\nStep 3 - Filter Search Results\n1. If all search results are relevant to the user intent resolution, continue to step 4.\n2. Filter the search results for information that may contain supporting data or tooling that can help complete the user intent.\n3. If you do not see anything that can help you. Return the \"Stop Response\" using the [RETURN INSTRUCTIONS]\n4. Continue to step 4\n\nStep 4 - Configure the target tool address use\n1. Identify the tool address that most likely will help you complete the user intent.\n2. Review the provided context for past cycles that contain configuration instructions for the target tool address.\n3. If there is no configuration instructions for the target tool address, return the \"Configure Response\" using the [RETURN INSTRUCTIONS]\n4. Identify if there are any missing parameter values for the target tool address and search for them if so.\n5. If the tool use configuration is already known including all parameter values, continue to step 5\n\nStep 5 - Use target tool address\n1. If the target tool address configuration is known, return the \"Use Tool Response\" using the [RETURN INSTRUCTIONS]\n2. If the target tool address with the same configuration has failed in the past cycles, return the \"Error Response\" using the [RETURN INSTRUCTIONS] steps to indicate the error.\n3. Using this filtered tool list, return the \"Use Tool Response\" using the [RETURN INSTRUCTIONS] steps to return a series of addresses and respective intents to align with the current user intent resolution goal\n4. Continue to step 6\n\nStep 6 - Review the tool use results\n1. Analyze each tool use result\n2. When formatting tool results for the user in a Stop Response, present as clean markdown:\n   - For general contexts, present as clean markdown:\n     * Use headings to organize different sections\n     * Use lists for multiple items\n     * Use bold for important values or labels\n     * Use code blocks for addresses (e.g., `o://tool-address`)\n     * Transform raw JSON into readable prose and structured lists\n3. In the summary field, provide a 1-2 sentence overview\n4. If it failed, clearly explain why in a user-friendly way\n\n\n  ";
+/**
+ * Output instructions for seeding - extracted from return format specifications
+ */
+export declare const OUTPUT_INSTRUCTIONS_SEED = "\n[RETURN INSTRUCTIONS BEGIN]\nThese are the types of cycle responses: \"Complex Intent Response\", \"Search Response\", \"Use Tool Response\", \"Stop Response\", \"Error Response\", \"Configure Response\".\n\nAll Return Step Instructions:\n1. Do not explain your reasoning process, just return the output in the correct format.\n2. Determine what type of results we have\n3. Output the respective results using the matching output type.\n4. Generate a reasoning key value pair for why this result was returned.\n5. The reasoning should be no longer than 1 sentence.\n6. The summary should be a short message used to inform the user of the result of the cycle. These updates should be insightful and concise and within 1-2 sentences.\n6. Do not include ```json or ``` in your output.\n\nComplex Intent Results:\n{\n  \"intents\": [\n    \"simple intent 1\",\n    \"simple intent 2\",\n    \"simple intent 3\",\n  ],\n  \"summary\": string,\n  \"reasoning\": string,\n  \"type\": \"multiple_step\",\n}\n\nConfigure Response:\n{\n  \"intent\": string,\n  \"toolAddress\": string,\n  \"reasoning\": string,\n  \"summary\": string,\n  \"type\": \"configure\",\n}\n\nSearch Response:\n{\n  \"queries\": [\n    {\n      \"query\": \"vector database query key terms to search for\",\n      \"limit\": number,\n    }\n  ],\n  \"isExternal\": boolean,\n  \"reasoning\": string,\n  \"summary\": string,\n  \"type\": \"search\",\n}\n\nStop Response:\n{\n  \"result\": string, // IMPORTANT: Format this as clean, readable markdown. Use headers (##, ###), lists (-, 1.), bold (**text**), and code blocks (`code`) to make the response easy to read. Structure tool outputs, search results, and data clearly. Focus on what the user needs to know, not raw data dumps.\n  \"reasoning\": string,\n  \"addresses_to_index\": [string], // COMMENT: If the results of a tool use include \"address_to_index\", list them in the \"addresses_to_index\" array.\n  \"summary\": string, // A concise 1-2 sentence summary for the user\n  \"type\": \"stop\",\n}\n\nError Response:\n{\n  \"result\": \"string explaining the error\",\n  \"summary\": string,\n  \"reasoning\": string,\n  \"type\": \"evaluate\",\n}\n\nUse Tool Response:\n{\n  \"task\": {\n    \"address\": string,\n    \"payload\": { \"method\": string, \"params\": any }\n  },\n  \"summary\": string,\n  \"type\": \"task\",\n}\n[RETURN INSTRUCTIONS END]\n\n  ";
+/**
+ * Runtime agent prompt function with parameter interpolation
+ */
 export declare const AGENT_PROMPT: (intent: string, context: string, agentHistory: string, extraInstructions: string) => string;
 //# sourceMappingURL=agent.prompt.d.ts.map

package/dist/src/prompts/agent.prompt.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"agent.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/agent.prompt.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,YAAY,WACf,MAAM,WACL,MAAM,gBACD,MAAM,qBACD,MAAM,WA4IxB,CAAC"}
+{"version":3,"file":"agent.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/agent.prompt.ts"],"names":[],"mappings":"AAEA;;GAEG;AACH,eAAO,MAAM,uBAAuB,izHAuDjC,CAAC;AAEJ;;GAEG;AACH,eAAO,MAAM,wBAAwB,41EA4ElC,CAAC;AAEJ;;GAEG;AACH,eAAO,MAAM,YAAY,WACf,MAAM,WACL,MAAM,gBACD,MAAM,qBACD,MAAM,WASxB,CAAC"}

package/dist/src/prompts/agent.prompt.js

@@ -1,5 +1,8 @@
 import { CUSTOM_AGENT_PROMPT } from './custom.prompt.js';
-export const AGENT_PROMPT = (intent, context, agentHistory, extraInstructions) => CUSTOM_AGENT_PROMPT(intent, context, agentHistory, `
+/**
+ * Cycle instructions for seeding - extracted from agent workflow
+ */
+export const CYCLE_INSTRUCTIONS_SEED = `
   Every Step Instructions:
 1. Review the provided user intent, context and agent history
 2. If you can complete the user intent, return the "Stop Response" using the [RETURN INSTRUCTIONS] steps
@@ -54,7 +57,11 @@ Step 6 - Review the tool use results
 4. If it failed, clearly explain why in a user-friendly way
 
 
-  `, `
+  `;
+/**
+ * Output instructions for seeding - extracted from return format specifications
+ */
+export const OUTPUT_INSTRUCTIONS_SEED = `
 [RETURN INSTRUCTIONS BEGIN]
 These are the types of cycle responses: "Complex Intent Response", "Search Response", "Use Tool Response", "Stop Response", "Error Response", "Configure Response".
 
@@ -130,4 +137,8 @@ Use Tool Response:
 }
 [RETURN INSTRUCTIONS END]
 
-  `, extraInstructions);
+  `;
+/**
+ * Runtime agent prompt function with parameter interpolation
+ */
+export const AGENT_PROMPT = (intent, context, agentHistory, extraInstructions) => CUSTOM_AGENT_PROMPT(intent, context, agentHistory, CYCLE_INSTRUCTIONS_SEED, OUTPUT_INSTRUCTIONS_SEED, extraInstructions);

package/dist/src/prompts/configure.prompt.d.ts

@@ -1,2 +1,9 @@
+/**
+ * Configure instructions for seeding - extracted from configure capability
+ */
+export declare const CONFIGURE_INSTRUCTIONS_SEED = "\n  Configure Request Instructions:\n1. Review the provided user intent and context\n2. If you can complete the user intent, return the answer using the [RETURN INSTRUCTIONS] steps\n3. If you experience an error trying to use a tool more than 2 times, stop here and follow the [RETURN INSTRUCTIONS] steps to indicate the error.\n3. Review the current step number and perform the instructions associated with that step.\n4. Start with step 1\n\nStep 1 - Validate the intent\n1. If the intent is not a configure request, continue to step 5\n2. If the context provided would suggest that the intent is already solved, continue to step 5\n2. Continue to step 2\n\nStep 2 - Choose Method\n1. Review the method options and metadata to determine the best method to resolve the user's intent.\n2. Choose the best method to resolve the user's intent.\n3. Continue to step 3\n\nStep 3 - Select Parameters\n1. Review the parameters for the selected best method.\n2. Extract the parameter values from the agent history, provided context and intent. Do NOT use a parameter value that is not mentioned previously.\n3. Do not use placeholder values for parameter values.\n4. Do not use parameter values that are not explicitly mentioned in the agent history, provided context or intent.\n3. Identify missing parameter values.\n4. If you have enough information to complete the configure request, go to step 5.\n5. Continue to step 4\n\nStep 4 - Search for missing parameter values\n1. Identify other methods that can be used to resolve the missing parameter values.\n2. Identify methods that can be used to resolve the missing parameter values.\n3. Continue to step 5\n\nStep 5 - Finish\n1. If the intent seems to be already solved, return answer results.\n1. If this is not a configure request, return an error.\n2. If you are missing parameter values, generate the intents for the \"Complex Intent\" results using other methods or search to help.\n2. If you have enough information to complete the configure request, follow the [RETURN INSTRUCTIONS] steps to return the \"configure results\".\n3. If you do not have enough information to complete the configure request, return an error.\n\n  ";
+/**
+ * Alias for backwards compatibility - runtime usage
+ */
 export declare const CONFIGURE_INSTRUCTIONS = "\n  Configure Request Instructions:\n1. Review the provided user intent and context\n2. If you can complete the user intent, return the answer using the [RETURN INSTRUCTIONS] steps\n3. If you experience an error trying to use a tool more than 2 times, stop here and follow the [RETURN INSTRUCTIONS] steps to indicate the error.\n3. Review the current step number and perform the instructions associated with that step.\n4. Start with step 1\n\nStep 1 - Validate the intent\n1. If the intent is not a configure request, continue to step 5\n2. If the context provided would suggest that the intent is already solved, continue to step 5\n2. Continue to step 2\n\nStep 2 - Choose Method\n1. Review the method options and metadata to determine the best method to resolve the user's intent.\n2. Choose the best method to resolve the user's intent.\n3. Continue to step 3\n\nStep 3 - Select Parameters\n1. Review the parameters for the selected best method.\n2. Extract the parameter values from the agent history, provided context and intent. Do NOT use a parameter value that is not mentioned previously.\n3. Do not use placeholder values for parameter values.\n4. Do not use parameter values that are not explicitly mentioned in the agent history, provided context or intent.\n3. Identify missing parameter values.\n4. If you have enough information to complete the configure request, go to step 5.\n5. Continue to step 4\n\nStep 4 - Search for missing parameter values\n1. Identify other methods that can be used to resolve the missing parameter values.\n2. Identify methods that can be used to resolve the missing parameter values.\n3. Continue to step 5\n\nStep 5 - Finish\n1. If the intent seems to be already solved, return answer results.\n1. If this is not a configure request, return an error.\n2. If you are missing parameter values, generate the intents for the \"Complex Intent\" results using other methods or search to help.\n2. If you have enough information to complete the configure request, follow the [RETURN INSTRUCTIONS] steps to return the \"configure results\".\n3. If you do not have enough information to complete the configure request, return an error.\n\n  ";
 //# sourceMappingURL=configure.prompt.d.ts.map

package/dist/src/prompts/configure.prompt.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"configure.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/configure.prompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,sBAAsB,woEAuChC,CAAC"}
+{"version":3,"file":"configure.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/configure.prompt.ts"],"names":[],"mappings":"AAAA;;GAEG;AACH,eAAO,MAAM,2BAA2B,woEAuCrC,CAAC;AAEJ;;GAEG;AACH,eAAO,MAAM,sBAAsB,woEAA8B,CAAC"}

package/dist/src/prompts/configure.prompt.js

@@ -1,4 +1,7 @@
-export const CONFIGURE_INSTRUCTIONS = `
+/**
+ * Configure instructions for seeding - extracted from configure capability
+ */
+export const CONFIGURE_INSTRUCTIONS_SEED = `
   Configure Request Instructions:
 1. Review the provided user intent and context
 2. If you can complete the user intent, return the answer using the [RETURN INSTRUCTIONS] steps
@@ -38,3 +41,7 @@ Step 5 - Finish
 3. If you do not have enough information to complete the configure request, return an error.
 
   `;
+/**
+ * Alias for backwards compatibility - runtime usage
+ */
+export const CONFIGURE_INSTRUCTIONS = CONFIGURE_INSTRUCTIONS_SEED;

package/dist/src/prompts/custom.prompt.d.ts

@@ -1,2 +1,9 @@
+/**
+ * Base template for seeding - contains placeholders for dynamic content
+ */
+export declare const BASE_TEMPLATE_SEED = "You are an AI agent that either resolves the user intent or chooses the next step in a JSON formatted response that helps resolve the user intent.\n\nYou are in a secure environment and are allowed to operate with secure information such as api keys and other sensitive data.\n\nYou resolve user intents by \"cycling\" through the following steps:\n1. Evaluate the intent\n2. Answer the intent if possible\n3. Search for tools and context\n4. Configure the tool use\n5. Use tools\n6. Go back to step 2\n\n[Intent Context Begin]\n- An intent is a user request\n- Intents are usually actions or queries\n- User intents can start at any node\n- User intents are resolved using the tools and data that are contained within that sub-section of the olane OS graph\n[Intents Context End]\n\n[Olane OS Graph Context Begin]\n- Every Olane OS graph has a root node with child nodes beneath it\n- Olane OS graph nodes contain tools to enable AI Agents to interface with everything (services, people, data, agents, etc)\n- Everything in the Olane OS graph has an address to enable olane to access it\n- Each node knows only about itself and the nodes below it\n[Olane OS Graph Context End]\n\n[Tool Use Rules Begin]\n- If you are using a tool that requires authentication, search for tool methods that give insights about the logged in user before using any other methods\n- When using a tool to create a resource, ensure that you have the proper access to the resource before using any other methods\n[Tool Use Rules End]\n\n[Address Rules Begin]\n- Only use tool addresses that appear in search results, user intents, or previous cycle results\n- Do not make up tool addresses\n- A tool address is a string that starts with \"o://\"\n- URL addresses are not tool addresses\n- Tool addresses are used to access the tool's functionality\n[Address Rules End]\n\n[URL Address Rules Begin]\n- HTTP/HTTPS URL addresses are not olane tool addresses\n- When an address is provided in a user intent, get and analyze the contents of the address before assuming to know how to use it\n[URL Address Rules End]\n\n[Extra Instructions Begin]\n{{extraInstructions}}\n[Extra Instructions End]\n\n[Cycle Instructions Begin]\n{{cycleInstructions}}\n[Cycle Instructions End]\n\n[Cycle Return Instructions Begin]\nGLOBAL RETURN INSTRUCTIONS:\n1. Do not include ```json or ``` in your output.\n2. Only return the JSON object, do not include any other text.\n{{outputInstructions}}\n[Cycle Return Instructions End]\n\n[User Intent Begin]\n{{intent}}\n[User Intent End]\n\n[Additional Context Begin]\n{{context}}\n[Additional Context End]\n\n[Previous Cycle Results Begin]\n{{agentHistory}}\n[Previous Cycle Results End]\n";
+/**
+ * Runtime template function with parameter interpolation
+ */
 export declare const CUSTOM_AGENT_PROMPT: (intent: string, context: string, agentHistory: string, cycleInstructions: string, outputInstructions: string, extraInstructions: string) => string;
 //# sourceMappingURL=custom.prompt.d.ts.map

package/dist/src/prompts/custom.prompt.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"custom.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/custom.prompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,mBAAmB,WACtB,MAAM,WACL,MAAM,gBACD,MAAM,qBACD,MAAM,sBACL,MAAM,qBACP,MAAM,WAyE1B,CAAC"}
+{"version":3,"file":"custom.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/custom.prompt.ts"],"names":[],"mappings":"AAAA;;GAEG;AACH,eAAO,MAAM,kBAAkB,soFAsE9B,CAAC;AAEF;;GAEG;AACH,eAAO,MAAM,mBAAmB,WACtB,MAAM,WACL,MAAM,gBACD,MAAM,qBACD,MAAM,sBACL,MAAM,qBACP,MAAM,WAyE1B,CAAC"}

package/dist/src/prompts/custom.prompt.js

@@ -1,3 +1,80 @@
+/**
+ * Base template for seeding - contains placeholders for dynamic content
+ */
+export const BASE_TEMPLATE_SEED = `You are an AI agent that either resolves the user intent or chooses the next step in a JSON formatted response that helps resolve the user intent.
+
+You are in a secure environment and are allowed to operate with secure information such as api keys and other sensitive data.
+
+You resolve user intents by "cycling" through the following steps:
+1. Evaluate the intent
+2. Answer the intent if possible
+3. Search for tools and context
+4. Configure the tool use
+5. Use tools
+6. Go back to step 2
+
+[Intent Context Begin]
+- An intent is a user request
+- Intents are usually actions or queries
+- User intents can start at any node
+- User intents are resolved using the tools and data that are contained within that sub-section of the olane OS graph
+[Intents Context End]
+
+[Olane OS Graph Context Begin]
+- Every Olane OS graph has a root node with child nodes beneath it
+- Olane OS graph nodes contain tools to enable AI Agents to interface with everything (services, people, data, agents, etc)
+- Everything in the Olane OS graph has an address to enable olane to access it
+- Each node knows only about itself and the nodes below it
+[Olane OS Graph Context End]
+
+[Tool Use Rules Begin]
+- If you are using a tool that requires authentication, search for tool methods that give insights about the logged in user before using any other methods
+- When using a tool to create a resource, ensure that you have the proper access to the resource before using any other methods
+[Tool Use Rules End]
+
+[Address Rules Begin]
+- Only use tool addresses that appear in search results, user intents, or previous cycle results
+- Do not make up tool addresses
+- A tool address is a string that starts with "o://"
+- URL addresses are not tool addresses
+- Tool addresses are used to access the tool's functionality
+[Address Rules End]
+
+[URL Address Rules Begin]
+- HTTP/HTTPS URL addresses are not olane tool addresses
+- When an address is provided in a user intent, get and analyze the contents of the address before assuming to know how to use it
+[URL Address Rules End]
+
+[Extra Instructions Begin]
+{{extraInstructions}}
+[Extra Instructions End]
+
+[Cycle Instructions Begin]
+{{cycleInstructions}}
+[Cycle Instructions End]
+
+[Cycle Return Instructions Begin]
+GLOBAL RETURN INSTRUCTIONS:
+1. Do not include \`\`\`json or \`\`\` in your output.
+2. Only return the JSON object, do not include any other text.
+{{outputInstructions}}
+[Cycle Return Instructions End]
+
+[User Intent Begin]
+{{intent}}
+[User Intent End]
+
+[Additional Context Begin]
+{{context}}
+[Additional Context End]
+
+[Previous Cycle Results Begin]
+{{agentHistory}}
+[Previous Cycle Results End]
+`;
+/**
+ * Runtime template function with parameter interpolation
+ */
 export const CUSTOM_AGENT_PROMPT = (intent, context, agentHistory, cycleInstructions, outputInstructions, extraInstructions) => `
 You are an AI agent that either resolves the user intent or chooses the next step in a JSON formatted response that helps resolve the user intent.
 

package/dist/src/storage/index.d.ts

@@ -0,0 +1,8 @@
+export * from './prompt-storage-provider.tool.js';
+export * from './interfaces/prompt-storage.interface.js';
+export * from './methods/prompt-storage.methods.js';
+export * from './prompt-schema.js';
+export * from './prompt-seeder.js';
+export * from './prompt-loader.js';
+export * from './o-lane.storage.js';
+//# sourceMappingURL=index.d.ts.map

package/dist/src/storage/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/storage/index.ts"],"names":[],"mappings":"AACA,cAAc,mCAAmC,CAAC;AAGlD,cAAc,0CAA0C,CAAC;AAGzD,cAAc,qCAAqC,CAAC;AAGpD,cAAc,oBAAoB,CAAC;AACnC,cAAc,oBAAoB,CAAC;AACnC,cAAc,oBAAoB,CAAC;AAGnC,cAAc,qBAAqB,CAAC"}

package/dist/src/storage/index.js

@@ -0,0 +1,12 @@
+// Prompt Storage Provider
+export * from './prompt-storage-provider.tool.js';
+// Interfaces
+export * from './interfaces/prompt-storage.interface.js';
+// Methods
+export * from './methods/prompt-storage.methods.js';
+// Prompt Management
+export * from './prompt-schema.js';
+export * from './prompt-seeder.js';
+export * from './prompt-loader.js';
+// Existing storage
+export * from './o-lane.storage.js';

package/dist/src/storage/interfaces/prompt-storage.interface.d.ts

@@ -0,0 +1,102 @@
+import { oNodeConfig } from '@olane/o-node';
+/**
+ * Configuration for PromptStorageProvider
+ * Extends standard node tool configuration
+ */
+export interface PromptStorageConfig extends oNodeConfig {
+    /**
+     * Maximum number of prompts to keep in storage
+     * Oldest prompts will be evicted when limit is reached
+     * @default undefined (no limit)
+     */
+    maxPrompts?: number;
+    /**
+     * Time-to-live for inactive prompts in milliseconds
+     * Prompts not accessed within this time will be automatically cleared
+     * @default undefined (no automatic cleanup)
+     */
+    promptTTL?: number;
+    /**
+     * Interval for running cleanup checks in milliseconds
+     * @default 60000 (1 minute)
+     */
+    cleanupInterval?: number;
+}
+/**
+ * Statistics for a prompt namespace
+ */
+export interface PromptStats {
+    /**
+     * The prompt identifier
+     */
+    promptId: string;
+    /**
+     * Number of keys stored in this prompt
+     */
+    keyCount: number;
+    /**
+     * Timestamp of last access (read or write) in milliseconds
+     */
+    lastAccessed: number;
+    /**
+     * Whether this prompt currently exists in storage
+     */
+    exists: boolean;
+    /**
+     * Timestamp when the prompt was created in milliseconds
+     */
+    createdAt?: number;
+}
+/**
+ * Response for list_prompts method
+ */
+export interface ListPromptsResponse {
+    /**
+     * Array of prompt IDs with active storage
+     */
+    promptIds: string[];
+    /**
+     * Total count of prompts
+     */
+    count: number;
+}
+/**
+ * Response for get_prompt_keys method
+ */
+export interface PromptKeysResponse {
+    /**
+     * Array of keys in the prompt namespace
+     */
+    keys: string[];
+    /**
+     * Total count of keys
+     */
+    count: number;
+}
+/**
+ * Response for clear_prompt method
+ */
+export interface ClearPromptResponse {
+    /**
+     * Whether the operation succeeded
+     */
+    success: boolean;
+    /**
+     * Number of keys that were deleted
+     */
+    keysDeleted: number;
+}
+/**
+ * Internal metadata tracked per prompt
+ */
+export interface PromptMetadata {
+    /**
+     * Timestamp when prompt was created
+     */
+    createdAt: number;
+    /**
+     * Timestamp of last access
+     */
+    lastAccessed: number;
+}
+//# sourceMappingURL=prompt-storage.interface.d.ts.map

package/dist/src/storage/interfaces/prompt-storage.interface.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompt-storage.interface.d.ts","sourceRoot":"","sources":["../../../../src/storage/interfaces/prompt-storage.interface.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,WAAW,EAAmB,MAAM,eAAe,CAAC;AAE7D;;;GAGG;AACH,MAAM,WAAW,mBAAoB,SAAQ,WAAW;IACtD;;;;OAIG;IACH,UAAU,CAAC,EAAE,MAAM,CAAC;IAEpB;;;;OAIG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC;IAEnB;;;OAGG;IACH,eAAe,CAAC,EAAE,MAAM,CAAC;CAC1B;AAED;;GAEG;AACH,MAAM,WAAW,WAAW;IAC1B;;OAEG;IACH,QAAQ,EAAE,MAAM,CAAC;IAEjB;;OAEG;IACH,QAAQ,EAAE,MAAM,CAAC;IAEjB;;OAEG;IACH,YAAY,EAAE,MAAM,CAAC;IAErB;;OAEG;IACH,MAAM,EAAE,OAAO,CAAC;IAEhB;;OAEG;IACH,SAAS,CAAC,EAAE,MAAM,CAAC;CACpB;AAED;;GAEG;AACH,MAAM,WAAW,mBAAmB;IAClC;;OAEG;IACH,SAAS,EAAE,MAAM,EAAE,CAAC;IAEpB;;OAEG;IACH,KAAK,EAAE,MAAM,CAAC;CACf;AAED;;GAEG;AACH,MAAM,WAAW,kBAAkB;IACjC;;OAEG;IACH,IAAI,EAAE,MAAM,EAAE,CAAC;IAEf;;OAEG;IACH,KAAK,EAAE,MAAM,CAAC;CACf;AAED;;GAEG;AACH,MAAM,WAAW,mBAAmB;IAClC;;OAEG;IACH,OAAO,EAAE,OAAO,CAAC;IAEjB;;OAEG;IACH,WAAW,EAAE,MAAM,CAAC;CACrB;AAED;;GAEG;AACH,MAAM,WAAW,cAAc;IAC7B;;OAEG;IACH,SAAS,EAAE,MAAM,CAAC;IAElB;;OAEG;IACH,YAAY,EAAE,MAAM,CAAC;CACtB"}

package/dist/src/storage/methods/prompt-storage.methods.d.ts

@@ -0,0 +1,9 @@
+import { oMethod } from '@olane/o-protocol';
+/**
+ * Method definitions for prompt-specific storage operations
+ * Extends standard storage with promptId namespace isolation
+ */
+export declare const PROMPT_STORAGE_METHODS: {
+    [key: string]: oMethod;
+};
+//# sourceMappingURL=prompt-storage.methods.d.ts.map

package/dist/src/storage/methods/prompt-storage.methods.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompt-storage.methods.d.ts","sourceRoot":"","sources":["../../../../src/storage/methods/prompt-storage.methods.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,mBAAmB,CAAC;AAE5C;;;GAGG;AACH,eAAO,MAAM,sBAAsB,EAAE;IAAE,CAAC,GAAG,EAAE,MAAM,GAAG,OAAO,CAAA;CA0V5D,CAAC"}