Core idea

Urban hierarchy is not just size ranking. It is the uneven distribution of transport, storage, governance, and coordination roles across settlements. A relay settlement, depot city, port hub, and capital may all be large, but they do different structural work.

This model helps when a world has many named cities yet cannot explain why one is indispensable, why another is rich but politically weak, or why a third is administratively heavy but commercially thin.

Differentiate nodes by role before size

Role 1Relay settlement

Small but indispensable places that keep movement stitched together through storage, escorting, or crossing services.

Role 2Market town

Nodes that aggregate nearby production and translate local surplus into wider exchange.

Role 3Depot city

Cities whose power comes from buffering, warehousing, and redistribution rather than ritual prestige alone.

Role 4Port or gateway hub

Nodes that dominate because routes or transport layers convert there at unusual scale.

Role 5Capital

Cities that carry coordination, legitimacy, and administrative burden beyond their own immediate market footprint.

Diagnostic frame

Axis	Question	Signal
Relay settlement	What keeps movement alive here?	Crossing point, waystation, fodder market, caravan repair, garrison escort
Market town	What nearby production does this node aggregate?	Weekly exchange, rural intake, tax collection, craft conversion, merchant mediation
Depot city	How much reserve and redistribution load does it hold?	Granaries, warehouses, barracks, arsenals, fiscal offices
Gateway hub	Which route layers convert here?	River-sea transfer, pass mouth, canal lock, estuary customs, lift point
Capital	What coordination burden makes this node politically exceptional?	Court, archives, command chain, ceremonial legitimacy, administrative ministries

Removal test

One useful test is to remove a node and ask what disappears with it. If closing a port only delays trade slightly, it was never really a gateway hub. If losing a depot city immediately breaks military pacing and market confidence, that node was carrying far more than local population size suggests.

Why hierarchies drift over time

Urban hierarchy is not static. Relay towns can become gateway hubs when one border opens, capitals can weaken if coordination moves elsewhere, and depot cities can become politically decisive when reserve burden rises faster than ceremonial prestige. The model therefore helps explain not only what a city is now, but why its role changes under new transport, migration, or administrative conditions.

That makes hierarchy a moving systems question rather than a fixed population ranking. Cities rise or fall when the work they do for the wider network changes.

Transfer value

The reusable lesson is that city systems feel more believable when each important node has a structural job. Once the hierarchy is explicit, urban inequality, capital relocation, depot vulnerability, and migration stress all become easier to reason about.

The model also keeps revision work disciplined. Instead of making every large city do everything, it asks which node is paying for coordination, which one is buffering flow, and which one only looks important because of population scale. That usually produces cleaner maps and more believable urban rivalry. It also clarifies why certain cities fear losing rank.

Relation Map

Urban-node continuations

Migration Corridor Model

Use this when repeated movement is thickening or destabilizing specific nodes along one corridor.

River Port Polity

Use this as a case for gateway dominance, storage load, and political coordination concentrated inside one port-centered hierarchy.

Relay Settlement

Use this when the first problem is distinguishing the smallest indispensable nodes from larger but less strategic towns.