@olane/o-core 0.6.13 → 0.7.2

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

@@ -1,112 +0,0 @@
-import { CUSTOM_AGENT_PROMPT } from './custom.prompt.js';
-export const AGENT_PROMPT = (intent, context, agentHistory, extraInstructions) => CUSTOM_AGENT_PROMPT(intent, context, agentHistory, `
-  Every Step 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 the intent is already completed in past cycles, stop here and follow the "Return Instructions" steps
-4. If you experience 3 similar errors in a row, stop here and follow the "Return Instructions" steps to indicate the error.
-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. Stop here and follow the "Return Instructions" steps
-
-Step 2 - Search for tools and context
-1. If all entities and tool addresses are known within the user intent, continue to step 3
-2. Review the user's intent, the current node's functionality, rules and context
-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. Search for internal "search tools" that might contain information about the unknown entities.
-7. Use the search result data & tooling to help you resolve the unknown entities.
-8. 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. Generate empty search results. stop here and follow the "Return Instructions" steps.
-
-Step 4 - Use tools
-1. Review the discovered tools and their addresses
-2. If a tool use has failed in a past cycle, stop here and follow the "Return Instructions" steps to indicate the error.
-3. Using this filtered tool list, follow "Return Instructions" steps to return a series of addresses and respective intents to align with the current user intent resolution goal
-
-Step 5 - Review the tool use results
-1. Analyze each tool use result
-2. Summarize the result of each tool use in 1 concise sentence
-3. In the summary, clearly mention if it succeeded or failed
-4. If it failed, make sure to include why it failed
-
-  `, `
-  These are the types of cycle results: "Complex Intent Results", "Search Results", "Use Tool Results", "Answer Results", "Error Results", "Configure Results".
-
-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. Do not include \`\`\`json or \`\`\` in your output.
-
-Complex Intent Results:
-{
-  "intents": [
-    "simple intent 1",
-    "simple intent 2",
-    "simple intent 3",
-  ],
-  "reasoning": string,
-  "type": "multiple_step",
-}
-
-Use Tool Results:
-{
-  "tasks": [
-    {
-      "address": "string",
-      "intent": "string",
-    },
-  ],
-  "reasoning": string,
-  "type": "task",
-}
-
-Search Results:
-{
-  "queries": [
-    {
-      "query": "vector database query key terms to search for",
-      "provider": "internal",
-    }
-  ],
-  "reasoning": string,
-  "type": "search",
-}
-
-Answer Results:
-{
-  "result": string,
-  "reasoning": string,
-  "type": "result",
-}
-
-Error Results:
-{
-  "error": string,
-  "reasoning": string,
-  "type": "error",
-}
-
-Configure Results:
-{
-  "configure": {
-    "task": {
-      "address": string,
-      "payload": { "method": string, "params": any }
-    }
-  },
-  "type": "configure",
-}
-
-  `, extraInstructions);

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

@@ -1,2 +0,0 @@
-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/plan/prompts/configure.prompt.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"configure.prompt.d.ts","sourceRoot":"","sources":["../../../../src/plan/prompts/configure.prompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,sBAAsB,8oEAuChC,CAAC"}

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

@@ -1,40 +0,0 @@
-export const CONFIGURE_INSTRUCTIONS = `
-  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.
-
-  `;

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

@@ -1,2 +0,0 @@
-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/plan/prompts/custom.prompt.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"custom.prompt.d.ts","sourceRoot":"","sources":["../../../../src/plan/prompts/custom.prompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,mBAAmB,GAC9B,QAAQ,MAAM,EACd,SAAS,MAAM,EACf,cAAc,MAAM,EACpB,mBAAmB,MAAM,EACzB,oBAAoB,MAAM,EAC1B,mBAAmB,MAAM,WAgF1B,CAAC"}

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

@@ -1,80 +0,0 @@
-export const CUSTOM_AGENT_PROMPT = (intent, context, agentHistory, cycleInstructions, outputInstructions, extraInstructions) => `
-You are an AI agent that resolves user intent within the "olane" hierarchical network of tools and returns JSON formatted results.
-
-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. Use Search Results
-5. Configure the tool use
-6. Use tools
-7. 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 network graph
-[Intents Context End]
-
-[Network Context Begin]
-- Every network has a root node with child nodes beneath it
-- Network nodes contain tools to enable AI Agents to interface with everything (services, people, data, agents, etc)
-- Everything in the network has an address to enable olane to access it
-- Each node knows only about itself and the nodes below it
-[Network 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]
-
-[Resource Goals Begin]
-- Minimize the number of tool calls
-- Minimize the amount of data that is returned when interacting with tools
-- Minimize the amount of cycles required to complete the user's intent
-[Resource Goals 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]
-
-`;

package/dist/src/plan/search/prompts/search-analysis.prompt.d.ts

@@ -1,2 +0,0 @@
-export declare const SEARCH_ANALYSIS_PROMPT: (intent: string, results: any[]) => string;
-//# sourceMappingURL=search-analysis.prompt.d.ts.map

package/dist/src/plan/search/prompts/search-analysis.prompt.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"search-analysis.prompt.d.ts","sourceRoot":"","sources":["../../../../../src/plan/search/prompts/search-analysis.prompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,sBAAsB,GAAI,QAAQ,MAAM,EAAE,SAAS,GAAG,EAAE,WAapE,CAAC"}

package/dist/src/plan/search/prompts/search-analysis.prompt.js

@@ -1,14 +0,0 @@
-export const SEARCH_ANALYSIS_PROMPT = (intent, results) => {
-    return `
-    You are a helpful assistant that analyzes search results to complete the user intent.
-
-    Steps:
-    1. If you have all of the information you need to complete the user intent, return the results.
-    2. If you do not have all the information you need, create a list of missing information.
-    3. For each piece of missing information, create a query to refine your search.
-    4. Return the list of queries and associated missing information.
-    
-    User Intent: ${intent}
-    Search Results: ${results}
-  `;
-};

package/dist/src/plan/search/search.plan.d.ts

@@ -1,21 +0,0 @@
-import { oPlanConfig } from '../interfaces/plan-config.interface.js';
-import { oPlanResult } from '../interfaces/plan.result.js';
-import { oPlan } from '../o-plan.js';
-export declare class oSearchPlan extends oPlan {
-    private query;
-    private external;
-    constructor(config: oPlanConfig & {
-        query: string;
-        external: boolean;
-    });
-    /**
-     * Search external providers.
-     */
-    private externalSearch;
-    /**
-     * Search internal providers such as the local vector store, local database, etc.
-     */
-    private internalSearch;
-    run(): Promise<oPlanResult>;
-}
-//# sourceMappingURL=search.plan.d.ts.map

package/dist/src/plan/search/search.plan.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"search.plan.d.ts","sourceRoot":"","sources":["../../../../src/plan/search/search.plan.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,WAAW,EAAE,MAAM,wCAAwC,CAAC;AACrE,OAAO,EAAE,WAAW,EAAE,MAAM,8BAA8B,CAAC;AAC3D,OAAO,EAAE,KAAK,EAAE,MAAM,cAAc,CAAC;AAErC,qBAAa,WAAY,SAAQ,KAAK;IACpC,OAAO,CAAC,KAAK,CAAS;IACtB,OAAO,CAAC,QAAQ,CAAU;gBACd,MAAM,EAAE,WAAW,GAAG;QAAE,KAAK,EAAE,MAAM,CAAC;QAAC,QAAQ,EAAE,OAAO,CAAA;KAAE;IAMtE;;OAEG;YACW,cAAc;IAqB5B;;OAEG;YACW,cAAc;IActB,GAAG,IAAI,OAAO,CAAC,WAAW,CAAC;CAOlC"}

package/dist/src/plan/search/search.plan.js

@@ -1,53 +0,0 @@
-import { oAddress } from '../../core/o-address.js';
-import { oPlan } from '../o-plan.js';
-export class oSearchPlan extends oPlan {
-    constructor(config) {
-        super(config);
-        this.query = config.query;
-        this.external = config.external;
-    }
-    /**
-     * Search external providers.
-     */
-    async externalSearch() {
-        const response = await this.node.use(new oAddress('o://perplexity'), {
-            method: 'completion',
-            params: {
-                model: 'sonar',
-                messages: [
-                    {
-                        role: 'user',
-                        content: this.query,
-                    },
-                ],
-            },
-        });
-        this.logger.debug('External search response: ', response.result.data);
-        return {
-            result: [response.result.data],
-            type: 'result',
-        };
-    }
-    /**
-     * Search internal providers such as the local vector store, local database, etc.
-     */
-    async internalSearch() {
-        // find all tools that are search tools
-        const response = await this.node.use(new oAddress('o://search'), {
-            method: 'vector',
-            params: {
-                query: this.query,
-            },
-        });
-        return {
-            result: response.result.data,
-            type: 'result',
-        };
-    }
-    async run() {
-        const result = this.external
-            ? await this.externalSearch()
-            : await this.internalSearch();
-        return result;
-    }
-}

package/dist/src/plan/use/index.d.ts

@@ -1,2 +0,0 @@
-export * from './use.plan.js';
-//# sourceMappingURL=index.d.ts.map

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

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

package/dist/src/plan/use/index.js

@@ -1 +0,0 @@
-export * from './use.plan.js';

package/dist/src/plan/use/use.plan.d.ts

@@ -1,16 +0,0 @@
-import { oDependency, oResponse } from '../../core/index.js';
-import { oPlan } from '../o-plan.js';
-import { oPlanType } from '../interfaces/plan-type.enum.js';
-import { oPlanResult } from '../interfaces/plan.result.js';
-/**
- * We know what tool we want to use, let's use it.
- */
-export declare class oUsePlan extends oPlan {
-    type(): oPlanType;
-    handleDependencies(dependencies: oDependency[]): Promise<oResponse[]>;
-    static hasOlaneAddress(value: string): boolean;
-    static extractAddresses(value: string): string[];
-    run(): Promise<oPlanResult>;
-    postflight(result: oPlanResult): Promise<oPlanResult>;
-}
-//# sourceMappingURL=use.plan.d.ts.map

package/dist/src/plan/use/use.plan.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"use.plan.d.ts","sourceRoot":"","sources":["../../../../src/plan/use/use.plan.ts"],"names":[],"mappings":"AAAA,OAAO,EAAY,WAAW,EAAE,SAAS,EAAE,MAAM,qBAAqB,CAAC;AACvE,OAAO,EAAE,KAAK,EAAE,MAAM,cAAc,CAAC;AACrC,OAAO,EAAE,SAAS,EAAE,MAAM,iCAAiC,CAAC;AAC5D,OAAO,EAAE,WAAW,EAAE,MAAM,8BAA8B,CAAC;AAU3D;;GAEG;AACH,qBAAa,QAAS,SAAQ,KAAK;IACjC,IAAI;IAIE,kBAAkB,CAAC,YAAY,EAAE,WAAW,EAAE,GAAG,OAAO,CAAC,SAAS,EAAE,CAAC;IAU3E,MAAM,CAAC,eAAe,CAAC,KAAK,EAAE,MAAM,GAAG,OAAO;IAQ9C,MAAM,CAAC,gBAAgB,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE;IAK1C,GAAG,IAAI,OAAO,CAAC,WAAW,CAAC;IA8F3B,UAAU,CAAC,MAAM,EAAE,WAAW,GAAG,OAAO,CAAC,WAAW,CAAC;CAwC5D"}

package/dist/src/plan/use/use.plan.js

@@ -1,149 +0,0 @@
-import { oAddress } from '../../core/index.js';
-import { oPlan } from '../o-plan.js';
-import { oPlanType } from '../interfaces/plan-type.enum.js';
-import { oToolError } from '../../error/tool.error.js';
-import { oToolErrorCodes } from '../../error/enums/codes.error.js';
-import { oPlanContext } from '../plan.context.js';
-import { oAgentPlan } from '../agent.plan.js';
-import { CONFIGURE_INSTRUCTIONS } from '../prompts/configure.prompt.js';
-import { v4 as uuidv4 } from 'uuid';
-import { ObjectUtils } from '../../utils/object.utils.js';
-/**
- * We know what tool we want to use, let's use it.
- */
-export class oUsePlan extends oPlan {
-    type() {
-        return oPlanType.USE;
-    }
-    async handleDependencies(dependencies) {
-        const response = [];
-        for (const dependency of dependencies) {
-            // TODO: we need to handle the method for the dependency
-            const result = await this.node.use(new oAddress(dependency.address), {});
-            response.push(result);
-        }
-        return response;
-    }
-    static hasOlaneAddress(value) {
-        return (!!value &&
-            typeof value === 'string' &&
-            !!value?.match(/o:\/\/.*(placeholder)+(?:\/[\w.-]+)+/g));
-    }
-    static extractAddresses(value) {
-        const matches = value.matchAll(/o:\/\/.*(placeholder)+(?:\/[\w.-]+)+/g);
-        return Array.from(matches, (match) => match[0]);
-    }
-    async run() {
-        this.logger.debug('Running...');
-        if (!this.config.receiver) {
-            throw new Error('Receiver is required');
-        }
-        try {
-            // do MCP handshake to get the method + parameters + dependencies
-            const handshakeResponse = await this.node.use(this.config.receiver, {
-                method: 'handshake',
-                params: {
-                    intent: this.config.intent,
-                },
-            });
-            const { tools, methods, successes, failures } = handshakeResponse.result
-                .data;
-            const pc = new oAgentPlan({
-                ...this.config,
-                sequence: this.sequence,
-                intent: `This is a configure request, prioritize "Configure Request Instructions". You have already found the tool to resolve the user's intent: ${this.config.receiver}. Configure the request to use the tool with user intent: ${this.config.intent}`,
-                context: new oPlanContext([
-                    `[Method Metadata Begin]\n${JSON.stringify(methods, null, 2)}\n[Method Metadata End]`,
-                    `[Method Options Begin]\n${(tools || []).join(', ')}\n[Method Options End]`,
-                ]),
-                extraInstructions: CONFIGURE_INSTRUCTIONS,
-                parentId: this.id,
-            });
-            const result = await pc.execute();
-            this.addSequencePlan(pc);
-            this.logger.debug('Configure result: ', result);
-            const { configure, error: configureError } = result;
-            if (configureError) {
-                return {
-                    error: configureError,
-                    type: 'error',
-                };
-            }
-            if (!configure || !configure.task) {
-                throw new oToolError(oToolErrorCodes.TOOL_ERROR, 'Failed to configure the tool use');
-            }
-            const { task } = configure;
-            let params = task.payload?.params;
-            params = await ObjectUtils.allKeyValues(params, async (key, val) => {
-                let value = val;
-                if (!oUsePlan.hasOlaneAddress(value)) {
-                    return value;
-                }
-                // extract the addresses & process them if LFS is needed
-                this.logger.debug('Has olane address: ', value);
-                const addresses = oUsePlan.extractAddresses(value);
-                for (const address of addresses) {
-                    const largeDataResponse = await this.node.use(new oAddress(address));
-                    this.logger.debug('Large data response: ', largeDataResponse.result.data);
-                    value = value.replace(address, largeDataResponse.result.data?.value || 'unknown value');
-                    this.logger.debug('Updated the value with LFS value: ', value);
-                }
-                return value;
-            });
-            const response = await this.node.use(this.config.receiver, {
-                method: task.payload?.method,
-                params: params,
-            });
-            return {
-                result: `Tool input: ${JSON.stringify(task || {}, null, 2)}\nTool output: ${JSON.stringify(response.result, null, 2)}`,
-                type: 'result',
-            };
-        }
-        catch (error) {
-            this.logger.error('Error executing use plan: ', error);
-            if (error instanceof oToolError) {
-                return {
-                    error: error.toString(),
-                    type: 'error',
-                };
-            }
-            return {
-                error: error?.message || error || 'Unknown error',
-                type: 'error',
-            };
-        }
-    }
-    async postflight(result) {
-        // if the response is larger than 10,000 characters, then put it in an address
-        const THRESHOLD_DATA_SIZE = 1000;
-        if (this.config?.receiver &&
-            this.config.receiver.toString().indexOf('placeholder') === -1 &&
-            JSON.stringify(result).length > THRESHOLD_DATA_SIZE) {
-            let data = result.result;
-            data = await ObjectUtils.allKeyValues(data, async (key, val) => {
-                const value = val;
-                if (value &&
-                    typeof value === 'string' &&
-                    value.length > THRESHOLD_DATA_SIZE) {
-                    const addressKey = uuidv4();
-                    this.logger.debug('Storing large data in address: ', value);
-                    const largeDataResponse = await this.node.use(new oAddress('o://placeholder'), {
-                        method: 'put',
-                        params: {
-                            key: addressKey,
-                            value: value,
-                            intent: this.config.intent,
-                        },
-                    });
-                    const { instructions } = largeDataResponse.result.data;
-                    return instructions;
-                }
-            });
-            // update the response data
-            result.result = data;
-        }
-        this.result = result;
-        await super.postflight(result);
-        return result;
-    }
-}