VI · Multi-AgentExperimental·

Joint Commitment Team

also known as Joint Intentions Team, Cohen-Levesque Team, Notification-Bound Team

A team of agents adopts a shared goal plus the meta-commitment that each member will notify the others as soon as it believes the goal is achieved, impossible, or no longer relevant.

Context

Multiple agents coordinate on a shared task — a research collective, a delivery team, a multi-step pipeline crossing agents. Each agent has a partial view of progress. When one agent learns the goal is satisfied, infeasible, or no longer wanted, the others continue working unless explicitly told.

Problem

Silent abandonment is the recurring failure. Agent A discovers the goal is impossible (the data the team was going to analyse doesn't exist) and stops, but Agent B keeps preparing analysis tooling for the missing data. Agent C learns the goal has been satisfied by an external event but doesn't tell Agent D, who keeps running expensive computations. Without an explicit meta-commitment that team members notify each other on these state changes, joint tasks waste effort and produce stale outputs.

Forces

  • Each member has a partial view; goal-state insights are not automatically shared.
  • Notification has cost but small compared to wasted work.
  • The meta-commitment must be enforceable, not advisory.
  • Notification semantics differ for 'achieved' vs 'impossible' vs 'no longer relevant'.

Example

A research-collective of three agents commits to 'produce a market analysis for product X by Friday'. Agent A discovers Wednesday that the underlying dataset is corrupted; it broadcasts an 'impossible' notification. Without the joint-commitment contract Agents B and C would have kept generating charts and outlines all of Thursday. With the contract, the team transitions to 'impossible' state and either replans or stands down.

Diagram

Solution

Therefore:

Following Cohen & Levesque's joint intentions framework: when agents form a team around a shared goal G, each agent commits to (a) pursue G as long as G is believed achievable, wanted, and unachieved, and (b) notify the rest as soon as it believes G is achieved, impossible, or no longer relevant. Notification is part of the contract, not extra-credit. The team's lifecycle has explicit transitions: forming, active, satisfied (notified by any member that G holds), impossible (notified by any member), abandoned (notified by the principal that G is no longer wanted).

What this pattern forbids. A team member must not silently abandon a shared goal; notification of belief that the goal is achieved, impossible, or no longer relevant is part of the team contract.

And the patterns that stand alongside it, or against it —

  • complementsCommitment Tracking·— Extract stated intents from each agent turn into a structured ledger with open / followed-through / expired status, making the gap between promise and follow-through visible and auditable.
  • composes-withCoalition Formation·— Agents form temporary subgroups around a task because the coalition can achieve more value than the sum of its members acting alone, with explicit rules for who joins and how payoff or credit is shared.
  • composes-withBDI Agent★★— Agent maintains explicit Beliefs about the world, Desires (goals), and Intentions (committed plans), and reasons by reconciling the three.
  • alternative-toSupervisor★★— Place a coordinating agent above a set of specialised agents and route work to them.
  • complementsWorld Model as Tool·— Let a planning agent invoke a generative world model as a tool to roll out hypothetical futures before committing to an action, treating the world model as a callable simulator rather than a training target.
  • alternative-toStigmergic Coordination★★— Agents coordinate indirectly by leaving and reading marks in a shared environment (files, queues, scratchpads, world model) so that one agent's trace stimulates another's next action, with no direct messaging.
  • complementsPartial Global Planning·— Each agent maintains a partial view of others' plans and incrementally merges local plans into a shared partial global plan, interleaving coordination with execution.

Neighbourhood

Click any neighbour to follow the language. Scroll to zoom, drag to pan.

Used in recipes

References

Provenance