Belief-Desire-Intention (BDI) Architecture

Unlike models that generate plans from first principles, classic BDI agents typically rely on a plan library—a predefined set of recipes for achieving goals.

• Each plan is a procedural template triggered by an intention and relevant belief conditions.
• Plans can include sub-goals, leading to hierarchical decomposition of tasks.
• Means-ends reasoning is the process of selecting an appropriate plan from the library that satisfies the current intention given the agent's beliefs.

This approach emphasizes efficiency and domain-specific knowledge over universal problem-solving, making BDI suitable for complex, time-constrained environments where pre-defined strategies are known. The agent's adaptability comes from choosing which pre-existing plan to use, not from constructing entirely new ones from scratch.

A defining feature of BDI is the treatment of intentions as commitments. This is not a blind commitment; it is governed by commitment strategies that determine when an agent should drop an intention.

Common strategies include:

• Blind Commitment: Persist with an intention until it is believed to be achieved.
• Single-Minded Commitment: Persist until it is believed either achieved or impossible.
• Open-Minded Commitment: Persist until it is believed achieved, impossible, or irrelevant (e.g., the goal is no longer desired).

This commitment creates persistence, preventing the agent from being overly fickle. It also introduces focus, as resources are dedicated to active intentions. The choice of strategy balances reactivity with tenacity, a key design decision in BDI agent implementation.

BDI agents are inherently event-driven. Changes in the environment (external events) or the internal state (goal achievement/failure, message receipt) trigger the reasoning cycle.

• Event Queue: Incoming events are placed in a queue for processing, allowing the agent to handle multiple, potentially concurrent, stimuli.
• Concurrent Intentions: An agent can actively pursue multiple intentions simultaneously. This requires managing shared resources and interleaving the execution steps of different plans.
• Interruption and Resumption: More important events can interrupt the execution of a plan for a current intention. The agent may later resume or replan.

This architecture supports the design of sophisticated agents that can manage multiple goals, respond to urgent situations, and maintain ongoing activities—a crucial capability for real-world deployment.

The BDI model has strong roots in philosophy of mind (Bratman's theory of human practical reasoning) and formal logic.

• Logical Formalizations: The concepts of belief, desire, and intention have been formalized using modal logics (e.g., BDI logics) to enable precise specification and verification of agent properties.
• Reference Implementations: The model has been realized in several influential agent programming platforms and frameworks.
  • PRS (Procedural Reasoning System): An early seminal implementation.
  • JACK™ Intelligent Agents: A commercial Java-based framework.
  • Jason: A widely-used open-source interpreter for an extended version of AgentSpeak(L), a BDI-inspired programming language.
  • Jadex: A BDI reasoning engine integrated into the JADE multi-agent middleware.

These implementations provide the tools to build BDI-based agents, handling the reasoning cycle, plan management, and event processing.

A normative framework that creates explicit obligations between agents, providing a mechanism for trust and coordination that complements internal BDI reasoning. A commitment is a tuple: Commit(Debtor, Creditor, Condition).

• Creates a persistent social relationship, obliging the debtor to bring about the condition for the creditor.
• Differs from a private intention; it is a public, verifiable promise that other agents can rely on for planning.
• Used to model contracts, protocols, and institutional rules, adding a layer of social accountability to agent interactions.

A planning methodology often integrated with BDI architectures to manage the complexity of plan generation. An HTN planner works by recursively decomposing high-level tasks into subtasks via pre-defined methods.

• Task Library: Contains abstract tasks (e.g., DeliverPackage) and primitive tasks (e.g., NavigateTo).
• Decomposition Methods: Rules for breaking down abstract tasks into networks of subtasks.
• In a BDI context, the intention structure often manages the execution of a plan (task network) generated by an HTN planner, linking high-level desires to executable actions.

A coordination approach where agents exchange and merge their local plans to form a partial view of a cooperative global plan. It addresses the limitation of purely local BDI reasoning in multi-agent settings.

• Agents broadcast their local plans (intentions).
• They analyze received plans to detect interactions (conflicts, synergies, dependencies).
• They then modify their own local plans to resolve conflicts or exploit cooperation opportunities.
• This creates a decentralized, evolving coordination structure without a central controller, suitable for dynamic environments.

A framework for governing open multi-agent systems by defining the norms, rules, and interaction spaces within which autonomous agents (including BDI agents) operate. It provides the "social infrastructure" for coordination.

• Scene Protocols: Define allowed conversation flows within a virtual room (e.g., a Dutch auction room).
• Normative Rules: Specify obligations, permissions, and prohibitions for agents in roles.
• Sanctions: Enforce rules through rewards or penalties.
• This external, institutional layer constrains and guides the practical reasoning of individual BDI agents, ensuring societal order.