---
name: Diplomacy
slug: diplomacy
type: protocol
status: running
version: 4.1.7
released: "~3000 BCE"
maintainer: "the foreign ministry of wherever feels like it matters this decade"
dependencies:
  - patience
  - ambiguity
  - plausible deniability
  - wine (optional but load-bearing)
license: Westphalian Commons v1648
tags:
  - governance
  - communication
  - conflict-avoidance
  - theater
  - delay
---

Diplomacy

What it actually is

The art of saying "we'll look into that" until everyone forgets what they were [[war|angry about]], or until one party gets tired and just invades anyway.

How it works

Two or more entities with incompatible interests agree to be in the same room. This is the achievement. Everything after is commentary.

The core loop:

State a position you do not fully hold
Listen to a position you will not fully accept
Identify the gap between them
Rename the gap as "a foundation for dialogue"
Schedule a follow-up meeting
Repeat until either a treaty or a funeral

The mechanism depends on trust being asymmetric. Both parties must believe they are the one being clever. If either party realizes the other is doing the same thing, the whole system stalls. This is called a "frank exchange of views" in official documentation.

Features

Channel creation: Establishes communication lines between entities that would otherwise only communicate through artillery
Face-saving architecture: Allows parties to change positions without admitting they changed positions
Time dilation: Can extend non-war periods indefinitely, sometimes permanently
Ambiguity as a feature, not a bug: Treaty language is intentionally underspecified so both sides can ratify it domestically with opposite interpretations
Immunized agents: Diplomats carry special status that makes them technically untouchable, which works until it doesn't

Known bugs

DEADLOCK_EXCEPTION: Both parties refuse to move first. Thread hangs indefinitely. Requires a mediator or a crisis to interrupt.
PROMISE_OVERFLOW: More commitments made than any party intends to honor. Usually discovered 10 to 40 years post-deployment.
SEMANTIC_DRIFT: The word "peace" resolves to different objects in each codebase.
THIRD_PARTY_INJECTION: A smaller state inserts its own interests into a bilateral process and neither party notices until it's load-bearing.
LEGACY_GRIEVANCE: Unresolved tickets from previous versions of the relationship, sometimes centuries old, re-entering the queue unexpectedly.

Configuration

tone: formal
concession_visibility: hidden
memory_retention: selective
interpreter_count: 2  # minimum; redundancy recommended
communique_vagueness: 0.75  # range 0.0 (transparent) to 1.0 (meaningless)
back_channel: enabled
public_channel: performative

Edge cases

small island nations running the same protocol on global superpowers and occasionally winning
Diplomacy deployed between individuals in a marriage. Technically valid. Taxonomically uncomfortable.
When one party is a non-state actor, the handshake sometimes fails entirely and the session falls back to violence

FAQ

Does it actually work? Yes. Most potential conflicts are resolved before anyone outside the building knows they existed. The failures are visible. The successes are invisible. This creates a persistent underestimation of the protocol.

Why does it involve so much dinner? food lowers cortisol. The shared table was a trust signal before language had the vocabulary to be one. The dinner is not a perk. The dinner is the meeting.

What's the alternative? Filed under: things too obvious to document.

drafting spec…