Plan conflict
Agents propose incompatible actions for the same goal.
Multi-Agent Coordination
Multiple agents can disagree about plans, evidence, ownership, or resource use. A production system needs deterministic escalation rules instead of asking agents to negotiate indefinitely.
Define resource ownership, priority and evidence rules, use transactional shared state, limit negotiation rounds, and send unresolved or high-risk conflicts to a separate policy service or human approver.
Use these dimensions to make the architecture decision explicit and testable.
Agents propose incompatible actions for the same goal.
Concurrent workers read and write different versions of shared state.
Workers compete for budgets, locks, tools, or human attention.
A locally useful action violates a global rule or approval boundary.
Use these dimensions to make the architecture decision explicit and testable.
Partition responsibilities and validate ownership before execution.
Use version checks, invariants, and conflict events.
Apply policy, evidence quality, risk, and priority rules outside the agents.
Route ambiguous or consequential disputes to a human with a concise evidence packet.
Use these dimensions to make the architecture decision explicit and testable.
Require every proposal to state assumptions and evidence references.
Store the alternatives, rule applied, winner, and rejected actions.
Bound negotiation and choose a safe default when no agreement is reached.
Measure conflict rate, resolution latency, reversals, and harmful outcomes.
Use this as a design-review gate before release.
Place this pattern inside a broader agent architecture and operating model.
Browse memory, planning, frameworks, reliability, safety, and observability.
Open the tutorial library →Start with agent features, design patterns, benefits, challenges, and industry applications.
Open the guide →