A modern object is rarely one invention. It is the visible end of a hidden dependency system.
That is the central lesson of the 1000-Year Civilisation Test. Send one educated person from 2026 back to roughly 1026 and ask them to build a computer. The difficulty is not simply that the computer is complicated. The difficulty is that almost every part of the computer depends on another capability, and those capabilities depend on still others.
Move downward far enough and the apparently digital problem becomes a problem of mining, heat, measurement, food, transport, written records, skilled labour, standards, institutions and time.
The Civilisation Dependency Tree asks a different question: not “Do you know how the final object works?” but “What must already exist before the final object can reliably exist?”
Start at the top: the object we want
Take a laptop computer as an example. At first glance its major dependencies seem obvious: processor, memory, storage, display, battery, keyboard, circuit boards, radio, operating system and software.
But each label hides another layer. A processor requires semiconductor fabrication. Semiconductor fabrication requires highly controlled materials, photolithography, chemical processing, vacuum systems, precision optics, metrology and large amounts of reliable energy. Those machines require other machines. The measurements require standards. The factories require trained specialists. The specialists require educational systems. The plant requires transport, finance, maintenance, documentation and an immense network of suppliers.
By the time we reach the bottom, the “computer problem” has become a civilisation problem.
A dependency tree is not really a tree
The phrase “dependency tree” is useful because it encourages us to move downward from a visible outcome toward prerequisites. But real civilisation is more entangled than a tree. The same dependency can serve many branches, and branches loop back into one another.
Better measurement improves metallurgy. Better metallurgy improves measuring instruments. Better instruments improve machine tools. Better machine tools improve printing presses and pumps. Better printing improves technical education. Better education improves the next generation of measurement, metallurgy and machines.
So the deeper structure is a network of reinforcing capabilities. Some nodes have unusually high leverage because improving them strengthens many branches at once.
The eight dependency layers
| Layer | Question | Examples |
|---|---|---|
| 1. Idea | Do we know what principle or design is wanted? | electromagnetism, germ theory, binary logic |
| 2. Materials | Do suitable substances exist in usable form? | copper, glass, steel, paper, acids, ceramics |
| 3. Tools | Can those materials be shaped and joined? | furnaces, drills, lathes, presses, kilns |
| 4. Measurement | Can parts and processes be compared reliably? | length, mass, temperature, time, calibration |
| 5. Energy | Can enough controlled work be delivered? | human labour, water, wind, steam, electricity |
| 6. Production | Can the result be repeated, not merely demonstrated? | workshops, process control, interchangeable parts |
| 7. Coordination | Can many specialised contributors work together? | records, contracts, logistics, standards, organisations |
| 8. Continuity | Can the capability survive turnover and time? | education, maintenance, archives, institutions, succession |
The traveller who understands only Layer 1 can speak brilliantly about the future and still build almost nothing. Civilisational capability emerges when enough layers become simultaneously reliable.
Example 1: build a reliable printed technical book
A printed technical book sounds far easier than a computer, and it is. But even here the dependency tree is revealing.
The traveller needs a writing system understood by readers, a way to create durable surfaces or paper, inks that adhere and remain legible, a method for producing many copies, type or another reproducible image-transfer method, alignment, pressure, drying, binding and distribution.
Then the social dependencies appear. Who decides which version is authoritative? How are errors corrected? How are diagrams reproduced? How do apprentices learn to set type or prepare plates? How are editions dated? How are copies stored? How does a reader know that a procedure in one book is compatible with the measurements used in another?
The object is a book. The capability is much larger: reliable replication of knowledge. Once that capability exists, every later branch benefits. A good printing system therefore has high civilisational leverage because it externalises memory and accelerates teaching.
Example 2: build a microscope
The traveller may know that microorganisms exist. That knowledge is potentially transformative, but convincing other people becomes easier when the invisible can be made visible.
A microscope requires more than the idea of magnification. It requires transparent material of adequate quality, shaping and polishing, control of curvature, a stable frame, controlled distance between optical elements and specimen, illumination, specimen preparation and enough repeatability to distinguish an observation from an optical defect.
Then comes verification. If one observer sees something, is it real? Can another observer see it? Can the instrument be focused in a repeatable way? Can drawings be compared? Can contamination be separated from the specimen? Can multiple instruments produce compatible observations?
The dependency tree moves from glass to grinding, measurement, frames, workshops, instruction and scientific practice. The scientific concept matters, but the ability to make trustworthy evidence depends on an engineering and institutional substrate. This is why How Science Works and Research & Inquiry belong in the same map.
Example 3: build an electric motor
An electric motor appears straightforward at the level of principle: electrical current and magnetic fields can produce force and rotation. Yet the reconstruction problem immediately spreads.
The traveller needs conductive material, insulation, magnetic materials, a shaft, bearings or bearing surfaces, a mechanically stable frame, a power source, switches or contacts, methods to reduce unwanted heating, and instruments that indicate whether improvements are actually improvements.
Uniform wire is already a manufacturing achievement. Good insulation is a materials problem. A straight shaft is a precision problem. Low-friction support is a mechanical problem. Reproducible dimensions are a standards problem. Reliable power is an energy-system problem. Repair is a maintenance problem.
One motor can be a demonstration. A society able to produce, install, repair and improve motors possesses an industrial capability.
Example 4: build a clean-water system
Some of the traveller’s most valuable contributions may not look futuristic at all. Reliable clean-water practices can matter more than advanced machines because they protect the people who must build everything else.
But again, the dependency tree prevents oversimplification. A water system may require source selection, transport, storage, separation from waste, containers, pipes or channels, filtration, boiling or another treatment process, fuel, maintenance, rules for use, inspection and records of failures.
Even when the scientific principle is known, sustained public-health capability depends on behaviour, infrastructure and governance. The traveller must therefore work with people, not merely with matter.
Example 5: build a computer
Now return to the computer. Suppose the traveller gives up on a modern semiconductor device and chooses a much simpler path: mechanical or electromechanical computation.
This is already a powerful change in strategy. The traveller has moved from copying a 2026 object to reconstructing the underlying function with locally attainable technology. That is exactly what first-principles education should make possible.
Even so, a useful calculating machine still depends on accurate gears or switching elements, stable numerical representation, repeatable components, documentation, error checking and operators who understand the procedure. A programmable machine adds another layer: a representation of instructions, reliable state transitions, a method of input and output, and conventions that allow programs to be written and debugged.
The lesson is not that computers are impossible. The lesson is that the shortest route to the function may differ radically from the shortest route to the modern form.
Function first, form second
This distinction is central to the entire experiment. If the traveller asks “How do I recreate a smartphone?” the dependency frontier is overwhelming. If the traveller asks “What functions does the smartphone provide, and which of those functions create the greatest leverage?” the problem becomes tractable.
| Modern form | Underlying function | Earlier attainable route |
|---|---|---|
| smartphone messaging | rapid information transfer | organised courier, signalling, later telegraphy |
| calculator app | reliable arithmetic | tables, abacus, mechanical calculation |
| camera | durable visual record | drawing standards, optical projection, later photography |
| database | structured external memory | indexed ledgers, catalogues, standard forms |
| search engine | rapid retrieval | classification, indexes, catalogues, cross-references |
| GPS | position and navigation | surveying, maps, astronomy, standard coordinates |
The traveller who understands functions can choose technologies appropriate to the available dependency level. This is much closer to engineering than imitation.
The bootstrap problem
The hardest dependencies are often recursive. Better machine tools require precise machine tools to manufacture them. Better measurement instruments require standards and materials that themselves depend on better instruments. Better chemicals may require vessels that resist the chemicals. Better furnaces may require refractories that need controlled furnaces to make consistently.
This is the bootstrap problem: how do you climb from low precision to high precision when the high-precision tool is needed to make the next tool?
The answer is usually iterative rather than magical. Build the best crude tool currently possible. Use it to make a somewhat better tool. Measure the improvement. Preserve what worked. Repeat. Civilisation often advances through ratchets rather than leaps.
A civilisation can climb a dependency ladder when each generation of tools helps produce a better generation of tools, records and people.
Standards are invisible infrastructure
Suppose two workshops can both make a bolt, but each uses a different diameter and thread. Individually they possess toolmaking skill. Collectively they lack interchangeability.
Standards reduce coordination cost. Shared units allow measurements to travel. Shared interfaces allow components to travel. Shared terminology allows instructions to travel. Shared test procedures allow evidence to travel.
In the time-travel experiment, standards are therefore not bureaucratic decoration. They are a form of compression: instead of renegotiating every relationship from scratch, participants inherit agreed constraints.
Maintenance belongs inside the dependency tree
A machine that works for one day is not equivalent to a machine that works for twenty years. Modern people often notice production but overlook maintenance because mature systems hide the constant labour required to keep them available.
Who lubricates it? Who notices wear? Who stocks replacement parts? Who records recurring failures? Who trains the next repairer? Who decides when a component is no longer safe? Which dimensions must be preserved so that a replacement fits?
Maintenance converts an invention into continuity. In the civilisation test, a capability that cannot be maintained has not yet passed the institutionalisation level.
Food and energy sit underneath almost everything
A specialist workshop requires people who can spend hours doing something other than producing food. A school requires teachers and learners with time. A research programme requires repeated trials that may not immediately improve survival. A mine, foundry or transport network requires sustained energy.
This means surplus is not merely an economic outcome; it is a technical dependency. Reliable food, fuel and transport create room for specialisation. Specialisation creates deeper expertise. Deeper expertise can improve food, fuel and transport. Again the network loops back on itself.
The dependency frontier
At any moment, a society has a frontier: the set of capabilities it can reliably support with its current materials, tools, knowledge, energy, institutions and skills.
A design beyond the frontier may be understood but not buildable. A design just inside the frontier may be buildable but too expensive or fragile. A design comfortably inside the frontier can spread.
The traveller’s strategic task is therefore to move the frontier outward. They should prefer interventions that unlock many downstream possibilities over impressive demonstrations that remain isolated.
High-leverage nodes
Some capabilities have unusually high fan-out. Improve them and many other branches become easier. Measurement and calibration, writing and printing, sanitation, agricultural records, metallurgy, toolmaking, mechanical power, shared standards, technical education, experimental practice and maintenance records are all examples of capability families whose effects can spread well beyond their original problem.
The correct ordering will depend on context. The point is not to create a universal recipe. The point is to learn to see leverage.
A new way to test understanding
This dependency method can be used directly in education. Give a student a familiar object—a pencil, bicycle, refrigerator, tap-water system, textbook, train, solar panel, calculator, concrete building or mobile phone—and ask them to trace downward until they reach capabilities they cannot explain.
At each node ask what function the component performs, which material property it needs, which tool makes it, how its quality is measured, what energy powers its production, which knowledge is required, which skill is tacit, which organisation coordinates production, what fails first if the supply chain disappears, and what simpler substitute might deliver the same function.
The exercise quickly reveals the difference between naming components and understanding systems. It also reconnects school subjects that are usually separated. A bicycle can become mathematics, physics, materials science, engineering, economics, design, logistics and history in one object.
The dependency tree is also a resilience test
The same method works forward rather than backward. Instead of asking what must exist to build a system, ask which missing dependency would stop it.
If electricity disappears, what survives? If one imported material becomes unavailable, what can be substituted? If a specialist leaves, is the knowledge documented? If a measuring instrument fails, is there a reference standard? If software becomes inaccessible, can essential operations continue manually?
A mature civilisation is not one in which nothing fails. It is one in which important capabilities have understood dependencies, alternatives, repair paths and people able to restore them.
The deepest lesson of the tree
The object at the top gets the attention. The layers underneath create the possibility.
A smartphone is impressive. So is the ability to make semiconductor-grade materials. So is the machine that makes the machine. So is the measurement standard. So is the technical drawing. So is the school that trains the engineer. So is the food system that allows the engineer to specialise. So is the institution that preserves the standard after its inventors die.
Civilisation is what exists underneath the object.
Continue the test
The 1000-Year Civilisation Test · The 1000-Year Education Test · The Civilisation Compression Ratio
What Is Civilisation? · STEM · How Science Works · How Mathematics Works
Follow the dependency chain into a practical foundation: Rebuild Measurement from Scratch.