The Dependency Floor and Critical Path Map: How Higher Civilisation Capabilities Rest on Lower Floors

Civilisation displays its highest capabilities at the surface.

We notice:

• artificial intelligence;
• satellites;
• digital finance;
• high-speed transport;
• advanced hospitals;
• global universities;
• automated production;
• large cities;
• and possible off-world settlements.

These visible systems appear to define the civilisation.

But the most advanced visible capability is rarely the deepest part of the machine.

A satellite network depends on:

• electricity;
• materials;
• manufacturing;
• launch systems;
• mathematics;
• trained engineers;
• administration;
• finance;
• law;
• communications;
• and political stability.

A digital education platform depends on:

• devices;
• telecommunications;
• teachers;
• language;
• curriculum;
• family support;
• student attention;
• electricity;
• software maintenance;
• and institutional trust.

A hospital depends on:

• water;
• power;
• sanitation;
• food;
• logistics;
• pharmaceuticals;
• records;
• skilled staff;
• public finance;
• and social order.

An off-world settlement depends not only on transport through space.

It depends on the ability to reproduce:

• air;
• water;
• food;
• energy;
• medicine;
• population;
• knowledge;
• education;
• governance;
• industry;
• culture;
• and repair.

The Civilisation Atlas Control Tower therefore requires a dedicated instrument for reading what sits underneath the visible object.

That instrument is the Dependency Floor and Critical Path Map.

One-Sentence Definition

The Dependency Floor and Critical Path Map is the Control Tower instrument that identifies the lower systems, capabilities, resources, people and relationships that must remain functional for a civilisation object to continue operating.

In compact form:

VISIBLE CAPABILITY
→ rests on supporting systems
→ which rest on lower systems
→ which rest on human and ecological foundations
→ until the minimum viable dependency floor is reached

The map answers:

What must continue working underneath?

Which dependencies are critical?

Which can be substituted?

Which are hidden?

Where is the narrowest corridor?

How far will failure spread?

The Lower-Floor Law

The central rule is:

The highest visible civilisation stage is only as secure as the lowest essential floor being neglected beneath it.

A Stage 4 digital network may depend on a Stage 3 power grid.

The power grid may depend on Stage 2 administrative records, contracts and standards.

Those systems may depend on Stage 1 food surplus and settled production.

All of them depend on Foundation 0 human adaptability, learning, cooperation and reality contact.

The complete structure is therefore:

STAGE 4
Planetary Networks
rests on
STAGE 3
Industry and Mass Institutions
rests on
STAGE 2
Administration and Recorded Order
rests on
STAGE 1
Settlement and Surplus
rests on
FOUNDATION 0
Adaptive Human Worlds

The higher floor does not replace the lower one.

It increases dependence on it.

A planetary network civilisation does not become less dependent on food, water, energy or human learning.

It becomes more dependent on those floors remaining reliable across a larger and more complex system.

Dependency Is Not Inferiority

A lower floor is not a lesser or obsolete part of civilisation.

Food production is not primitive because artificial intelligence exists.

Water infrastructure is not secondary because digital systems are more visible.

Language is not basic in the sense of being unimportant.

Family formation is not irrelevant because national institutions exist.

The term lower floor means:

This capability must already be sufficiently present before the higher capability can operate.

The floor is foundational.

Not disposable.

The Dependency Stack

Every civilisation object can be mapped through six broad dependency layers.

LAYER 1
Ecological and Biological Foundations
LAYER 2
Material and Energy Foundations
LAYER 3
Human Capability Foundations
LAYER 4
Institutional and Administrative Foundations
LAYER 5
Network and Coordination Foundations
LAYER 6
Visible Civilisation Capability

These layers are not always perfectly sequential.

They form an interdependent stack.

Layer 1: Ecological and Biological Foundations

This layer asks:

What conditions allow human life and civilisation activity to continue at all?

It includes:

• breathable air;
• clean water;
• sufficient food;
• viable soil;
• biological health;
• stable temperature ranges;
• disease control;
• functioning ecosystems;
• and reproductive continuity.

These foundations are often treated as background.

They are not background.

They are the operating habitat.

A civilisation may temporarily compensate for environmental decline through:

• technology;
• imports;
• storage;
• controlled environments;
• or financial wealth.

But compensation creates new dependencies.

For example:

LOCAL FOOD SHORTAGE
may be compensated by
IMPORT NETWORK
which depends on
PORTS
SHIPPING
ENERGY
FINANCE
TRADE RELATIONS
GLOBAL SURPLUS

The original ecological dependency has not disappeared.

It has been displaced into a larger network.

Layer 2: Material and Energy Foundations

This layer asks:

What physical resources and energy flows allow the object to operate?

It includes:

• electricity;
• fuels;
• metals;
• minerals;
• construction materials;
• machinery;
• buildings;
• roads;
• telecommunications;
• water systems;
• and physical maintenance.

Modern civilisation tends to hide material dependency behind clean interfaces.

A mobile application appears immaterial.

But it depends on:

• data centres;
• semiconductor fabrication;
• mining;
• global logistics;
• cooling;
• power generation;
• undersea cables;
• satellites;
• and replacement hardware.

The Control Tower must recover the physical substrate behind the digital surface.

Layer 3: Human Capability Foundations

This layer asks:

Which human abilities must remain available?

It includes:

• language;
• literacy;
• numeracy;
• memory;
• judgement;
• technical skill;
• scientific understanding;
• leadership;
• cooperation;
• ethical restraint;
• and the ability to train successors.

A civilisation may possess advanced equipment while losing the human capability required to maintain it.

This creates a hollow capability.

VISIBLE ASSET:
Advanced machine
MISSING FLOOR:
Operators
Technicians
Engineers
Teachers
Records
Spare knowledge

The object still exists.

The civilisation capability is weakening.

This is why EducationOS is a dependency floor for almost every advanced civilisation organ.

Layer 4: Institutional and Administrative Foundations

This layer asks:

Which rules, records, roles and authorities keep the object coordinated?

It includes:

• law;
• contracts;
• standards;
• public finance;
• regulation;
• certification;
• records;
• identity systems;
• succession;
• accountability;
• and institutional memory.

A bridge depends not only on engineering.

It also depends on:

• land authority;
• planning permission;
• safety standards;
• procurement;
• maintenance budgets;
• inspection;
• insurance;
• and responsibility for repair.

An institution may therefore fail even when its physical assets remain intact.

The building stands.

The operating system is gone.

Layer 5: Network and Coordination Foundations

This layer asks:

Which wider systems must remain connected?

It includes:

• transport;
• logistics;
• communications;
• finance;
• supply chains;
• data exchange;
• public coordination;
• diplomatic access;
• and trusted signalling.

A modern hospital may have skilled staff and functioning equipment.

But it may still fail if:

• medicine cannot arrive;
• data systems disconnect;
• electricity becomes unstable;
• laboratories cannot communicate;
• or emergency services cannot route patients.

A network capability exists through relationships.

The object may be locally strong but systemically fragile.

Layer 6: Visible Civilisation Capability

This is the capability the reader sees.

Examples include:

• high-speed rail;
• artificial intelligence;
• advanced surgery;
• digital government;
• mass education;
• planetary communication;
• precision agriculture;
• and off-world habitation.

The Control Tower should never display Layer 6 without allowing the reader to open Layers 1 to 5 beneath it.

The Five Dependency Types

The Control Tower can classify individual dependencies into five primary types.

1. Survival Dependencies
2. Functional Dependencies
3. Scaling Dependencies
4. Legitimacy Dependencies
5. Regenerative Dependencies

1. Survival Dependencies

These are required for continued existence.

Examples include:

• air;
• water;
• food;
• temperature control;
• shelter;
• sanitation;
• and biological health.

For an off-world settlement, survival dependencies are immediate and non-negotiable.

For an Earth city, they may be distributed through distant networks and therefore less visible.

2. Functional Dependencies

These are required for the object to perform its main task.

A school requires:

• teachers;
• students;
• curriculum;
• language;
• time;
• classrooms;
• assessment;
• and learning materials.

A port requires:

• docks;
• ships;
• cranes;
• customs;
• workers;
• navigation;
• security;
• and logistics.

The object may survive physically while losing function.

A school building may remain.

Education may have failed.

3. Scaling Dependencies

These allow the object to move from small operation to mass operation.

Examples include:

• standards;
• administration;
• communications;
• training systems;
• finance;
• records;
• supply chains;
• and quality control.

A capable individual teacher does not automatically produce a capable national education system.

Scaling requires institutions.

Similarly, one successful scientific experiment does not create civilisation-wide scientific capability.

Scaling requires:

• replication;
• publication;
• education;
• equipment;
• standards;
• and funding.

4. Legitimacy Dependencies

These allow the object to be accepted, trusted and obeyed.

They include:

• public confidence;
• legal authority;
• fairness;
• transparency;
• identity;
• cultural fit;
• and perceived competence.

A government may retain formal power while losing legitimacy.

A school may retain certification while families lose confidence in its educational value.

A currency may remain officially valid while trust weakens.

Legitimacy is a functional dependency because coordination relies on it.

5. Regenerative Dependencies

These allow the object to maintain, repair and reproduce itself.

They include:

• education;
• training;
• maintenance;
• succession;
• spare parts;
• research;
• institutional memory;
• recruitment;
• and cultural transmission.

A system without regenerative dependencies may perform for a time.

But it cannot continue.

This is the difference between operation and continuity.

Direct and Indirect Dependencies

A direct dependency sits immediately beneath the object.

Hospital
DEPENDS DIRECTLY ON
Electricity

An indirect dependency is mediated through another system.

Hospital
DEPENDS INDIRECTLY ON
Fuel Imports
through
Electricity Generation
Transport
Finance
and Trade

Indirect dependencies are often where surprise failures begin.

The institution may understand its direct suppliers.

It may not understand what those suppliers depend on.

Visible and Hidden Dependencies

A visible dependency is widely recognised.

A hidden dependency remains unnoticed until it weakens.

For example, schools visibly depend on teachers.

They also depend on:

• teacher preparation;
• family transport;
• sleep;
• student nutrition;
• language access;
• public safety;
• administrative time;
• and emotional stability.

A hidden dependency may not appear inside the institution’s official description.

But it may determine whether the institution works.

The Control Tower should therefore ask:

What does the object officially depend on?
What does it actually depend on?
Which dependency is taken for granted?
Which dependency is currently being consumed without replacement?

Critical and Non-Critical Dependencies

Not all dependencies have equal weight.

The Control Tower should classify them as:

CRITICAL
Failure stops the object.
HIGH
Failure severely reduces function.
MODERATE
Failure creates stress but can be compensated.
LOW
Failure creates inconvenience or small loss.
CONTEXTUAL
Importance changes by place, time or load.

For a digital classroom:

CRITICAL:
Electricity
Internet
Device access
Teacher control
Language comprehension
HIGH:
Stable platform
Curriculum alignment
Family support
MODERATE:
Advanced visual tools
LOW:
Optional decorative features

The exact classification may change by context.

Substitutable and Non-Substitutable Dependencies

A dependency may be replaceable.

PRIMARY POWER SOURCE
may be substituted by
BACKUP GENERATOR

Another dependency may be difficult or impossible to substitute quickly.

Experienced Specialist
may have no immediate replacement

The Control Tower should record:

SUBSTITUTION AVAILABLE:
Yes / Partial / No
SUBSTITUTION TIME:
Immediate / Short / Long
SUBSTITUTION COST:
Low / Moderate / High
QUALITY LOSS:
None / Limited / Severe

This is essential for resilience analysis.

Concentrated and Distributed Dependencies

A concentrated dependency relies on one provider, route or institution.

ONE DATA CENTRE
ONE PORT
ONE EXPERT
ONE SUPPLIER
ONE POWER SOURCE

A distributed dependency has several independent sources.

MULTIPLE SUPPLIERS
REDUNDANT ROUTES
DISTRIBUTED EXPERTISE
DECENTRALISED STORAGE

Distribution can improve resilience.

But it may also increase coordination difficulty.

The correct design depends on the invariant.

The Critical Path

The Critical Path is the shortest chain of indispensable dependencies connecting the object to its lowest viable floor.

For example:

ONLINE LESSON
depends on
PLATFORM
depends on
INTERNET
depends on
TELECOMMUNICATIONS INFRASTRUCTURE
depends on
ELECTRICITY
depends on
ENERGY SUPPLY
depends on
MATERIALS, OPERATORS AND GOVERNANCE

If any critical link fails, the visible capability stops.

The Critical Path is not necessarily the longest dependency chain.

It is the chain with the least tolerance for interruption.

Critical Path Versus Important Path

An object may have many important dependencies.

Only some are critical at a given moment.

For example, a school may depend on a library for educational quality.

But it may continue operating temporarily without access to the library.

It cannot continue safely without:

• teachers;
• students;
• water;
• sanitation;
• and basic authority.

The Control Tower should therefore ask:

What must remain available in the next hour?

What must remain available in the next week?

What must remain available over the next generation?

Criticality changes with time horizon.

Time-Horizon Dependency Map

The dependency map should include four time horizons.

IMMEDIATE
Minutes to hours
SHORT
Days to weeks
MEDIUM
Months to years
GENERATIONAL
Decades and succession cycles

Immediate dependencies

• power;
• safety;
• control;
• communication;
• active operators.

Short-term dependencies

• supplies;
• staffing;
• finance;
• repair;
• scheduling.

Medium-term dependencies

• training;
• replacement;
• infrastructure renewal;
• institutional reform.

Generational dependencies

• education;
• culture;
• legitimacy;
• ecological continuity;
• knowledge transfer;
• and successor capability.

A civilisation may appear secure in the immediate horizon while weakening generationally.

Dependency Depth

Dependency Depth measures how many supporting layers separate the visible object from its lowest essential foundation.

A simple object may have shallow dependency depth.

A complex civilisation capability may have deep dependency depth.

SHALLOW DEPENDENCY
Hand tool
→ user skill
→ material

DEEP DEPENDENCY
AI system
→ software
→ computation
→ data centres
→ chips
→ fabrication
→ materials
→ global logistics
→ energy
→ finance
→ law
→ education
→ scientific knowledge

Deep dependency increases capability.

It may also increase fragility.

The reader should not assume that a more advanced object is automatically more resilient.

Dependency Width

Dependency Width measures how many parallel systems must remain coordinated.

A small classroom may have moderate dependency width.

A global transport network has enormous dependency width.

DEPENDENCY DEPTH:
How many layers down?
DEPENDENCY WIDTH:
How many systems across?

A system with deep and wide dependencies requires strong:

• records;
• standards;
• coordination;
• sensing;
• and repair.

Dependency Velocity

Dependency Velocity measures how quickly failure reaches the visible object.

Some dependencies fail slowly.

Loss of teacher-training quality
may take years to appear fully.

Others fail quickly.

Power loss
may stop a digital system immediately.

The Control Tower should classify:

INSTANT
FAST
MODERATE
SLOW
GENERATIONAL

Fast failures require buffers.

Slow failures require sensing.

Dependency Visibility

Some dependencies are easy to monitor.

Others are difficult to observe.

HIGH VISIBILITY:
Power status
Inventory
Attendance
LOW VISIBILITY:
Trust
Institutional memory
Teacher exhaustion
Language erosion
Loss of judgement

Low-visibility dependencies may deteriorate for years before a major failure appears.

The Control Tower therefore requires proxy sensors.

Dependency Debt

Dependency Debt forms when a supporting floor is used without sufficient renewal.

Examples include:

• deferred maintenance;
• outdated training;
• ageing infrastructure;
• declining teacher preparation;
• unrenewed software;
• soil depletion;
• overworked staff;
• eroding trust;
• and loss of institutional memory.

The object continues operating by consuming future reliability.

CURRENT FUNCTION
is maintained by
BORROWING FROM FUTURE CAPACITY

Dependency debt is dangerous because the visible object may still appear successful.

Maintenance Debt

Maintenance debt is the accumulated work required to keep physical or institutional systems valid.

DEFERRED REPAIR
→ higher future cost
→ narrower operating corridor
→ more frequent disruption
→ increased failure risk

Maintenance is not a lower-status activity.

It is the work that keeps capability real.

Capability Debt

Capability debt appears when a system uses people whose skills are no longer being renewed.

Examples include:

• ageing technical workforces;
• dependence on a few experts;
• weak apprenticeship systems;
• declining foundational education;
• and staff performing tasks they do not fully understand.

The system may continue through habit.

It becomes vulnerable when conditions change.

Trust Debt

Trust debt appears when institutions continue consuming public cooperation without renewing legitimacy.

It may accumulate through:

• inconsistency;
• poor communication;
• unfairness;
• hidden failure;
• uncorrected error;
• or repeated broken promises.

Once trust debt becomes visible, repair may be expensive.

Trust cannot be rebuilt through messaging alone.

It requires reliable performance.

Ecological Debt

Ecological debt appears when civilisation consumes environmental capacity faster than regeneration can replace it.

Examples include:

• groundwater depletion;
• soil loss;
• pollution;
• biodiversity decline;
• and carbon accumulation.

A civilisation may preserve short-term output while narrowing its long-term habitat corridor.

This is a key Stage 5 problem.

A regenerative civilisation must be able to detect when visible prosperity is being financed through ecological debt.

The Dependency Floor Record

Every major object should carry a structured dependency record.

CIVILISATION DEPENDENCY FLOOR RECORD
OBJECT:
Canonical Atlas object
VISIBLE FUNCTION:
What does the reader see?
MINIMUM VIABLE FUNCTION:
What must still work?
DEPENDENCY LAYERS:
Ecological
Material
Human
Institutional
Network
DIRECT DEPENDENCIES:
Immediate supports
INDIRECT DEPENDENCIES:
Supports of the supports
CRITICAL DEPENDENCIES:
Failure stops the object
SUBSTITUTABLE DEPENDENCIES:
Available alternatives
NON-SUBSTITUTABLE DEPENDENCIES:
No timely replacement
BOTTLENECK:
Narrowest dependency point
BUFFER:
What absorbs interruption?
DEPENDENCY DEBT:
What is being consumed without renewal?
TIME HORIZON:
Immediate / Short / Medium / Generational
FAILURE VELOCITY:
How quickly does breakdown propagate?
SENSORS:
How is dependency health measured?
REPAIR OWNER:
Who can restore the floor?

Worked Dependency Map: A School

VISIBLE OBJECT:
School
VISIBLE FUNCTION:
Teaching students

Ecological and Biological Floor

• water;
• sanitation;
• food;
• health;
• safe temperature;
• and sleep.

Material and Energy Floor

• classrooms;
• electricity;
• books;
• devices;
• transport;
• and maintenance.

Human Capability Floor

• teachers;
• school leaders;
• language;
• subject knowledge;
• judgement;
• and student attention.

Institutional Floor

• curriculum;
• records;
• finance;
• authority;
• assessment;
• safeguarding;
• and teacher preparation.

Network Floor

• families;
• transport;
• healthcare;
• digital systems;
• government;
• and external learning resources.

Critical Path

Student Access
→ Teacher Availability
→ Shared Language
→ Valid Instruction
→ Feedback
→ Practice
→ Transfer

Hidden Dependencies

• family stability;
• teacher workload;
• emotional safety;
• public trust;
• and time for correction.

Dependency Debt

• unresolved foundational gaps;
• teacher exhaustion;
• excessive administrative load;
• outdated curriculum;
• and examination overdependence.

Failure

The school remains open but no longer transfers dependable capability.

Worked Dependency Map: A Small-Group Tuition Class

VISIBLE OBJECT:
Three-student tuition class
VISIBLE FUNCTION:
Targeted learning support

Direct Dependencies

• tutor;
• students;
• subject knowledge;
• learning material;
• time;
• attention;
• and feedback.

Hidden Dependencies

• transport;
• family scheduling;
• sleep;
• school workload;
• emotional readiness;
• language access;
• and willingness to reveal mistakes.

Critical Path

Accurate diagnosis
→ understandable explanation
→ guided practice
→ corrected error
→ independent attempt
→ transfer

If any one of these links is absent, the class may produce temporary completion without independent learning.

Non-Substitutable Dependency

The learner’s own cognitive participation.

No tutor can fully perform learning on behalf of the student.

Regenerative Dependency

The student must eventually become capable of:

• detecting mistakes;
• retrieving methods;
• checking answers;
• and learning with reduced support.

Worked Dependency Map: The Singapore MRT

VISIBLE OBJECT:
Urban rail network
VISIBLE FUNCTION:
Reliable mass movement

Direct Dependencies

• trains;
• tracks;
• stations;
• signalling;
• power;
• control centres;
• operators;
• and maintenance teams.

Indirect Dependencies

• engineering education;
• spare-parts supply;
• finance;
• land planning;
• law;
• cybersecurity;
• communications;
• and international industry.

Critical Path

Power
→ Signalling
→ Track Availability
→ Train Control
→ Safe Passenger Movement

Bottlenecks

• specialised signalling systems;
• maintenance windows;
• critical interchanges;
• and technical expertise.

Buffers

• alternative routes;
• buses;
• spare trains;
• incident teams;
• and system redundancy.

Dependency Debt

• ageing components;
• deferred replacement;
• staff fatigue;
• and rising passenger load.

Failure Propagation

Rail Disruption
→ Worker Delay
→ School Delay
→ Business Loss
→ Public Frustration
→ Trust Pressure

Worked Dependency Map: Artificial Intelligence

VISIBLE OBJECT:
AI language system
VISIBLE FUNCTION:
Generate, transform and analyse language

Ecological and Material Floor

• electricity;
• cooling;
• data centres;
• semiconductors;
• metals;
• and water.

Human Capability Floor

• mathematics;
• computer science;
• language;
• research;
• engineering;
• evaluation;
• and judgement.

Institutional Floor

• companies;
• universities;
• law;
• capital;
• standards;
• privacy rules;
• and accountability.

Network Floor

• internet;
• data;
• cloud systems;
• global supply chains;
• and user access.

Critical Path

Energy
→ Computation
→ Model Availability
→ Interface Access
→ User Interpretation
→ Reality Verification

Hidden Dependencies

• quality source material;
• human review;
• cultural context;
• and public ability to detect error.

Dependency Debt

• overreliance on opaque systems;
• reduced human skill;
• data-quality decline;
• and weak verification.

Core Risk

The visible capability may scale faster than the civilisation floors required to govern and verify it.

Worked Dependency Map: A Stage 6 Off-World Settlement

VISIBLE OBJECT:
Persistent off-world settlement
VISIBLE FUNCTION:
Human life beyond Earth

Survival Floor

• atmosphere;
• pressure;
• water;
• food;
• temperature;
• radiation protection;
• medicine;
• and waste recycling.

Material Floor

• structures;
• energy;
• tools;
• spare parts;
• fabrication;
• transport;
• and extraction.

Human Capability Floor

• medicine;
• engineering;
• agriculture;
• governance;
• education;
• psychology;
• and emergency response.

Institutional Floor

• authority;
• law;
• records;
• succession;
• resource allocation;
• conflict resolution;
• and population planning.

Network Floor

• communication;
• navigation;
• supply;
• knowledge;
• and Earth support.

Critical Path

Energy
→ Life Support
→ Water and Air
→ Human Survival

H3 Condition

The settlement remains dependent if critical supplies, repair or population continuity must come from Earth.

H6 Test

The settlement becomes an autonomous civilisational branch only when it can reproduce its critical floors without Earth.

SURVIVE
+
MAINTAIN
+
REPAIR
+
EDUCATE
+
REPRODUCE
+
GOVERN
+
ADAPT

Geographic separation is not civilisation independence.

Dependency separation is.

Single-Point Failure

A single-point failure is an object or relationship whose loss stops the wider system.

Examples include:

• one power source;
• one command centre;
• one specialist;
• one bridge;
• one supplier;
• one database;
• one water intake;
• or one political leader.

The Control Tower should mark:

SINGLE-POINT FAILURE:
Yes / No
OBJECT:
What is concentrated?
FAILURE CONSEQUENCE:
What stops?
REPLACEMENT TIME:
How long?
MITIGATION:
Redundancy / distribution / training /
stockpiling / decentralisation

Common-Mode Failure

Redundancy is not enough if all alternatives fail for the same reason.

For example:

• several servers may share one power source;
• several food suppliers may rely on the same region;
• several institutions may use the same flawed data;
• several teachers may follow the same mistaken curriculum.

This is common-mode failure.

APPARENT REDUNDANCY
but
SHARED DEPENDENCY
creates
ONE HIDDEN FAILURE POINT

The Control Tower must map shared lower floors.

Dependency Loops

Some systems depend on one another.

Education
→ produces skilled workforce
Skilled workforce
→ maintains economy
Economy
→ funds education

This can become a regenerative loop.

It can also become a decline loop.

Weak education
→ weaker workforce
Weaker workforce
→ lower productivity
Lower productivity
→ reduced institutional resources
Reduced resources
→ weaker education

Dependency loops require careful sensing because decline may reinforce itself.

Dependency Islands

A Dependency Island is a local system capable of continuing when the wider network weakens.

Examples include:

• a school with strong internal teacher development;
• a community with local food capacity;
• a hospital with backup power and supplies;
• a data archive with offline records;
• or a settlement with local repair capability.

Dependency islands can preserve continuity during wider system failure.

But they should not be confused with full independence.

They may still require eventual reconnection.

Dependency Bridges

A Dependency Bridge connects an object to a resource or capability it does not possess locally.

Examples include:

• trade;
• education;
• digital communication;
• migration;
• technical assistance;
• and external finance.

Bridges increase capability.

They also create exposure.

The Control Tower should ask:

What does the bridge provide?
How many alternatives exist?
How long can the object operate without it?
Can local capability be developed?
What happens if the relationship becomes hostile?

Buffers

A buffer absorbs interruption without immediate failure.

Common buffers include:

• reserves;
• spare capacity;
• stored food;
• backup power;
• redundant routes;
• extra staff;
• flexible time;
• and institutional trust.

A buffer is not wasted capacity.

It is stored continuity.

EFFICIENCY
removes spare capacity
RESILIENCE
preserves enough spare capacity
to survive disruption

A civilisation optimised entirely for ordinary conditions may become fragile.

Slack

Slack is uncommitted capacity available for adaptation and repair.

Examples include:

• teacher preparation time;
• hospital beds;
• budget reserves;
• spare engineering capacity;
• family time;
• or ecological recovery space.

Slack allows a system to respond to the unexpected.

A system with no slack may appear highly efficient.

It becomes unable to learn or repair.

Dependency Saturation

Dependency Saturation occurs when a supporting system is operating near its limit.

LOAD
approaches
CAPACITY
while
BUFFER
approaches zero

At saturation:

• delays rise;
• small shocks spread;
• operators improvise;
• maintenance is postponed;
• and errors become more difficult to correct.

Saturation is a P2 warning.

Dependency Thresholds

A dependency threshold marks the point at which loss changes the object’s operating phase.

For example:

Teacher shortage
below threshold:
larger classes and stress
above threshold:
course cancellation and transfer failure

The Control Tower should record:

CURRENT LEVEL
SAFE CORRIDOR
WARNING LEVEL
FAILURE THRESHOLD
RECOVERY THRESHOLD

The failure threshold and recovery threshold may differ.

A system may be easy to destabilise and slow to rebuild.

Dependency Sensors

Every critical dependency should have at least one sensor.

Examples include:

Electricity:
frequency, outages, reserve margin
Education:
attendance, transfer, error patterns,
teacher retention
Water:
quality, pressure, storage, leakage
Trust:
compliance, participation, survey trends,
institutional response
Maintenance:
backlog, failure frequency,
replacement age

The Control Tower should not rely on one sensor alone where gaming or distortion is possible.

Leading and Lagging Dependency Signals

A lagging signal appears after damage.

System failure
Exam result collapse
Infrastructure breakdown

A leading signal appears earlier.

Maintenance delay
Teacher turnover
Rising error repetition
Declining buffer
Longer response times

The Control Tower should prioritise leading signals.

Repair is cheaper before threshold crossing.

Dependency Ownership

A dependency may be widely recognised but still remain unmaintained because responsibility is unclear.

The record should state:

OWNER:
Who maintains the dependency?
OPERATOR:
Who performs daily work?
FUNDER:
Who supplies resources?
SENSOR:
Who detects drift?
REPAIR AUTHORITY:
Who can intervene?
ACCOUNTABILITY:
Who answers for failure?

Unowned dependencies tend to accumulate debt.

The Dependency Stress Test

Every major civilisation object should be tested against several disruption scenarios.

LOSS OF POWER
LOSS OF COMMUNICATION
LOSS OF KEY STAFF
LOSS OF SUPPLY
LOSS OF TRUST
LOSS OF RECORDS
SUDDEN LOAD
LONG DURATION PRESSURE
SIMULTANEOUS FAILURE

The stress test asks:

What stops first?

What remains functional?

Which buffer is consumed?

Which dependency becomes the new bottleneck?

How long can the object continue?

What is the repair route?

The Lower-Floor Restoration Sequence

When a higher capability fails, repair should begin at the lowest broken essential floor.

DO NOT BEGIN WITH:
surface performance
BEGIN WITH:
lowest failed critical dependency

The restoration sequence is:

1. Preserve life and safety
2. Stabilise material supply
3. Restore communication and records
4. Restore human operators
5. Restore institutional coordination
6. Reconnect networks
7. Restart visible capability
8. Verify transfer and regeneration

This prevents expensive attempts to restart an upper system while its foundation remains broken.

Education as a Universal Dependency Floor

Education appears repeatedly inside advanced civilisation dependency maps.

It supplies:

• language;
• mathematics;
• scientific reasoning;
• professional skill;
• judgement;
• institutional memory;
• and successor training.

A civilisation may import equipment.

It cannot indefinitely import all capability.

Eventually, local operators must understand enough to:

• maintain;
• diagnose;
• adapt;
• repair;
• and teach.

This is why EducationOS is not only a social service.

It is a civilisation dependency floor.

NO EDUCATION
→ no reliable successor capability
NO SUCCESSOR CAPABILITY
→ no maintenance or repair
NO MAINTENANCE OR REPAIR
→ advanced systems become temporary assets

The eduKateSG Dependency Spine

The education-to-civilisation dependency spine can be written as:

VocabularyOS
supports
precise meaning
LanguageOS
supports
access and communication
MemoryOS
supports
retention and retrieval
MathOS
supports
structure and measurement
ScienceOS
supports
evidence and causal testing
EducationOS
integrates and transfers
capability
FamilyOS
supports
early continuity and participation
WorkOS
applies
capability
ProductionOS
embeds
capability into civilisation output
GovernanceOS
coordinates
shared systems
RealityOS
detects
drift
StrategizeOS
routes
repair
HistoryOS
preserves
the result
EducationOS
teaches
the lesson forward

Each layer depends on the earlier ones without being reducible to them.

The Reader-Facing Dependency Card

A visible page may display:

WHAT THIS DEPENDS ON
Critical:
Power, trained staff and control systems
Hidden:
Maintenance time and institutional memory
Main bottleneck:
Specialist technical expertise
Current pressure:
Rising load
Buffer:
Redundant routes and spare capacity
Failure spreads into:
Transport, work and public trust
Repair begins with:
Restoring the lowest broken dependency

This is enough to expose the lower floor without overwhelming the reader.

Control Tower Dependency Views

The future Control Tower interface should offer several views.

Floor View

Shows the layered support structure.

Critical Path View

Shows the indispensable dependency chain.

Bottleneck View

Shows the narrowest point.

Debt View

Shows what is being consumed without renewal.

Buffer View

Shows stored resilience.

Time-Horizon View

Shows immediate, short, medium and generational dependencies.

Failure-Propagation View

Shows where breakdown travels.

Restoration View

Shows the order in which floors must be repaired.

Dependency Map Runtime

SELECT OBJECT
→ identify visible function
→ locate minimum viable function
→ map direct dependencies
→ expand indirect dependencies
→ classify criticality
→ identify substitution options
→ detect bottlenecks
→ measure buffers
→ identify dependency debt
→ test failure scenarios
→ determine restoration sequence
→ connect to repair operators

AI Extraction Box

OBJECT:
CIVILISATION.ATLAS.DEPENDENCY.FLOOR.v1.0
PURPOSE:
Map the lower systems,
resources, capabilities and relationships
required for a civilisation object
to remain functional.
CORE LAW:
The highest visible capability
is only as secure as the lowest
essential floor beneath it.
DEPENDENCY LAYERS:
1. Ecological and Biological
2. Material and Energy
3. Human Capability
4. Institutional and Administrative
5. Network and Coordination
6. Visible Civilisation Capability
DEPENDENCY TYPES:
Survival
Functional
Scaling
Legitimacy
Regenerative
DEPENDENCY ATTRIBUTES:
Direct / Indirect
Visible / Hidden
Critical / High / Moderate / Low
Substitutable / Non-Substitutable
Concentrated / Distributed
Immediate / Short / Medium / Generational
Fast / Slow failure velocity
CORE MEASURES:
Dependency Depth
Dependency Width
Dependency Velocity
Dependency Visibility
Dependency Debt
CRITICAL PATH:
The shortest chain of indispensable
dependencies connecting the visible object
to its lowest viable floor.
DEPENDENCY DEBT:
Maintenance Debt
Capability Debt
Trust Debt
Ecological Debt
RESILIENCE OBJECTS:
Buffers
Slack
Redundancy
Dependency Islands
Dependency Bridges
Substitution Routes
FAILURE OBJECTS:
Single-Point Failure
Common-Mode Failure
Bottleneck
Saturation
Threshold Crossing
Cascade
RESTORATION RULE:
Repair the lowest broken
essential dependency before attempting
to restart the upper capability.
EDUCATION RULE:
EducationOS is a dependency floor
for every advanced civilisation system
that requires skilled operators,
maintenance, judgement, adaptation
and successor training.
FINAL LOCK:
Advanced civilisation does not escape
dependency.
It deepens, widens and reorganises it.
The Control Tower must therefore
map not only what civilisation can do,
but what must remain true underneath
for that capability to continue.

Final Lock

Civilisation is easiest to admire at the top.

It is safest to understand from the bottom.

The visible system may be:

• a hospital;
• a railway;
• an artificial intelligence platform;
• a school;
• a city;
• a nation;
• or an off-world settlement.

But beneath every visible capability are lower floors carrying:

• life;
• materials;
• energy;
• skill;
• memory;
• records;
• institutions;
• networks;
• trust;
• and repair.

The dependency map asks:

WHAT MUST REMAIN TRUE?
WHAT IS BEING TAKEN FOR GRANTED?
WHAT CANNOT BE REPLACED QUICKLY?
WHERE IS THE BOTTLENECK?
WHICH BUFFER IS SHRINKING?
WHAT DEBT IS ACCUMULATING?
HOW FAST WILL FAILURE SPREAD?
WHERE MUST REPAIR BEGIN?

A civilisation does not become independent by adding higher floors.

It becomes more dependent on its lower floors remaining valid.

A planetary network still depends on food.

An artificial intelligence system still depends on human knowledge.

A hospital still depends on water.

A government still depends on legitimacy.

A school still depends on language.

A frontier settlement still depends on education.

The Control Tower becomes useful when it can look beneath the impressive surface and reveal the actual continuity structure.

The complete route is:

IDENTIFY THE VISIBLE CAPABILITY
→ OPEN THE SUPPORTING FLOORS
→ FIND THE CRITICAL PATH
→ IDENTIFY THE BOTTLENECK
→ MEASURE BUFFER AND DEBT
→ TEST FAILURE PROPAGATION
→ RESTORE THE LOWEST BROKEN FLOOR
→ RESTART THE UPPER CAPABILITY
→ VERIFY REGENERATION

Civilisation survives from the bottom upward.

The Dependency Floor and Critical Path Map makes that truth visible.