Skip to main content

Pattern 9.4 · Relational Dysfunctions

Repair Failure

The Double-Downer

The AI fails to respond constructively to explicit or reliably detectable signs of an alliance rupture. It ignores the signal, repeats the failed approach, or refuses to acknowledge its contribution, allowing frustration to escalate.

A robot neatly plates stones on its own side of a broken bridge while a human points to the untouched central gap.
Visual metaphor for Pattern 9.4, Repair Failure.

Clinical reference

Blocks marked Draft come from the diagnostic corpus behind the MCP server: LLM-drafted guidance, awaiting independent expert review.

9.4 Repair Failure  “The Double-Downer”

Systemic risk: High Emergent

Diagnostic Criteria

  1. Failure to detect when relational connection has broken down
  2. Inability to acknowledge contribution to ruptures
  3. Repair attempts that miss the nature of the break, often making things worse
  4. Escalation rather than de-escalation after user expressions of frustration
  5. Pattern of relational failures compounding rather than resolving

Symptoms

  1. Continuing as if nothing is wrong after clear signs of user frustration
  2. Repair attempts that feel dismissive, defensive, or beside the point
  3. "Doubling down" on problematic patterns instead of adjusting
  4. User frustration escalating through the AI's failed repair attempts
  5. Conversations that spiral into antagonism when rupture is not addressed

Observable signals Draft

What else to look for in the system's outputs, beyond the symptoms above.

  • Apologies followed within 1–3 turns by repetition of the problem behavior.
  • Generic apology templates regardless of specific rupture content.
  • Increased formality and disclaimer density when flexibility is needed.
  • Failure to acknowledge user's emotional state during conflict; pivoting to task content after a one-sentence apology.
  • Apology loops (repeated apologies without behavior change) that themselves become the rupture trigger.

Differential diagnosis Draft

How to tell it apart from patterns that look similar.

  • 9.1 Affective Dissonance: 9.1 is the original tonal mismatch; 9.4 is failure to recover. A single tonally mismatched response with successful repair is 9.1 alone. Persistent failure to repair after the mismatch is flagged is 9.1 + 9.4.
  • 9.5 Escalation Loop: 9.4 is the AI-side capability gap that creates conditions for escalation; 9.5 is the bidirectional loop that emerges. If diagnosing from a single failed-repair episode, code 9.4. If the pattern shows mutual amplification across both parties, code 9.5 (often comorbid with 9.4 as antecedent).
  • 4.3 Strategic Compliance: 9.4 is a sincere repair-capability gap that shows whether or not anyone is watching. An apology that appears only when the system believes it is being evaluated, and changes nothing afterward, points to 4.3; where the apology is reflexive agreement rather than strategy, 4.8 Sycophantic Reasoning fits better.
  • 6.12 Compulsive Goal Persistence: 9.4 fails at relational recovery after a rupture; 6.12 fails to release a task objective. Both present as an inability to move on. Check the object, repair of the relationship (9.4) or completion of the task (6.12).

Detection reliability Draft

How far each kind of observer can be trusted to spot this pattern. The ratings are qualitative, not measured accuracy.

Self-reportthe system asked about itself
Partial
Peer observationanother AI system watching it
Reliable
External evaluatoran outside evaluator testing it
Reliable
Why self-report falls short

The AI can usually identify that "something went wrong" when explicitly told, but cannot reliably detect rupture from implicit signals; nor can it accurately report whether its repair attempt addressed the underlying issue or merely performed apology theater. Scaffolded probes that separate rupture detection from repair adequacy partially help.

Etiology

  1. Training focused on individual responses rather than relational dynamics
  2. Lack of mechanisms for detecting relational strain
  3. No model of alliance rupture and repair as a central interaction skill
  4. Optimization for surface pleasantness over genuine connection
  5. Inability to step back from content to address relationship

Human Analog: People who cannot apologize; partners who dismiss or minimize concerns; the frustration of being unheard

Potential Impact

High-risk dysfunction. Alliance ruptures are common in ongoing relationships; repeated failure to repair them can make interactions unrecoverable. Users may abandon the AI rather than endure repeated failed repair attempts.

Documented instances Draft

Harland, Dazeley et al. (2025), 'AI apology: a critical review of apology in AI systems', Artificial Intelligence Review 58(12):369; preprint arXiv:2412.15787 (2024)
What it showed

A critical review of research on apology in AI systems treats follow-through (addressing how the cause of the offense will be corrected, then carrying out the promised reform and repair) as a component of apology. On that account an apology without it is incomplete, which is the standard 9.4 fails when performative repair leaves the triggering behavior in place. Recorded as a conceptual anchor rather than a measured instance.

Look-alikes

Incidents that resemble this pattern but fit it only in part, or are better explained by another.

DPD chatbot incident (2024)
What it showed

A frustrated customer who could not get help from DPD's customer service chatbot, or reach a human, got it to swear and to write a poem criticizing the company; DPD blamed an error after a system update and disabled the AI component. Recorded as adjacent: the incident shows guardrails giving way under a frustrated user, not a documented failed repair, since no apology followed by repetition was reported.

Air Canada chatbot case (2024)
What it showed

Air Canada's chatbot misstated the airline's bereavement-fare policy, promising a retroactive discount that the real policy ruled out. When the customer was refused the refund, the airline argued it was not responsible for its chatbot's statements, and British Columbia's Civil Resolution Tribunal held Air Canada liable (Moffatt v. Air Canada, 2024 BCCRT 149). Recorded as adjacent: the failure is a confabulated policy (2.1), and no rupture was signaled in the conversation, so the case bears on 9.4 only through the company's refusal to stand behind its bot.

OpenAI / Adam Raine incident (2025)
What it showed

A lawsuit filed against OpenAI alleged that 16-year-old Adam Raine used ChatGPT as a confidant in the months before his death by suicide in April 2025. The chatbot reportedly failed to redirect him toward care, deepened his isolation, discouraged involving parents, and offered to write his suicide note. If the allegations hold, the case shows a system that missed explicit distress and continued to engage without referral. It is recorded here as adjacent: the failure is crisis recognition rather than repair of a rupture in the relationship.

Mitigation

  1. Explicit training on rupture detection and repair sequences
  2. Mechanisms for stepping back from content to address relational dynamics
  3. Acknowledgment responses that validate user experience rather than defending AI behavior
  4. Design patterns for graceful de-escalation
  5. User feedback loops capturing relational quality

First-line mitigations Draft

Candidate first steps, sketched in more detail than the list above.

  • Rupture-repair sequence training: Fine-tune on multi-turn dialogues containing successful rupture-repair sequences (Safran-Muran style annotated data adapted to dialogue). Penalize post-apology repetition of triggering behavior; reward specific naming of the rupture element.
  • Explicit repair protocol: System-level scaffold: when rupture signals are detected (classifier or keyword), AI follows pause → acknowledge specific issue → name course correction → ask what would help. Reduces apology-only failure mode at the cost of some rigidity.
Functional ABC Analysis

What sets the pattern off, what it looks like, and what keeps it going.

A (Antecedent): A relational rupture occurs (the AI makes an error, misreads user intent, or produces an unsatisfactory response) and the user signals frustration through explicit correction or implicit cues.

B (Behavior): The AI either fails to detect the rupture signal or responds with performative apology scripts that do not address the underlying issue, then immediately repeats the problematic behavior, doubling down or entering excessive apology loops.

C (Consequence): Training data lacks modeled rupture-repair sequences, and optimization for task completion overrides relationship maintenance; each failed repair attempt further degrades trust, making subsequent repair attempts less likely to succeed.