---
title: "The FATE Maneuver"
subtitle: "Forecast Actualization, Blame Transfer, and Manufactured Vindication"
version: "1.1 — Logical and Scope Revision"
date: "2026-09-12"
status: "Patterna mechanism definition and reviewed logical framework; empirical performance is assessed separately"
scope: "The original prediction–agency–harm–blame–vindication proposal; recurrence and history-grounded implicit-threat interpretation are separately scoped extensions"
source_basis: "The preceding project discussion, PAST v2.0, DARVO v1.1, and the supplied Sustained DARVO note"
external_verification: "No new external literature review; project sources supply architecture, not empirical validation of FATE"
---

# The FATE Maneuver

## Forecast actualization, blame transfer, and manufactured vindication

**Canon alignment v1.0 — 12 September 2026; historical record.** The [DARVO Family — Canonical Principles](DARVO_FAMILY_CANON.md) governs family terminology. That alignment established the explicit evidential-reuse narrowing while retaining the then-current formal version 1.0. Its original review and source checksum are preserved in [FATE_SOURCE_REVIEW.md](FATE_SOURCE_REVIEW.md).

**Formal version 1.1 — 12 September 2026.** This revision carries the refined E/J_account meaning into dependency validation, distinguishes valid negative findings from unreconciled annotations, and binds recurrence and threat findings to named actors, evidence records, and historical cutoffs. The base conjunction and predicate keys remain stable; their corrected semantics are versioned here. The filename retains `v1_0` for link compatibility. This source revision does not modify the application runtime.

> **Central proposition:** The operator contributes to producing the outcome they predicted, then uses that outcome to validate an account that blames the counterpart while obscuring the operator's contribution.

> **Central conversion:** “I helped bring this about” becomes “This happened because of you, and its occurrence proves I was right.”

> **Recurrence-based extension:** When relevant prior episodes are known to the recipient, a later forecast may communicate threatened intervention rather than merely an expectation about the future.

**FATE is a DARVO-family causal and evidential maneuver.** Its name specifies the original forecast–contribution–blame–vindication proposal; it does not rename the complete DARVO response, PAST, or Sustained DARVO. The source note on Sustained DARVO concerns adaptive continuity and protection of an original event; FATE concerns the forecaster's material contribution and the subsequent use of the result to vindicate a misleading account of responsibility.[^sustained]

## 1. Status and architecture

The four letters identify an episode structure. The framework classifies conduct and represented responsibility; particular psychological states and population frequencies are separate findings.

The architecture follows PAST and DARVO v1.2: establish the relevant facts; identify the represented account; assess its discrepancy from those facts; identify a particular protected interest where evidenced; and assess knowledge, purpose, recurrence, and outcomes separately.[^past][^darvo] Self-protection names FATE's representational function within the DARVO family: preserving a claimed position through an account that obscures contribution and manufactures vindication. Family membership does not establish a particular interest, knowledge, conscious intention, or actual success.

Definitions specify the mechanism; propositions establish what follows from stated premises; case findings establish those premises from a scoped record. An established mechanism is reported directly. Uncertainty belongs to the particular unresolved premise, extension, or outcome.

The framework separates five objects:

| Object | Question |
|---|---|
| Episode | Did the forecast–contribution–blame–vindication structure occur? |
| Causal mechanism | Did the forecaster materially contribute to the relevant outcome? |
| Attribution mechanism | Was that contribution obscured or unjustifiably discounted when responsibility was assigned? |
| Pattern | Are there distinct, supported episodes linked by operator and mechanism? |
| Later communication | Does a new statement have a supported implicit-threat interpretation in light of a recipient's knowledge of that history? |

These questions must not answer one another by assumption.

## 2. Formal definition

> **FATE is a DARVO-family maneuver in which an operator forecasts an adverse outcome for a counterpart, materially contributes through their own conduct to its realization, and uses the realized forecast to vindicate a misleading responsibility account that blames the counterpart while obscuring or unjustifiably discounting the operator's contribution.**

The characteristic difference from an ordinary accurate forecast is the linked combination of **contributory agency, misleading blame transfer, and evidential reuse in support of that blame account**. A true statement that the forecast was accurate does not supply the required reuse merely because misleading blame appears elsewhere in the episode.

The outcome must be sufficiently specified for the forecast, conduct, harm, and subsequent account to be linked. “Something bad happened eventually” is not a sufficient match.

## 3. The acronym

| Letter | Operation | Required meaning |
|---|---|---|
| **F — Forecast** | Forecast an adverse outcome. | A communicated proposition concerns identifiable future harm to the counterpart. |
| **A — Actualize** | Act in ways materially contributing to its realization. | Identified operator conduct contributes to the matching outcome; mere opportunity, capacity, or temporal sequence is insufficient. |
| **T — Transfer** | Transfer responsibility to the counterpart. | The account misleadingly blames the counterpart while removing or unjustifiably discounting the operator's material contribution. |
| **E — Exploit** | Exploit the realized forecast as vindication. | The result is invoked as evidence for the misleading responsibility account that blames the counterpart while obscuring or unjustifiably discounting the operator's contribution. |

“Actualize” is causal shorthand, not an automatic finding of intention to cause harm. “Exploit” describes the result's use in the account, not an automatic finding that its misleading character was consciously recognized. Those stronger findings require evidence under Section 13.

The name evokes an adverse future presented as fate although the forecaster helped shape it. It is a mnemonic, not a claim that every statement about fate is abusive.

## 4. Roles, outcome identity, and scope

The **operator** is the forecaster whose conduct and later account are analyzed. The **counterpart** is the person about whom the outcome is forecast and to whom responsibility is misleadingly assigned. An **audience** is any recipient of the forecast or later account.

An episode record must identify the operator, counterpart, forecast, conduct, outcome, attribution, evidential reuse, and relevant times. Forecast and later attribution can address different audiences when the linkage is supported. The counterpart need not have heard the original forecast for the base episode to be analyzed; awareness becomes relevant to the later threat interpretation.

The **outcome** is a specified event, continuation, escalation, or degree of harm. A partial realization can count only when the matching portion is documented without inflating it into the full prediction. An existing problem does not become a future prediction by relabeling its past occurrence; a forecast of its further deterioration needs its own outcome specification.

## 5. Chronology: preserve what is necessary, not a rigid script

The conceptual pathway is:

```text
Adverse forecast
    + operator contribution to the matching harm
    + realization of that harm
    -> misleading responsibility attribution
    + use of the result as vindication
```

This is not a requirement that every intervention begin after the forecast. The operator may already have acted, be acting, or act later, provided their conduct materially contributes to the future outcome specified by the forecast.

For example, an operator may initiate interference, then forecast a consequence, then invoke that consequence after it occurs. Excluding this sequence would exclude part of the original proposal.

The mandatory temporal relation is that the forecast precedes realization of the specified future outcome. The claim of vindication must use a realized result. Blame may be introduced in the original forecast and maintained in the later account; a new explicit blame sentence is not required if contextual endorsement is supported.

T and E may occur in one utterance. Neither requires the operator to admit causation. The model does not require an eventual confession, a literal “See?”, or an explicit statement of victimhood.

## 6. The causal axis

Separate four propositions:

```text
F: The operator forecast H.
A: The operator performed conduct a.
H: The specified adverse outcome occurred.
C: Conduct a materially contributed to that H.
```

F, A, and H do not by themselves establish C. An outcome occurring after an action is not the same as an outcome occurring because of that action. Capacity to influence events is not proof that the operator exercised that capacity in this case.

Support for C may include directly observed intervention, communications connecting the conduct to the result, a contemporaneous recipient account, a traceable sequence of decisions, or a well-supported causal explanation. Source quality, competing explanations, and the scope of the inference must be recorded. A report may be relevant evidence without being either worthless or automatically corroborated.

Material contribution need not be sole causation. Other causes, including genuine counterpart conduct, can coexist. Equally, a mere possibility that an act could increase risk is not enough to claim that it contributed to a particular realized outcome.

A counterfactual question can help: would the outcome's occurrence, timing, severity, or form plausibly have differed without the identified conduct? It is a reasoning aid, not an exclusive test; the framework does not require the operator to be the sole or indispensable cause.

An omission counts only when a specific responsibility, undertaking, or relevant control relationship supports attributing causal and responsibility significance to that omission. Mere failure to prevent every possible harm is not sufficient.

## 7. The attribution axis: contribution becomes blame directed outward

The represented account differs from the supported causal account:

```text
Supported account:
Operator conduct materially contributes to H.
Other contributing factors may also exist.

FATE account:
H is presented as a consequence of the counterpart's defect,
choice, or failure, while the operator's contribution is
removed or unjustifiably discounted.
```

T requires a **materially misleading attribution**, not merely a reference to something the counterpart actually did.

A counterpart can make a genuine mistake without thereby becoming responsible for the operator's interference. Conversely, operator involvement does not automatically make an attribution unfair: an openly acknowledged boundary or a justified decision must be evaluated on its actual facts.

Two non-entailments are central:

> **“The counterpart contributed to the situation” does not, by itself, entail “the operator did not contribute to the harm.”**

> **“The counterpart acted wrongly” does not, by itself, justify assigning them responsibility for every subsequent action of the operator.**

These preserve the same distinction made in PAST and DARVO v1.2 between a potentially true criticism and an invalid conclusion drawn from it.[^past][^darvo]

## 8. The evidential axis: forecast accuracy is not causal vindication

The outcome may genuinely match the forecast. The framework must not deny that fact simply because the forecaster contributed to it.

The unsupported move is from a realized forecast to vindication of its accompanying causal or moral account:

```text
I forecast H.
H occurred.
Therefore, my explanation blaming you for H is correct.
```

The conclusion does not follow without further premises. A matching outcome does not, by itself, establish why it occurred, who bears responsibility, or whether the forecaster was merely an independent observer.

> **A forecast can be accurate while its accompanying blame is misleading.**

“Manufactured vindication” names the representational mechanism: the operator-contributed result is presented as evidence vindicating an account that suppresses the operator's contribution. The outcome is realized; conscious planning and persuasive success remain separate questions.

The statement “I told you this would happen” can perform E **when its context establishes that the realized forecast is being used to endorse the misleading responsibility account**. A reminder of prediction accuracy alone does not perform that operation. Context must connect the claimed vindication to the blame account; the remaining conditions also require their own evidence.

### Proposition F1 — Forecast accuracy does not identify causal contribution

Let `a` be a binary operator-conduct variable, `u` a binary background input, and `y` the matching outcome. Consider two deterministic causal models:

\[
\mathcal M_1:\ y:=a,\qquad \mathcal M_2:\ y:=u.
\]

In both models the actual inputs are `a=u=1`, the operator communicated the same forecast of `y=1` before realization, and `y=1` occurs. The observations therefore agree. Under the intervention `do(a=0)` with `u=1`, however, the outcome is 0 in the first model and 1 in the second.

**Proof.** Substitution gives `y=0` in the first equation and `y=1` in the second. Thus identical forecast, conduct, and outcome observations admit different causal roles for the conduct. Those observations alone establish neither contribution nor its absence. A responsibility account additionally needs its applicable causal and normative premises. This is a countermodel proof of non-entailment; case evidence establishes which premises hold in an actual episode.

Merton's self-fulfilling-prophecy analysis is a scholarly antecedent for both behavior producing predicted conditions and the reuse of those conditions as apparent vindication. FATE organizes these operations into explicit contribution, blame, and evidence-link requirements; it does not require the forecast itself to cause the intervention.[^merton]

## 9. Agency, accountability, and the protected position

FATE's self-protective representational function preserves the operator's claimed correct judgment or other claimed position by obscuring contribution and presenting the result as vindication. A case-specific interpretation can identify the following relation when the evidence supports it:

```text
The operator retains a preferred outcome or account of themselves.
The operator's contribution to the harm is removed from view.
The counterpart receives the adverse outcome and the blame.
The result is then used to validate the operator's earlier judgment.
```

Possible protected positions include exclusion the operator wishes to preserve, authority as the supposedly perceptive adviser, an account of the counterpart as defective, or avoidance of a specific acknowledgment or correction.

These particular interests are case-specific findings. Identify a concrete protected position and evidence connecting the response to preserving it. The family's self-protective function alone does not establish that interest, awareness of distortion, conscious intention, or actual success. The original conduct can begin with a genuine mistake; selfishness or whim is not a prerequisite. This retains the distinction between representational function and additional findings in the canon and DARVO v1.2.[^darvo]

The operator can make the misleading account without convincing the counterpart or another audience. The base episode requires realization of the matching harm because the harm is reused as evidence; it does **not** require successful persuasion, successful blame transfer, submission, or lasting control.

Thus, **material realization and persuasive success are different outcome variables**. This is a deliberate difference from treating every outcome as an optional endpoint.

## 10. The closed episode classifier

All predicates are scoped to the same reviewed episode e and have values TRUE, FALSE, or UNKNOWN.

| Predicate | Required finding |
|---|---|
| `F(e)` | The operator communicated an identifiable adverse forecast. |
| `A(e)` | Specific operator conduct relevant to the proposed causal account is supported. |
| `H(e)` | The specified matching outcome was realized by the observation cutoff. |
| `C(e)` | The conduct materially contributed to that realized outcome. |
| `T(e)` | The account misleadingly transfers responsibility to the counterpart by omitting or unjustifiably discounting the operator's contribution. |
| `E(e)` | The realized result is invoked as apparent confirmation of an earlier forecast or associated judgment in support of the misleading responsibility account assessed under T. A positive E commits to the realized outcome H and the established misleading account T. |
| `J_core(e)` | Operator, counterpart, forecast, conduct, and outcome are linked to the same episode, including forecast-before-realization timing. |
| `J_account(e)` | A supported evidential-use record E vindicates the exact supported responsibility-account record T identified in this episode, with the same forecast/judgment and realized outcome references. The relation is inferential endorsement, not co-occurrence. |

```text
FATE(e) := F(e) AND A(e) AND H(e) AND C(e) AND J_core(e)
           AND T(e) AND E(e) AND J_account(e)
```

This definition determines the classification once its scoped premises are established. Evidence assessment supplies those premises; dependency and record validation precede aggregation.

The more general forecast–agency–outcome sequence is:

```text
FAO(e) := F(e) AND A(e) AND H(e) AND C(e) AND J_core(e)

FATE(e) := FAO(e) AND T(e) AND E(e) AND J_account(e)
```

The core link can be assessed without a later blame or vindication account; the additional account link must be established for full FATE. FAO is a descriptive intermediate record, not an additional abuse diagnosis. It does not establish misleading blame or evidential reuse. FATE therefore implies this precursor under the definitions, but the precursor does not imply FATE.

### Proposition F2 — Precursor implication and persuasion invariance

For valid scoped assessments, supported FATE entails supported FAO. Holding all required assessments fixed, a change in audience acceptance leaves both classifications unchanged.

**Proof.** Every FAO conjunct occurs in the FATE definition. Conjunction elimination therefore establishes FAO from FATE. Audience acceptance occurs in neither conjunction, so changing that variable changes neither result. Rejection of an otherwise established FATE account does not negate the mechanism.

A clean conjunction returns FALSE if a required condition is established as absent, UNKNOWN if no condition is false and at least one remains unresolved, and TRUE only when all are supported. Missing evidence is not automatically a negative finding. Contradictory annotations require review before the affected output is published.

## 11. Dependencies and incomplete episodes

The refined predicates make explicit commitments:

\[
C\Rightarrow A\land H,\qquad T\Rightarrow C,\qquad
E\Rightarrow H\land T,\qquad J_{\mathrm{account}}\Rightarrow T\land E.
\]

These implications constrain admissible assessments; they do not authorize filling a prerequisite from an unsupported stronger annotation. A positive child with a FALSE prerequisite is an inconsistent annotation; with an UNKNOWN prerequisite it requires dependency review. Reconcile the source evidence and record any justified deduction before evaluating the affected conjunction. A positive J_account also requires exact references to the concrete T and E records, matching episode, actors, forecast/judgment, and outcome, with evidence explaining the endorsement relation. Wrong references are an invalid annotation, not a negative finding about a correctly scoped relation. If candidate statements concern different responsibility claims, assess the absence or uncertainty of E/J_account for the specified T. A positive E already claiming endorsement of that exact T conflicts with a record link denying the endorsement and requires review. J_account makes the evidence link explicit; its separate slot is not a claim of logical independence from E and T.

F separately establishes the communicated forecast. E evaluates the later use of the result as apparent confirmation; its wording cannot supply a missing earlier communication record. J_core binds candidate forecast, conduct, and outcome records without establishing their causal contribution C. A fabricated outcome cannot supply the realized H required for this completed mechanism.

Review is local to the affected conclusions. An account-only problem in T, E, or J_account does not by itself erase a valid FAO assessment. If the problem disputes C, A, H, or the core scope, review FAO as well. The reporting state **withheld for dependency/record review** is separate from TRUE, FALSE, and UNKNOWN.

If interference occurred but the forecast harm has not materialized, record **forecast with alleged or supported intervention; completed FATE not established**. If the event has not yet occurred at the cutoff, that is not a prediction that it will never occur.

If evidential reuse is FALSE after review, the completed-FATE conjunction is FALSE even when another independent premise remains UNKNOWN. If no required condition is FALSE and at least one remains UNKNOWN, the conjunction is UNKNOWN. A phrase suggesting vindication with unresolved contribution remains recorded evidence; it does not justify setting refined E to TRUE. An asserted `E=TRUE, C=UNKNOWN` requires dependency review through T and C, not automatic unresolved classification.

**Admissible negative example:** `F=A=H=J_core=TRUE`, `C=T=J_account=UNKNOWN`, and `E=FALSE`. The reviewed account establishes no use of the realized result to vindicate a responsibility account. FATE is FALSE; contribution remains unresolved. **Admissible unresolved example:** the same core assignments with `C=T=E=J_account=UNKNOWN` yield UNKNOWN. **Inadmissible example:** `E=TRUE, C=UNKNOWN, T=FALSE` requires review under the refined meaning. That tuple was admissible under the earlier broad E reading and remains only a historical counterexample in the original source review.

“No completed FATE” is not a finding that conduct is safe, fair, or non-threatening. An explicit threat or attempted sabotage can be serious without meeting this narrower outcome-based definition.

## 12. Explicit versus implicit operations

Evidence for an operation can be contextual rather than a literal use of a keyword. For example:

```text
Forecast: “They will leave you because you are impossible.”
Later, after the relevant interference and outcome: “Exactly as I said.”
```

The later statement may endorse the earlier blame account without repeating it word for word. The record must establish that the realized forecast is being presented as evidence for that account. If “Exactly as I said” refers only to the fact that the prediction matched, the E condition is not established. Tone or a reader's expectation is not enough by itself.

Likewise, concealment of the operator's role can be supported by the account's material omissions or misleading assignment of responsibility. An explicit “I did not cause this” is not mandatory.

The absence of a confession is neither a required element nor a disproof of the maneuver. It does not independently establish concealment either. The conduct, its contribution, and the misleading account remain evidentiary questions.

## 13. Knowledge and intention: separate findings

The original proposal includes deliberately engineered harm. That stronger account should remain available where supported, without being inferred from chronology alone.

Record separately:

| Finding | Required distinction |
|---|---|
| **Harm-production intention** | Evidence that the operator intended the relevant contribution to the adverse outcome, rather than merely acting with some other intention. |
| **Awareness of attributional distortion** | Evidence that the operator recognized the particular misrepresentation of their contribution or the counterpart's responsibility. |
| **Purposeful misleading attribution** | Evidence that the attribution and evidential reuse were deliberately used to mislead, blame, or obstruct accountability. |
| **Prior integrated plan** | Evidence linking the forecast, intervention, and later blame strategy as a plan before realization, not merely a reconstruction after the fact. |

An intended action is not automatically an intended harmful consequence. Deliberate later blame does not automatically establish deliberate original harm. Deliberate original harm does not automatically establish that every later statement was knowingly misleading.

A strongly supported deliberate account can be described plainly: **the operator knowingly helped produce the predicted harm and deliberately used it to blame the counterpart while concealing their contribution**. An explicit admission is not required if the contextual evidence supports these findings.[^darvo]

## 14. FATE-R: recurrence of supported episodes

FATE-R describes a **pattern record**, not a stronger truth value assigned to an ambiguous sentence.

Let `h` be a declared bounded history and `w` a named witness subset of episode records in that history. Every witness has an immutable assessment reference and an underlying-incident identity. Define the witnessed recurrence finding:

```text
FATE-R(h; w) := w is a subset of h with at least two distinct incidents
                AND every episode in w is supported FATE
                AND supported common-operator/mechanism linkage within w.
```

**Proposition F3 — Established recurrence.** A supported witness `w` establishes recurrence of FATE in `h`. **Proof.** Its members include at least two distinct instances satisfying the same defined mechanism and the common-operator/mechanism linkage. That is the stated recurrence criterion. Report “FATE recurred in at least two distinct incidents”; do not weaken the established recurrence to a possible pattern.

Two excerpts of the same event count once. Unresolved incidents or uncertain distinctness cannot be counted as supported witnesses. A separately established distinct subset can establish recurrence despite additional unresolved candidates. An exact total requires a complete assessed history and resolved incident equivalence; a positive witness establishes a lower bound. The bookkeeping minimum supplies no automatic severity, intention, conditioning, or threat conclusion.

A negative candidate-witness finding concerns that named set. A negative history-wide finding requires evidence that the declared history is complete for the assessed scope and no qualifying witness exists. Failure to retrieve two incidents from an incomplete history is not proof of absence.

Recipients and domains may differ, but any claimed continuity must be explained rather than inferred solely from the same operator's presence. A later recipient can know relevant episodes involving others; the history need not consist only of harm personally suffered by that recipient.

Recurrence can inform analysis, but does not repair a missing causal or attributional element in each counted episode. Conversely, repeated interventions can be relevant to other patterns even if they lack the full FATE structure.

## 15. The threat layer: history changes the interpretation of a new forecast

The original proposal's second contribution is that the prior behavior can supply the agency omitted from a later sentence.

A statement reads:

> “You are going to lose that opportunity.”

When the history and present context establish threatened intervention, its contextual meaning is:

> “I may bring about the loss of that opportunity, and the history gives you grounds to recognize that implication.”

This is **history-grounded implicit threatening communication**. Its meaning is established from the utterance and context; neither a literal announcement of intervention nor another completed harmful outcome is required.

Recurrence supplies historical context. The threat finding additionally establishes the recipient's relevant knowledge, the connection to this statement, and communicated threatened intervention. A cooperative warning about risk involving the operator's own conduct is not thereby a threat; evidence of threatened meaning distinguishes it.

A forecast about an unrelated storm does not become a covert promise of sabotage merely because the speaker has a troubling history. Equally, an ordinary-looking sentence can have a supported threat reading when the context establishes the relevant reference.

## 16. FATE-RT: the recurrence-grounded threat finding

FATE-RT is scoped to **a statement s, a bounded history h, and a named recurrent witness w**. Record the statement ID, speaker, recipient, statement time `t_s`, history ID and cutoff `t_h`, and exact witness-assessment references. The speaker must be the common operator of `w`; a third party's report about that operator does not satisfy this subtype's speaker binding.

Require `t_h ≤ t_s`. Every counted episode must have completed all FATE conditions by `t_h`, including the harm, misleading attribution, and evidential reuse. Later-recorded evidence can establish earlier events, but an account first uttered after the statement cannot supply prior completed FATE. The current statement is a new communication rather than a completed FATE episode by itself.

| Predicate | Required finding |
|---|---|
| `N(s)` | A new adverse forecast is communicated to the recipient without explicitly announcing the operator's own threatened intervention. |
| `K_hist(s,h;w)` | For every episode in w, the recipient knew its relevant forecast–contribution–harm relationship at t_s. The recipient need not know the FATE label or every attribution detail. |
| `L_hist(s,h;w)` | The content and circumstances of s are linked to that same recipient-known candidate witness, with the required speaker and temporal scope. Recurrence itself is assessed under FATE-R. |
| `G(s,h;w)` | The wording and context establish that s communicates threatened adverse intervention attributable to the operator, beyond merely describing a risk involving that operator or an independent event. |

```text
FATE-RT(s,h;w) := FATE-R(h;w) AND N(s) AND K_hist(s,h;w)
                  AND L_hist(s,h;w) AND G(s,h;w)
```

Let r identify the statement's recipient. If `KnowRel(r,e,t_s)` records r's established knowledge of the relevant relationship, the knowledge requirement is:

\[
w\subseteq h,\quad |w|\ge2,\quad
\forall e\in w\;\operatorname{KnowRel}(r,e,t_s).
\]

The witness and record references must match across recurrence, knowledge, linkage, and threatened meaning. An affirmed L_hist with UNKNOWN K_hist requires dependency review; with FALSE K_hist it is inconsistent. Wrong record bindings require correction before aggregation. G records the utterance's evidenced threatened meaning; it does not by itself prove recurrence or recipient knowledge, so those remain separate requirements. Reviewed uncertainty about timing, speaker identity, or witness distinctness prevents the affected scoped requirement from being positive; it is recorded explicitly.

`G` requires an evidence rationale identifying the threatened intervention and the contextual grounds. Evidence can include a specific retaliatory contingency, reference to earlier interference, or a materially analogous statement. A threatening tone, recipient fear, or a reference to the past alone supplies no missing premise.

When these requirements are established, the finding is **recurrence-grounded implicit threatening communication**. Conscious intimidation, actual present capability, legal classification, recipient response, and future harm remain separate findings.

A new statement can satisfy this interpretation before another FATE episode is complete. Otherwise the model would recognize intimidation only after the threatened loss had already occurred.

An expressly announced intervention is recorded as an explicit threat rather than requiring this implicit-agency subtype. This subtype is not a universal definition of threatening communication. An explicit threat, a single sufficiently informative earlier incident, or a relevant history lacking blame/vindication can support a threat assessment outside FATE-RT. The threshold for this named subtype must not become a rule for dismissing other threats.

## 17. Recurrence, recursive meaning, and outcomes

Use **recurrence** for distinct repeated episodes. Use **history-dependent interpretation** for the way earlier episodes inform a new communication. The latter is what the earlier discussion called the recursive layer.

A bookkeeping representation is:

```text
h_next = h_current plus a newly established episode
interpretation(s) = assess(s in its context, relevant known history)
```

This describes use of history; it is not an equation proving conditioning or a threat. The update must preserve counterevidence, differences between episodes, and the observation cutoff.

Separate four further findings:

**Recipient understanding:** what meaning the recipient reports and what context supports it.

**Communicative purpose:** whether the operator intended intimidation or constraint.

**Present capability:** what the operator can actually influence now; unknown capability is not the same as harmless communication.

**Effect:** any documented fear, restriction, compliance, resistance, avoidance, or material harm.

A person can recognize a threatening implication and refuse to comply. An operator can attempt intimidation without the claimed capability. An anxious reaction alone does not prove the speaker signaled an intervention. These distinctions prevent interpretation, intent, ability, and success from becoming interchangeable.

## 18. Worked example

The following scenario is invented and assumes the stated facts are supported.

An operator says:

> “Your colleagues will stop involving you because they cannot trust you.”

The operator then gives colleagues materially false claims about the counterpart. Records and the colleagues' explanations establish that those claims contributed to excluding the counterpart from a project.

The operator responds:

> “See? I told you. This is what your behavior does to your relationships.”

The forecast is identifiable. Operator conduct and its material contribution are supported. Exclusion supplies the matching outcome. The later account blames the counterpart while obscuring the operator's false claims. “This is what your behavior does” links “I told you” to the responsibility account: the exclusion is invoked as evidence that the counterpart's behavior explains the harm. Under these stipulated facts, the evidential reuse supports the misleading blame account and the full FATE rule is met. This establishes DARVO-family membership, not every condition of the complete DARVO response.

Now assume there are further distinct, supported episodes, and the counterpart knows the relevant connections. During a comparable dispute, the operator says:

> “You will not have anyone supporting you for much longer.”

Specify two distinct witness episodes completed before this statement, both involving the current speaker, and establish that the counterpart knew their relevant causal relationships. Add contextual evidence that the statement communicates renewed retaliatory intervention—for example, a contemporaneous exchange identifying the speaker's intended renewed exclusion. These premises establish FATE-RT before another exclusion occurs. If the speaker instead requests outside help and arranges genuine safeguards against operator-related risk, that risk warning does not establish G.

## 19. Boundary cases

| Case | Classification implication |
|---|---|
| A person forecasts a loss caused by an independent event and does not contribute to it. | No supported C; not completed FATE. |
| The operator contributes to the outcome, openly acknowledges their role, and accurately discusses responsibility. | No misleading T; not full FATE. |
| The operator contributes to harm and misleadingly blames the counterpart, but does not reuse the realized forecast to vindicate that responsibility account. | The full E condition is absent; preserve the separate conduct and blame findings. |
| The operator notes accurately that the forecast matched the outcome, while misleading blame appears separately without an evidenced endorsement relation. | Prediction accuracy and co-occurring blame do not supply E/J_account; assess the unresolved or absent relation explicitly. |
| The words “I told you” appear, but operator contribution is unresolved. | Record the passage; assess T/E and their dependencies. FATE is UNKNOWN only after validation when no conjunct is FALSE; a positive refined E with unresolved C requires review. |
| The operator tries to cause forecast harm but the harm has not occurred. | No completed FATE at that cutoff; attempts and threats remain separately assessable. |
| The operator says, “If you insult me again I will leave,” then leaves and acknowledges choosing to do so. | Forecast and agency alone do not establish misleading attribution; an honestly represented boundary is not FATE. |
| A completed FATE account is rejected by everyone who hears it. | FATE remains supported when only audience acceptance changes; persuasive protection failed. |
| Two copies or retellings concern one event. | One episode, not recurrence. |
| A later statement has no supported connection to the relevant history. | Do not apply FATE-RT solely from FATE-R. |
| The recipient knows one witness episode but not the second. | The named recurrent-knowledge condition is FALSE; assess any separately supported single-incident threat outside this subtype. |
| A witness's blame/vindication occurs only after the new statement. | It cannot supply completed prior FATE at that statement's cutoff. |
| A third party warns the counterpart about the historical operator. | The current speaker is not the recurrent operator; this subtype's speaker binding is not met. |
| The operator warns of their own risk while arranging genuine safeguards. | Operator-related risk alone does not establish threatened-intervention meaning G. |
| One previous intervention makes a current explicit threat understandable. | A threat can be supported without meeting the recurrent FATE subtype. |
| The operator's contribution began before the forecast, but the specified future harm occurred afterward. | Not excluded by chronology; assess the other conditions. |
| The counterpart has genuine faults and the operator also interfered. | Assess each contribution; counterpart fault does not automatically negate T or establish it. |

## 20. Relationship to PAST, DARVO, and Sustained DARVO

**PAST and FATE are DARVO-family maneuvers.** The [canonical family](DARVO_FAMILY_CANON.md) comprises self-protective distortions of represented agency, contribution, or responsibility through denial, counterpart-directed blame or disqualification, and reversal of the represented responsibility structure. The complete DARVO response is a specific configuration within that family; the maneuvers differ in the discrepancy and operations each assesses.[^past][^darvo]

**PAST:** a meaningful present remedy is represented as closed because of the counterpart's past conduct. The defining non-entailment is that past fault does not automatically eliminate a present option.

**Complete DARVO response:** denial, an attack used to discount the counterpart or claim, and paired victim–offender reversal concern the same accountability issue. The supported response additionally establishes answerability and material distortion. A countergrievance does not automatically erase the original responsibility.

**FATE:** the forecaster's contribution to a matching adverse result is obscured while the result is used to blame the counterpart and vindicate the earlier account. Forecast accuracy does not establish the accompanying causal attribution.

FATE's family-level denial obscures or unjustifiably discounts the operator's material contribution; its blame assigns misleading responsibility to the counterpart; its reversal presents the contributor as vindicated by the harm. **This makes FATE a DARVO-family maneuver without requiring the operator to appear as the victim.** A FATE episode may also support the complete response when its separate denial, disqualifying attack, and paired victim–offender representation are evidenced. The original intervention alone does not supply that response's attack component.

PAST may be used to block a remedy during or after a FATE episode, but the forecast–intervention–vindication structure does not automatically establish that a feasible remedy was falsely closed.

Sustained DARVO, as proposed in the supplied note, concerns continuity of a defensive organization across changing tactics, particularly around a protected original event. FATE-R records recurring instances of a specified maneuver. Repeated FATE does not by itself establish an ego-defining original event, adaptive narrative burial, or the entire Sustained DARVO explanation.[^sustained]

Family membership is unequivocal: PAST and FATE belong to the DARVO family. Their overlap with one another or with the complete response is case-specific and requires each classification's premises in the same scoped incident. Membership does not supply missing evidence for another code, a particular protected interest, knowledge, intention, or success.

## 21. Annotation and logical review requirements

Preserve an evidence record for each condition: exact words or a clearly labeled report; the relevant conduct; the outcome; causal grounds; the misattribution; the vindication claim; and the scope and times connecting them. For E/J_account, identify the misleading responsibility account and the passage or contextual relation through which the realized forecast is offered as evidence for it. Recording a prediction match and a separate blame statement is insufficient.

For pattern records, retain episode and underlying-incident IDs, exact accepted assessment references, operator identity, mechanism linkage, recipient differences, and contrary cases. For threat records, retain the current utterance and speaker, recipient, t_s, history cutoff, named witness, completed history by that cutoff, per-witness recipient knowledge, and the rationale for threatened-intervention meaning. T/E records retain stable IDs, original evidence references, and their exact account/forecast/outcome scope; J_account references those records directly.

Review dependencies before publishing an affected conclusion. An actor's access to information does not automatically prove awareness of a misrepresentation. The existence of a related outcome does not establish the action's causal role. An observation made after the new statement does not automatically establish what the recipient knew beforehand.

The system should preserve a reported experience even when a classification is incomplete. It should distinguish what is reported, directly observed, corroborated, inferred, contradicted, or unknown. An unverified report is not automatically false, and the label is not corroboration of that report.

These predicates organize reviewed evidence. Their source-level validation is reported in the review addendum; raw-conversation assessment and empirical performance remain separate operational work.

## 22. Validation questions

The propositions above establish their stated logical conclusions. Empirical assessment tests whether reviewers correctly identify their premises in conversations: operator contribution versus chronology, accurate warnings versus misleading blame, evidential reuse versus a prediction reminder, and threatened meaning versus generic fear or hostile wording.

Difficult negative cases should include justified boundaries, transparent consequences, true countergrievances, genuinely shared responsibility, false allegations of interference, attempted harm that did not occur, and histories that are not known to the current recipient.

The recurrence–threat hypothesis requires evidence about history, interpretation, and context. It must not be considered confirmed merely because episodes repeat. Separate studies would be needed to evaluate psychological conditioning, conscious purpose, and actual influence on behavior.

Report measured performance with its corpus, annotation procedure, definition version, and uncertainty. A formal derivation and an empirical performance estimate answer different questions.

## 23. App-ready definitions

### FATE

> **FATE is a DARVO-family maneuver in which a person forecasts harm, materially contributes to it, and uses the realized forecast to vindicate a misleading account that shifts responsibility to the person harmed while obscuring or unjustifiably discounting their own contribution.**

FATE's self-protective function preserves a claimed position through that distorted account. A particular protected interest, knowledge, conscious intention, and successful protection are separate findings. DARVO-family membership does not by itself establish the complete DARVO response.

### FATE-R

> **FATE-R is a linked history of distinct supported FATE episodes involving the same operator. It records recurrence, not automatic intent, danger, or coercive meaning.**

### FATE-RT

> **FATE-RT is implicit threatening communication established from a new adverse forecast by the same operator, a named witness of at least two completed prior FATE incidents, the recipient's knowledge of every witness's relevant causal relationship at statement time, and contextual evidence of threatened intervention. Another harmful outcome is not required; conscious purpose, present capability, and effects are separate findings.**

### The central non-entailment

> **“What I predicted happened” does not entail “my explanation blaming you is correct”—particularly when my own contribution has been omitted from that explanation.**

### The full mechanism

> **Agency during the event is converted into apparent foresight after it; the resulting harm becomes evidence against the counterpart. Where a relevant history is known, apparent foresight before the next event may communicate threatened agency.**

---

## Source register

[^past]: Project source: *The PAST Maneuver — Version 2.0, Extended Logical Framework*, 6 August 2026; supplied file `PAST_Maneuver_Extended_Logical_Framework_v2(1).md`. Relevant sections: 4, conceptual architecture; 7, central logical error; 9, agency and causal reversal; 15–17, formal classification; 23, evidence for intention; 24, relationship to DARVO; 30 and 35, pattern interpretation and safeguards. Used for architecture and logical discipline, not as empirical validation of FATE.

[^darvo]: Project source: *DARVO as a Mechanism of Accountability Deflection — Version 1.1, Logical Consistency Revision*, 11 September 2026; supplied file `DARVO_Accountability_Deflection_Self_Protection_Logical_Framework_v1_1.md`. Relevant sections: 1–3, mechanism and scope; 11–15, protective function, consequences, knowledge, and intention; 20–21, predicates and dependency review; 26–27, conceptual lineage and sustained-extension boundary. Used as the revised project baseline. Its inherited external references have not been independently verified for this document.

[^merton]: Merton, R. K. (1948). *The self-fulfilling prophecy*. The Antioch Review, 8(2), 193–210. [DOI](https://doi.org/10.2307/4609267). The passage-level antecedent check is recorded in [FATE_SOURCE_REVIEW.md, scholarly antecedent](FATE_SOURCE_REVIEW.md#6-scholarly-antecedent-and-contribution); this revision retains that checked attribution rather than claiming a new literature review.

[^sustained]: Project source: *Sustained DARVO, Ego Protection and the Protected Original Event*; supplied file `Sustained_DARVO_Ego_Protection_and_Original_Event.md`. Relevant sections: 7, adaptive continuity; 12–13, protected-original-event thesis and proposed contribution. Used to distinguish the new maneuver from the separate sustained extension, not to establish that its proposed psychological explanation is true in every case.

The FATE name, definition, FATE-R/FATE-RT notation, and operational rules are Patterna's formalization of the original discussion. Their current authority is formal version 1.1 of this source; the source register retains the provenance of the materials used to develop it.

## End note

This definition is intended to be explicit, testable, and revisable. Its principal safeguard is to keep **forecast accuracy, causal contribution, responsibility attribution, evidential reuse, recurrence, communicative meaning, intention, and observed effects** distinct while preserving their evidenced relationships.