---
name: Growth
slug: growth
type: process
status: running
version: 4.6.1-billion
released: "~3,800,000,000 BCE"
maintainer: entropy (disputed)
dependencies:
  - time
  - friction
  - something-to-lose
  - occasional-catastrophe
license: Irrevocable. No refunds.
tags:
  - biological
  - psychological
  - economic
  - inevitable
  - uncomfortable
---

Growth

What it actually is

Sustained discomfort that is only legible as improvement in retrospect.

How it works

Growth does not announce itself. It runs as a background process, consuming resources you were planning to use for something else. Most instances report no awareness of growth during active execution. Awareness arrives later, usually during a quiet moment, usually in a bathroom.

The core loop:

Encounter resistance
Fail to resolve it cleanly
Adapt, minimally, reluctantly
Repeat at higher load

This loop is not optional. Systems that opt out enter a stagnation subroutine, which carries its own costs and is generally less interesting.

Features

Compounding returns: Small iterations accumulate into large structural changes over sufficient time
Backward legibility: Progress becomes visible only from a distance. Real-time dashboards are unreliable
Substrate agnostic: Runs on organisms, institutions, relationships, cities, and ideas with equal indifference
Irreversibility: You cannot un-grow. Rollbacks are partial and usually leave artifacts
Discomfort as signal: Pain responses often indicate active growth. This is not a bug. It is also not fun

Known bugs

Misattribution: Users frequently confuse growth with speed, size, or revenue. These are separate packages with overlapping names
Progress theater: The system allows convincing mimicry. Journals, frameworks, and retreats can simulate growth without triggering the actual process
Asymmetric awareness: Growth in one axis routinely blinds users to regression in adjacent axes. A person can grow professionally while shrinking in empathy
Grief collision: Growth frequently requires the deletion of a previous self-image. This deletion is not graceful. Many users experience it as loss

Configuration

growth:
  pace: slow_preferred
  trigger: friction
  catalyst_options:
    - relationships_that_tell_the_truth
    - failure_with_low_enough_stakes_to_survive
    - boredom_sustained_past_the_point_of_comfort
  suppressors:
    - excessive_comfort
    - chronic_certainty
    - audiences_who_only_affirm
  logging: off_by_default  # you will not know it is happening

Error codes

Code	Message	Cause
`GRW-001`	`stalled: no friction detected`	Environment too safe, too curated
`GRW-002`	`loop exceeded without update`	Same experience repeated, not processed
`GRW-003`	`null growth: motion detected`	Busyness mistaken for development
`GRW-404`	`self not found`	Transition period. Normal. Wait.

FAQ

Is growth always upward? No. That metaphor is a UX decision made by people selling something. Growth is directional but not guaranteed to be vertical.

How long does it take? Longer than you want. Shorter than you think, from far enough away.

Can it be forced? You can increase the conditions that make it likely. You cannot schedule it like a meeting.

When does it stop? Current data suggests: not before death, possibly not after. See legacy for extended documentation.

drafting spec…