Administrative load is the cost of keeping a system legible and governable: tax collection, records, law, communication, provisioning, supervision, and enforcement.
It rises with distance, fragmentation, conflict, and infrastructural weakness. It falls where routes are reliable, institutions are dense, and local conditions are easy to standardize.
Many worlds assume that large territory automatically means strong rule. Administrative load explains why the opposite is often true: beyond a certain point, more territory can mean more drag than more power.
Administrative load is not just generic difficulty or evidence of bad rulers. It refers to the cumulative work of keeping a system legible, synchronized, and enforceable once territory, obligations, and institutional layers start multiplying.
If adding territory, offices, or legal obligations increases coordination work faster than it increases usable output, administrative load is rising faster than state capacity.
The term is most useful when paired with a specific mechanism such as road delay, ledger complexity, language fragmentation, or delegated enforcement. Naming the load source prevents governance problems from reading like generic incompetence.
Typical signals include backlogs, delayed decrees, inconsistent records, and rising dependence on local brokers to keep central obligations functioning at all.
A frontier province that yields new taxes but requires far more escorts, translators, audits, and exception handling than the core is increasing administrative load faster than it is increasing usable state strength.
That mismatch matters because the apparent gain can still weaken the system overall. The province adds obligations faster than the center can standardize, monitor, and service them.
The added territory becomes a coordination bill before it becomes usable power.
That is the point where scale starts behaving like drag instead of leverage.
Glossary entries define Spcent's shared vocabulary. They are conceptual anchors designed to stabilize how an abstraction is used across pages and modules.
Glossary
Reading use
Read for precision
A glossary term should lock down what a phrase means so later reading is not burdened by ambiguity.
Use glossary entries as entry points
When you know the concept but not yet the best framework or model, start here and then move outward through related nodes.
Glossary should connect outward
A useful definition points toward the frameworks, models, and studies that actually use the term in context.
Send entry feedback with this page already attached.
Use these links for corrections, missing examples, worksheet requests, or confusing sections. Each link includes the current URL, slug, kind, and Program.
Report correction
Flag a factual issue, unclear claim, typo, or outdated passage.
