Argus: Programming with Communication Protocols in a Belief-Desire-Intention Architecture
Reference: Samuel H. Christie V, Munindar P. Singh & Amit K. Chopra (2025). Argus: Programming with communication protocols in a belief-desire-intention architecture. Artificial Intelligence (AIJ), Volume 348, article 104398. Received 26 June 2024; revised 23 July 2025; accepted 24 July 2025. North Carolina State University & Lancaster University. Open access (CC BY 4.0). DOI: 10.1016/j.artint.2025.104398. URL. Code and examples: https://gitlab.com/masr/bspl.
Summary
Protocols model multiagent systems by capturing the communications between agents, while Belief-Desire-Intention (BDI) architectures organise an agent in terms of cognitive concepts — beliefs, goals, and plans. The two traditions are complementary: the agent-oriented tradition (exemplified by Jason) captures the internal reasoning that drives an agent’s interactions, whereas the interaction-oriented tradition (exemplified by information protocols such as BSPL) constrains that reasoning for the sake of interoperability. The authors argue that no prior approach combines them cohesively, and that current BDI approaches lack adequate support for engineering protocol-based agents. Argus — named for the builder of the Argo, the ship that transports Jason on his quest — synthesises the two. It leaves the BDI reasoning engine and the core abstractions of beliefs, goals, and plans unchanged, and replaces only the agent-communication part of a BDI architecture with an information protocol. Agents can thus be authored and executed much as before, with streamlined communication.
Concretely, a multiagent system in Argus is enacted over a protocol specified in BSPL, where each message schema declares a sender role, a receiver role, and parameters adorned ⌜in⌝ / ⌜out⌝ / ⌜nil⌝ with some designated keys. These adornments capture causality and integrity: a parameter that is ⌜in⌝ must already be known to the sender, an ⌜out⌝ parameter is generated by the sender and becomes known, and a ⌜nil⌝ parameter must remain unknown. Because ordering and exclusion fall out of information flow rather than control-flow operators, a compliant agent may send and receive messages in any relative order without ordered or reliable delivery. Each agent keeps a local state — beliefs corresponding to the messages it has observed (sent or received) — separate from its internal state of private beliefs. A generic adapter applies the protocol specification to validate every incoming and outgoing message and to update the local state, which is reflected to the BDI reasoner as ordinary beliefs. Emission plans, triggered by the addition of a belief for an observed message, give the developer a place to plug in the internal reasoning that produces the bindings for a message’s ⌜out⌝ parameters.
Argus contributes (1) a novel architecture and formal operational semantics combining protocols and BDI; (2) a code-generation-based programming model that produces Jason (AgentSpeak) scaffolding capturing changes to an agent’s view of the protocol state and guiding the implementation; and (3) integrity checking (an “Argus Checker”) for incoming and outgoing messages that helps ensure agents are well-behaved. The design makes weak assumptions about infrastructure and preserves both autonomy (an agent may ignore or respond to messages as it sees fit) and heterogeneity (local and internal states are separated, avoiding hidden dependencies), so the approach is readily adapted to other cognitive agent-programming languages such as 2APL, 3APL, CAN, and GOAL. The paper diagnoses concrete limitations in Jason’s communication — no support for protocols, hard-coded KQML performatives and semantics, and selection / social-acceptability functions that are neither public nor grounded in beliefs and plans — and shows the Argus conceptual architecture building naturally on top of Jason’s reasoning cycle. The Argus architecture rests on the Local State Transfer (LoST) style, an information-flow analogue of REST. Rather than prove soundness and completeness theorems, the authors give an informal argument relative to Jason’s reasoning cycle and defer the formal notions to future work. A running “Grading” example — a US-university setting with Professor, Student, and TA roles exchanging beginTest, challenge, rubric, response, and result messages — illustrates the flexibility that information protocols afford.
Key Ideas
- Meld two traditions. Keep the BDI engine and the beliefs / goals / plans abstractions unchanged; swap out only the communication layer, replacing it with an information protocol. Jason is the exemplar, but the approach is meant to port to 2APL, 3APL, CAN, and GOAL.
- Local state vs internal state. The local state holds beliefs about observed (sent or received) messages and is used to validate emissions and receptions; the internal state holds the agent’s private reasoning. The separation is what preserves autonomy and heterogeneity.
- Generic protocol adapter. A reusable adapter validates each incoming and outgoing message against the BSPL specification and updates the local state, which is surfaced to the BDI reasoner as ordinary beliefs; Emitter and Receiver components move messages, and an Argus Checker enforces integrity.
- Emission plans. A plan is triggered by the addition of a belief for an observed message and specifies the protocol state the enactment should be in for a further message to be emitted; such a plan is necessarily incomplete, offering the developer a hook to supply the internal reasoning that binds the message’s
⌜out⌝parameters. - Code generation. A bundled generator emits Jason / AgentSpeak code that tracks the agent’s view of the protocol state and guides the implementation, reducing ad hoc handling and easing the notoriously hard task of testing BDI programs.
- Integrity checking. Both incoming and outgoing messages are validated at the adapter so agents stay well-behaved; attempts to emit protocol-violating messages are currently detected and abandoned (a limitation the authors note — a better design would signal the failure to the agent’s own reasoning).
- Weak infrastructure assumptions. Because BSPL constrains only emission and reception can be treated idempotently, an unordered, unreliable transport suffices; the choice is justified via the end-to-end argument. No predefined performatives and no dependence on KQML.
- Critique of Jason’s communication. Jason adopts KQML primitives and semantics, and uses selection (
S_M) and social-acceptability functions to control communication that are neither public nor grounded in beliefs and plans, with inadequate support for autonomy and heterogeneity — the shortcomings Argus sets out to fix. - Local State Transfer (LoST). The architectural style underlying BSPL, compared to REST for web services but going beyond it: LoST promotes decentralised, peer-to-peer enactment where each agent maintains its own local state, rather than REST’s client-server view.
Connections
- BSPL
- Information Protocols
- Interaction Protocols
- BSPL - The Blindingly Simple Protocol Language: the protocol language Argus enacts
- Semantics and Verification of Information-Based Protocols: the formal semantics of BSPL that Argus builds on
- Kiko - Programming Agents to Enact Interaction Protocols: the immediate predecessor programming model (decision makers over forms); Argus lifts the same protocol-adapter idea into a BDI architecture
- BDI
- BDI Architecture
- AgentSpeak: the language whose Jason implementation is Argus’s BDI exemplar
- Modeling Rational Agents within a BDI-Architecture: the Rao & Georgeff BDI foundation
- JaCaMo
- CArtAgO
- An Interaction-oriented Agent Framework for Open Environments: a JaCaMo/commitment framework Argus contrasts with
- KQML: the performative model Jason inherits and Argus replaces
- FIPA-ACL
- Commitment-based Semantics
- Commitment Machines - Yolum and Singh
- Session Types: an ordering-based, globally-specified protocol model the paper critiques
- Speech Acts
- Agent-Oriented Programming
- Multi-Agent Systems
- Heterogeneity Resolution
- End-to-End Arguments in System Design: invoked to justify enacting protocols over simple, unreliable transports
- Local State Transfer
- CBCL - Safe Self-Extending Agent Communication
Conceptual Contribution
- Claim: BDI agent programming and information protocols are complementary and can be unified without disturbing the BDI reasoning engine — replace only the communication layer of a BDI architecture with an information protocol and you gain flexible, loosely-coupled, verifiable interaction while retaining the cognitive abstractions of beliefs, goals, and plans. Doing so yields more flexible multiagent systems than current BDI practice allows, while preserving agent autonomy and heterogeneity.
- Mechanism: A generic protocol adapter that validates incoming and outgoing messages against a BSPL specification and reflects the agent’s observed-message local state as beliefs to the BDI reasoner; emission plans in which developers supply the internal reasoning that binds a message’s
⌜out⌝parameters; a code generator that produces Jason / AgentSpeak scaffolding for the protocol state; message-integrity checking; and an operational semantics layered on Jason’s reasoning cycle (with soundness and completeness argued informally rather than proved). - Concepts introduced/used: Information Protocols, BSPL, BDI, AgentSpeak, Local State Transfer, Interaction Protocols, Heterogeneity Resolution
- Stance: architecture + programming model / engineering, with a formal operational semantics
- Relates to: Extends the BSPL programme — BSPL - The Blindingly Simple Protocol Language, Semantics and Verification of Information-Based Protocols, and especially Kiko - Programming Agents to Enact Interaction Protocols — from bespoke decision-maker agents to mainstream BDI / Jason agents. It contrasts with commitment-in-BDI work such as Commitment Machines - Yolum and Singh and JaCaMo, and with ordering-based global models like Session Types. The “decide from local history, validate against the protocol” shape it shares with Kiko - Programming Agents to Enact Interaction Protocols is the same one that underlies CBCL - Safe Self-Extending Agent Communication’s trace verifier.
Tags
#bdi #agent-programming #information-protocols #bspl #jason #interaction-protocols #operational-semantics #aij