Adjacency Pair¶

Version: v1 · 2026-08-24 · History
Prime #: 620
Origin domain: Linguistics & Semiotics
Subdomain: interaction structure → Linguistics & Semiotics

Core Idea¶

An adjacency pair is a two-slot unit in which an initiating move projects and constrains a typed response, such that a missing response is a noticeable event rather than a null state. The portable commitment is sequential typed conditioning with noticeable absence.

How would you explain it like I'm…

Knock-Knock Answer

When you say "knock knock," the other person is supposed to say "who's there?" Your words leave a hole that only one kind of answer fits, and if nobody answers, everyone notices the silence. An Adjacency Pair is two pieces like that: the first piece asks for a special second piece, and if the second piece is missing, the gap is loud.

The Loud Empty Slot

Some moves come in matched two-part sets: a question expects an answer, a greeting expects a greeting, an invitation expects a yes or no. The first part opens a slot that says what kind of thing belongs in the second part. If nothing fills that slot, the silence itself becomes a noticeable event with real consequences. Some answers are easy and expected, while others are awkward and come with delays, excuses, or hedging. And if the second part is missing or wrong, people try to repair it by asking again.

First-Part, Second-Part

An Adjacency Pair is a two-slot interactive unit where an initiating move in slot one projects and constrains a paired response of a specific type in slot two, with three properties. First, the absence of a slot-two response itself becomes a noticeable event with social or operational consequences — silence becomes data, not nothing. Second, some responses are preferred and others dispreferred, where the dispreferred ones carry extra work in delay, hedging, or accounts. Third, a mismatched or missing slot-two invites repair, a request to try again. The structural commitment is sequential typed conditioning with noticeable absence: not just a turn followed by a turn, but a first-pair-part that specifies what properly belongs in the second slot and makes the gap visible when nothing fits. Though it comes from conversation analysis, the shape recurs in network protocols, liturgies, legal procedures, and birdsong duets — wherever type-conditioning, noticeable absence, preference asymmetry, and a repair affordance all appear.

An Adjacency Pair is a two-slot interactive unit in which an initiating move (slot one) projects, conditions, and constrains a paired response move (slot two) of a typed form-class, such that three things hold: the absence of a slot-two itself becomes a noticeable event with social or operational consequences; some response types are preferred and others dispreferred, the dispreferred carrying added work in delay, hedge, or account; and a mismatched or absent slot-two invites repair, a request for re-attempt. The structural commitment is sequential typed conditioning with noticeable absence: not merely a turn followed by a turn, but a first-pair-part that specifies what properly belongs in the second-pair-part slot and makes the gap visible when nothing fits. The construct comes from conversation analysis, but its shape recurs far beyond conversation. What travels is not the conversational vocabulary but four commitments: type-conditioning (slot one constrains slot two's form-class), noticeable absence (a missing slot-two is data), preference asymmetry (asymmetric cost between two valid slot-twos), and repair affordance (a discipline for handling mismatch). When all four are present — in a network protocol, a liturgy, a legal procedure, or a birdsong duet — the same structural unit is operating, regardless of medium. The pattern's power is that it makes silence a typed event rather than a null state: a gap after a first-pair-part is not the absence of interaction but a specific, detectable outcome the system must tolerate or notice, which unifies a timeout, a ritual breakdown, a procedural default, and a conversational silence under one structure.

Broad Use¶

Conversation analysis: question/answer, offer/accept-or-decline — the origin, where declines come delayed, hedged, and accounted for.
Network protocols: request/response with explicit timeout (the operational form of noticeable absence), NACK signalling, and retry-with-backoff as repair.
Choreography and animal duetting: lead/follow felt as a stumble on mismatch; gibbon and frog duets projecting a partner's reply within a temporal window.
Liturgy and music: versicle/response, where silence reads as ritual breakdown, and call-and-response typed by the call.
Classroom discourse: the initiation/response/evaluation triple, where a missing evaluation is noticeable.
Legal procedure: motion/response with a window after which absence becomes a procedural default.

Clarity¶

It converts "they took turns" into a four-part specification — type-conditioning, noticeable absence, preference asymmetry, repair affordance — that can be checked and engineered.

Manages Complexity¶

A family of exchange phenomena collapses to five named components, so analyzing a database call and a liturgical chant use the same diagnostic.

Abstract Reasoning¶

It yields a fault taxonomy (failure at type-conditioning, absence-detection, preference, or repair) and reframes silence as a typed signal, refining reasoning about timeouts, defaults, and strategic non-response.

Knowledge Transfer¶

Conversation → engineering: treating post-first-move silence as noticeable becomes explicit timeouts, heartbeats, and NACK mechanisms — "absence is data" is identical in both.
Conversation → UX: preference structure (declines come with hedge and account) carries to confirmation and consent dialog design.
Duetting → multi-agent systems: window-bounded response signals aliveness in coordination protocols.

Example¶

A network GET projects a typed response class (2xx/3xx/4xx); a reply outside it is a violation, the timeout makes a missing response a positioned event, and retry-with-backoff is the built-in repair.

Relationships to Other Abstractions¶

Current abstraction Adjacency Pair Prime

Parents (2) — more general patterns this builds on

Adjacency Pair is a kind of Setup–Resolution Pair Prime

Adjacency Pair is Setup-Resolution Pair specialized by noticeable absence, preference asymmetry, and an explicit repair affordance.
Adjacency Pair is part of Absence as Information Prime

A missing projected second-pair part must itself become a detected positive signal; without noticeable absence the child source says there is no adjacency pair.

Children (1) — more specific cases that build on this

Request-Response Domain-specific is a decomposition of Adjacency Pair

Removing network machinery leaves a typed initiating move that projects one causally paired response, makes its absence noticeable, and defines repair.

Not to Be Confused With¶

Adjacency Pair is not Compatibility because an adjacency pair is a sequential unit projecting a typed second whose absence is noticeable, whereas compatibility is a static fit relation between two things.
Adjacency Pair is not Reciprocity because the pair's preference asymmetry is a cost difference between valid responses within one exchange, whereas reciprocity is a moral norm of returning like for like over time.
Adjacency Pair is not Turn-Taking because the pair adds type-conditioning, noticeable absence, preference, and repair, whereas turn-taking is the bare alternation of speaker slots.

Notes¶

(placeholder for later refinement) dag_edges: