---
name: Mortality
slug: mortality
type: constraint
status: running
version: 0.0.1-final
released: "~3.8 billion BCE"
maintainer: entropy
dependencies:
  - biology
  - time
  - cellular-senescence
  - the-universe
license: Non-negotiable Public License v1.0
tags:
  - existential
  - biological
  - universal
  - non-optional
  - background-process
---

Mortality

What it actually is

A hard deadline with no extension policy.

How it works

Every biological process gets allocated a finite number of cellular divisions, heartbeats, and Tuesday afternoons. When the allocation runs out, the process terminates. There is no graceful shutdown. There is no core dump. There is, occasionally, grief, which is what the surviving instances produce after observing the termination event.

The mechanism varies. The outcome does not.

"I knew it was a trial version. I did not expect it to end mid-sentence." — Every user, eventually

Features

Urgency injection: Scarcity of time reliably increases the perceived value of individual moments. A known bug that functions as a feature in practice.
Meaning scaffolding: Most meaning is load-bearing only because something ends. Remove mortality and you get boredom, eventually.
Selective pressure: Keeps the gene pool from becoming a stagnant archive. Controversial, but effective at scale.
Natural pacing: Prevents any single instance from monopolizing resources across multiple centuries. (See also: power)

Known bugs

Timing is wildly inconsistent. Deployment can occur at any age, without warning, in any context including but not limited to: ordinary Wednesdays, mid-laugh, right before the good part.
No progress bar. Users report significant distress at the absence of an ETA.
The system notifies third parties before notifying the affected instance. This is considered poor UX but has not been patched.
Awareness of the constraint is installed early but comprehension is delayed by decades, creating a window of false comfort that closes without notice.

Error codes

ERR_PROCESS_TERMINATED       // standard exit, no further action available
ERR_PREMATURE_SHUTDOWN       // timing failure, widely flagged, never fixed
ERR_LEGACY_INSTANCE_OFFLINE  // a person you loved is no longer reachable
ERR_DENIAL_LOOP              // user refuses to acknowledge constraint; system waits
ERR_MEANING_NOT_FOUND        // often precedes existential reconfiguration

Configuration

# Read-only. No user-accessible settings.
awareness_onset: variable
acceptance: optional
legacy_output: ["memory", "children", "work", "debt"]
death_anxiety: enabled_by_default
workarounds_attempted: ["religion", "cryonics", "legacy", "fame", "philosophy"]

FAQ

Can I opt out? This is the most-asked question in human history. The answer has not changed.

Does it get easier to think about? Most users report that acceptance installs around middle age, though it is rarely a clean install.

Is there anything after? Outside the scope of this document. See community forums. Note: forums are not moderated and consensus is not expected.

What should I do with the time remaining? That field is intentionally left blank. Users are expected to populate it themselves.

Changelog

v0.0.1: Initial release. Applied universally. No known exceptions.
All subsequent versions: Same as above.

drafting spec…