Methodology:
how this book tells time
This page explains the adaptive resolution, card grammar, source boundary, people layer, and scenario protocol behind the Humanity History.
1. Adaptive resolution
Early human history begins with 20,000-year cards for deep prehistory, then tightens to 1,000-year cards near the Ice Age/agriculture threshold because the evidence becomes denser and change accelerates. A fixed century-by-century pace would create fake precision.
From cities and writing onward, the book can move closer to 100-year cards, then 50-year, 20-year, 10-year, 5-year, and 1-year cards as evidence density rises.
The changing frame rate is part of the argument: human progress accelerates as memory, energy, coordination, and cognition become externalized.
2. A4 card grammar
Each card is one printable narrative unit. The usual structure is: human state, good, bad, deep pattern, and bridge. The goal is not a list of facts, but a readable compression of the era.
3. Source boundary
Factual chapters use external source anchors and cautious synthesis. Source anchors are not exhaustive bibliographies; they are verification points for important claims. The last chapter uses project files as primary sources because it is a scenario based on Bojan’s AI8 / DCC / Good Future material.
4. People layer
The v0.16.7 patch adds a “People who shaped this period” section to factual chapters. Influence is not endorsement. The lists include builders, healers, thinkers, rulers, conquerors, witnesses, and destructive actors. For deep prehistory, no names survive, so the section names roles and traces instead of inventing people.
5. Scenario protocol
Factual history stops at 2026. Part 11 is a worked example of one possible human–AI collaborative research branch. It keeps other futures alive and includes a falsifiability rule: the branch must shrink or change when evidence breaks it.
6. Omissions and scope
This is a serious narrative atlas, not a complete academic encyclopedia. It necessarily omits many regions, people, languages, and events. The right use is: read the compression, check the anchors, then improve the map.