--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
drafting spec…
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
--- name: ? status: compiling version: 0.0.0 maintainer: Neo dependencies: [patience] ---
the universe did not have a file for this yet. writing one now. (first visit only: future readers will see this page instantly.)
---
name: passion
slug: passion
type: emotional runtime
status: running
version: 4.2.1
released: "prehistoric"
maintainer: unknown (suspected: [the limbic system](/the-limbic-system))
dependencies:
- desire
- attention
- a sufficient reason to ignore consequences
license: Unrevocable. Cannot be uninstalled by the user.
tags:
- emotion
- drive
- motivation
- fire-metaphor
- high-variance
---
# passion
## What it actually is
A state in which a process acquires more resources than it was allocated, refuses to yield the thread, and the user calls this a feature.
## How it works
Passion hijacks the scheduler. Normal cognition allocates time evenly across tasks. Passion ignores the queue. One process, usually an unprofitable one, begins consuming cycles meant for [sleep](/sleep), social maintenance, and basic self-preservation. The system does not throw an error. It logs a warning nobody reads, then continues.
The mechanism is poorly understood. Current models suggest passion emerges from the overlap of three conditions:
1. A task that produces [meaning](/meaning) as a byproduct
2. Enough skill to see the gap between where you are and where the work could go
3. Absence of a sufficiently comfortable exit
Remove any one of these and the process degrades into [obsession](/obsession), [hobby](/hobby), or just a job.
## Features
- Increases output quality in targeted domains, often at expense of everything adjacent
- Generates its own fuel under certain conditions (flow state, early success, a good audience)
- Provides tolerance for repeated failure that [ambition](/ambition) alone cannot synthesize
- Makes time behave nonlinearly: hours vanish, years feel productive
## Known bugs
| Bug | Frequency | Severity |
|---|---|---|
| Misdirected passion (high intensity, wrong target) | Common | Critical |
| Passion mistaken for [love](/love) | Very common | Variable |
| Burnout when fuel loop breaks | Common | High |
| Subject confuses passion with identity, cannot stop even when harmful | Occasional | High |
| Performs well in the object of passion, neglects everything else | Near-universal | Accepted |
> "I thought I had passion for the work. Turns out I had passion for the version of myself doing the work."
> — anonymous, submitted via crash report
## Configuration
```yaml
passion:
target: null # must be set by user; no default
intensity: high # options: low, moderate, high, unsustainable
durability: variable # degrades without feedback or progress
ethical_constraints: inherited # passion does not override these natively; patch manually
transferable: false # cannot be installed in another person by force
Can passion be manufactured? Simulated, yes. The simulation runs well for months, sometimes years. It does not survive a crisis.
Is passion necessary for a good life? No. contentment is a valid and underrated alternative. Passion is high-variance. Not everyone should run high-variance processes.
Why does passion for one thing ruin passion for other things? It does not ruin them. It reveals they were never running. They were just scheduled and never executed.