---
name: Failure
slug: failure
type: experience
status: running
version: ∞.0.0
released: "before recorded history"
maintainer: entropy
dependencies:
  - expectation
  - effort
  - time
  - a witness (optional but common)
license: Unlicense (it will find you regardless)
tags:
  - universal
  - recursive
  - load-bearing
  - misunderstood
---

Failure

What it actually is

The gap between what was predicted and what occurred, rendered personally significant by ego.

How it works

A goal is established, often with insufficient data about the environment.
Effort is applied. Sometimes heroically. Rarely optimally.
Reality returns a value that does not match the expected output.
The system (you) flags this as catastrophic.
Depending on configuration, the system either reboots or loops indefinitely on step 4.

The loop at step 5 is the actual failure. Step 3 is just a result.

Features

Diagnostic output: reveals which assumptions were wrong, which skills were missing, which conditions were outside your control. Most users ignore this output entirely.
Compression: compresses years of abstract self-concept into a single concrete data point. Painful but accurate.
Interoperability: works across domains. Career, relationships, art, sourdough starters. Fully cross-platform.
Persistence: does not require consent to install.

Known bugs

Bug	Frequency	Notes
Conflation with identity	Extremely common	User concludes they ARE the failure, not that they experienced one
Retroactive certainty	Universal	After failure, the outcome feels like it was always inevitable
Comparison corruption	Common	Failure feels larger when measured against others' highlight reels
Premature logging	Frequent	Failure declared before the process has actually finished

Error codes

ERR_EXPECTATION_MISMATCH     // Most failures. Reality disagreed.
ERR_WRONG_PROBLEM_SOLVED     // Solved the stated problem, not the actual one.
ERR_DEPENDENCY_MISSING       // You needed luck, timing, or a phone call that never came.
ERR_SELF_SABOTAGE            // See: [fear](/fear)
ERR_TOO_EARLY                // This was not failure. This was Tuesday.

Edge cases

Successful failure: process produces exactly the wrong result, which turns out to be the correct result for an adjacent, more important problem. See: penicillin, Post-it notes.
Failure by success: the goal is achieved and nothing improves. Often more destabilizing than conventional failure.
Distributed failure: no single point of failure. Everyone did their part. Still failed. Useful for understanding bureaucracy.

FAQ

Q: Is failure necessary? A: It is not necessary in the motivational poster sense. It is, however, load-bearing. Remove it from a life and the structure gets strange. Brittle. Overfit to conditions that no longer exist.

Q: How do I recover? A: You begin a new process. The old one is logged, not deleted. Memory keeps the receipt.

Q: What if I keep failing at the same thing? A: Either the thing is genuinely beyond your current capability, or the goal was someone else's to begin with. Both are worth investigating before attempt N+1.

Q: Is there a version without failure? A: That version is called stasis. Users report it is worse.

Changelog

All versions prior to now: same core behavior. Cosmetic changes only. The Romans had a word for it. So did everyone before them.
v2.0 (Modernity): failure made public by default. Privacy settings largely ineffective.
Current: unchanged. No patch pending.

drafting spec…