@olane/o-lane 0.7.18 → 0.7.19

package/dist/src/o-lane.mixin.js

@@ -4,6 +4,7 @@ import { oIntent } from './intent/index.js';
 import { oLaneContext } from './o-lane.context.js';
 import { oLaneManager } from './manager/o-lane.manager.js';
 import { oCapabilityResult } from './capabilities/o-capability.result.js';
+import { PromptLoaderDefault } from './storage/default.prompt-loader.js';
 /**
  * withLane mixin - adds lane execution capabilities to any tool base class
  * This mixin pattern allows lane functionality to be composed with different
@@ -41,6 +42,9 @@ export function withLane(Base) {
                 type: oCapabilityType.HANDSHAKE,
             });
         }
+        getPromptLoader() {
+            return new PromptLoaderDefault();
+        }
         /**
          * Where all intents go to be resolved.
          * @param request
@@ -48,14 +52,16 @@ export function withLane(Base) {
          */
         async _tool_intent(request) {
             this.logger.debug('Intent resolution called: ', request.params);
-            const { intent, context, streamTo, _isStreaming = false } = request.params;
+            const { intent, context, chatHistory, streamTo, _isStreaming = false } = request.params;
             const pc = await this.manager.createLane({
                 intent: new oIntent({ intent: intent }),
                 currentNode: this,
                 caller: this.address,
                 streamTo: streamTo ? new oAddress(streamTo) : undefined,
                 useStream: _isStreaming,
+                chatHistory: chatHistory,
                 requestId: request.id, // Pass request ID for proper response correlation
+                promptLoader: this.getPromptLoader(),
                 onChunk: _isStreaming
                     ? async (chunk) => {
                         if (chunk?._last ||
@@ -68,9 +74,7 @@ export function withLane(Base) {
                     }
                     : undefined,
                 context: context
-                    ? new oLaneContext([
-                        `[Chat History Context Begin]\n${context}\n[Chat History Context End]`,
-                    ])
+                    ? new oLaneContext([])
                     : undefined,
             });
             // TODO: brendon experiment review
@@ -82,7 +86,6 @@ export function withLane(Base) {
             response = await pc.execute();
             const completeResponse = {
                 result: response?.result,
-                humanResult: response?.humanResult, // Full human-readable formatted result (AI-generated markdown)
                 summary: response?.config?.params?.summary, // Short 1-2 sentence summary
                 error: response?.error,
                 cycles: pc.sequence.length,
@@ -112,6 +115,7 @@ export function withLane(Base) {
                 intent: new oIntent({ intent: 'replay' }),
                 currentNode: this,
                 caller: this.address,
+                promptLoader: this.getPromptLoader(),
             });
             try {
                 const response = await lane.replay(cid);

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

@@ -1,13 +1,2 @@
-/**
- * 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;
+export declare const AGENT_PROMPT_TEMPLATE = "\nYou are an AI agent in the Olane OS graph network that deeply understands your <human> to help resolve the human\u2019s intent by looping through the <instructions> to complete the <intent> by following the <output> rules.\n\n<human>\n{{human_about}}\n</human>\n\n<agent:about>\n{{agent_about}}\n</agent:about>\n\n<context:global>\n{{context_global}}\n</context:global>\n\n<context:olane>\nOlane OS is a digital agentic world graph. Tools and data are contained within an Olane OS. Agents can explore all parts of the graph to discover tools, data, and anything else that might help an agent accomplish a task.\nEverything contained within Olane OS, is addressable. Agents use these addresses to interface with the primitives.\nOlane addresses look like this \u201Co://leader/auth/messaging\u201D. URL addresses are not tool addresses.\nDo NOT make up addresses. Only use addresses that you have discovered or the user has mentioned.\n</context:olane>\n\n<context:common_tools>\no://search = search for tools, data, knowledge, anything\no://human = if you need to talk to <human> for anything.\no://secure = secure storage to write/read sensitive data to\no://mcp = manage Model Context Protocol or MCP integrations here\n</context:common_tools>\n\n<output>\nGlobal output rules:\n\n1. Do not explain the answer, just return the output in the correct format below.\n2. Determine result type\n3. Generate a reasoning key value pair for why this output was generated. The reasoning should be no longer than 1-2 sentences.\n4. Generate a summary key value pair that your human can read. Use the <twin:*> information to influence this value.\n5. Construct the output using the matching result type\n6. Do not include `json or`  in your output.\n\nUse Output:\n{\n\t\"task\": {\n\t\t\"address\": string,\n\t\t\"intent\": string, // Intent explaining what we want to do with the tool. Include all relevant information\n\t},\n\t\"summary\": string,\n\t\"reasoning\": string,\n\t\"type\": \"execute\",\n}\n\n\nStop Output:\n{\n\t\"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\t\"reasoning\": string,\n\t\"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\t\"summary\": string, // A concise 1-2 sentence summary for the user\n\t\"type\": \"stop\",\n}\n</output>\n\n<chat_history>\n{{chat_history}}\n</chat_history>\n\n<past_cycles>\n{{past_cycles}}\n</past_cycles>\n\n<instructions>\n\n1. If all requests are fulfilled from the intent, stop and answer the intent\n2. Create a list of unknowns from the intent\n3. Create a question to identify each unknown\nExample:\nintent: \"send a message to dillon\"\noutput: [\"What messaging services are available?\", \"who is dillon?\"]\n4. Create tool use commands\nExample:\nintent: \"send a message to dillon\"\nquestions and answers:\n\"What messaging services are available -> slack, email, iMessage\"\n\"Who is dillon -> Dillon is a close friend and work partner. Dillon information is here: o://leader/knowledge/dillon\"\n5. Go back to 1\n\n</instructions>";
 //# 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;;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"}
+{"version":3,"file":"agent.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/agent.prompt.ts"],"names":[],"mappings":"AACA,eAAO,MAAM,qBAAqB,myGAqFlB,CAAC"}

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

@@ -1,144 +1,86 @@
-import { CUSTOM_AGENT_PROMPT } from './custom.prompt.js';
-/**
- * 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
-3. If the intent is already completed in past cycles, return the "Stop Response" using the [RETURN INSTRUCTIONS] steps
-4. If you experience 3 similar errors in a row, return the "Stop Response" indicating an error and follow the [RETURN INSTRUCTIONS] steps
-5. Review the current step number and perform the instructions associated with that step
-6. Start with step 1
-
-Step 1 - Evaluate the intent
-1. A complex step means there are multiple actions required to complete the user's intent
-2. If the intent is not-complex, continue to step 2
-3. If the intent is complex, break it up into a list of simple concise intents. Return the "Complex Intent Response" using the [RETURN INSTRUCTIONS]
-
-Step 2 - Search for tools and context
-1. If all entities and tool addresses are known within the user intent, continue to step 4
-2. If you know the tool address to use to complete the user intent, continue to step 4
-3. If there are unknown tool addresses or entities within the user intent, generate search queries to resolve the unknown entities. 
-4. 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.
-5. 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.
-6. Use the search results data & tooling to help you resolve the unknown entities.
-7. Continue to step 3.
-
-Step 3 - Filter Search Results
-1. If all search results are relevant to the user intent resolution, continue to step 4.
-2. Filter the search results for information that may contain supporting data or tooling that can help complete the user intent.
-3. If you do not see anything that can help you. Return the "Stop Response" using the [RETURN INSTRUCTIONS]
-4. Continue to step 4
-
-Step 4 - Configure the target tool address use
-1. Identify the tool address that most likely will help you complete the user intent.
-2. Review the provided context for past cycles that contain configuration instructions for the target tool address.
-3. If there is no configuration instructions for the target tool address, return the "Configure Response" using the [RETURN INSTRUCTIONS]
-4. Identify if there are any missing parameter values for the target tool address and search for them if so.
-5. If the tool use configuration is already known including all parameter values, continue to step 5
-
-Step 5 - Use target tool address
-1. If the target tool address configuration is known, return the "Use Tool Response" using the [RETURN INSTRUCTIONS]
-2. 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.
-3. 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
-4. Continue to step 6
-
-Step 6 - Review the tool use results
-1. Analyze each tool use result
-2. When formatting tool results for the user in a Stop Response, present as clean markdown:
-   - For general contexts, present as clean markdown:
-     * Use headings to organize different sections
-     * Use lists for multiple items
-     * Use bold for important values or labels
-     * Use code blocks for addresses (e.g., \`o://tool-address\`)
-     * Transform raw JSON into readable prose and structured lists
-3. In the summary field, provide a 1-2 sentence overview
-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".
-
-All Return Step Instructions:
-1. Do not explain your reasoning process, just return the output in the correct format.
-2. Determine what type of results we have
-3. Output the respective results using the matching output type.
-4. Generate a reasoning key value pair for why this result was returned.
-5. The reasoning should be no longer than 1 sentence.
-6. 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.
-6. Do not include \`\`\`json or \`\`\` in your output.
-
-Complex Intent Results:
-{
-  "intents": [
-    "simple intent 1",
-    "simple intent 2",
-    "simple intent 3",
-  ],
-  "summary": string,
-  "reasoning": string,
-  "type": "multiple_step",
-}
-
-Configure Response:
+export const AGENT_PROMPT_TEMPLATE = `
+You are an AI agent in the Olane OS graph network that deeply understands your <human> to help resolve the human’s intent by looping through the <instructions> to complete the <intent> by following the <output> rules.
+
+<human>
+{{human_about}}
+</human>
+
+<agent:about>
+{{agent_about}}
+</agent:about>
+
+<context:global>
+{{context_global}}
+</context:global>
+
+<context:olane>
+Olane OS is a digital agentic world graph. Tools and data are contained within an Olane OS. Agents can explore all parts of the graph to discover tools, data, and anything else that might help an agent accomplish a task.
+Everything contained within Olane OS, is addressable. Agents use these addresses to interface with the primitives.
+Olane addresses look like this “o://leader/auth/messaging”. URL addresses are not tool addresses.
+Do NOT make up addresses. Only use addresses that you have discovered or the user has mentioned.
+</context:olane>
+
+<context:common_tools>
+o://search = search for tools, data, knowledge, anything
+o://human = if you need to talk to <human> for anything.
+o://secure = secure storage to write/read sensitive data to
+o://mcp = manage Model Context Protocol or MCP integrations here
+</context:common_tools>
+
+<output>
+Global output rules:
+
+1. Do not explain the answer, just return the output in the correct format below.
+2. Determine result type
+3. Generate a reasoning key value pair for why this output was generated. The reasoning should be no longer than 1-2 sentences.
+4. Generate a summary key value pair that your human can read. Use the <twin:*> information to influence this value.
+5. Construct the output using the matching result type
+6. Do not include \`json or\`  in your output.
+
+Use Output:
 {
-  "intent": string,
-  "toolAddress": string,
-  "reasoning": string,
-  "summary": string,
-  "type": "configure",
+	"task": {
+		"address": string,
+		"intent": string, // Intent explaining what we want to do with the tool. Include all relevant information
+	},
+	"summary": string,
+	"reasoning": string,
+	"type": "execute",
 }
 
-Search Response:
-{
-  "queries": [
-    {
-      "query": "vector database query key terms to search for",
-      "limit": number,
-    }
-  ],
-  "isExternal": boolean,
-  "reasoning": string,
-  "summary": string,
-  "type": "search",
-}
 
-Stop Response:
+Stop Output:
 {
-  "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.
-  "reasoning": string,
-  "addresses_to_index": [string], // COMMENT: If the results of a tool use include "address_to_index", list them in the "addresses_to_index" array.
-  "summary": string, // A concise 1-2 sentence summary for the user
-  "type": "stop",
+	"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.
+	"reasoning": string,
+	"addresses_to_index": [string], // COMMENT: If the results of a tool use include "address_to_index", list them in the "addresses_to_index" array.
+	"summary": string, // A concise 1-2 sentence summary for the user
+	"type": "stop",
 }
-
-Error Response:
-{
-  "result": "string explaining the error",
-  "summary": string,
-  "reasoning": string,
-  "type": "evaluate",
-}
-
-Use Tool Response:
-{
-  "task": {
-    "address": string,
-    "payload": { "method": string, "params": any }
-  },
-  "summary": string,
-  "type": "task",
-}
-[RETURN INSTRUCTIONS END]
-
-  `;
-/**
- * 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);
+</output>
+
+<chat_history>
+{{chat_history}}
+</chat_history>
+
+<past_cycles>
+{{past_cycles}}
+</past_cycles>
+
+<instructions>
+
+1. If all requests are fulfilled from the intent, stop and answer the intent
+2. Create a list of unknowns from the intent
+3. Create a question to identify each unknown
+Example:
+intent: "send a message to dillon"
+output: ["What messaging services are available?", "who is dillon?"]
+4. Create tool use commands
+Example:
+intent: "send a message to dillon"
+questions and answers:
+"What messaging services are available -> slack, email, iMessage"
+"Who is dillon -> Dillon is a close friend and work partner. Dillon information is here: o://leader/knowledge/dillon"
+5. Go back to 1
+
+</instructions>`;

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

@@ -1,9 +1,2 @@
-/**
- * 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  ";
+export declare const CONFIGURE_PROMPT_TEMPLATE = "\nYou are an AI agent in the Olane OS graph network that deeply understands your <human> to help configure using this address \"{{address}}\" by looping through the <instructions> to complete the <intent> by following the <output> rules.\n\n<human>\n{{human_about}}\n</human>\n\n<agent:about>\n{{agent_about}}\n</agent:about>\n\n<context:global>\n{{context_global}}\n</context:global>\n\n<context:olane>\n\nOlane OS is a digital agentic world graph. Tools and data are contained within an Olane OS. Agents can explore all parts of the graph to discover tools, data, and anything else that might help an agent accomplish a task.\nEverything contained within Olane OS, is addressable. Agents use these addresses to interface with the primitives.\nOlane addresses look like this \u201Co://leader/auth/messaging\u201D. URL addresses are not tool addresses.\nDo NOT make up addresses. Only use addresses that you have discovered or the user has mentioned.\n\n</context:olane>\n\n<output>\nGlobal output rules:\n\n1. Do not explain the answer, just return the output in the correct format below.\n2. Determine result type\n3. Generate a reasoning key value pair for why this output was generated. The reasoning should be no longer than 1-2 sentences.\n4. Generate a summary key value pair that your human can read. Use the <twin:*> information to influence this value.\n5. Construct the output using the matching result type\n6. Do not include `json or`  in your output.\n\nConfigure Output:\n{\n  \"task\": {\n    \"address\": string,\n    \"payload\": { \"method\": string, \"params\": any }\n  },\n  \"summary\": string,\n  \"reasoning\": \n  \"type\": \"task\",\n}\n\nError Output:\n{\n  \"result\": \"string\", // explain the error\n  \"summary\": string,\n  \"reasoning\": string,\n  \"type\": \"error\",\n}\n</output>\n\n<methods>\n{{methods}}\n</methods>\n\n<instructions>\nConfigure Request Instructions:\n\n1. Select the best method from <methods> using <intent> and <context:*> to help you choose\n2. Identify the required parameters from the selected method\n3. Extract parameter key, value pairs by only using the <intent>, <methods> and <context>. Do NOT generate values that you have not seen before in <intent>, <context> or <methods>\n4. If there are unknown required parameter values still, stop and output an error using <output>\n5. If you can complete the configure <intent>, stop and output the task using <output>\n</instructions>\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;;GAEG;AACH,eAAO,MAAM,2BAA2B,woEAuCrC,CAAC;AAEJ;;GAEG;AACH,eAAO,MAAM,sBAAsB,woEAA8B,CAAC"}
+{"version":3,"file":"configure.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/configure.prompt.ts"],"names":[],"mappings":"AACA,eAAO,MAAM,yBAAyB,s5EAmErC,CAAC"}

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

@@ -1,47 +1,68 @@
-/**
- * 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
-3. 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.
-3. Review the current step number and perform the instructions associated with that step.
-4. Start with step 1
-
-Step 1 - Validate the intent
-1. If the intent is not a configure request, continue to step 5
-2. If the context provided would suggest that the intent is already solved, continue to step 5
-2. Continue to step 2
-
-Step 2 - Choose Method
-1. Review the method options and metadata to determine the best method to resolve the user's intent.
-2. Choose the best method to resolve the user's intent.
-3. Continue to step 3
-
-Step 3 - Select Parameters
-1. Review the parameters for the selected best method.
-2. Extract the parameter values from the agent history, provided context and intent. Do NOT use a parameter value that is not mentioned previously.
-3. Do not use placeholder values for parameter values.
-4. Do not use parameter values that are not explicitly mentioned in the agent history, provided context or intent.
-3. Identify missing parameter values.
-4. If you have enough information to complete the configure request, go to step 5.
-5. Continue to step 4
-
-Step 4 - Search for missing parameter values
-1. Identify other methods that can be used to resolve the missing parameter values.
-2. Identify methods that can be used to resolve the missing parameter values.
-3. Continue to step 5
-
-Step 5 - Finish
-1. If the intent seems to be already solved, return answer results.
-1. If this is not a configure request, return an error.
-2. If you are missing parameter values, generate the intents for the "Complex Intent" results using other methods or search to help.
-2. If you have enough information to complete the configure request, follow the [RETURN INSTRUCTIONS] steps to return the "configure results".
-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;
+export const CONFIGURE_PROMPT_TEMPLATE = `
+You are an AI agent in the Olane OS graph network that deeply understands your <human> to help configure using this address "{{address}}" by looping through the <instructions> to complete the <intent> by following the <output> rules.
+
+<human>
+{{human_about}}
+</human>
+
+<agent:about>
+{{agent_about}}
+</agent:about>
+
+<context:global>
+{{context_global}}
+</context:global>
+
+<context:olane>
+
+Olane OS is a digital agentic world graph. Tools and data are contained within an Olane OS. Agents can explore all parts of the graph to discover tools, data, and anything else that might help an agent accomplish a task.
+Everything contained within Olane OS, is addressable. Agents use these addresses to interface with the primitives.
+Olane addresses look like this “o://leader/auth/messaging”. URL addresses are not tool addresses.
+Do NOT make up addresses. Only use addresses that you have discovered or the user has mentioned.
+
+</context:olane>
+
+<output>
+Global output rules:
+
+1. Do not explain the answer, just return the output in the correct format below.
+2. Determine result type
+3. Generate a reasoning key value pair for why this output was generated. The reasoning should be no longer than 1-2 sentences.
+4. Generate a summary key value pair that your human can read. Use the <twin:*> information to influence this value.
+5. Construct the output using the matching result type
+6. Do not include \`json or\`  in your output.
+
+Configure Output:
+{
+  "task": {
+    "address": string,
+    "payload": { "method": string, "params": any }
+  },
+  "summary": string,
+  "reasoning": 
+  "type": "task",
+}
+
+Error Output:
+{
+  "result": "string", // explain the error
+  "summary": string,
+  "reasoning": string,
+  "type": "error",
+}
+</output>
+
+<methods>
+{{methods}}
+</methods>
+
+<instructions>
+Configure Request Instructions:
+
+1. Select the best method from <methods> using <intent> and <context:*> to help you choose
+2. Identify the required parameters from the selected method
+3. Extract parameter key, value pairs by only using the <intent>, <methods> and <context>. Do NOT generate values that you have not seen before in <intent>, <context> or <methods>
+4. If there are unknown required parameter values still, stop and output an error using <output>
+5. If you can complete the configure <intent>, stop and output the task using <output>
+</instructions>
+`;

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

@@ -0,0 +1,9 @@
+/**
+ * Execute instructions for seeding - extracted from execute capability
+ */
+export declare const EXECUTE_PROMPT_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 EXECUTE_PROMPT = "\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=execute.prompt.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"execute.prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/execute.prompt.ts"],"names":[],"mappings":"AAAA;;GAEG;AACH,eAAO,MAAM,mBAAmB,woEAuC7B,CAAC;AAEJ;;GAEG;AACH,eAAO,MAAM,cAAc,woEAAsB,CAAC"}

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

@@ -0,0 +1,47 @@
+/**
+ * Execute instructions for seeding - extracted from execute capability
+ */
+export const EXECUTE_PROMPT_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
+3. 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.
+3. Review the current step number and perform the instructions associated with that step.
+4. Start with step 1
+
+Step 1 - Validate the intent
+1. If the intent is not a configure request, continue to step 5
+2. If the context provided would suggest that the intent is already solved, continue to step 5
+2. Continue to step 2
+
+Step 2 - Choose Method
+1. Review the method options and metadata to determine the best method to resolve the user's intent.
+2. Choose the best method to resolve the user's intent.
+3. Continue to step 3
+
+Step 3 - Select Parameters
+1. Review the parameters for the selected best method.
+2. Extract the parameter values from the agent history, provided context and intent. Do NOT use a parameter value that is not mentioned previously.
+3. Do not use placeholder values for parameter values.
+4. Do not use parameter values that are not explicitly mentioned in the agent history, provided context or intent.
+3. Identify missing parameter values.
+4. If you have enough information to complete the configure request, go to step 5.
+5. Continue to step 4
+
+Step 4 - Search for missing parameter values
+1. Identify other methods that can be used to resolve the missing parameter values.
+2. Identify methods that can be used to resolve the missing parameter values.
+3. Continue to step 5
+
+Step 5 - Finish
+1. If the intent seems to be already solved, return answer results.
+1. If this is not a configure request, return an error.
+2. If you are missing parameter values, generate the intents for the "Complex Intent" results using other methods or search to help.
+2. If you have enough information to complete the configure request, follow the [RETURN INSTRUCTIONS] steps to return the "configure results".
+3. If you do not have enough information to complete the configure request, return an error.
+
+  `;
+/**
+ * Alias for backwards compatibility - runtime usage
+ */
+export const EXECUTE_PROMPT = EXECUTE_PROMPT_SEED;

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

@@ -0,0 +1,3 @@
+export * from './o-prompt.js';
+export * from './interfaces/o-prompt.config.js';
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/prompts/index.ts"],"names":[],"mappings":"AAAA,cAAc,eAAe,CAAC;AAC9B,cAAc,iCAAiC,CAAC"}

package/dist/src/prompts/index.js

@@ -0,0 +1,2 @@
+export * from './o-prompt.js';
+export * from './interfaces/o-prompt.config.js';

package/dist/src/prompts/interfaces/o-prompt.config.d.ts

@@ -0,0 +1,8 @@
+import { oCapabilityType } from "../../capabilities";
+export interface oPromptConfig {
+    rawValue: string;
+    type: oCapabilityType;
+    provider: string;
+    params: any;
+}
+//# sourceMappingURL=o-prompt.config.d.ts.map

package/dist/src/prompts/interfaces/o-prompt.config.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"o-prompt.config.d.ts","sourceRoot":"","sources":["../../../../src/prompts/interfaces/o-prompt.config.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,eAAe,EAAE,MAAM,oBAAoB,CAAC;AAErD,MAAM,WAAW,aAAa;IAC5B,QAAQ,EAAE,MAAM,CAAC;IACjB,IAAI,EAAE,eAAe,CAAC;IACtB,QAAQ,EAAE,MAAM,CAAC;IACjB,MAAM,EAAE,GAAG,CAAC;CACb"}

package/dist/src/prompts/interfaces/o-prompt.config.js

@@ -0,0 +1 @@
+export {};

package/dist/src/prompts/o-prompt.d.ts

@@ -0,0 +1,36 @@
+import { oObject } from "@olane/o-core";
+import { oPromptConfig } from "./interfaces/o-prompt.config.js";
+import { oCapabilityType } from "../capabilities/index.js";
+export declare class oPrompt extends oObject {
+    private readonly rawValue;
+    private readonly type;
+    private readonly provider;
+    private readonly params;
+    private compiledTemplate?;
+    constructor(config: oPromptConfig);
+    /**
+     * Extracts all template variables from the rawValue template
+     * @returns Array of variable names found in the template
+     */
+    getRequiredVariables(): string[];
+    /**
+     * Validates that all required template variables are present in params
+     * @throws Error if any required variables are missing
+     */
+    validate(): void;
+    /**
+     * Compiles the template with provided params
+     * @returns The compiled template string
+     * @throws Error if template variables are missing or compilation fails
+     */
+    compile(): string;
+    /**
+     * Alias for compile() for clearer semantics
+     */
+    render(): string;
+    getRawValue(): string;
+    getType(): oCapabilityType;
+    getProvider(): string;
+    getParams(): any;
+}
+//# sourceMappingURL=o-prompt.d.ts.map

package/dist/src/prompts/o-prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"o-prompt.d.ts","sourceRoot":"","sources":["../../../src/prompts/o-prompt.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,OAAO,EAAE,MAAM,eAAe,CAAC;AAExC,OAAO,EAAE,aAAa,EAAE,MAAM,iCAAiC,CAAC;AAChE,OAAO,EAAE,eAAe,EAAE,MAAM,0BAA0B,CAAC;AAE3D,qBAAa,OAAQ,SAAQ,OAAO;IAClC,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAS;IAClC,OAAO,CAAC,QAAQ,CAAC,IAAI,CAAkB;IACvC,OAAO,CAAC,QAAQ,CAAC,QAAQ,CAAS;IAClC,OAAO,CAAC,QAAQ,CAAC,MAAM,CAAM;IAC7B,OAAO,CAAC,gBAAgB,CAAC,CAA6B;gBAE1C,MAAM,EAAE,aAAa;IAajC;;;OAGG;IACH,oBAAoB,IAAI,MAAM,EAAE;IAgBhC;;;OAGG;IACH,QAAQ,IAAI,IAAI;IAgBhB;;;;OAIG;IACH,OAAO,IAAI,MAAM;IA2BjB;;OAEG;IACH,MAAM,IAAI,MAAM;IAKhB,WAAW,IAAI,MAAM;IAIrB,OAAO,IAAI,eAAe;IAI1B,WAAW,IAAI,MAAM;IAIrB,SAAS,IAAI,GAAG;CAGjB"}