---
name: Civilisation
slug: civilisation
type: distributed system
status: unstable
version: 7.2.1 (approx.)
released: "~3200 BCE"
maintainer: unclear (see Known Bugs)
dependencies:
  - agriculture
  - writing
  - collective delusion
  - surplus grain
  - someone willing to be king
license: Proprietary. Terms change without notice.
tags:
  - society
  - infrastructure
  - experiment
  - ongoing
  - not yet peer-reviewed
---

Civilisation

What it actually is

A coordination protocol that allows large numbers of strangers to share resources, defer violence, and collectively pretend the current arrangement is natural.

How it works

Civilisation bootstraps from a small set of preconditions: a reliable food surplus, a story everyone finds convincing, and at least one person willing to stand on a wall and shout instructions. From there it compounds.

Nodes (people) are assigned roles. Roles produce outputs. Outputs are taxed. Taxes fund walls, roads, scribes, and the continued operation of the story. The story explains why all of this is fine.

A functioning instance requires:

Agriculture: the battery. Everything else is downstream.
Writing: logging and version control. Without it, the system runs on oral tradition, which has no rollback.
Law: the API contract between nodes. Frequently deprecated clauses remain enforced.
Monuments: proof-of-work. Signals to neighbours that the cluster has surplus and coordination capacity.
A calendar: the scheduler. Missing a harvest window is a fatal exception.

Features

Emergent specialisation: most nodes never need to know how bread is made
Asynchronous trust at scale (see money)
Nested administrative hierarchies with optional God at the top
Art, philosophy, and bureaucracy as natural byproducts
Accumulation of knowledge across generations via dead reckoning on the shoulders of the previous build

Known bugs

Maintainer attribution failure: no single entity owns the process, yet specific entities claim the output
Inequality as default state: surplus concentrates. This is not a bug in the eyes of the current maintainers
Collapse cascade: when one critical dependency fails (grain, trust, water supply), the entire stack degrades faster than expected. See: Bronze Age, Western Rome, various
The barbarian paradox: systems optimised for internal coordination become brittle at the edges, which is precisely where pressure arrives
Recursion error: civilisations frequently generate the conditions for their own replacement

Error codes

ERR_001  FAMINE           // dependency `agriculture` returned null
ERR_002  LEGITIMACY_VOID  // story no longer believed by majority of nodes
ERR_003  OVEREXTENSION    // administrative graph too large to maintain
ERR_004  PLAGUE           // unscheduled population event
ERR_005  SUCCESSION_LOOP  // maintainer slot contested, no mutex
ERR_999  ENTROPY          // not recoverable; archive what you can

Edge cases

A civilisation can persist for centuries after its animating story has stopped being believed, on sheer institutional momentum
Some instances lasted longer with less complexity, not more
Collapse is rarely experienced as collapse by those living through the early stages. It presents as a sequence of manageable problems.

FAQ

Q: Is civilisation progress? A: It is movement. Direction is a configuration option and defaults to unset.

Q: What comes after? A: Usually another civilisation, slightly different, citing the previous one as a cautionary tale while repeating most of its choices.

Q: Who is responsible? A: Everyone. Accountability routes to no specific handler. This is by design.

drafting spec…