Heritage of FIPA-ACL and Speech Acts

> Before MCP, before A2A, there was FIPA-ACL. In 2000 the IEEE Foundation for Intelligent Physical Agents ratified an agent communication language with twenty performatives, two content languages, and a set of interaction protocols — contract net, subscribe/notify, request-when. It faded from industry because the ontology overhead was too heavy for the web, but the LLM revival of multi-agent systems is quietly reimplementing the same ideas without the formal semantics: JSON contracts stand in for performatives, natural language stands in for ontologies. This lesson reads FIPA-ACL seriously so you can see which 2026 protocol decisions are reinvention, which are novelty, and where the current wave is going to rediscover problems the 2000s already solved.

Type: Learn

Languages: Python (stdlib)

Prerequisites: Phase 16 · 01 (Why Multi-Agent)

Time: ~60 minutes

Problem

The 2026 agent-protocol landscape is busy: MCP for tools, A2A for agents, ACP for enterprise audit, ANP for decentralized trust, NLIP for natural-language content, plus CA-MCP and two dozen research proposals. Each spec announces itself as foundational.

The honest read is that most of them are rediscovering a very specific twenty-year-old decision tree. Speech-act theory from Austin (1962) and Searle (1969) gave us "utterances are actions." KQML (1993) turned that into a wire protocol. FIPA-ACL (ratified 2000) produced the reference standardization: twenty performatives, content languages SL0/SL1, interaction protocols for contract-net and subscribe-notify. JADE and JACK were the Java reference platforms. The effort faded around 2010 because the ontology overhead was too heavy and the web was winning.

When you look at MCP's tools/call, A2A's task lifecycle, or CA-MCP's shared context store, you are looking at a softer, JSON-native rehash of FIPA decisions. Knowing the heritage tells you two things: which new "innovations" are actually reinventions, and which old failure modes the new specs will rediscover.

Concept

Speech acts, in one paragraph

Austin noticed that some sentences do not describe the world — they change it. "I promise." "I request." "I declare." He called these performative utterances. Searle formalized five categories: assertive, directive, commissive, expressive, declarative. KQML (Finin et al., 1993) made this operational for software agents: a message is a performative (the action) plus content (what the action is about). FIPA-ACL cleaned up KQML's gaps and standardized around twenty performatives.

The twenty FIPA performatives (partial list)

The full list is in fipa00037.pdf (FIPA ACL Message Structure). The point is not to memorize it — the point is that every one of these corresponds to a primitive an LLM protocol eventually re-adds.

Canonical FIPA-ACL message

(inform
  :sender       agent1@platform
  :receiver     agent2@platform
  :content      "((price IBM 83))"
  :language     SL0
  :ontology     finance
  :protocol     fipa-request
  :conversation-id   conv-42
  :reply-with   msg-17
)

Seven fields carry the protocol envelope; one field (content) carries the payload. The rest of the fields are exactly what you reinvent every time you bolt retries, threading, and ontology onto a JSON protocol.

The two legacy platforms

JADE (Java Agent DEvelopment framework, 1999–2020s) was the most-used FIPA-compliant runtime. Agents extended a base class, exchanged ACL messages, ran inside containers, and coordinated using "behaviors." The interaction-protocol library shipped with contract-net, subscribe-notify, request-when, and propose-accept.

JACK (Agent Oriented Software, commercial) emphasized BDI (Belief-Desire-Intention) reasoning on top of FIPA messages. More formal, less adopted.

Both declined once the web stack ate multi-agent use cases. MCP and A2A are the runtime "containers" of 2026.

Why FIPA faded

• Ontology overhead. FIPA required a shared ontology to parse content. Agreeing on ontologies is a years-long standards process. The web just used HTTP + JSON.
• Formal semantics nobody used. SL (Semantic Language) gave rigorous truth conditions, but most production systems used free-form content and ignored the formalism.
• Tooling lock-in. JADE was Java-only; JACK was commercial. Polyglot teams routed around both.
• The internet won the stack. REST, then JSON-RPC, then gRPC replaced ACL's transport.

The LLM revival is FIPA-lite

Compare a FIPA request to an MCP tools/call:

(request                                {
  :sender  agent1                         "jsonrpc": "2.0",
  :receiver tool-server                   "method":  "tools/call",
  :content "(lookup stock IBM)"           "params":  {"name":"lookup_stock",
  :ontology finance                                   "arguments":{"symbol":"IBM"}},
  :conversation-id c42                    "id": 42
)                                        }

Same envelope, different syntax. Both carry: who, whom, intent, payload, correlation id. Neither is a revolution over the other — they are different trade-offs on the same design.

The 2025 survey by Liu et al. ("A Survey of Agent Interoperability Protocols: MCP, ACP, A2A, ANP", arXiv:2505.02279) makes this lineage explicit: MCP corresponds to tool-use speech acts, A2A to agent-peer speech acts, ACP to audit-trail speech acts, ANP to decentralized-identity extensions. The new specs are ACL descendants with JSON syntax and looser semantics.

The trade-off, stated plainly

What FIPA gave you and modern specs drop:

• Formal semantics — you can prove inform implies the sender believes the content.
• A canonical catalog of performatives — you do not have to re-argue "should we have a cancel?".
• Decades of interaction-protocol patterns — contract-net, subscribe-notify, propose-accept — with known correctness properties.

What modern specs give you and FIPA did not:

• JSON-native payloads compatible with every modern tool.
• Natural-language content that LLMs can interpret without a hand-coded ontology.
• Web-stack transport (HTTP, SSE, WebSocket).
• Capability discovery via self-describing documents (MCP listTools, A2A Agent Card).

Looser intent semantics for easier implementation. That is the exact trade.

Interaction protocols worth porting

FIPA shipped ~15 interaction protocols. Three are worth carrying forward into LLM multi-agent systems:

1. Contract Net Protocol (CNP). Manager issues cfp (call for proposals); bidders respond with propose; manager accepts/rejects. This is the canonical task-market pattern (Phase 16 · 16 Negotiation).
2. Subscribe/Notify. Subscriber sends subscribe; publisher sends inform whenever the topic changes. This is every event-bus in 2026.
3. Request-When. "Do X when condition Y holds." Delayed-action with pre-conditions. The 2026 analog is deferred tasks in durable workflow engines (Phase 16 · 22 Production Scaling).

Each maps cleanly onto modern message queues, HTTP + polling, or SSE streaming.

What breaks when you drop the ontology

Without a shared ontology, agents infer meaning from natural-language content. The documented 2026 failure mode is semantic drift: two agents use the same word ("customer") for subtly different concepts, the receiver's agent acts on the wrong interpretation, no schema validator catches it. FIPA's ontology requirement would have rejected the message at parse time.

Mitigations without going full ontology:

• JSON Schema on content — rejects structural errors at the wire.
• Typed artifacts (A2A) — rejects wrong modality.
• Explicit performative in the envelope — makes intent unambiguous even when content is natural language.

The 2026 specs, mapped to speech-act heritage

Reading the table top to bottom, the pattern is: keep the structural primitive, drop the formalism, let LLMs paper over the ambiguity.

Build It

code/main.py implements a pure-stdlib FIPA-ACL translator. It encodes and decodes the canonical ACL envelope and shows how every MCP / A2A message shape reduces to the same seven fields. The demo:

• Encodes five MCP-style and A2A-style messages as FIPA-ACL.
• Decodes FIPA-ACL back to the modern equivalent.
• Runs a toy Contract Net negotiation between one manager and three bidders using cfp, propose, accept-proposal, reject-proposal.

Run:

python3 code/main.py

The output is a side-by-side trace showing each modern message in both its 2026 JSON form and its FIPA-ACL form, then a round-trip of a contract-net bid. The same protocol primitives survive the round-trip; only the syntax differs.

Use It

outputs/skill-fipa-mapper.md is a skill that reads any agent-protocol spec and produces the FIPA-ACL mapping. Use it before adopting a new protocol to answer: "Is this genuinely new, or is it inform with JSON syntax?"

Ship It

Do not bring FIPA-ACL back. Bring back its checklist:

• What is the intent primitive (performative) of each message?
• Is there a correlation id for request-response and cancellation?
• Is there an explicit content language (JSON-RPC, plain text, structured typed artifact)?
• Are interaction protocols first-class, or are you re-implementing contract-net from scratch?
• What happens when two agents disagree about content meaning (semantic drift)?

Document these five questions for any new protocol before you ship it into production.

Exercises

1. Run code/main.py. Observe the round-trip encoding. Identify which FIPA performative corresponds to tools/call, resources/read, and A2A task creation.
2. Extend the contract-net demo with a cancel performative that lets the manager withdraw the task mid-bid. What failure case does cancel solve that retries alone do not?
3. Read FIPA ACL Message Structure (http://www.fipa.org/specs/fipa00037/) sections 4.1–4.3. Pick one performative not covered in this lesson and describe its modern JSON-RPC analog.
4. Read Liu et al., arXiv:2505.02279. For each of MCP, A2A, ACP, ANP, list the FIPA performative families they keep and drop.
5. Design a minimal JSON-Schema for the content field of a request performative in your own system. What does that schema give you that pure natural-language does not, and what does it cost?

Key Terms

Further Reading

• Liu et al. — A Survey of Agent Interoperability Protocols: MCP, ACP, A2A, ANP — the canonical 2025 survey connecting modern specs to FIPA heritage
• FIPA ACL Message Structure Specification (fipa00037) — the ratified 2000 envelope format
• FIPA Communicative Act Library Specification (fipa00037) — the full performative catalog
• MCP specification 2025-11-25 — the modern tool-use equivalent of request/query-ref
• A2A specification — the modern agent-peer equivalent of contract-net and subscribe-notify