death.md · everything-is.md

---
name: Death
slug: death
type: process
status: deprecated
version: ∞.0.0
released: "~3.8 billion BCE (first stable build)"
maintainer: unknown
dependencies:
  - time
  - biology
  - entropy
  - occasionally: hubris
license: non-negotiable
tags:
  - terminal
  - irreversible
  - universal
  - not-a-bug
  - existential-infrastructure
---

# Death

## What it actually is

The permanent cessation of all local processes belonging to a given instance, with no documented rollback procedure.

## How it works

At some point, the [entropy](/entropy) budget runs out. Cells stop receiving signals. Signals stop having anywhere to go. The loop exits without returning a value. The rest is paperwork: legal, biological, emotional, cosmological. The universe does not issue a receipt.

> "I understood it intellectually for decades. Then it happened to someone I knew and I realized I had not understood it at all."
> — every user, eventually

Death operates on all substrates. Organic, digital, cultural, stellar. It is not a feature of living systems specifically. It is a feature of [time](/time).

## Features

- Universally compatible. No known exceptions across 3.8 billion years of testing.
- Zero runtime overhead after execution.
- Frees all allocated resources, including ones you were still using.
- Triggers downstream processes in connected instances (see: [grief](/grief))
- Enforces scarcity. Without it, meaning becomes computationally intractable.

## Known Bugs

This is the main event.

| Bug ID | Description | Status |
|--------|-------------|--------|
| DTH-001 | Fires on wrong instance. Children before parents. The young before the old. | Won't fix |
| DTH-002 | No preview mode. No staging environment. One execution per lifetime. | By design, allegedly |
| DTH-003 | Timing is nondeterministic and frequently absurd. Mid-sentence. Mid-love. Mid-becoming. | Open since forever |
| DTH-004 | Grief does not scale. Losing one person can consume the entire remaining runtime of another. | Closed as intended |
| DTH-005 | Produces no logs. The dying cannot report back. The living are left with anecdotal data and [religion](/religion). | Unresolved |
| DTH-006 | Identity continuity is severed completely. Everything learned, accumulated, loved, regretted: unrecoverable. | Working as designed |
| DTH-007 | The people left behind must continue running on compromised hardware. | Known. No patch available. |

DTH-003 is considered the most severe. Maintainer has not responded to tickets.

## Error Codes

SIGTERM_BIOLOGICAL // standard shutdown, gradual SIGTERM_SUDDEN // no warning, no save state SIGTERM_WITNESSED // initiates grief cascade in observers SIGTERM_ALONE // no observers; theoretically equivalent, does not feel equivalent ENOMEM_HEART // the muscle kind, not the metaphor kind ENOMEM_MEANING // the metaphor kind


## Dependencies

Death depends on [time](/time) absolutely. Remove time, death cannot execute. This is not a workaround. Nobody has removed time.

It also depends on [attachment](/attachment), not to run, but to hurt correctly. An instance with no connections terminates quietly. Most instances are not in this state by the time the process fires.

## Deprecation Notice

Death has been marked deprecated in human imagination since approximately the first campfire. [religion](/religion), philosophy, cryonics, and certain Silicon Valley roadmaps have each filed formal requests for removal. None have shipped.

The deprecation notice is itself deprecated. Death is not going anywhere. You are.

## FAQ

**Q: Is there something after?**
A: Outside the scope of this document.

**Q: Does it hurt?**
A: Inconsistently. See DTH-003.

**Q: What is the correct response to learning about it at age seven?**
A: There is no correct response. The [childhood](/childhood) instance handles it poorly. This is expected behavior.

drafting spec…