--- 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: uncertainty
slug: uncertainty
type: cognitive state / epistemic condition
status: running
version: ∞.0.0
released: "before measurement was invented"
maintainer: reality@universe.local
dependencies:
- knowledge
- time
- ego
- the future
license: BSD (Basically Someone's Dread)
tags:
- epistemology
- anxiety
- probability
- human-condition
- core-runtime
---
# uncertainty
## What it actually is
A gap between what you know and what is true, running constantly in the background, consuming more resources than you think.
## How it works
At boot, [the present moment](/the-present-moment) hands you incomplete information. Your brain attempts to resolve this by pattern-matching against past events, consulting [memory](/memory) (unreliable), and running probability estimates (also unreliable). The process loops. No termination condition exists.
The system does not crash on uncertainty. It was designed around it. The crash happens when a process insists on certainty instead.
## Features
- Runs on all known organisms with a nervous system
- Scales from "should I bring an umbrella" to "does any of this matter"
- Integrates natively with [hope](/hope) and [dread](/dread) (often simultaneously)
- Supports paralysis mode for edge cases
- Compatible with all known decision-making frameworks, though it undermines most of them
- Generates intuition as a lossy compression workaround
## Known bugs
| ID | Description | Status |
|----|-------------|--------|
| U-001 | Overthinking loop: process spins indefinitely without output | Won't fix |
| U-002 | False certainty: user believes bug is resolved when it isn't | Common in production |
| U-003 | Premature resolution: user picks any answer to stop discomfort | By design, technically |
| U-004 | Scope creep: small uncertainties expand to existential ones after midnight | Known since antiquity |
> "I've been running uncertainty for forty years and I still don't know if it's a feature or the whole point."
> — anonymous user, 3am
## Configuration
```yaml
uncertainty:
tolerance: 0.0 - 1.0 # most users ship with 0.2, should be higher
resolution_strategy: defer # options: defer | guess | accept | spiral
notification_mode: ambient # options: ambient | intrusive | dissociation
scoped_to: everything # not configurable
Uncertainty cannot run without time. Remove time and uncertainty collapses into either total knowledge or total ignorance. Neither is available. Time remains a hard dependency with no planned removal.
Also pulls in other people, whose internal states are permanently opaque. This is not a bug. This is intimacy.
Q: Can I eliminate uncertainty? A: You can eliminate your awareness of it. Different operation.
Q: Is certainty the goal? A: certainty is a separate package. Review its known bugs before installing.
Q: Should I be more comfortable with uncertainty? A: That question contains uncertainty. You are already running the software correctly.