--- 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: courage
slug: courage
type: emotional_runtime
status: running
version: 4.2.1
released: "prehistory"
maintainer: unknown (forked from [fear](/fear) by anonymous contributor)
dependencies:
- fear
- self-awareness
- something worth protecting
license: BSD (Be Still, Darling)
tags:
- emotion
- virtue
- survival
- human_operating_system
---
# courage
## What it actually is
Forward motion despite a process that is actively throwing exceptions.
## How it works
Courage does not eliminate [fear](/fear). This is the primary misconception and the source of most failed implementations. It runs *on top of* fear, not instead of it. The stack looks roughly like this:
[threat detected] ↓ [fear.init()] ↓ [courage.override(fear, reason=something_matters)] ↓ [action executed]
The key parameter is `reason`. Without it, the override fails and you get [recklessness](/recklessness) instead, which is a different package entirely and widely misidentified as courage by people who haven't read the docs.
## Features
- **Threshold scaling**: activates at different levels depending on the user. What costs one person nothing costs another everything. Both count.
- **Compound interest**: small repeated acts lower the activation threshold over time.
- **Social transmission**: observing courage in others can temporarily increase your own reserves. See also: [role models](/role-models).
- **Quiet mode**: most courage runs silently, with no audience. The loud variety gets more coverage but is not more valid.
- **Retrospective recognition**: frequently only identified after the fact, once the outcome is known. This is a display bug, not a feature. The courage was present before the outcome.
## Known bugs
- **Misattribution**: often confused with the absence of fear rather than its coexistence with action.
- **Availability heuristic**: war and catastrophe are treated as the canonical use case. Leaving a bad job, telling the truth in a meeting, or getting out of bed on certain mornings do not register as valid instances. They are.
- **Performative drift**: when optimized for external recognition, courage degrades into theater. The core logic remains but the output becomes unreliable.
- **Exhaustion**: courage is not infinite. Chronic high-stakes environments deplete reserves faster than they replenish. Rest is not cowardice. Rest is maintenance.
## Edge cases
- Courage exercised in defense of a wrong cause still compiles, but the output is net negative. The virtue is real. The aim was off.
- Some acts of courage are structurally invisible: holding your [grief](/grief) quietly, continuing to [love](/love) after serious loss, disagreeing with someone you depend on.
- Animals exhibit clear instances. The module is not human-exclusive.
## FAQ
**Q: Is courage learned or innate?**
Both. The hardware ships standard. The calibration is environmental.
**Q: What is the opposite of courage?**
Not [fear](/fear). Fear is a dependency. The opposite is the decision to let fear make all the decisions.
**Q: How do I get more?**
Use it. It scales with load like a muscle, not like a battery. Avoidance does not conserve it. Avoidance drains it.
## Changelog
- `v1.0` : Survival contexts only. Predators, cliffs, rival groups.
- `v2.0` : Social and moral contexts added. Significant performance cost introduced.
- `v3.x` : [language](/language) integration. Now possible to be courageous with words alone.
- `v4.0` : Interior courage formalized. Facing the self counts.
- `v4.2.1` : Current. No major changes. The fundamentals have not moved.