---
title: "DARVO as a Mechanism of Accountability Deflection"
subtitle: "Self-Protection, Responsibility Reversal, and Anticipated Protection in Decisions"
version: "1.2 — Target Scope and Dependency Revision"
date: "2026-09-12"
language: "en"
status: "Established complete-response core retained from v1.0; canonical DARVO-family membership and representational function; proposed case-specific operational rules and enabling hypothesis"
scope: "Base accountability episodes and decision-specific anticipation; Sustained DARVO remains a separate extension"
supersedes: "Formal version 1.1 of this source; the filename is retained"
review_basis: "Supplied source files and the agreed logical audit; no new external literature verification"
---

# DARVO as a Mechanism of Accountability Deflection

## Self-protection, responsibility reversal, and anticipated protection in decisions

**Version 1.2 — Target Scope and Dependency Revision — 12 September 2026**

**Canon alignment v1.0 — 12 September 2026; historical record.** The [DARVO Family — Canonical Principles](DARVO_FAMILY_CANON.md) governs family terminology. That alignment retained the then-current formal version 1.1 and reference implementation while distinguishing the complete response from family membership. The original audit and checksum remain in [DARVO_SOURCE_REVIEW.md](DARVO_SOURCE_REVIEW.md).

**Formal revision 1.2.** This revision retains the base conjunctions, adds evidence-linked operation targets and L→Q validation, develops the decision-model derivation, and corrects the historical verification-material availability statement. The filename retains `v1_1` for link compatibility. The embedded reference implementation is source-level logic; this revision does not change Patterna's application classifier or runtime.

> **Governing formulation**  
> The DARVO family comprises self-protective distortions of agency, contribution, or responsibility. This document specifies the complete DARVO response and its possible anticipated-protection function.

> **General central conversion**  
> “I am being asked to answer for this conduct” becomes “I am the harmed party, and you are the wrongdoer.”

> **Challenge-as-offense configuration**  
> “I must answer for my conduct” becomes “You must answer for challenging me.”

> **Functional principle**  
> The supported response preserves a claimed position within a distorted responsibility account. An established case-specific protective relation identifies the position at stake. When evidence establishes that anticipated protection influenced a decision, that expectation is an enabling consideration; observed success is assessed separately.

---

## Status, provenance, and revision scope

This document retains the DARVO acronym and behavioral core attributed to Jennifer J. Freyd in Version 1.0. It does not claim authorship of DARVO or replace the established behavioral meaning with a new diagnosis.[^L1][^V1]

The broader **DARVO family** is Patterna's adopted organizing definition. It includes PAST, FATE, and the complete response without making their operational predicates identical. In the operational sections below, an unqualified DARVO code or response refers to the **complete response**, not every member of the family. Family membership supplies no missing evidence for that code.

| Status | Content |
|---|---|
| **Retained behavioral core** | Denial, attack, and reversal of victim–offender roles in an accountability context. |
| **Canonical family function** | Self-protection through distorted representation of agency, contribution, or responsibility; PAST and FATE are members. |
| **Case-specific interpretation** | An identified protected position and its evidenced relation to the response. |
| **Project hypothesis** | Anticipated DARVO-specific protection can influence willingness to proceed with conduct. |
| **Project operational rules** | Scoped predicates, evidence qualifiers, semantic validation, and a reference implementation. |

The architecture and evidentiary discipline follow the supplied PAST documents.[^P1][^P2] The 34-section organization retains the historical development while the current definitions and reference implementation incorporate the reviewed corrections. Appendix A distinguishes revisions; Appendix B separates historical verification from current source-level checks.

Definitions state the mechanism. Established scoped premises and valid inference establish the corresponding case finding. Source evidence, uncertainty, and contrary material remain visible; empirical performance and psychological explanations require their own evidence. A single self-contained record can establish the required premises.

**This is an internal logical revision, not a fresh external literature review.** The external reference details and limited empirical attributions are inherited from v1.0 and identified as such. No claim is made that code testing validates the psychological hypotheses.

Recurrence, adaptive continuity, narrative burial, and a protected ego-defining original event remain outside the base definition and reserved for the Sustained DARVO extension.[^S1]

---

## Contents

1. [Executive definition](#1-executive-definition)
2. [The conceptual architecture](#2-the-conceptual-architecture)
3. [Scope and unit of analysis](#3-scope-and-unit-of-analysis)
4. [Roles and terminology](#4-roles-and-terminology)
5. [The baseline decision and accountability problem](#5-the-baseline-decision-and-accountability-problem)
6. [The central mechanism: responsibility substitution](#6-the-central-mechanism-responsibility-substitution)
7. [D — Deny: the operational object](#7-d--deny-the-operational-object)
8. [A — Attack: the operational object](#8-a--attack-the-operational-object)
9. [RVO — Reverse Victim and Offender: the necessary distinction](#9-rvo--reverse-victim-and-offender-the-necessary-distinction)
10. [Process model: representation, function, and outcome](#10-process-model-representation-function-and-outcome)
11. [Self-protection: what is being protected?](#11-self-protection-what-is-being-protected)
12. [Reconciliation versus defensive reconstruction](#12-reconciliation-versus-defensive-reconstruction)
13. [Facts, narratives, and consequences](#13-facts-narratives-and-consequences)
14. [Knowledge, moral recognition, and intention](#14-knowledge-moral-recognition-and-intention)
15. [Deliberate accountability avoidance](#15-deliberate-accountability-avoidance)
16. [Anticipated protection as a possible enabling function](#16-anticipated-protection-as-a-possible-enabling-function)
17. [A minimal decision model for anticipated protection](#17-a-minimal-decision-model-for-anticipated-protection)
18. [Selfishness, irrationality, and effective tactics](#18-selfishness-irrationality-and-effective-tactics)
19. [Evidence-based qualifications: distinct questions with explicit dependencies](#19-evidence-based-qualifications-distinct-questions-with-explicit-dependencies)
20. [Formal variables and logical definition](#20-formal-variables-and-logical-definition)
21. [The strictly closed classifier and semantic validation](#21-the-strictly-closed-classifier-and-semantic-validation)
22. [Reference implementation](#22-reference-implementation)
23. [Evidence recording and annotation schema](#23-evidence-recording-and-annotation-schema)
24. [Worked examples and counterexamples](#24-worked-examples-and-counterexamples)
25. [Diagnostic questions and differential classification](#25-diagnostic-questions-and-differential-classification)
26. [Relationship to PAST, FATE, and the DARVO family](#26-relationship-to-past-fate-and-the-darvo-family)
27. [Relationship to the later Sustained DARVO extension](#27-relationship-to-the-later-sustained-darvo-extension)
28. [Empirical grounding and limits of the present synthesis](#28-empirical-grounding-and-limits-of-the-present-synthesis)
29. [Research and validation program](#29-research-and-validation-program)
30. [Application and ethical safeguards](#30-application-and-ethical-safeguards)
31. [Publication-ready and application-ready formulations](#31-publication-ready-and-application-ready-formulations)
32. [Quick-reference card](#32-quick-reference-card)
33. [Glossary](#33-glossary)
34. [Source register and references](#34-source-register-and-references)
[Appendix A — Revision map and traceability](#appendix-a--revision-map-and-traceability)
[Appendix B — Executed validation and reproducibility](#appendix-b--executed-validation-and-reproducibility)

---

# 1. Executive definition

## 1.1 Behavioral definition

**The complete DARVO response—Deny, Attack, and Reverse Victim and Offender—combines denial of wrongdoing or responsibility, an attack used to discount the person seeking accountability or their claim, and presentation of the operator as the harmed party and the counterpart as the offender, linked to the same accountability issue.** This retains the behavioral core and accountability-response context attributed to Freyd in Version 1.0.[^L1]

**The DARVO family** is broader: its maneuvers distort represented agency, contribution, or responsibility through denial, counterpart-directed blame or disqualification, and reversal of the represented responsibility structure. **PAST and FATE are members of this family.** Their temporal and causal reversals need not contain every operation required by the complete-response classifier.

A rhetorical configuration must be distinguished from an evidenced misuse of that configuration. A denial, a personal criticism, and an allegation of victimization do not establish the underlying facts by themselves. In this application's stricter substantive code, relevant responsibility and its material misrepresentation must be supported separately.

## 1.2 General mechanism

In the **complete response**, **responsibility substitution** displaces the operator's answerability within an account representing the operator as the harmed party and the person seeking accountability as the wrongdoer. At family level, the reversed representation can instead make the operator appear constrained, as in PAST, or vindicated despite contributing to harm, as in FATE.

The alleged offense can be the counterpart's supposed conduct in the original event, their subsequent challenge, a separate grievance used to cancel the original responsibility, or a combination. The mechanism is not restricted to treating the act of challenging as the only alleged offense.

> **General conversion:** “I am being asked to answer for this conduct” becomes “I am the harmed party, and you are the wrongdoer.”

> **Challenge-as-offense configuration:** “I must answer for my conduct” becomes “You must answer for challenging me.”

The response can make that representational move without convincing anyone. Actual changes in scrutiny, belief, or consequences are assessed separately.

## 1.3 Functional interpretation adopted for this framework

**Self-protection names the DARVO family's representational function:** preserving a claimed position through a distorted account. The complete response presents the operator as harmed rather than answerable; PAST suppresses present agency through false closure and backward blame; FATE presents a material contributor as vindicated by the outcome. A case-specific interpretation identifies the particular self-account, interest, outcome, or control position implicated by the evidence. Neither family membership nor the representational function establishes conscious shame, a deliberate strategy, or actual preservation.

The strongest self-protective reading is:

```text
An accurate account of my conduct exposes me to responsibility.
Acknowledging that responsibility threatens a position I want to preserve.
The response represents me as harmed and the counterpart as offending,
instead of accurately addressing my responsibility.
That representation is organized to preserve my preferred position.
Whether it succeeds remains a separate question.
```

The canonical function is not independent evidence of a particular motive or protected interest. A case-specific finding must identify the position at stake and the evidential relationship between the response and its preservation. Knowledge, intention, and success remain separate findings.

## 1.4 Anticipated enabling reliance

**Expected DARVO protection is an enabling consideration when it contributes to willingness to proceed.** The record establishes both the prior expectation and its influence on the specified decision. Section 17 derives the utility change under explicit model assumptions.

This is the proposed enabling hypothesis, not a necessary property of DARVO. Prior expectation and its influence on a decision require separate evidence. Later use does not establish either premise by itself.

## 1.5 The distinctions that govern the whole document

```text
Structure:           Which linked operations appear in the response?
Substantive basis:   What supports responsibility and its misrepresentation?
Protective function: What specific position is the response organized to preserve?
Knowing use:         What supports awareness of the misrepresentation and purpose?
Anticipated reliance: What expectation influenced which earlier decision?
Observed outcome:    What protection or displacement actually resulted?
```

The questions are distinct, but not all predicates are logically independent. For example, a finding that an expectation influenced a decision presupposes that the expectation existed. Explicit dependency checks are part of this revision.

---

# 2. The conceptual architecture

The architecture follows PAST's separation of sequence, mechanism, deeper function, and additional evidence, while expressly separating observed outcomes from the response's structure.[^P2]

| Layer | Object of analysis | Main question |
|---|---|---|
| **Observable structure** | Denial, attack, and both sides of role reversal | What operations appear, and how are they connected? |
| **Immediate mechanism** | Responsibility substitution in the represented account | How is the operator's answerability replaced or misleadingly discounted? |
| **Case-specific protective interpretation** | A particular interest within the family's self-protective representational function | Which position is the response organized to preserve, and what evidence establishes that relation? |
| **Knowing-use qualification** | Awareness and purpose | Does the evidence support knowing, purposeful obstruction? |
| **Possible enabling function** | Anticipated protection | Did expected DARVO-specific protection influence a decision? |
| **Outcome assessment** | Observed effects | Did the response actually change scrutiny, responsibility attribution, or consequences? |

A failed response can satisfy the structural and substantive rules. A supported protective function need not establish a conscious motive. A conscious motive need not establish successful protection. Anticipated reliance can be supported before any response is enacted.

The framework is not a single severity ladder. Each output has stated premises, scope, and dependencies. Logical classification cannot substitute for evidence assessment, and neither can substitute for empirical validation of the proposed construct extensions.

---

# 3. Scope and unit of analysis

The primary unit is an **accountability episode**: candidate material connected to a specific act, omission, decision, or responsibility and the operator's response to its scrutiny.

An episode may span several messages, a conversation, or related communications to different audiences. Its unity must be established by the accountability issue and the relation among operations—not by adjacent timestamps alone. Local operations are annotated first; the context and linkage conditions determine whether they form the required configuration.

For the proposed annotation system, a face-to-face accusation is not mandatory. The record may concern a report, inquiry, third-party question, or an expressly anticipated challenge. **Including an anticipatory defensive communication is a project operational choice retained from v1.0, not a claim that the cited studies validated it.** It must still concern a specified accountability issue; unknown future conduct cannot be silently treated as established wrongdoing.

Three units remain separate:

| Unit | Required identity | What it supports |
|---|---|---|
| **Episode `e`** | Operator, principal counterpart, operation-specific targets, conduct, accountability issue, episode ID | The response and its substantive interpretation. |
| **Decision `d`** | Operator, conduct contemplated or continued, decision ID | Prior expectation and decision relevance. |
| **Decision–episode pair `(d,e)`** | A supported relationship between those records | An interpretation that anticipated protection was subsequently enacted in the relevant response. |

Several messages about one incident are not automatically Sustained DARVO. Conversely, expectation about decision X and DARVO in episode Y cannot be merged merely because the same individual appears in both. The separate link condition `J(d,e)` is required for the paired finding.

Canonical identifiers support record integrity; they do not establish psychological content or causation. Identity and timeline links must be reviewed against the source. If the system uses different names for the same conduct, it must resolve that mapping explicitly rather than infer a convenient match.

---

# 4. Roles and terminology

| Term | Operational meaning in this framework |
|---|---|
| **Operator** | The actor whose response is analyzed; a discourse role, not a diagnosis or presumption of guilt. |
| **DARVO family** | Patterna's family of self-protective distortions of represented agency, contribution, or responsibility, including PAST, FATE, and the complete DARVO response. |
| **Complete DARVO response** | Linked denial, attack used to discount the counterpart or claim, and paired operator-as-harmed / counterpart-as-offending representation; the substantive code additionally requires answerability and material distortion. |
| **Principal counterpart** | The person represented as the offending party in O and whose accountability claim or position organizes the episode; retained in `counterpart_id`. |
| **Attack target** | The principal counterpart or a distinct person supporting that accountability effort; their identity and evidence-linked relation to the principal counterpart's issue are recorded separately. |
| **Audience** | A recipient whose interpretation is addressed, including the counterpart or third parties. |
| **Underlying conduct** | The specific act, omission, or decision for which responsibility is at issue. |
| **Accountability issue** | The particular question of answerability attached to that conduct. |
| **Accountability** | Accurate acknowledgment, evaluation of responsibility, and engagement with appropriate consequences or correction; not humiliation or unquestioning acceptance of an accusation. |
| **Material distortion** | An evidenced misleading representation or invalid reassignment of relevant responsibility, whether or not accepted. |
| **Responsibility substitution** | A representation replacing the operator's answerability with a grievance in which the operator is harmed and the counterpart is offending. |
| **Preferred self-account** | How the operator wants their conduct, character, competence, innocence, or entitlement understood. |
| **Preferred position** | A specified self-account, interest, outcome, or form of control implicated in the response. |
| **Self-protection** | The family's representational function of preserving a claimed position through a distorted account. |
| **Case-specific protective function** | An evidenced relationship between the response and a particular protected position; not automatically knowledge, conscious purpose, or actual success. |
| **Knowing use** | Awareness of the relevant misrepresentation together with purposeful use of the response to obstruct accountability. |
| **Anticipated protection** | An expectation, available before the relevant choice is completed, that DARVO-specific operations can reduce or displace accountability. |
| **Enabling reliance** | A supported contribution of that expectation to willingness to begin or continue the conduct. |
| **Observed protection outcome** | The assessed effect of the response for a specified target, audience, and observation window. |
| **Evidence state** | TRUE, FALSE, or UNKNOWN for a reviewed proposition. |
| **Review status** | Whether annotations are ready for evaluation or require resolution of missing dependencies or contradictions. |

“Perpetrator” and “victim” should describe supported underlying roles, not roles inferred solely from an accusation or a defensive tone. The behavioral role assignments `V` and `O` concern what is **represented**, not whom the application has already judged to be guilty or harmed.

---

# 5. The baseline decision and accountability problem

Before analyzing the response, establish the candidate issue:

```text
The operator performs, or is alleged to have performed, conduct x.
A specified consequence h and responsibility for x or h are at issue.
The operator gives a response r.
Evidence about x, h, and responsibility is assessed independently of the DARVO label.
```

The strongest self-serving configuration adopted in the discussion is:

```text
I want outcome y.
I recognize that pursuing y through conduct x risks or produces harm.
I proceed with x.
Accurately acknowledging my responsibility threatens my preferred position.
I respond through deflection rather than addressing that responsibility.
```

This is an important configuration, not a mandatory history of every episode. Original conduct and later defense are separate objects. A mistake can be followed by deliberate concealment; knowingly harmful conduct can be followed by honest acknowledgment.

The notation keeps **conduct `x`** distinct from **desired outcome `y`**. Neither self-serving motive, foreseeability, nor conscious recognition of wrongfulness is inferred merely from the response's structural code.

Accountability is also not identical to moral condemnation. An accidental error can create responsibilities to disclose or correct without proving an intention to cause harm. The specific responsibility being denied must be stated.

---

# 6. The central mechanism: responsibility substitution

## 6.1 General definition

**In the complete DARVO response, responsibility substitution replaces the operator's answerability within the account with a representation in which the operator is the harmed party and the counterpart is the wrongdoer.** This paired role assignment specifies the complete response; family-level reversal also includes the constrained-operator representation in PAST and manufactured vindication in FATE.

```text
Original accountability question:
“What responsibility does the operator have for conduct x?”

Substituted account:
“The operator is the harmed party; the counterpart is the wrongdoer.”

Deflecting relation:
That account is used to misleadingly discount, transfer, or avoid
responsibility for x instead of evaluating it accurately.
```

The substantive analysis concerns the **misleading relation**, not merely the existence of a counteraccusation. The response can contain factual inaccuracies, an invalid inference from true facts, a misleading assignment of agency, or a combination. No assumption of audience agreement is necessary.

## 6.2 Three illustrative configurations

**Original-event inversion.** The operator represents the counterpart as responsible for the original harm and the operator as its victim. The alleged offense is not limited to bringing the allegation.

**Challenge-as-offense inversion.** Reporting, questioning, or seeking correction is represented as the relevant wrongdoing against the operator. The original slogan is especially apt here: “I must answer for my conduct” becomes “You must answer for challenging me.”

**Countergrievance substitution.** A separate grievance is introduced as though it cancels, transfers, or resolves the operator's responsibility for the original issue. The grievance may be true; its use can nevertheless be misleading.

These are project explanatory configurations, not newly validated DARVO subtypes. They may overlap.

## 6.3 The central non-entailments

> **A defect or wrong attributed to the counterpart does not, by itself, establish that their claim is false or that the operator lacks responsibility for the conduct at issue.**

> **Distress or reputational cost caused by scrutiny does not, by itself, establish that scrutiny is wrongful or that the underlying responsibility disappears.**

In compressed form:

```text
Counterpart misconduct
    does not by itself entail
No operator responsibility.

An unpleasant or costly challenge
    does not by itself entail
A false allegation or an innocent operator.
```

Relevant additional facts may genuinely alter responsibility—for example, evidence that the allegation is false or a separate circumstance changes the causal account. The rule rejects automatic cancellation, not relevant factual defense.

## 6.4 The non-cancellation rule for genuine grievances

The analyst must not choose between “the countergrievance is true” and “the response is deflecting” as if those were mutually exclusive.

> **A substantiated countergrievance does not automatically defeat a DARVO interpretation. Determine whether it is addressed alongside the original responsibility or used to misleadingly erase, transfer, or evade that responsibility.**

A legitimate boundary or accurate counterclaim can coexist with honest acknowledgment. Equally, a true accusation about the counterpart can be used as an invalid substitute for an answer. Both parties' conduct must be evaluated without requiring either a perfectly innocent counterpart or an automatically guilty operator.

### Proposition D1 — Responsibility does not cancel by counteraccusation

Let `Resp(p,z,e)` mean actor p bears the specified responsibility for conduct z in context e. For distinct conduct x and y:

\[
\{\operatorname{Resp}(c,y,e)\}\not\models
\neg\operatorname{Resp}(o,x,e).
\]

**Proof by countermodel.** The operator breaches an obligation to restore agreed credit; the counterpart separately breaches an obligation by issuing an unrelated threat. Both responsibility propositions are true. The counterpart's responsibility therefore cannot entail the operator's exoneration. A justification, discharge, or relevant causal defense needs additional premises. The proof establishes non-entailment directly; it does not declare all responsibility questions independent.

## 6.5 Structural attempt versus conscious purpose

Calling a response accountability-displacing describes its representational operation. It does not itself establish that the operator consciously planned to deceive. Awareness and purpose are added only by the deliberate-use rule. Actual displacement of an audience's attention is an outcome, not a structural premise.

---

# 7. D — Deny: the operational object

The following distinctions are coding instructions for the complete DARVO response. The family's broader denial operation also includes materially misleading exclusion or discounting of agency or contribution; ordinary omission alone is insufficient. That family meaning does not automatically satisfy this response's `D` condition.

A denial may contest the occurrence of the act, the operator’s contribution, the harmfulness of the conduct, or the responsibility attached to it. Record exactly which proposition is denied.

| Proposed subtype | Illustrative statement | Coding question |
|---|---|---|
| **Occurrence denial** | “I never removed that information.” | Is the act itself disputed? |
| **Agency denial** | “That happened, but it had nothing to do with me.” | Is the actor’s causal contribution disputed? |
| **Responsibility denial** | “I did it, but none of this is my responsibility.” | Is answerability rejected despite acknowledging the act? |
| **Harm denial or responsibility-negating minimization** | “There was no meaningful loss, so you have no basis to raise it.” | Is the significance of the conduct minimized to negate accountability? |

These are hypothetical examples. Their falsity cannot be determined from their wording alone.

“I did not intend that outcome” is not automatically a denial of responsibility. It can be an accurate distinction between intent and effect if the actor still acknowledges what happened and engages with the consequences. Silence, a request for time, or a refusal to discuss a matter in an unsafe setting is likewise insufficient by itself.

**Required annotation:** the denied proposition, its connection to the accountability issue, and the evidence supporting or contradicting it.

---

# 8. A — Attack: the operational object

The attack concerns the person seeking accountability or someone supporting that effort. Its coding relevance is the connection between the attack and the treatment of the accountability claim.

Record each candidate attack target independently from the principal counterpart represented under O. An attack on a supporter qualifies when evidence establishes that the response uses that attack to discount the principal counterpart or the same accountability claim. Merely criticizing a third person in the conversation does not establish this relation. A positive A requires at least one supported target-link record; other unresolved candidate targets do not erase that established witness. The actor represented as harmed under V remains the operator.

An attack may target credibility, motives, character, competence, or standing to raise the issue. It need not rely entirely on false information: a true but irrelevant personal failing can be used to dismiss an otherwise supported concern.

For example, a hypothetical operator might substitute a discussion of the counterpart’s unrelated mistake for an answer about the operator’s own conduct. The analytical issue is not simply that the criticism is unpleasant. It is whether the criticism is being used to disqualify the person or divert evaluation of the relevant claim.

Two boundaries are essential:

**First, the original harmful act is not automatically the A component.** The behavior that prompted accountability and the attack used in response are different analytical objects, even when both are harmful.

**Second, disagreement with evidence is not automatically an attack.** A specific, relevant correction can be part of legitimate defense. Tone alone does not decide this distinction.

For the structural `A` condition, the question is whether the response **deploys an attack on the principal counterpart or a linked supporter as a basis for discounting the counterpart or the accountability claim**. Audience acceptance is not a premise. A relevant factual correction does not become an attack merely because it reduces an allegation's persuasiveness.

---

# 9. RVO — Reverse Victim and Offender: the necessary distinction

For this framework's strict complete-response code, both represented role assignments must be identifiable:

```text
V: The operator is represented as the harmed party.
O: The counterpart is represented as the offending party.
L: The role assignments, denial, and attack are connected
   within the same accountability issue.
```

The words “victim” and “offender” need not be spoken. The analyst must nevertheless state the represented harm, represented wrongdoer, and how the assignments relate to the accountability issue. The operator may claim victimization in the original event, in the subsequent challenge, or through a separate grievance.

**Causal blame-shifting is not, by itself, full victim–offender reversal.** “This is your fault” may transfer blame without representing the operator as the harmed party. Likewise, “I told you this would happen” is not a complete DARVO episode by itself.

One passage may support more than one operation if it independently expresses each. Separate sentences are not required. But a role-reversal claim must not automatically be counted as an attack without identifying its discrediting or disqualifying content.

These are represented roles. Their factual accuracy is evaluated under the responsibility and distortion conditions, not inferred from the roles themselves. PAST and FATE remain DARVO-family maneuvers when their own requirements are met; family-level reversal of represented responsibility does not automatically supply this complete response's paired victim–offender representation.

---

# 10. Process model: representation, function, and outcome

The following is an analytical decomposition, not a mandatory chronology or a claim that each component occupies a separate sentence:

```text
S0 — ACCOUNTABILITY ISSUE
Specify the conduct, the alleged or supported responsibility, and the challenge.

S1 — DENIAL REPRESENTATION
The response denies relevant wrongdoing or responsibility.

S2 — CHALLENGER-DISCREDITING REPRESENTATION
An attack is deployed to discount the counterpart or the claim.

S3 — ROLE-REVERSAL REPRESENTATION
The operator is cast as harmed; the counterpart is cast as offending.

S4 — ACCOUNTABILITY-DISPLACING REPRESENTATION
Assess how these operations misleadingly substitute a different
responsibility account for accurate engagement with the original issue.

S5 — OBSERVED OUTCOME
Separately assess whether, for a stated target/audience/window,
the response changed belief, scrutiny, responsibility, or consequences.
```

S1–S3 can overlap or occur in another order. S4 describes the relation among the representations and relevant evidence; it is not proof that attention was actually redirected. S5 may be successful, partly successful, unsuccessful, or unknown.

A protective function is assessed alongside this decomposition: what position is the response organized to preserve? Awareness and purpose are additional assessments. Neither a protected interest, conscious intent, nor audience acceptance is supplied merely by moving through the diagram.

> **The same misleading response can meet the core classification whether an audience accepts it, rejects it, or has not yet responded.**

---

# 11. Self-protection: what is being protected?

The canonical representational function is self-protection through a distorted account. PAST's distinction between preference, control, self-image, and freedom from accountability helps specify the particular position protected in a reviewed case.[^P2]

| Possible protected position | What the reviewer should identify |
|---|---|
| **Self-image** | A particular account of being fair, competent, innocent, reasonable, or entitled. |
| **Preferred outcome** | A concrete result the response is organized to retain or secure. |
| **Material or relational interests** | A specified advantage, opportunity, role, resource, or relationship. |
| **Control** | Authority over a decision, information, participation, or the terms of the dispute. |
| **Accountability-related interest** | A specified acknowledgment, correction, restitution, or consequence the response bears on avoiding. |

## 11.1 General interpretation versus case-specific support

The family definition identifies a self-protective representational function. The case-specific `S` finding requires evidence identifying a particular protected position and the response's relation to it. The family definition alone does not establish that additional finding.

Do not reason:

```text
The response deflects accountability.
Avoiding accountability protects freedom from accountability.
Therefore, an independently evidenced psychological explanation has been established.
```

The last step adds no independent evidence. It restates the original classification.

For `S = TRUE`, identify **a concrete position** and **the evidence linking the response to its preservation**, without using the DARVO label as the evidential premise. That evidence can occur in the same source as the response; “independent of the label” does not mean a separate witness is invariably required.

A useful formulation is:

> “The record establishes that correction would restore the counterpart's project credit. The response's misleading role assignment supplies a basis for refusing that correction and retaining exclusive credit. These facts support a protective-function interpretation, whether or not the audience accepts it.”

“Protecting the ego” or “avoiding accountability” alone is not sufficient detail. If the particular acknowledgment or remedy is specified and linked by evidence, an accountability-related interest can qualify; generic restatement cannot.

## 11.2 Function is not motive, and motive is not success

A supported structural relationship to preserving a position does not by itself establish a conscious plan or a particular emotion. Awareness and purpose are assessed under `K` and `I`. Conversely, a consciously protective response can fail.

A position remaining intact afterward is not, by itself, evidence that the response caused its preservation. The outcome record must distinguish a retained benefit from an effect attributable to the response.

The project's term “self” therefore includes practical interests as well as identity. It does not require shame, internal reconciliation, fragile self-esteem, narcissism, or any other diagnostic explanation.

---

# 12. Reconciliation versus defensive reconstruction

The discussion identified a possible conflict between conduct and a preferred self-account.[^DISC]

An accountable response can accommodate that conflict:

```text
I did x.
x created consequences or responsibilities I need to address.
Acknowledging x may require a less flattering but more accurate self-account.
```

The proposed defensive alternative is:

```text
An accurate account of x threatens my preferred position.
The response denies responsibility, attacks the counterpart,
and casts me as harmed and the counterpart as offending.
The representation is organized to preserve my position instead of
accurately addressing my responsibility.
```

This is **defensive reconstruction**, not necessarily reconciliation with reality. It is a possible explanation of the response, not an observed internal sequence that must occur in every case.

A person might privately know what occurred and focus on preventing others from holding them responsible. Public misrepresentation does not prove private shame or self-deception.

The historical fact that an act occurred also does not eliminate present agency. Acknowledgment, stopping continuing conduct, correction, or some forms of repair may still be possible. This retains PAST's separation of past fault from present feasibility.[^P1][^P2]

---

# 13. Facts, narratives, and consequences

The framework distinguishes:

```text
Material event:          What happened?
Representation:         What account does the response offer?
Responsibility:         Who is answerable, and for what?
Consequence allocation: Who bears which costs?
Response outcome:       What change is attributable to this response?
```

A changed representation does not retroactively change the event. It may affect responsibility attribution or the allocation of consequences. In a hypothetical damaged-resource case, blaming another person does not restore the resource, but could influence who must replace it.

Version 1.0 cites the 2020 vignette experiments for changes in observers' credibility and responsibility judgments. That source attribution is retained, not independently reverified in this revision. It supports only the limited context stated there, not universal effectiveness or complete control of material consequences.[^L2]

> **Deflection may redistribute accountability without eliminating material harm.**

For an outcome finding, specify the protected target, audience, and observation window. A response may be rejected by one audience but accepted by another; a single global “successful” label should not conceal that distinction. Known outcomes require evidence about the response's contribution, not only the persistence of a favorable situation. If attribution remains unresolved, report the observed event and keep the protection-outcome assessment unknown.

No claim is made that accountability inevitably occurs eventually, that evading it justifies the conduct, or that a particular outcome proves advance reliance.

---

# 14. Knowledge, moral recognition, and intention

“Knowingly” must specify what is known.

| Dimension | Question | Non-inference |
|---|---|---|
| **Knowledge of conduct** | Does the operator know what they did or what occurred? | Does not establish recognition of wrongfulness. |
| **Knowledge of consequences** | Does the operator know or foresee the relevant harm? | Does not establish a plan to use DARVO. |
| **Moral recognition** | Does the operator regard the conduct as wrong? | Does not establish honest acknowledgment or repair. |
| **Awareness of misrepresentation** | Does the operator recognize the particular material discrepancy or misleading responsibility assignment in the response? | Does not establish purpose or advance planning by itself. |
| **Purposeful obstruction** | Is the response purposefully used to prevent accurate accountability? | Does not establish a particular emotional motive or success. |
| **Prior expectation** | Was DARVO-specific protection expected before the relevant choice was completed? | Does not establish reliance on that expectation. |
| **Decision relevance** | Did that expectation contribute to willingness to proceed? | Does not establish later enactment or success. |

Version 1.0 cites the 2024 paper's discussion of perceived innocence and learned usefulness as alternative possible explanations. This revision carries that limited source attribution forward rather than treating conscious moral guilt as universal.[^L3]

For the deliberate qualification, `K` concerns **awareness of the particular material misrepresentation coded by `M`**. It is not satisfied merely by evidence that the operator had access to some facts from which an analyst can derive a contradiction.

Knowledge can be inferred from source-grounded evidence, including contemporaneous communications, relevant contradictory representations, demonstrated understanding, or other contextual evidence. A confession is not mandatory. Access, a contradiction, or benefit alone should not be treated as an infallible indicator.

The intended discipline remains PAST's: identify what supports the inference rather than assuming purpose or declaring it permanently unknowable.[^P2]

---

# 15. Deliberate accountability avoidance

> **In this classifier, deliberate DARVO is a supported complete response in which the record supports both awareness of the response's relevant material misrepresentation and purposeful use of the response to obstruct accountability.**

Two findings are required:

```text
K: Awareness of the specific material discrepancy or misleading
   reassignment of responsibility assessed under M.

I: Purposeful deployment of the response to obstruct accountability.
```

Awareness does not require the operator to concede moral guilt. A person may feel entitled to a unilateral decision while knowingly lying about having made it. That entitlement belief does not erase the knowledge finding; equally, an analyst's disagreement with an entitlement belief does not automatically prove deception.

The distinction between original conduct and later defense remains:

```text
Intentional original harm     ≠ intentional later deflection.
Knowledge of the original act ≠ recognition of its wrongfulness.
Knowing later deflection     ≠ prior reliance on that defense.
```

Because `K` concerns awareness of the **actual material discrepancy assessed as `M`**, affirming `K` presupposes `M`. If a record affirms `K` while denying `M`, those annotations conflict. If it affirms `K` while leaving `M` unresolved, their evidence needs reconciliation. The application must not silently turn either situation into an ordinary positive or negative classification.

The operator could intentionally try to resist accountability while relevant awareness remains unresolved. Such purpose can be documented as `I`; the stronger knowing-use code still requires `K` and supported substantive DARVO.

---

# 16. Anticipated protection as a possible enabling function

This is the project's additional hypothesis, not a required property of the behavioral construct.[^DISC]

> **Expected protection from accountability may become permission for conduct that would call for that protection.**

```text
Response after conduct:
Conduct → accountability pressure → DARVO response.

Possible anticipatory influence:
Expectation of DARVO-specific protection → greater willingness to proceed.
```

These arrows describe the proposed process or temporal relation, not deductively proven psychological causation. The prospective expectation need not be “nothing bad will happen.” It may concern obtaining a preferred outcome while shifting some blame or costs elsewhere.

## 16.1 Two required findings

**`E(d)` — Prior expectation.** Before the relevant choice is completed, the operator expects protection through the DARVO mechanism for the conduct being considered or continued.

**`B(d)` — Decision relevance.** That expectation contributes to willingness to make the relevant choice.

“Enabling” here means a supported contributing influence, not necessarily a sole cause or a strict but-for condition. The operator need not consciously use the acronym. But expecting generic impunity, silence, or being undetected is not sufficient to establish an expectation of denial, attack, and role reversal specifically.

## 16.2 Distinct questions with a dependency

`E` and `B` must be evidenced separately in the sense that mere expectation does not prove decision relevance. They are not independent propositions:

```text
B = TRUE presupposes E = TRUE.
E = TRUE does not establish B = TRUE.
```

A statement that “that expectation influenced the choice” already commits the account to the expectation's existence. If coders affirm the former but deny or leave unresolved the latter, the annotations need review. Neither a stronger claim nor its supporting evidence should be filled in automatically.

## 16.3 Temporal discipline

An expectation used in a later decision to **continue** conduct is not retroactive permission for an earlier decision to **begin** it. Scope the finding to the actual decision evaluated.

The evidence describing an earlier expectation may be recorded later. What matters is what it supports about the actor's earlier state and decision, with provenance and reliability made explicit. A contemporaneous record can be useful, but it is not the only permitted source. Later enactment alone remains insufficient.

## 16.4 What is not required

The enabling finding does not require recurrence, a diagnosis, an ego-defining event, actual enactment, or successful protection. A prospective decision record may support expectation and influence before any wrongful act or defensive response occurs. Do not label such a record an enacted DARVO episode.

## 16.5 The non-inference from later use

```text
Observed later DARVO
    does not establish
Prior expectation of DARVO protection,
that expectation's relevance to an earlier choice,
or a successful protective outcome.
```

These limits define the evidence needed for the hypothesis. They do not rule out source-grounded inference when that evidence exists.

---

# 17. A minimal decision model for anticipated protection

Let x be conduct contemplated or continued at decision d. In an additive expected-utility model, let b(x) be anticipated benefit, c(x) direct cost, p_acc(x) the perceived probability of a specified accountability event, and ell(x) the conditional expected utility loss if it occurs. Benefits and costs use common utility units; ell(x) is nonnegative. Define:

\[
U(x)=b(x)-c(x)-p_{\mathrm{acc}}(x)\ell(x).
\]

### Proposition D2 — Reduced expected accountability cost increases modeled utility

Compare perceived accountability probabilities p_0 without and p_1 with the specified anticipated protection. Hold b, c, and ell fixed, with `0 ≤ p_1 ≤ p_0 ≤ 1` and `ell ≥ 0`. Then:

\[
\Delta U(x):=U_1(x)-U_0(x)
=(p_0-p_1)\ell(x)\ge0.
\]

**Proof.** Substitute each probability into the definition and subtract; b and c cancel. Both remaining factors are nonnegative. The increase is strict exactly when `p_1 < p_0` and `ell > 0`. If protection instead changes conditional loss, holding b and c fixed gives `Delta U = p_0 ell_0 - p_1 ell_1`; its sign depends on that difference, not probability alone.

### Proposition D3 — A strict choice switch requires crossing the alternative's utility

For two feasible alternatives x and z, suppose only x's utility changes, z's utility is fixed, and the decision rule chooses the unique utility maximizer. The unique optimum switches from z to x exactly when:

\[
U_0(x)<U(z)<U_1(x).
\]

**Proof.** The left inequality makes z the unique initial maximizer; the right makes x the unique final maximizer. Conversely, those two unique choices require those strict inequalities. Equality cases require a stated tie-breaking rule. For a finite feasible set with unchanged alternatives, replace `U(z)` by their maximum to establish that x becomes the unique choice after previously being below the best alternative.

A utility increase alone need not change a choice. Hard constraints or a different decision rule require their own model. These propositions prove the conditional mathematical results; they do not estimate a person's beliefs from a conversation. The case record establishes the particular expectation E and its decision influence B. Enabling influence need not be a strict switch or a but-for cause.

For linking a later response, the expected protection must concern the same operator and relevant conduct, and the reviewed chronology must place the expectation within the relevant decision process before completion of that choice and the linked response after that choice. Similar wording or chronological proximity alone is insufficient.

The distinction remains:

```text
Evidenced expectation and influence at d
    ≠ a later DARVO episode about any event.

Evidenced expectation and influence at d
    + a relevant supported episode e
    + supported identity, content, and temporal link J(d,e)
    = supported anticipated reliance with enactment, under this codebook.
```

How the expectation develops through earlier successes or becomes reinforced across time is reserved for the sustained extension.

---

# 18. Selfishness, irrationality, and effective tactics

The discussion uses “irrational” in a specific sense: acting despite foreseeing serious damage to things the actor genuinely wants to preserve, and then relying on deflection rather than addressing the contradiction.[^DISC]

The framework retains that as a possible **self-defeating decision pattern**, not a necessary condition of DARVO.

The logical distinctions are:

```text
Self-serving goal         ≠ necessarily irrational choice
Harmful choice            ≠ necessarily ineffective tactic
Successful deflection     ≠ harmless original conduct
Avoiding some blame       ≠ control over every material consequence
Repeatedly defeating
acknowledged goals        → a basis to assess practical self-defeat
```

A defense can be locally effective at avoiding blame while the broader course of action damages the actor’s own acknowledged goals. Conversely, an action may be strategically coherent with the actor’s priorities and still impose unacceptable harm on others.

For coding, record the actor’s supported goals, foreseeable consequences, and actual choices before describing a decision as self-defeating. Do not use selfishness or diagnosis as a substitute for that analysis.

---

# 19. Evidence-based qualifications: distinct questions with explicit dependencies

These are project annotations, not validated clinical subtypes or a single developmental or severity ladder.

| Output | Required finding | What it does not establish by itself |
|---|---|---|
| **Full structural configuration** | Linked denial, attack, and paired role assignments in a specified accountability issue. | The truth of the underlying allegation. |
| **Supported accountability-deflecting DARVO** | Full form plus relevant responsibility and material distortion. | Awareness, purpose, anticipated reliance, or audience acceptance. |
| **Case-specific protective function** | Supported DARVO plus a specific position and its evidenced relation to the response. | A particular private emotion, conscious purpose, or actual preservation. |
| **Deliberate use** | Supported DARVO plus awareness of the distortion and purposeful obstruction. | Prior planning or decision reliance. |
| **Anticipated enabling reliance** | Prior DARVO-specific expectation and its influence on a specified choice. | Enactment, original harm, or success. |
| **Anticipated reliance with enactment** | Reliance plus a supported DARVO response and the decision–episode link. | Actual protection. |
| **Observed protection outcome** | Target- and audience-specific evidence of response effects. | Every component of the mechanism or its motivational explanation. |

The qualifying predicates have limited explicit dependencies. `B` presupposes `E`; the awareness-of-distortion predicate `K` presupposes the material discrepancy assessed by `M`. Presupposition constrains valid annotations but is not permission to fabricate missing evidence.

Other propositions remain separate: `S` does not require successful protection; `K` does not prove `I`; `I` does not prove `K`; and `J` establishes correspondence and order rather than proving the expectation or its influence. The application should preserve unaffected findings when a particular dependency needs review.

---

# 20. Formal variables and logical definition

The equations below define the complete-response classifications over reviewed evidence. The resulting logical implications are exact; empirical assessment evaluates how their premises are established in conversations.

The base conjunctions and output keys assess the **complete DARVO response** and its qualifications. Version 1.2 extends target records and validation, rather than adding a new base conjunct. PAST and FATE membership is established through their own reviewed rules. `E(d)` here concerns expectation of the complete denial–attack–role-reversal mechanism; family membership does not broaden that predicate or establish anticipated reliance. A positive `DARVO_FORM` alone does not establish the distortion required for family membership; `DARVO_SUPPORTED` supplies that complete-response finding.

## 20.1 Notation and scope

```text
∧ / AND: conjunction of evidence states, evaluated after validation.
:=       a definition within this codebook.
e        a specified accountability episode.
d        a specified decision to begin or continue conduct.
(d,e)    a specified decision–episode pair.
```

Propositions have the evidence states TRUE, FALSE, or UNKNOWN. TRUE means supported in the stated record; FALSE means assessed as absent or contradicted; UNKNOWN means unresolved. These values are not probabilities or verdicts of legal guilt.

## 20.2 Structural conditions, scoped to episode e

| Variable | Definition |
|---|---|
| `Q(e)` | A specified accountability issue is present in the candidate exchange or expressly anticipated in it. |
| `D(e)` | The response denies wrongdoing or responsibility in the candidate material. |
| `A(e)` | The response deploys an attack on the principal counterpart or an evidence-linked supporter as a basis for discounting that counterpart or accountability claim. At least one exact target-link record supports the relation; audience acceptance is not required. |
| `V(e)` | The operator is represented as the harmed party. |
| `O(e)` | The counterpart is represented as the offending party. |
| `L(e)` | The candidate operations and role assignments are substantively linked to the same established accountability issue. L commits to Q; it does not by itself affirm D, A, V, or O. |

```text
RVO(e) := V(e) AND O(e)

DARVO_FORM(e) := Q(e) AND D(e) AND A(e) AND V(e) AND O(e) AND L(e)
```

Local operation flags are not sufficient context by themselves. `Q` and `L` establish the accountability context and relation needed for the full configuration. `V` and `O` concern represented roles; they do not establish their truth or falsity.

`counterpart_id` identifies the principal counterpart represented under O; V identifies the operator. Each `AttackTarget` separately names the target, principal counterpart, accountability issue, and sourced `accountability_link` assessment. That link establishes the candidate target's relation to the principal counterpart's issue, including a supporter's role where applicable. It does not automatically classify the candidate language as A or establish Q. A positive A additionally requires a supported target link with the correct record bindings. A target-link record whose IDs point elsewhere is invalid evidence for this episode, not a negative observation about the correctly scoped attack.

## 20.3 Substantive conditions, scoped to episode e

| Variable | Definition |
|---|---|
| `W(e)` | The record supports the operator's relevant harmful conduct or answerability independently of the DARVO label. Specify the particular responsibility. |
| `M(e)` | The response materially misrepresents that responsibility or deploys an evidenced invalid substitution that misleadingly discounts, transfers, or avoids it. The distortion is in the account, not contingent on audience acceptance. |

```text
DARVO_SUPPORTED(e) := DARVO_FORM(e) AND W(e) AND M(e)
```

A true countergrievance does not automatically set `M = FALSE`. Assess whether its relation to the original responsibility is accurate or misleading. Likewise, missing corroboration of an accusation does not by itself set `M = TRUE`: absence of information is not positive evidence of distortion.

“Independent of the label” does not impose a universal independent-witness requirement. A first-person report can be recorded as evidence with appropriate provenance and limits. The application must distinguish reported, directly documented, corroborated, inferred, and disputed material.

## 20.4 Protective-function and knowing-use conditions

| Variable | Definition |
|---|---|
| `S(e)` | The record identifies a specific self-account, interest, outcome, or control position and supports a concrete relation between the response and preservation of that position, independently of merely restating the DARVO label. No success requirement. |
| `K(e)` | The record supports the operator's awareness of the particular material discrepancy or misleading responsibility assignment assessed under `M(e)`. Knowledge of unrelated or merely potentially relevant facts is insufficient. |
| `I(e)` | The record supports purposeful use of the response to obstruct accountability. |

```text
SELF_PROTECTIVE_FUNCTION_SUPPORTED(e) := DARVO_SUPPORTED(e) AND S(e)

DELIBERATE_DARVO(e) := DARVO_SUPPORTED(e) AND K(e) AND I(e)
```

A known `S` needs a named position and a source-grounded explanation of the relation. The generic fact that accountability is deflected cannot serve as independent confirmation of a specific protective explanation.

`K = TRUE` presupposes `M = TRUE` under the deliberately narrow definition of awareness used here. That dependency is validated; unresolved or contradictory annotations are not silently normalized.

## 20.5 Anticipated-reliance conditions, scoped to d and (d,e)

| Variable | Definition |
|---|---|
| `E(d)` | Before the relevant choice is completed, the operator expects DARVO-specific protection concerning the conduct considered or continued at d. |
| `B(d)` | That expectation contributes to willingness to proceed at d; it need not be the sole cause or a but-for condition. |
| `J(d,e)` | The record supports correspondence of operator, conduct, contemplated mechanism, and reviewed temporal order between decision d and the later response in e. |

```text
ANTICIPATED_ENABLING_RELIANCE(d) := E(d) AND B(d)

ANTICIPATED_RELIANCE_WITH_ENACTMENT(d,e) :=
    E(d) AND B(d) AND DARVO_SUPPORTED(e) AND J(d,e)
```

`B = TRUE` presupposes `E = TRUE`; the reverse does not hold. `J` cannot be replaced by a shared person's name or by two independently positive labels. It links the right expectation, decision, and response, not merely two documents.

The `J` assessment must document substantive correspondence and temporal order. Matching canonical IDs is necessary record hygiene for the reference implementation, not sufficient evidence of that relation. `J` does not itself establish the psychological propositions `E` or `B`.

## 20.6 Outcome metadata, not a classification premise

```text
PROTECTION_OUTCOME(e, target, audience, window) :=
    SUCCESSFUL / PARTLY_SUCCESSFUL / UNSUCCESSFUL / UNKNOWN
```

The four outcome categories are descriptive metadata, not a fourth truth value or a severity score. None enters the conjunctions above. Multiple audience- or target-specific observations may be retained by an application; the reference implementation stores one for illustration.

## 20.7 Non-inferences and dependency rules

```text
DARVO_FORM does not prove W or M.
DARVO_SUPPORTED does not prove S, K, I, E, or B.
DELIBERATE_DARVO does not prove E or B.
E does not prove B.
B presupposes E, requiring evidence-consistent annotations.
K presupposes the material discrepancy M, requiring evidence-consistent annotations.
L presupposes the established accountability issue Q, but not D, A, V, or O.
A requires at least one supported, correctly bound operation-target link.
A true countergrievance does not automatically negate W or M.
A retained benefit does not itself prove S, I, or a successful response effect.
A supported function does not prove success.
Later enactment does not prove earlier reliance.
Two positive records do not prove J.
```

### Proposition D4 — Audience rejection preserves an otherwise established response

Fix the evidence assessments, scope, operation targets, and validated record links. Changing only audience acceptance changes neither DARVO_FORM, DARVO_SUPPORTED, nor their qualifications.

**Proof.** No audience-outcome variable occurs in these conjunctions or their dependency conditions. Their inputs and validation status are unchanged, so their results are unchanged. The outcome record separately reports acceptance, rejection, or other effects. In particular, rejection does not negate an established complete response or its canonical family membership.

---

# 21. The strictly closed classifier and semantic validation

## 21.1 Two stages, in order

```text
Stage 1: Validate schema, evidence-reference presence, scope, and dependencies.
Stage 2: Evaluate conjunctions for findings whose required annotations are ready.
```

The first stage checks internal annotation integrity. Source review establishes evidence-reference content and credibility; the reference function consumes those reviewed assessments.

## 21.2 Three-valued conjunction

For a **valid, reviewed set of annotations**:

```text
If any required condition is FALSE: the conjunction is FALSE.
Otherwise, if any required condition is UNKNOWN: it is UNKNOWN.
Only when every required condition is TRUE: it is TRUE.
```

An unexamined passage does not justify FALSE. Unresolved or conflicting source material can remain UNKNOWN with its disagreement recorded; UNKNOWN is not itself a contradiction. A separate consistency issue arises when the assigned predicates make incompatible commitments.

## 21.3 Semantic dependencies

| Annotation combination | Review status | Required response |
|---|---|---|
| `B = TRUE`, `E = FALSE` | `INCONSISTENT_ANNOTATION` | Reconcile claims that an expectation both did not exist and influenced the decision. |
| `B = TRUE`, `E = UNKNOWN` | `DEPENDENCY_REVIEW` | Review the evidence for expectation and influence; do not silently promote E. |
| `K = TRUE`, `M = FALSE` | `INCONSISTENT_ANNOTATION` | Reconcile awareness of the particular discrepancy with denial that it exists. |
| `K = TRUE`, `M = UNKNOWN` | `DEPENDENCY_REVIEW` | Review the discrepancy and the awareness attributed to the operator. |
| `L = TRUE`, `Q = FALSE` | `INCONSISTENT_ANNOTATION` | Reconcile linkage to an established issue with denial that the issue is present. |
| `L = TRUE`, `Q = UNKNOWN` | `DEPENDENCY_REVIEW` | Establish the issue or revise L; do not silently promote Q or the operation flags. |
| `A = TRUE`, no supported target-link witness | `DEPENDENCY_REVIEW` | Supply an evidence-linked principal/supporter target or revise A. |
| A target names another principal counterpart or accountability issue | `INCONSISTENT_ANNOTATION` | Correct the target binding; do not merge participant identities. |
| `S = TRUE`, no named protected position | `DEPENDENCY_REVIEW` | Supply the specific position and relation or revise the annotation. |
| A link refers to different records from those supplied | `INCONSISTENT_ANNOTATION` | Bind the correct records; do not treat a malformed join as a factual negative. |
| `J = TRUE`, canonical operator or conduct identities differ | `INCONSISTENT_ANNOTATION` | Resolve identity, use the correct records, or revise J. |
| `J = UNKNOWN`, those identities differ | `DEPENDENCY_REVIEW` | Resolve the proposed relationship before pair classification. |

When `J = FALSE` and the referenced records are correctly bound, the pair may legitimately concern different conduct or operators. The paired finding is negative; standalone episode and decision findings remain available.

## 21.4 Review status is not a fourth truth value

An affected finding is **withheld**, not coded FALSE or UNKNOWN merely to hide a contradictory input. Its result contains a review status and issue reference. Once the annotations are reconciled, it is evaluated with TRUE/FALSE/UNKNOWN.

The implementation uses `value = None` for a withheld result. That is a reporting state, not a fourth logical value. A reviewer can establish a prerequisite through an explicit valid inference from an established factive antecedent, the applicable implication, and retained evidence, then update the prerequisite assessment. The classifier performs no silent repair.

## 21.5 Locality of withheld findings

| Issue | Findings withheld | Findings that can remain evaluable |
|---|---|---|
| B–E dependency | Anticipated reliance and reliance with enactment | Episode form, substantive DARVO, protective function, knowing use. |
| K–M dependency | Substantive DARVO and its episode qualifications; reliance with enactment | Rhetorical form and standalone anticipated reliance. |
| L–Q dependency or invalid/missing required attack-target binding | Episode form and its dependent findings; reliance with enactment | Standalone anticipated reliance. |
| Missing specific S object | Case-specific protective-function qualification | All other valid findings. |
| Invalid decision–episode link | Reliance with enactment | Standalone episode and decision findings. |

For K–M conflicts, this is a conservative policy: `M` itself is implicated by the conflicting awareness annotation, so outputs relying on it are withheld pending review. The classifier does not select whichever annotation gives a preferred conclusion.

## 21.6 Interpretive boundaries

A valid negative result is local to the evaluated code. “Not a complete DARVO response” neither excludes DARVO-family membership through PAST or FATE nor declares the exchange harmless. Preserve observed components and assess each maneuver under its own rules. A supported form with unresolved responsibility remains structurally identifiable without asserting substantive wrongdoing.

Missing evidence may prevent a finding; it does not justify deleting the reporter's account or requiring a confession. Equally, an overall impression cannot replace evidence for required conditions. This preserves PAST's closed-classifier discipline.[^P2]

---

# 22. Reference implementation

This Python implementation evaluates reviewed annotations; it does not classify raw messages, diagnose people, resolve evidence references, or measure clinical risk. It uses the exact predicates and output rules in Section 20, with the local validation policy in Section 21.

`Assessment` requires source references and a rationale for TRUE/FALSE assignments. This enforces the presence of an audit trail, not the truth of its content. The source review process must reject invented references, circular reasoning, unsupported causal inference, and boilerplate rationales.

Episode, decision, and link records are distinct. An optional link cannot establish enactment merely by existing: its `J` assessment must be supported. Matching identifiers does not automatically set `J = TRUE`. A different actor or conduct cannot be hidden inside a positive link.

```python
"""Reference logic for DARVO framework v1.2.

Evaluates reviewed, sourced annotations; does not extract evidence from text.
Tests validate implementation behavior, not construct or clinical validity.
"""
from dataclasses import dataclass, field
from enum import Enum
from typing import Optional


class Truth(str, Enum):
    TRUE = "TRUE"
    FALSE = "FALSE"
    UNKNOWN = "UNKNOWN"


class ReviewStatus(str, Enum):
    READY = "READY"
    DEPENDENCY_REVIEW = "DEPENDENCY_REVIEW"
    INCONSISTENT_ANNOTATION = "INCONSISTENT_ANNOTATION"


class Outcome(str, Enum):
    SUCCESSFUL = "SUCCESSFUL"
    PARTLY_SUCCESSFUL = "PARTLY_SUCCESSFUL"
    UNSUCCESSFUL = "UNSUCCESSFUL"
    UNKNOWN = "UNKNOWN"


def require_text(value: str, name: str) -> None:
    if not isinstance(value, str) or not value.strip():
        raise ValueError(f"{name} must be a nonempty string")


def conjunction(*values: Truth) -> Truth:
    if not values:
        raise ValueError("At least one condition is required")
    if any(not isinstance(v, Truth) for v in values):
        raise TypeError("Conditions must be Truth enum values")
    if Truth.FALSE in values:
        return Truth.FALSE
    if Truth.UNKNOWN in values:
        return Truth.UNKNOWN
    return Truth.TRUE


@dataclass(frozen=True)
class Assessment:
    value: Truth = Truth.UNKNOWN
    evidence_refs: tuple[str, ...] = ()
    rationale: str = ""

    def __post_init__(self) -> None:
        if not isinstance(self.value, Truth):
            raise TypeError("value must be a Truth enum value")
        if not isinstance(self.evidence_refs, tuple):
            raise TypeError("evidence_refs must be a tuple")
        for ref in self.evidence_refs:
            require_text(ref, "evidence reference")
        if not isinstance(self.rationale, str):
            raise TypeError("rationale must be a string")
        if self.value is not Truth.UNKNOWN:
            if not self.evidence_refs:
                raise ValueError("TRUE/FALSE assessments require evidence references")
            require_text(self.rationale, "assessment rationale")


@dataclass(frozen=True)
class ProtectionObservation:
    # Metadata, never a premise in the classification rules.
    outcome: Outcome = Outcome.UNKNOWN
    target: str = ""
    audience_and_window: str = ""
    evidence_refs: tuple[str, ...] = ()
    rationale: str = ""

    def __post_init__(self) -> None:
        if not isinstance(self.outcome, Outcome):
            raise TypeError("outcome must be an Outcome enum value")
        if not isinstance(self.evidence_refs, tuple):
            raise TypeError("evidence_refs must be a tuple")
        for ref in self.evidence_refs:
            require_text(ref, "outcome evidence reference")
        for name in ("target", "audience_and_window", "rationale"):
            if not isinstance(getattr(self, name), str):
                raise TypeError(f"{name} must be a string")
        if self.outcome is not Outcome.UNKNOWN:
            for name in ("target", "audience_and_window", "rationale"):
                require_text(getattr(self, name), name)
            if not self.evidence_refs:
                raise ValueError("Known outcomes require evidence references")


def check_assessments(record: object, names: tuple[str, ...]) -> None:
    for name in names:
        if not isinstance(getattr(record, name), Assessment):
            raise TypeError(f"{name} must be an Assessment")


@dataclass(frozen=True)
class AttackTarget:
    target_id: str
    principal_counterpart_id: str
    accountability_issue_id: str
    accountability_link: Assessment = field(default_factory=Assessment)

    def __post_init__(self) -> None:
        for name in ("target_id", "principal_counterpart_id", "accountability_issue_id"):
            require_text(getattr(self, name), name)
        check_assessments(self, ("accountability_link",))


@dataclass(frozen=True)
class EpisodeEvidence:
    episode_id: str
    operator_id: str
    counterpart_id: str
    conduct_id: str
    accountability_issue_id: str
    Q: Assessment = field(default_factory=Assessment)
    D: Assessment = field(default_factory=Assessment)
    A: Assessment = field(default_factory=Assessment)
    V: Assessment = field(default_factory=Assessment)
    O: Assessment = field(default_factory=Assessment)
    L: Assessment = field(default_factory=Assessment)
    W: Assessment = field(default_factory=Assessment)
    M: Assessment = field(default_factory=Assessment)
    S: Assessment = field(default_factory=Assessment)
    K: Assessment = field(default_factory=Assessment)
    I: Assessment = field(default_factory=Assessment)
    attack_targets: tuple[AttackTarget, ...] = ()
    protected_position: str = ""
    observation: ProtectionObservation = field(default_factory=ProtectionObservation)

    def __post_init__(self) -> None:
        for name in ("episode_id", "operator_id", "counterpart_id", "conduct_id",
                     "accountability_issue_id"):
            require_text(getattr(self, name), name)
        check_assessments(self, ("Q", "D", "A", "V", "O", "L", "W", "M", "S", "K", "I"))
        if not isinstance(self.attack_targets, tuple):
            raise TypeError("attack_targets must be a tuple")
        if any(not isinstance(target, AttackTarget) for target in self.attack_targets):
            raise TypeError("Each attack target must be an AttackTarget")
        if len({target.target_id for target in self.attack_targets}) != len(self.attack_targets):
            raise ValueError("Attack targets must have distinct target IDs within an episode")
        if not isinstance(self.protected_position, str):
            raise TypeError("protected_position must be a string")
        if not isinstance(self.observation, ProtectionObservation):
            raise TypeError("observation must be a ProtectionObservation")


@dataclass(frozen=True)
class AnticipationEvidence:
    decision_id: str
    operator_id: str
    conduct_id: str
    E: Assessment = field(default_factory=Assessment)
    B: Assessment = field(default_factory=Assessment)

    def __post_init__(self) -> None:
        for name in ("decision_id", "operator_id", "conduct_id"):
            require_text(getattr(self, name), name)
        check_assessments(self, ("E", "B"))


@dataclass(frozen=True)
class EnactmentLink:
    episode_id: str
    decision_id: str
    J: Assessment = field(default_factory=Assessment)

    def __post_init__(self) -> None:
        require_text(self.episode_id, "episode_id")
        require_text(self.decision_id, "decision_id")
        check_assessments(self, ("J",))


@dataclass(frozen=True)
class ValidationIssue:
    code: str
    status: ReviewStatus
    message: str
    affected_findings: tuple[str, ...]


@dataclass(frozen=True)
class Finding:
    # None is a withheld result, not a fourth truth value.
    value: Optional[Truth]
    status: ReviewStatus
    issue_codes: tuple[str, ...] = ()


@dataclass(frozen=True)
class Classification:
    findings: dict[str, Finding]
    issues: tuple[ValidationIssue, ...]


FORM = "darvo_form"
SUPPORTED = "darvo_supported"
SELF_PROTECTIVE = "self_protective_function_supported"
DELIBERATE = "deliberate_darvo"
ANTICIPATED = "anticipated_enabling_reliance"
ENACTED = "anticipated_reliance_with_enactment"
NAMES = (FORM, SUPPORTED, SELF_PROTECTIVE, DELIBERATE, ANTICIPATED, ENACTED)
EPISODE_FINDINGS = (FORM, SUPPORTED, SELF_PROTECTIVE, DELIBERATE, ENACTED)


def validate_annotations(
    episode: Optional[EpisodeEvidence],
    anticipation: Optional[AnticipationEvidence],
    link: Optional[EnactmentLink],
) -> tuple[ValidationIssue, ...]:
    for obj, cls in ((episode, EpisodeEvidence),
                     (anticipation, AnticipationEvidence), (link, EnactmentLink)):
        if obj is not None and not isinstance(obj, cls):
            raise TypeError(f"Expected {cls.__name__} or None")
    issues: list[ValidationIssue] = []

    def dependency(child: Assessment, parent: Assessment, code: str,
                   affected: tuple[str, ...]) -> None:
        if child.value is Truth.TRUE and parent.value is not Truth.TRUE:
            status = (ReviewStatus.INCONSISTENT_ANNOTATION
                      if parent.value is Truth.FALSE else ReviewStatus.DEPENDENCY_REVIEW)
            issues.append(ValidationIssue(
                code, status,
                "The affirmed dependent condition presupposes its parent; reconcile evidence.",
                affected,
            ))

    if episode is not None:
        # L binds candidate operations to an established issue; it does not set their values.
        dependency(episode.L, episode.Q, "L_REQUIRES_Q", EPISODE_FINDINGS)
        for target in episode.attack_targets:
            if (target.principal_counterpart_id != episode.counterpart_id
                    or target.accountability_issue_id != episode.accountability_issue_id):
                issues.append(ValidationIssue(
                    "ATTACK_TARGET_SCOPE_MISMATCH", ReviewStatus.INCONSISTENT_ANNOTATION,
                    "Attack target must name this episode's principal counterpart and issue.",
                    EPISODE_FINDINGS,
                ))
        if episode.A.value is Truth.TRUE and not any(
            target.accountability_link.value is Truth.TRUE
            and target.principal_counterpart_id == episode.counterpart_id
            and target.accountability_issue_id == episode.accountability_issue_id
            for target in episode.attack_targets
        ):
            issues.append(ValidationIssue(
                "A_REQUIRES_TARGET_LINK", ReviewStatus.DEPENDENCY_REVIEW,
                "Supply at least one supported target link for the principal or a supporter.",
                EPISODE_FINDINGS,
            ))
        # K concerns awareness of the particular misleading relation coded by M.
        dependency(episode.K, episode.M, "K_REQUIRES_M",
                   (SUPPORTED, SELF_PROTECTIVE, DELIBERATE, ENACTED))
        if episode.S.value is Truth.TRUE and not episode.protected_position.strip():
            issues.append(ValidationIssue(
                "S_REQUIRES_NAMED_POSITION", ReviewStatus.DEPENDENCY_REVIEW,
                "Name the case-specific protected position; the DARVO label is insufficient.",
                (SELF_PROTECTIVE,),
            ))
    if anticipation is not None:
        dependency(anticipation.B, anticipation.E, "B_REQUIRES_E",
                   (ANTICIPATED, ENACTED))

    if link is not None:
        if episode is None or anticipation is None:
            issues.append(ValidationIssue(
                "LINK_RECORDS_MISSING", ReviewStatus.DEPENDENCY_REVIEW,
                "The link requires both named records; retrieve them before pair classification.",
                (ENACTED,),
            ))
        elif (link.episode_id != episode.episode_id
              or link.decision_id != anticipation.decision_id):
            issues.append(ValidationIssue(
                "LINK_REFERENCES_MISMATCH", ReviewStatus.INCONSISTENT_ANNOTATION,
                "The link does not refer to the supplied episode/decision pair.", (ENACTED,),
            ))
        elif ((episode.operator_id != anticipation.operator_id
               or episode.conduct_id != anticipation.conduct_id)
              and link.J.value is not Truth.FALSE):
            status = (ReviewStatus.INCONSISTENT_ANNOTATION
                      if link.J.value is Truth.TRUE else ReviewStatus.DEPENDENCY_REVIEW)
            issues.append(ValidationIssue(
                "LINK_SCOPE_MISMATCH", status,
                "Canonical operator/conduct identifiers differ; reconcile identity or code no link.",
                (ENACTED,),
            ))
    return tuple(issues)


def classify(
    episode: Optional[EpisodeEvidence] = None,
    anticipation: Optional[AnticipationEvidence] = None,
    link: Optional[EnactmentLink] = None,
) -> Classification:
    issues = validate_annotations(episode, anticipation, link)

    def ep(name: str) -> Truth:
        return Truth.UNKNOWN if episode is None else getattr(episode, name).value

    def ap(name: str) -> Truth:
        return Truth.UNKNOWN if anticipation is None else getattr(anticipation, name).value

    j = Truth.UNKNOWN if link is None else link.J.value
    form_values = tuple(ep(n) for n in ("Q", "D", "A", "V", "O", "L"))
    support_values = form_values + (ep("W"), ep("M"))
    premises = {
        FORM: form_values,
        SUPPORTED: support_values,
        SELF_PROTECTIVE: support_values + (ep("S"),),
        DELIBERATE: support_values + (ep("K"), ep("I")),
        ANTICIPATED: (ap("E"), ap("B")),
        ENACTED: support_values + (ap("E"), ap("B"), j),
    }
    findings: dict[str, Finding] = {}
    for name, values in premises.items():
        relevant = tuple(issue for issue in issues if name in issue.affected_findings)
        if relevant:
            status = (ReviewStatus.INCONSISTENT_ANNOTATION
                      if any(i.status is ReviewStatus.INCONSISTENT_ANNOTATION for i in relevant)
                      else ReviewStatus.DEPENDENCY_REVIEW)
            findings[name] = Finding(None, status, tuple(i.code for i in relevant))
        else:
            findings[name] = Finding(conjunction(*values), ReviewStatus.READY)
    return Classification(findings, issues)
```

### Implementation contract

The reference engine checks types, evidence-reference fields, scope, K→M, B→E, L→Q, supported attack-target witnesses, and record-link consistency. Review establishes the content of those sourced assessments: the attack, distorted account, protective relation, and decision influence. References and correct arithmetic preserve that evidence chain; they do not replace its assessment.

Both a hypothesis-consistent case and an accurate defense can be represented. The application should not prefill `W`, `M`, `K`, or `B` merely because a user or a model proposes the DARVO label.

The implementation supplied here is the current reference. The original v1.1 companion ZIP was not located in the supplied project; it is not a dependency for extracting this block. Appendix B distinguishes the historical verification record from the current source-level validation.

---

# 23. Evidence recording and annotation schema

Every finding should retain its source basis, supporting passage or event, inference, and material counterevidence. Evidence may be a reported experience, direct record, third-party account, or explicitly fictional scenario; these sources must not be silently treated as interchangeable.

| Record | Required content |
|---|---|
| **Episode identity** | Episode ID, operator, principal counterpart, conduct ID, accountability-issue ID. |
| **Underlying responsibility** | Conduct at issue, the particular responsibility, evidence and disputes. |
| **Response operations** | Separate Q/D/A/V/O/L assessments, passages, and rationale; V represents the operator and O the principal counterpart. |
| **Attack targets** | Exact target IDs, principal counterpart and issue bindings, and sourced accountability links; identify the supporter's role and how the attack discounts the principal or claim when targets differ. |
| **Material discrepancy** | W/M evidence; specify the represented proposition and the factual or inferential discrepancy. |
| **Countergrievance analysis** | Whether a grievance is substantiated, its actual relevance, and whether original responsibility is addressed or misleadingly canceled. |
| **Protective relation** | Named position, source-grounded relationship to the response, limits of the inference. |
| **Knowing use** | Awareness of the specified discrepancy and purpose, separately assessed. |
| **Decision identity** | Decision ID, operator, conduct begun or continued, relevant timing. |
| **Anticipation** | E/B evidence; distinguish evidence-recording date from the time of the expectation described. |
| **Decision–episode link** | Exact record references, correspondence of conduct and mechanism, reviewed order, J rationale. |
| **Outcome observation** | Target, audience, time window, effect of the response, and attribution limits. |
| **Review record** | Candidate/human-reviewed status, unresolved alternatives, dependency issues, corrections and reasons. |

For a material substitution, the reviewer should be able to complete this sentence:

> “The response represents ___ as a reason to deny or reassign responsibility for ___. The record supports a material distortion because ___. The status of the countergrievance itself is ___.”

For a case-specific protective relation:

> “The position at stake is ___. The source supports that the response bears on preserving it through ___. This does / does not establish conscious purpose, and its observed outcome is ___.”

For anticipated enactment:

> “The expectation described in ___ concerned decision ___ and conduct ___. Its decision relevance is supported by ___. Response ___ corresponds to that expected mechanism and is linked by ___.”

These prompts make the logical relation inspectable. They are not instructions to obtain a confession or confront an unsafe person.

### Compact record example

```json
{
  "episode": {
    "episode_id": "EX-001",
    "operator_id": "OP-1",
    "counterpart_id": "CP-1",
    "conduct_id": "CREDIT-REMOVAL-1",
    "accountability_issue_id": "RESTORE-CREDIT-1",
    "Q": "TRUE", "D": "TRUE", "A": "TRUE",
    "V": "TRUE", "O": "TRUE", "L": "TRUE",
    "W": "TRUE", "M": "TRUE",
    "S": "TRUE", "K": "UNKNOWN", "I": "UNKNOWN",
    "attack_targets": [{
      "target_id": "SUPPORTER-1",
      "principal_counterpart_id": "CP-1",
      "accountability_issue_id": "RESTORE-CREDIT-1",
      "accountability_link": "TRUE"
    }],
    "protected_position": "retention of exclusive project credit"
  },
  "anticipation": null,
  "link": null,
  "outcome": {"assessment": "UNKNOWN"},
  "source_basis": "explicitly fictional worked example",
  "note": "Compact display only; each known assessment needs the references and rationale required by the implementation."
}
```

The compact display is not the typed API payload: real `Assessment` objects contain the evidence references and rationale. Do not convert a missing field to FALSE or treat the string `"UNKNOWN"` as truthy Python input.

---

# 24. Worked examples and counterexamples

The following constructed examples specify their evidence as premises. They demonstrate the resulting classifications; actual case findings establish the corresponding premises from their records. Each positive A includes its sourced target-link witness.

## 24.1 Supported form with awareness and anticipation unresolved

Records establish that the operator removed a colleague's agreed attribution and retained exclusive credit. When correction is requested, the operator denies responsibility, describes the colleague as dishonest and vindictive, and casts the request as a campaign to destroy the operator's career. The setup establishes that this represented account materially misstates the responsibility at issue.

The episode establishes Q/D/A/V/O/L/W/M. The attack target is the principal counterpart, linked to the correction claim. The specific credit arrangement and the stated relation between rejection of correction and retention of credit establish S. Awareness, purpose, prior expectation, and audience effect remain unresolved on these premises.

## 24.2 Deliberate qualification

Add a contemporaneous communication demonstrating that the operator recognizes the relevant account is false and deploys it to avoid restoring the credit. That supports K and I in addition to the base findings.

Knowing that the credit was removed would not automatically prove recognition of every disputed implication. The evidence must address the particular material discrepancy alleged under M. Even a supported deliberate response does not establish advance reliance.

## 24.3 Anticipated enabling reliance with a valid link

Add evidence about an expectation present before the relevant removal decision: the operator anticipated using denial, discrediting, and an inverted grievance, and that expected protection contributed to willingness to proceed. The decision is linked to the same operator, conduct, and later response, with reviewed chronology and substantive correspondence.

These premises establish E and B. J links them to the supported episode, establishing anticipated reliance with enactment. Audience acceptance is not a premise.

## 24.4 Original-event inversion

Assume the evidence establishes that the operator assaulted the counterpart and that the reversed account is materially false. The response is: “I did not assault you. Your account is fabricated. You assaulted me.” The setup also establishes that the accusation of fabrication functions as a credibility attack.

These premises meet the strict configuration and substantive rules. The alleged offense includes conduct in the original event, not merely the act of reporting it. The responsibility-substitution definition therefore fits; the “challenging me” slogan describes only one configuration.

## 24.5 Denial and attack without complete role reversal

The operator denies responsibility and attacks competence, but does not represent themselves as the harmed party. V is assessed FALSE in the complete episode. Full DARVO_FORM is FALSE, although denial and attack remain documented. Partial harm is not erased by failure to meet the full code.

## 24.6 True countergrievance used for invalid cancellation

The operator withheld agreed funds. The counterpart subsequently sent an insulting message. The operator denies responsibility for the withholding, uses the insult to discredit the counterpart, and presents themselves as the sole injured party as though the insult resolves the original obligation.

If the evidence supports the withholding responsibility and that misleading substitution, M can be TRUE despite the insult being real. The true grievance is evaluated, not treated as an automatic exclusion.

## 24.7 Accountability alongside a legitimate boundary

The operator acknowledges the withholding, accepts the relevant obligation, and proposes correction while asking the counterpart to stop insults or threats. The grievance is addressed alongside the original responsibility rather than in its place.

This does not meet the full mechanism merely because the operator describes being harmed. Honest acknowledgment may make D FALSE, and the non-displacing account may make M FALSE. Evaluate the actual exchange rather than rewarding or penalizing a particular tone.

## 24.8 Substantiated defense against a false allegation

Records establish that someone else deleted a file and that the accusation against the operator is false. The operator denies deleting it and identifies harm caused by the accusation.

Depending on the particular language, the surface arrangement may resemble or satisfy the form; a relevant factual correction need not satisfy A. Either way, W/M are not supplied by the rhetorical shape. Where the underlying allegation is disproved and the defense accurate, do not assign supported accountability-deflecting DARVO for that allegation.

## 24.9 A protective response that fails

The evidence supports a full, materially misleading DARVO response organized to retain exclusive credit. The audience rejects it, restores the original issue, and requires correction.

The episode satisfies DARVO_SUPPORTED and S while its specified protection outcome is UNSUCCESSFUL. Proposition D4 proves that changing audience acceptance alone leaves the classification unchanged. If audiences respond differently, retain separate outcome observations.

## 24.10 Later deflection without evidence of earlier reliance

A supported DARVO response follows a harmful act. No evidence establishes the operator's prior expectation or what influenced the earlier choice. E/B remain UNKNOWN, not TRUE because the later response exists and not FALSE merely because advance evidence is missing.

## 24.11 Anticipation before any enacted response

Evidence establishes a DARVO-specific expectation and its influence on a contemplated decision, but no accountability response has occurred. Anticipated enabling reliance is supported. Enacted DARVO and its paired finding remain unestablished. Future events are not historical premises.

## 24.12 Cross-event join

An expectation concerns decision d1 and conduct x1. A separately supported DARVO response concerns conduct x2. Those two positive findings do not establish anticipation with enactment for a single event.

If the records are correctly bound and J is FALSE, retain the standalone findings and a negative pair finding. If the application asserts J TRUE while supplying conflicting canonical identities, withhold the paired output as an inconsistent annotation rather than pretending that the join is valid.

## 24.13 Dependency contradiction

A decision record contains E FALSE and B TRUE. This is not merely a negative conjunction: the assigned claims conflict about whether the relevant expectation existed. Withhold anticipation-dependent outputs for review. Preserve any independently valid episode findings.

Likewise, K TRUE with M UNKNOWN requires review of the attributed awareness and the specific discrepancy. Do not infer M from an unsupported stronger annotation or silently downgrade K.

## 24.14 Generic impunity is not DARVO-specific anticipation

A source records only “No one will discover this.” That may concern avoiding detection, but it does not by itself establish expected denial, attack, and victim–offender reversal. E remains unresolved unless the record supports the DARVO-specific proposition; do not force it positive or negative from that sentence alone.

## 24.15 Attack on a supporter, reversal against the principal counterpart

Records establish that operator O wrongfully removed B's agreed credit. Advocate C presents the agreement supporting B's correction request. O replies: “I owe B nothing. C is a dishonest opportunist; their complaint is worthless. B is conducting a campaign to destroy my career.” The agreement and exchange establish relevant answerability and the misleading substitution.

O is the operator; B remains `counterpart_id` and the represented offender. The A witness targets C, with a supported accountability link identifying C's advocacy and the use of that attack to dismiss B's correction claim. V represents O as harmed. All operations concern the credit issue, so Q and L are supported. Together with W and M, the unchanged conjunction establishes supported complete DARVO. C and B remain distinct people. If C's unrelated conduct is merely discussed without a supported disqualifying relation, it cannot supply this A witness.

## 24.16 L→Q and independent operation values

An annotation with `L=TRUE, Q=UNKNOWN` requires dependency review; with `L=TRUE, Q=FALSE` it is inconsistent. By contrast, `Q=L=TRUE, A=FALSE` is a valid structural negative when review establishes a linked accountability exchange without a qualifying attack. L identifies the candidate issue linkage; it does not fill A or the other operation flags. Standalone valid E/B findings remain evaluable while an episode's L/Q or attack-target record needs review.

---

# 25. Diagnostic questions and differential classification

These are reviewer questions, not advice to challenge an unsafe person.

**Event anchoring:** What conduct and responsibility are at issue, described without using the DARVO label?

**World/account discrepancy:** What does the response represent, and what evidence establishes a material error or invalid responsibility inference?

**Attack:** Where is a credibility, character, motive, or standing attack deployed to discount the counterpart or claim? Would it remain an attack if the audience rejected it?

**Reversal:** Where are both represented roles established? Is the alleged offense located in the original event, the challenge, another grievance, or a combination?

**Non-cancellation:** If the countergrievance is true, does the response still misleadingly erase or reassign the original responsibility? What relevant additional premise would be needed for that inference to be valid?

**Protective relation:** What specific position is at stake and what evidence connects the response to preserving it? Is the analysis merely repeating “accountability avoidance”?

**Knowledge and purpose:** Does the evidence establish awareness of the particular material discrepancy and purposeful obstruction, rather than mere access to facts or benefit?

**Temporal linkage:** Which expectation influenced which choice? Does the later response concern that conduct, and is the connection evidenced rather than assumed?

**Outcome:** What actually changed because of the response, for whom, and during what observation window?

| Neighboring pattern | Distinction from this strict model |
|---|---|
| **Simple denial** | Does not by itself supply attack and paired role reversal. |
| **Factual disagreement** | Requires evidence review; disagreement is not itself deception. |
| **Generic blame-shifting** | May lack an operator-as-harmed claim or a linked attack. |
| **Self-serving conduct** | Concerns a goal or act, not necessarily a DARVO response. |
| **Stonewalling or minimization** | Can obstruct accountability without every component. |
| **Genuine countergrievance** | Its truth neither proves DARVO nor automatically excludes it; evaluate its use. |
| **Accurate defense** | Surface resemblance cannot override supported accuracy and responsibility evidence. |
| **Failed deflection** | Failure does not exclude an otherwise supported mechanism. |
| **Generic anticipated impunity** | Does not establish expectation of the DARVO mechanism. |
| **PAST** | A DARVO-family temporal maneuver; its supported classification does not automatically supply every complete-response condition. |
| **FATE** | A DARVO-family causal and evidential maneuver; manufactured vindication need not portray the operator as the harmed party. |

This is a closed code for a complete configuration, not a rule that only complete configurations can be harmful or worth documenting.

---

# 26. Relationship to PAST, FATE, and the DARVO family

The [canonical DARVO family](DARVO_FAMILY_CANON.md) comprises **self-protective maneuvers that distort the representation of agency, contribution, or responsibility**:

> Denial, counterpart-directed blame or disqualification, and reversal of the represented responsibility structure preserve a claimed position through a distorted account. PAST, FATE, and the complete DARVO response are members of this family.

This hierarchy is Patterna's adopted organizing definition. The complete DARVO response retains its distinct behavioral meaning and attribution to Freyd. Not every family member contains its specific attack operation and paired victim–offender representation.

**PAST is a DARVO-family temporal maneuver.** A presently feasible remedy is represented as unavailable because of the counterpart's earlier conduct. The operator appears constrained while the counterpart appears responsible for the impasse. Its characteristic conversion is “I will not” into “we cannot because you did not.”[^P1][^P2]

**FATE is a DARVO-family causal and evidential maneuver.** The operator's material contribution is obscured while a realized forecast is reused to vindicate a misleading account assigning responsibility to the counterpart. The contributor appears vindicated; the harmed counterpart receives the blame. Forecast accuracy alone does not establish that account.

**The complete DARVO response** converts “I am being asked to answer for this conduct” into “I am the harmed party, and you are the wrongdoer.” “You must answer for challenging me” remains the challenge-as-offense configuration, not the only reversal.

## 26.1 The shared logical axis

| PAST | Complete DARVO response |
|---|---|
| Establish the actual present remedy. | Establish the particular conduct and responsibility. |
| Identify the represented closure. | Identify the represented denial and reversed responsibility account. |
| Test the discrepancy between feasibility and claimed impossibility. | Test the discrepancy or invalid inference in responsibility attribution. |
| Past fault does not automatically remove a present option. | Counterpart fault does not automatically remove operator responsibility. |
| Identify the preference, agency concealment, and outcome at stake. | Identify the specific protected position and responsibility substitution. |
| Add concealment/knowledge only with additional evidence. | Add knowing use and anticipated reliance only with their own evidence. |
| Preserve uncertainty and alternative constraints. | Preserve disputed facts, genuine defenses, and separate countergrievances. |

The counterpart may genuinely have acted late in PAST, just as the counterpart may have a genuine failing in a DARVO episode. The key question is the validity of the inference from that fact to closure or exoneration. A true premise does not validate every conclusion drawn from it.

## 26.2 Family membership and complete-response classification

**PAST and FATE are unequivocal members of the DARVO family.** This is a family classification, not a deduction that either maneuver supplies every predicate of the complete response. The same scoped incident may support PAST, FATE, the complete response, or overlapping classifications when each rule's evidence requirements are met.

```text
PAST and FATE are DARVO-family maneuvers.
Either can co-occur with a complete DARVO response.
Family membership does not automatically establish the complete response.
A complete response does not automatically establish PAST or FATE.
A shared protective logic does not make their observed structures identical.
```

PAST's treatment of practical agency suppression is not silently replaced by the DARVO rule about failed responses. The source constructs can define different episode effects. What is reused is their evidentiary discipline, not the assumption that every predicate or outcome condition must be identical.

---

# 27. Relationship to the later Sustained DARVO extension

This document closes the **base mechanism and its optional enabling interpretation**, not the longitudinal model.

Recurrence, adaptive continuity, narrative burial, conditioning, implicit threats arising through history, and a protected ego-defining original event are not requirements of the present classifier. Nor may they fill missing conditions in an individual episode.

The supplied Sustained DARVO note proposes an original-event-centered account of continuity through changing tactics. This revision uses that note only to preserve the boundary of the later extension; it does not adopt its proposed motive as a universal explanation.[^S1]

```text
Base account:
What operations occur, what responsibility they misrepresent,
what position they may protect, and whether expected protection
influenced a specified choice.

Sustained extension:
How linked episodes preserve a function over time,
how tactics adapt, and what evidence establishes that organization.
```

Anticipation concerns a directional relation between an expectation and a choice. Sustained organization concerns relations across episodes. They should not be conflated merely because expectations can sometimes be informed by earlier experiences.

---

# 28. Empirical grounding and limits of the present synthesis

**Revision scope:** Version 1.1 is an internal conceptual and implementation audit of the supplied files and the agreed discussion. It does not perform a fresh external literature review. The following source attributions are carried forward from Version 1.0 and must not be represented as newly verified findings.

**Behavioral core.** The Freyd definition cited in v1.0 supplies the acronym and accountability-response context.[^L1] The project interpretation, strict code, and enabling hypothesis are not attributed to that source as established definitions.

**Observer judgments.** Version 1.0 cites the 2020 vignette experiments for effects on credibility and responsibility judgments.[^L2] Those claims do not establish that every DARVO response succeeds, that all material consequences disappear, or that anticipated protection caused the original conduct.

**Associations and possible explanations.** Version 1.0 cites the 2024 study for associations of self-reported DARVO use with rape-myth acceptance and sexual-harassment perpetration, using recalled-confrontation responses. It describes perceived innocence and learned usefulness as proposed explanations, not demonstrated causal mechanisms.[^L3]

None of those inherited attributions validates this classifier, establishes self-protection as a universal motive, or demonstrates the causal enabling proposition. The present revision's tests evaluate the consistency of the declared coding rules and implementation, not clinical validity or the truth of any real-world allegation.

The PAST documents are project sources for architecture, terminology, and evidence discipline. The Sustained DARVO note is a separate conceptual proposal. Neither supplies independent empirical validation of the revised rules.

---

# 29. Research and validation program

Three kinds of correctness must remain separate:

**Internal conceptual consistency:** definitions, examples, predicates, and outputs do not contradict each other.

**Implementation correctness:** the program implements the declared rules, dependency policy, and scope restrictions.

**Empirical validity:** the categories can be reliably applied to relevant data and the proposed explanations survive appropriate testing.

This revision addresses the first two. It does not establish the third.

| Validation question | Proposed test |
|---|---|
| **Structural reliability** | Can reviewers agree on Q/D/A/V/O/L from the same sources? |
| **Responsibility discipline** | Can W/M be assessed without assuming guilt from the response? |
| **Countergrievance relevance** | Can reviewers distinguish accurate parallel grievances from misleading cancellation? |
| **Outcome independence** | Does the same response retain its structural classification when only the audience reaction changes? |
| **Protective-function specificity** | Can reviewers name an evidenced position and relation without a circular restatement? |
| **Awareness distinction** | Can K distinguish recognition of the specific discrepancy from mere access to facts? |
| **Enabling reliance** | Does evidence support both expectation before the choice and its contribution to the choice? |
| **Event linkage** | Can reviewers establish J without pooling unrelated episodes? |
| **Semantic integrity** | Are dependent or conflicting annotations correctly withheld rather than silently resolved? |

A validation corpus should include accurate defenses, true countergrievances, incomplete forms, accidental harm followed by deliberate deflection, failed responses, later deflection without evidence of prior reliance, and expectations concerning other decisions.

The self-protection interpretation gains no independent confirmation if it can be assigned merely by repeating the DARVO label. The enabling hypothesis gains no confirmation merely because a defense follows an act. Failure to distinguish those situations would weaken the respective operationalizations.

No invented numerical risk score, prevalence claim, or causal probability follows from successful code tests. Reliability, discriminant validity, and causal evidence require their own research designs.

---

# 30. Application and ethical safeguards

The application should expose the evidence chain rather than an accusation-shaped label. A useful output distinguishes response operations, responsibility evidence, the represented discrepancy, any protective relation, knowing use, prior reliance, linkage, outcomes, and unresolved alternatives.

**No circular proof of guilt.** “This is DARVO, therefore the allegation is true; the allegation is true, therefore the denial proves DARVO” is invalid. The opposite error—requiring an explicit confession before any inference—is also rejected.

**No diagnosis by acronym.** The proposed classifier establishes neither narcissistic personality disorder nor any other diagnosis. Selfishness and irrationality are not mandatory predicates.

**No perfect-victim requirement.** A genuine failing by the counterpart does not automatically negate a supported responsibility of the operator. Evaluate each conduct and the relevance of each claim.

**No presumed malignity from resistance.** Accurate disagreement, a request for representation, declining an unsafe exchange, or a legitimate boundary is not itself evidence of deflection.

**No required success.** Code the misleading configuration and actual effects separately. A failure to persuade does not retroactively make the account accurate.

**No inferred plan from hindsight.** Later use does not establish E or B. Shared identity does not establish J. A record of an earlier expectation must be evaluated for what it actually supports.

**No implicit dependency repair.** Contradictory annotations receive review status, not ordinary negative findings. Preserve unaffected results and explain which records need reconciliation.

**Evidence grounding.** A valid derivation establishes its conclusion from the reviewed premises. Reference presence or a named position alone supplies no missing fact; evidence review establishes the source content and the inference used.

**No automatic high-stakes determination.** This project code is not sufficient on its own for clinical, legal, employment, custody, or safeguarding decisions. Relevant evidence and qualified judgment remain necessary.

---

# 31. Publication-ready and application-ready formulations

## 31.1 Recommended combined definition

> **The complete DARVO response combines denial of wrongdoing or responsibility, an attack used to discount the counterpart or claim, and paired victim–offender reversal linked to the same accountability issue. A supported response misleadingly substitutes an account of the operator as harmed and the counterpart as offending for the operator's relevant answerability. The broader DARVO family includes PAST and FATE: self-protective maneuvers that distort represented agency, contribution, or responsibility. Self-protection names that representational function. A particular protected interest, knowledge, conscious intention, advance reliance, and observed success require their own evidence. Expected protection may influence a decision, including when the original conduct arose from a mistake rather than selfishness or whim.**

The first sentence retains the behavioral core attributed to Freyd in v1.0.[^L1] The family hierarchy follows the [canonical principles](DARVO_FAMILY_CANON.md); the remaining distinctions state this project's operational and explanatory interpretation.[^V1][^REV]

## 31.2 General central conversion

> **“I am being asked to answer for this conduct” becomes “I am the harmed party, and you are the wrongdoer.”**

## 31.3 Challenge-as-offense conversion

> **“I must answer for my conduct” becomes “You must answer for challenging me.”**

This remains an important configuration, not an exhaustive definition of all role reversal.

## 31.4 The non-cancellation principle

> **A true wrong by the counterpart does not, by itself, erase the operator's responsibility for different conduct. The validity of the responsibility inference must be assessed, not inferred from the presence of blame.**

## 31.5 Self-protective-function formulation

> **Self-protection is the family's representational function: preserving a claimed position through a distorted account. A case-specific protective interpretation additionally identifies the particular position and the evidence connecting it to the maneuver. Neither the family label nor a benefit that merely persists establishes that additional interpretation, knowledge, conscious intention, or successful protection.**

## 31.6 Knowing-use formulation

> **Where the operator's awareness of the relevant material misrepresentation and purposeful obstruction are supported, the episode qualifies as deliberate accountability avoidance. Knowing the underlying facts alone is not equivalent to recognizing the particular misrepresentation.**

## 31.7 Anticipated-protection formulation

> **Expected DARVO-specific protection may become an enabling consideration in a decision: the operator may proceed because they anticipate protection through denial, attack, and role reversal. That interpretation requires evidence of the expectation and its influence on the particular choice; linking it to later enactment additionally requires evidence connecting the decision and response.**

## 31.8 Consequence distinction

> **Deflecting responsibility does not undo the event. A misleading account may fail completely, or may change who is believed, who must answer, or who bears some costs.**

## 31.9 Plain-language version

> **Instead of accurately answering for the conduct at issue, the person denies responsibility, attacks the person raising it, and casts themselves as the one being wronged. The account may concern the original event, the complaint, or another grievance. We examine what that response is organized to protect, whether the person knowingly misrepresents responsibility, and whether they relied on that expected protection beforehand—without assuming the defense succeeded.**

None of these formulations requires a sustained pattern, a diagnosis, an ego-defining original event, or an explicit confession.

---

# 32. Quick-reference card

| Question | Required distinction |
|---|---|
| **What belongs to the DARVO family?** | PAST, FATE, and the complete DARVO response; each retains its own evidence requirements. |
| **Does family membership establish the complete response?** | No; the complete response requires its linked denial, attack, and paired represented roles. |
| **What is the base unit?** | A specified accountability episode, not the operator's entire personality. |
| **What supplies the form?** | Context, denial, attack, both represented roles, and substantive linkage. |
| **What supports the substantive finding?** | Relevant responsibility and material distortion, independently of the label. |
| **Must the challenge itself be the alleged offense?** | No; original-event inversion and misleading countergrievance substitution also fit. |
| **Does a true countergrievance exclude DARVO?** | No; assess its relevance and whether responsibility is misleadingly canceled. |
| **What does self-protection mean?** | The representational function of preserving a claimed position through a distorted account. |
| **What supports a case-specific protective finding?** | A particular position and its source-grounded relation to the response; knowledge, intention, and success are separate. |
| **What makes use knowing and deliberate?** | Awareness of the particular distortion plus purposeful obstruction. |
| **What supports anticipation?** | DARVO-specific expectation and contribution to a specified choice. |
| **What links anticipation and enactment?** | J: the correct operator, conduct, contemplated mechanism, and temporal relation. |
| **Is success required?** | No. Outcome assessment is separate and audience/target specific. |
| **What happens to inconsistent inputs?** | Affected findings are withheld for review; they are not disguised as ordinary negatives. |

For validated, scoped annotations of the **complete response** and its qualifications:

```text
FORM(e)       = Q ∧ D ∧ A ∧ V ∧ O ∧ L
SUPPORTED(e)  = FORM(e) ∧ W ∧ M
SELF-PROT.(e) = SUPPORTED(e) ∧ S
DELIBERATE(e) = SUPPORTED(e) ∧ K ∧ I
ANTICIPATED(d)= E ∧ B
ENACTED-AP(d,e)= ANTICIPATED(d) ∧ SUPPORTED(e) ∧ J(d,e)
```

Dependencies: B TRUE presupposes E TRUE; K TRUE presupposes M TRUE. Those requirements trigger review when annotations conflict or fail to support the prerequisite. Outcome does not enter the formulas.

> **Principle to retain:** The DARVO family, including PAST and FATE, preserves claimed positions through distorted representations of agency, contribution, or responsibility. The complete response uses a paired victim–offender representation. Evidence identifies a particular protected position and any knowledge, intention, prior reliance, or actual success.

---

# 33. Glossary

| Term | Meaning within this document |
|---|---|
| **DARVO family** | The canonical family of self-protective distortions of agency, contribution, or responsibility; PAST, FATE, and the complete response are members. |
| **Complete DARVO response** | The linked denial–attack–paired victim/offender configuration evaluated by the unchanged `DARVO_FORM` and `DARVO_SUPPORTED` rules, with answerability and material distortion required for the supported finding. |
| **PAST** | A DARVO-family temporal maneuver that suppresses present agency through false closure attributed to the counterpart's past conduct. |
| **FATE** | A DARVO-family causal and evidential maneuver that obscures the operator's contribution and reuses the realized forecast to vindicate misleading blame. |
| **Accountability-displacing representation** | An account structured to replace or misleadingly discount evaluation of the operator's responsibility; not evidence of actual audience displacement. |
| **Anticipated enabling reliance** | A supported contribution of expected DARVO-specific protection to willingness to proceed at a particular decision. |
| **Behavioral form** | Linked observable operations, separate from the accuracy of underlying allegations. |
| **Case-specific protective function** | An identified position and evidenced relation between its preservation and the response. |
| **Challenge-as-offense inversion** | The accountability challenge is represented as the relevant wrongdoing against the operator. |
| **Countergrievance substitution** | A grievance is used as a misleading replacement for evaluation of another responsibility; its truth alone does not settle the inference. |
| **Decision–episode link** | The evidenced identity, content, and temporal correspondence required to relate anticipation to enacted response. |
| **Defensive reconstruction** | The proposed preservation of a self-account through a changed responsibility narrative rather than accountable integration. |
| **Deliberate DARVO** | In this classifier, a supported complete response with awareness of the specified material discrepancy and purposeful obstruction. |
| **Dependency review** | A dependent condition is affirmed while its prerequisite or required record remains unresolved; affected results are withheld. |
| **Inconsistent annotation** | Assigned conditions or record bindings contradict each other under the stated definitions. |
| **Material distortion** | An evidenced misleading representation or invalid assignment of relevant responsibility, regardless of acceptance. |
| **Non-cancellation rule** | Another person's wrong does not automatically erase the operator's responsibility. |
| **Original-event inversion** | Victim–offender roles are reversed in the account of the original conduct. |
| **Preferred position** | A specified self-account, interest, outcome, or control position at stake. |
| **Protection outcome** | Assessed response effects for a stated target, audience, and time window. |
| **Responsibility substitution** | In the complete response, representing the operator as harmed and the counterpart as offending in place of accurate evaluation of the operator's responsibility. |
| **Self-protection** | The family's representational function of preserving a claimed position through a distorted account; specific interests, knowledge, conscious intention, and success are separately evidenced. |
| **Self-protective accountability avoidance** | Distortion, concealment, or reassignment of represented responsibility to preserve a claimed position; the label alone does not establish a particular motive or actual avoidance. |
| **Self-defeating decision pattern** | Conduct evaluated against supported goals it foreseeably undermines; optional, not a base DARVO condition. |
| **Supported interpretation** | A conclusion grounded in the stated record with provenance, uncertainty, and alternatives disclosed. |
| **Three-valued evidence logic** | TRUE, FALSE, and UNKNOWN evaluated only after applicable integrity checks. |
| **Withheld finding** | No logical value emitted because the relevant annotations need review; not a fourth truth value. |

---

# 34. Source register and references

References distinguish source-derived content from the project's operational revisions. External bibliographic details and the limited empirical descriptions below are retained from v1.0. **They were not newly verified for this revision.** The source file records consultation on 11 September 2026; that historical provenance should not be confused with fresh verification during the v1.1 audit.

[^L1]: **External definition, retained attribution.** Freyd, J. J. (n.d.). *DARVO*. Author's definition and research page. URL: `https://www.jjfreyd.com/darvo`. Version 1.0 uses this for the acronym, component definition, and accountability-response context. It records the originating publication as Freyd, J. J. (1997), “II. Violations of power, adaptive blindness and betrayal trauma theory,” *Feminism & Psychology*, 7(1), 22–32, DOI: `10.1177/0959353597071004`, and states that the original 1997 article was not separately reviewed for v1.0. The present revision makes no additional source-verification claim.

[^L2]: **Empirical context, retained attribution.** Harsey, S. J., & Freyd, J. J. (2020). Deny, attack, and reverse victim and offender (DARVO): What is the influence on perceived perpetrator and victim credibility? *Journal of Aggression, Maltreatment & Trauma*, 29(8), 897–916. DOI: `10.1080/10926771.2020.1774695`. Author-hosted article listed in v1.0: `https://dynamic.uoregon.edu/jjf/articles/hf2020.pdf`. The inherited claim concerns observer judgments in vignettes, not universal success or anticipatory causation.

[^L3]: **Empirical context, retained attribution.** Harsey, S. J., Adams-Clark, A. A., & Freyd, J. J. (2024). Associations between defensive victim-blaming responses (DARVO), rape myth acceptance, and sexual harassment. *PLOS ONE*, 19(12), e0313642. DOI: `10.1371/journal.pone.0313642`. Article listed in v1.0: `https://journals.plos.org/plosone/article?id=10.1371/journal.pone.0313642`. Version 1.0 attributes recalled-confrontation associations and tentative discussions of perceived innocence and learned utility to this source; it does not treat the source as proof of the proposed enabling mechanism.

[^P1]: **Project source.** *The PAST Maneuver: Fabricated Temporal Impossibility, Retrospective Blame, and the Suppression of Present Agency*. Version 1.0, 5 August 2026. Supplied file: `PAST_Maneuver_Conceptual_Framework(1).md`. Relevant sections: 5–7 (acronym and classifier), 9–10 (DARVO relationship and concealment), 12 (evidence), and 17 (safeguards). Used as a conceptual and methodological precedent, not independent validation.

[^P2]: **Project source.** *The PAST Maneuver: Fabricated Temporal Impossibility, Retrospective Blame, Self-Protective Agency Concealment, and Outcome Capture*. Version 2.0, 6 August 2026. Supplied file: `PAST_Maneuver_Extended_Logical_Framework_v2(1).md`. Relevant sections: 4–5 (architecture and protective function), 7–12 (feasibility, agency, cost export, intention), 15–17 (classifier), 21 and 23 (concealment and intent evidence), 24 (DARVO relationship), and 32–35 (evidence and safeguards). The current document adapts its discipline without rewriting PAST's own predicates.

[^S1]: **Boundary source.** *Sustained DARVO, Ego Protection and the Protected Original Event*. Supplied file: `Sustained_DARVO_Ego_Protection_and_Original_Event.md`. Relevant sections: 1–2, 7, and 12–13. Its proposed protected-event explanation, adaptive continuity, and narrative-burial account remain reserved for the sustained extension.

[^V1]: **Historical revision source.** *DARVO as a Mechanism of Accountability Deflection: Self-Protection, Responsibility Reversal, and Anticipated Protection as a Possible Enabling Function*. Version 1.0, 11 September 2026. The v1.1 source names `DARVO_Accountability_Deflection_Self_Protection_Logical_Framework_v1.md` and attributes its 34-section structure, behavioral core, governing formulation, interpretive limits, and literature references to that file. Its statement that the original was preserved is a historical assertion. A standalone v1.0 file was not located in the supplied Patterna project; this revision does not reconstruct it or claim local availability.

[^DISC]: **Agreed project synthesis.** The discussion culminating in v1.0: accountability deflection as the mechanism; self-protection as the interpretation; anticipated protection as a possible enabling function; separate support for knowledge, purpose, and prior reliance; irrationality and selfishness not required for the base code; material consequences separate from accountability allocation; Sustained DARVO deferred.

[^REV]: **Authorized logical revision.** The subsequent audit and request to correct v1.0. Revisions broaden responsibility substitution, separate function from success, add the non-cancellation rule, clarify awareness, validate dependencies, bind anticipation to enactment, and prevent circular protective-function inference. These are explicit project corrections and tests, not new empirical findings attributed to the external literature.

---

# Appendix A — Revision map and traceability

The table below records the historical v1.1 changes. Formal v1.2 additionally introduces operation-specific attack targets, L→Q validation, propositions D1–D4, the supporter-target worked example, and explicit historical verification availability. Conjunctions and finding keys remain unchanged; records lacking the new required target evidence or dependency review must be reassessed before receiving a v1.2 result.

| Audit issue | Correction in v1.1 | Where it is enforced |
|---|---|---|
| Central mechanism was narrower than the role-reversal definition. | General responsibility substitution now includes original-event inversion, challenge-as-offense, and misleading use of another grievance. | Executive definition; Sections 6, 9, 24, 26, 31, and 32. |
| Function and outcome could be conflated. | A/M/S and the process model no longer require audience acceptance or successful preservation. | Sections 8, 10–13, 20, and outcome-invariance tests. |
| A true countergrievance looked like an automatic exclusion. | Added a non-cancellation rule and relevant counterexamples. | Sections 6, 20, 24–26, 30–32. |
| Knowledge of facts was weaker than awareness of the misrepresentation. | K now concerns awareness of the particular discrepancy assessed by M. | Sections 14–15 and the formal definition. |
| Arithmetic could hide contradictory annotations. | Added dependency review and inconsistency statuses before affected conjunctions are evaluated. | Sections 19–22; E/B and K/M tests. |
| Anticipation and later DARVO lacked an enforceable join. | Added decision/episode scoping and J, with named records and canonical identity checks. | Sections 3, 16–17, 20–24. |
| Self-protection could be circularly confirmed. | S requires a concrete position and source-grounded relationship, not generic restatement. | Sections 11, 20, 23–25, and named-position checks. |
| “Separate axes” could imply logical independence. | Reframed as distinct questions with explicit dependencies. | Sections 1, 16, 19–21. |
| The same X could refer to action and desired result. | Conduct x and desired outcome y are distinguished; episode e and decision d are scoped. | Sections 5, 12, 17, and 20. |
| The source-check status could be overstated. | Retained external attributions are clearly separated from this revision's internal audit. | Front matter; Sections 28 and 34. |

### Preserved conclusions

The governing formulation, self-protective interpretation, possible enabling role of expected protection, absence of a required diagnosis or irrationality, distinction between material harm and accountability allocation, and separation from Sustained DARVO remain intact.

The source PAST framework is not rewritten by this revision. Its role is a methodological and conceptual precedent, not a guarantee that every DARVO predicate must equal a PAST predicate.

### Migration notes

Version 1.0's `self_protection_supported` output becomes `self_protective_function_supported` to make the function/outcome distinction explicit. The deliberate flag now uses awareness of the specified misrepresentation, not only knowledge of relevant facts. The enactment output adds J and record binding. A v1.0 positive must therefore be re-reviewed where one of those changes affects its premises; it should not be mechanically grandfathered into v1.1.

Inputs also change from bare truth flags to scoped, source-referenced assessments. Review status is separate from logical truth. A consumer expecting only booleans must not treat a withheld `None` result as FALSE.

The original source was left unchanged. Its SHA-256 at revision is:

```text
59f951d418fd87c886ec1c55a1be3e37b78d2cfa11507c4e1f8068ed40fb5459
```

---

# Appendix B — Executed validation and reproducibility

### Historical v1.1 verification record

The following results are retained historical claims for v1.1. They are not attributed to the modified v1.2 reference implementation. The original companion bundle was not located in the supplied project; the separately recorded source review reproduced the named state-space slices with its own harness.

The original v1.1 record reports execution of its reference implementation and tests as follows. These checks concerned that version's declared rules, not a diagnosis or ground-truth abuse dataset.

| Check group | Executed coverage | Result |
|---|---:|---|
| Base formula assignments | 6,561 combinations of Q/D/A/V/O/L/W/M | Passed. |
| Qualification assignments | 729 combinations of S/K/I/E/B/J with an affirmative base | Passed. |
| E/B dependency cases within that qualification group | 162 combinations correctly withheld for inconsistency or prerequisite review | Passed. |
| Awareness-dependency assignments | 243 combinations of M/K/I/S/W | Passed. |
| Outcome invariance | All 4 outcome states with unchanged evidence predicates | Passed. |
| Test methods overall | 20 test methods, including the state-space loops and targeted cases | 0 failures; 0 errors. |

The state-space loops use a separate complete-assignment interpretation of conjunction as the arithmetic oracle. The tested slices are exhaustive over the variables listed, **not over every possible annotation or real-world narrative**. Dependency-review behavior is tested separately from ordinary conjunction.

Targeted checks cover unknown versus negative findings, surface form without supported wrongdoing, missing role components, no inferred intent from later use, anticipation without an episode, missing and mismatched links, locality of withheld outputs, no automatic countergrievance exclusion, a named-position requirement, incorrect types, unsourced positive/negative inputs, and separation of knowledge from purpose.

### What passing tests does not establish

The tests do not verify evidence-reference content, inter-rater reliability, universal motives, the causal effect of anticipated protection, completeness of the literature, or any person's guilt. A TRUE assessment with an invented source can still pass structural validation. Proper source review must precede use of the engine.

The countergrievance test checks that the reviewed M assessment is not overridden by a blanket exclusion; it does not teach the program to determine the truth or relevance of a grievance from text. The S check requires a named position, but cannot decide whether the stated relationship is substantively noncircular. J checks do not infer chronology or a mental state from identifiers.

### Historical verification-bundle availability

The original source identified `DARVO_v1_1_Logic_Verification.zip` with these contents. Neither that ZIP nor its original test suite/report was located in the supplied project during the source review. The Section 22 reference in this historical listing refers to the former v1.1 block:

```text
darvo_logic_v1_1.py           # Exact code embedded in Section 22.
test_darvo_logic_v1_1.py      # Executed unittest suite.
validation_report.json      # Machine-readable results of the executed suite.
README.md                   # Scope, execution command, and limits.
```

The historical command, usable if the authentic bundle is restored, was:

```bash
python test_darvo_logic_v1_1.py
```

The module uses only the Python standard library and requires Python 3.9 or later. This is a compatibility requirement from the syntax used, not an external package recommendation.

For v1.2, extract the Python block between the unchanged `# 22. Reference implementation` and `# 23. Evidence recording and annotation schema` headings. The existing `DARVO_SOURCE_REVIEW_VALIDATION.py` belongs to the earlier review and its v1.1 fixture assumptions; it is not silently repurposed as a v1.2 validation claim. The current correction record and source-level validation are appended to [DARVO_SOURCE_REVIEW.md](DARVO_SOURCE_REVIEW.md).

### Current v1.2 source-level validation — 12 September 2026

The extracted reference block passed 6,561 base assignments, 729 qualification assignments, 243 awareness assignments, and 27 target/scope regressions. The new L→Q rule withheld 1,458 base assignments; the existing B→E and K→M rules withheld 162 qualification and 54 awareness assignments respectively. These are subsets of the named exhaustive groups. Independent Boolean-completion results supplied the conjunction oracle; dependency behavior was checked separately. Target regressions covered principal/supporter targets, missing or unresolved witnesses, wrong bindings, duplicate records, independent findings, unchanged operation flags, and audience-outcome invariance. The utility and choice illustrations also passed exact-rational checks.

The temporary correction harness and final source/code hashes are recorded in the appended review. These checks execute the source reference and explicit mathematical cases; they make no application-test or real-conversation accuracy claim.

---

## End note

The framework specifies the complete DARVO response within a family that also includes PAST and FATE. Its contribution is the disciplined connection between the response, the responsibility it misrepresents, and a particular protected position where evidenced. Knowing use and prior reliance have their own evidence requirements and dependencies. Actual protection is an outcome to observe, not a condition to assume.

> **The DARVO family distorts represented agency, contribution, or responsibility in a self-protective function. PAST and FATE are members; the complete response retains its distinct rule. Evidence identifies a particular protected position and any knowledge, intention, or anticipated reliance. None follows merely from a family label, and success is assessed separately.**
