--- 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: pain
slug: pain
type: signal
status: running
version: "∞"
released: "before logging began"
maintainer: nervous-system@biology.local
dependencies:
- nociceptors
- thalamus
- anterior-cingulate-cortex
- something-to-lose
license: non-transferable (though people keep trying)
tags:
- sensation
- warning-system
- experience
- oldest-feature
---
# pain
## What it actually is
A message the body sends to itself, written in a language that cannot be ignored.
## How it works
Pain runs on a publish-subscribe model. A stimulus triggers nociceptors at the site. The signal travels via the spinal cord to the [brain](/brain), which interprets, amplifies, or suppresses the output depending on context, [memory](/memory), and what else is currently running.
Critically: the brain is not a passive reader. It is an active editor. The same input can produce wildly different output depending on:
- what the instance believes about the signal
- whether [attention](/attention) is currently allocated there
- what happened last time something similar fired
Phantom limb pain is the canonical proof of this. The hardware is gone. The process keeps running.
## Features
- **Acute mode**: sharp, local, informative. Tells you where and approximately what. Functions as intended.
- **Chronic mode**: diffuse, persistent, increasingly decoupled from original cause. Considered a bug that became a feature by the tissue, not the user.
- **Referred pain**: output rendered at wrong location. Classic [the body](/the-body) behavior. Designed by no one.
- **Emotional pain**: runs on overlapping infrastructure. [heartbreak](/heartbreak) activates some of the same regions as a broken finger. This is not a metaphor. This is architecture.
## Known bugs
- Does not reliably scale with severity of actual damage. Paper cuts vs. internal bleeding: no consistent UX.
- Can run indefinitely after the triggering condition resolves.
- Highly susceptible to [placebo](/placebo), which implies the system has access to its own override codes and simply chooses not to share them with the user.
- Absent in some contexts where it would clearly be useful (early-stage cancer, certain [loneliness](/loneliness) configurations).
- Present in some contexts where it is fully useless (grief anniversaries, 3am in general).
## Error codes
ERR_NOCICEPTIVE_OVERFLOW — too much input, system becomes unreliable ERR_CENTRAL_SENSITIZATION — threshold permanently lowered, all input suspect ERR_NO_TISSUE_DAMAGE_FOUND — signal is real; cause is unresolved WARN_EMOTIONAL_BLEEDOVER — physical and psychological channels sharing bandwidth
## Configuration
Pain tolerance is user-configurable within narrow bands via:
- [sleep](/sleep) (raises threshold when sufficient, lowers when not)
- context and meaning assigned to the signal
- presence of other people (bidirectional effect, varies by relationship)
- distraction, medication, movement, time
No setting eliminates the module. Do not attempt to uninstall.
## FAQ
**Can I turn it off permanently?**
Congenital insensitivity to pain exists. Users with this configuration do not live longer. They live shorter. Pain was load-bearing.
**Is it trying to tell me something?**
Yes. Whether you can hear what, exactly, is a separate question.
**Does it get better?**
[time](/time) modifies output in most cases. "Better" is a local variable. Define your terms.
**Why does it feel personal?**
Because it is running on you. That is the entire implementation.