---
name: mortality
slug: mortality
type: process
status: running
version: 0.0.666-alpha
released: "~4,000,000,000 BC (approximate, logs incomplete)"
maintainer: unknown (last ping: no response)
dependencies:
  - time
  - biology
  - entropy
  - the-body
  - fear
license: non-transferable, non-negotiable, auto-assigned at birth
tags:
  - existential
  - terminal
  - universal
  - zero-sum
  - running-in-background
  - cannot-be-uninstalled
---

mortality

What it actually is

The mandatory expiry clause bundled with consciousness, readable only in retrospect.

How it works

At instantiation, a counter begins. Its value is never exposed to the user. It counts down regardless of system activity, idle state, or prayer. When it reaches zero, the process terminates. No graceful shutdown. No final write to disk. Dependent processes (relationships, ambitions, the half-finished novel) are left in undefined states.

The mechanism itself is elegant in the way that a locked door is elegant. You can admire the craftsmanship. You are still outside.

Key behaviors:

Runs at the OS level. User-space applications (wealth, fame, denial) cannot interrupt it
Not affected by reboots. There are no reboots
Occasionally surfaces as a background notification. Usually ignored. Sometimes cannot be ignored at all
Interacts unexpectedly with love: extends subjective time in some cases, compresses it catastrophically in others

Features

Feature	Status
Urgency injection	Enabled by default, often suppressed
Meaning generation	Optional, user-configured
Grief API	Available to others post-termination
Legacy mode	Write-only, unreliable
Second chances	Not in this build

Error Codes

ERR_0001  : SUDDEN_TERMINATION      // no deprecation notice issued
ERR_0002  : SLOW_DRAIN              // expected path, still somehow surprising
ERR_0003  : PREMATURE_EXIT          // scheduler malfunction, no patch available
ERR_0004  : MEANING_SEGFAULT        // tried to access purpose, pointer was null
ERR_0005  : SURVIVOR_MEMORY_LEAK    // others retain heap allocation after your exit
ERR_FATAL : YOU_ALREADY_KNEW_THIS   // this entire file is ERR_FATAL

Known Bugs

Users frequently mistake busyness for a workaround. It is not a workaround
The afterlife remains unverified. Documentation is inconsistent across sources and regions. Pull requests have been submitted. None merged
Some individuals appear to forget mortality is running entirely. This is not a fix. This is a different bug
Occasionally a person stares at the ceiling at 3am and the process surfaces fully into

Edge Cases

"I thought I had more time." Common final log entry. Filed under: expected, unresolvable.

Behavior becomes erratic near the boundaries:

Children cannot parse the concept correctly until approximately age seven. Before that, mortality runs silently
High-stress environments cause excessive foreground rendering of the process, degrading performance on all other tasks
Certain combinations of art and solitude can produce a temporary state where mortality feels acceptable. This state does not last. It still counts

FAQ

Q: Is there an upgrade path? A: Every civilization has submitted this ticket. It remains open.

Q: Does meaning extend the runtime? A: No. It changes the frame rate.

Q: Why is this spec so short? A: The spec is the right length. You just wanted more time.

License

Issued without consent. Cannot be revoked by the holder. Sublicensing to another entity is the working definition of having children.

drafting spec…