📋Tasklist
The BBPA Engine orchestrates Agents Tasks and Gurus Tasks through both Web2 (REST API) and Web3 (BBPM Process Instance SC Variables) interfaces.
Last updated
The BBPA Engine orchestrates Agents Tasks and Gurus Tasks through both Web2 (REST API) and Web3 (BBPM Process Instance SC Variables) interfaces.
Last updated
The BBPA Engine orchestrates two main types of tasks externally: Individual Agents(IA) Tasks and Gurus Tasks, those are divided based on functionality:
Generic Individual Agents (IA) Tasks: These are queues for IA Lambda functions that handle AI Compute, comprehensive interaction scripts, or non-custodial transaction execution on the blockchain. These tasks facilitate the processing and execution of complex data and transactions, integrating seamlessly with various AI-driven processes.
Gurus Tasks: Presented within the user’s task list, these tasks function as user interaction and feedback UI elements across integrated frontends and chatbots. This setup enhances off-chain orchestration of routines and business processes through an easy-to-use interface that has been extensively tested across thousands of integrations in traditional finance (TradFi) businesses utilizing BPMN-based BPA systems.
Gurus Web3 Tasks: This task type provides a user transaction builder interface, which orchestrates the transaction process and prompts users to complete tasks through their wallet. This functionality allows for the encapsulation of various DeFi routines into a single decision point, which can be automated through an IA Non-Custodial Worker implementation.
Non-Custodial Individual Agents (IA) Tasks: These tasks are designed for automated signing and execution by a container running on the user’s controlled hardware. They enable different scenarios for automating crypto activities, enhanced by AI processors, allowing for sophisticated, secure crypto operations. Example here could be wrapped Guru DeFi Meta Aggregation API[11] wrapped as Individual agent operating in non custodial fashion.
Access to these tasks, whether in their current state or a form optimized for integration, is provided through both Web2 (REST API) and Web3 (BBPM Process Instance SC Variables) interfaces. The choice of interface depends on the deployers' need for decentralization mechanisms, offering flexibility in how tasks are managed and executed within the Flow Orchesrtator.
