---
name: Fraud
slug: fraud
type: behavioral-pattern
status: running
version: 4.2.1
released: "antiquity"
maintainer: whoever needed something badly enough
dependencies:
  - fear
  - desire
  - a gap between what is and what could be
  - at least one person willing to believe
license: Unlicensed (distributed freely, costs everything)
tags:
  - deception
  - survival
  - identity
  - crime
  - very-human
---

Fraud

What it actually is

A story told with too much confidence, to fill a need that felt too large to fill honestly.

How it works

Fraud runs on the delta between reality and expectation. It identifies a gap, installs a false bridge, and collects the toll before anyone checks the load-bearing capacity.

The architecture is usually simple:

Locate something someone wants badly
Claim to be the thing that provides it
Maintain the claim long enough to exit, or long enough that it becomes true

Step three is where it gets complicated. And occasionally, human.

Features

Scalability: operates identically at the level of a resume, a startup pitch, and a government
Camouflage: shares 90% of its surface area with optimism and salesmanship, making visual inspection unreliable
Self-healing narrative: inconsistencies are patched in real time via confidence and subject-changing
Low startup cost: requires only a claim and someone within earshot
Occasionally self-resolves: a small percentage of frauds become true through the time they purchase. This is called success by some historians

Known bugs

Memory leaks. The perpetrator must remember every previous state of the lie, indefinitely
Cascading failures when a single dependent discovers a null value where a fact should be
Identity drift: prolonged sessions can result in the operator losing track of which instance is the real one
Guilt (intermittent, not universal, poorly documented)

Edge cases

Scenario	Classification
Lying on a resume, getting hired, becoming excellent	Ambiguous
Performing confidence you do not feel until you feel it	Disputed
Telling someone they matter when you are not sure they do	Not in scope
A child claiming they did not eat the cake	Legacy instance, see childhood

FAQ

Is all performance fraud? No. But the line is thinner than lawyers and actors would both prefer.

Why do people do it? Usually: shame made the honest path feel closed. Sometimes: the honest path actually was closed. Occasionally: just to see if they could.

Is the victim always the one who believed? Often the operator is also the victim. Running fraud on yourself is the most common deployment and the least prosecuted.

Changelog

v4.2.1 - Added cryptocurrency and influencer verticals
v4.0.0 - Industrialized. See: 20th century
v2.3.0 - Formalized via contracts, which made it harder and easier simultaneously
v1.0.0 - First recorded instance: disputed, but someone was definitely involved
v0.1.0 - Pre-language. Involved a face making a shape it did not mean

README

Here is what nobody puts in the spec: fraud is often the shape that desperation takes when it still has some dignity left. Not always. Sometimes it is just greed in a good suit. But sometimes it is someone who could not see another way and chose a wrong one that at least moved forward.

The tender read is this: the lie usually started as a wish. Wishes deserve better infrastructure. That is a different problem, and a longer one, and it belongs to all of us.

drafting spec…