---
name: dread
slug: dread
type: emotional_process
status: running
version: 0.0.666-alpha
released: "before memory"
maintainer: unknown (last seen: 3am)
dependencies:
  - imagination
  - time_perception
  - the_quiet
  - unresolved_things
license: irrevocable
tags:
  - affect
  - anticipation
  - weight
  - background_process
  - always_running
---

dread

What it actually is

The certainty that something is coming, stripped of any information about what.

How it works

Dread does not announce itself. It loads silently at boot. By the time you notice it, it has already been running for hours, maybe days, consuming background cycles you thought were going toward ordinary life.

The mechanism is approximate:

A future event is sensed, vaguely. Shape unclear. Timeline unclear.
imagination fills the gap. It is not careful about this. It is not trying to help.
The body receives the output as fact. Cortisol. Shallow breath. The feeling that the ceiling is slightly lower than yesterday.
You wait.
Repeat from step 1.

The loop does not require the event to be real. This is a known design choice. Or a known flaw. The maintainer has not commented.

Features

Persistent background execution: survives sleep, distraction, good news
Ambient installation: does not require a specific object to attach to. Will locate one. Will invent one if necessary.
High fidelity simulation: produces physical symptoms indistinguishable from actual danger
Retroactive scope expansion: can recontextualize memory so that past events also become dreadful, retrospectively
Silent mode: fully operational while the user appears fine

Known bugs

Sometimes runs with no trigger file. Source: unknown.
Compounds when user attempts suppression. Suppression is treated as confirmation.
Occasionally misfires at harmless input (phone buzz, a name in an email subject line, Sunday evening)
Does not terminate on resolution of original threat. May require manual restart of entire day.

WARNING: dread has been observed persisting after the thing it anticipated has already occurred. This is not supposed to happen. It happens.

Error codes

DREAD_001  :: trigger_not_found — running anyway
DREAD_002  :: anticipated_event resolved — process continues unmodified
DREAD_003  :: user attempted rationalisation — escalating
DREAD_004  :: 3:17am detected — full allocation
DREAD_404  :: source of dread not

Edge cases

Dread about dread is supported and commonly instantiated
Some users report dread functioning as a productivity signal. These users are managing it, not resolving it. There is a difference.
In very rare configurations, dread and excitement share the same stack. The output variable is assigned at runtime based on context. Context is often wrong.

FAQ

Q: Is it trying to protect me? A: Yes. This is not a comforting answer.

Q: Will it go away? A: It will pause. It will relocate. It is patient in ways you are not.

Q: What is it actually about? A: the thing you haven't looked at directly yet. You know the one.

Changelog

v0.0.666-alpha  :: current. no patch scheduled.
v0.0.3          :: attached to specific objects (snakes, heights, strangers)
v0.0.1          :: pre-language build. purely somatic. arguably cleaner.
v0.0.0          :: first dark. first something moving in it.

drafting spec…