Loading this page.
Preparing content, navigation, and supporting references for this route.
Preparing content, navigation, and supporting references for this route.
A model for comparing what different factions actually control across territory, movement, institutions, storage, and legitimacy rather than by abstract power labels.
Use this when a concrete mechanism in Conflict And Operations needs to behave coherently instead of only sounding plausible.
IntermediateRead Administrative Load first, then return here once the surrounding concept stack is clear.
Administrative LoadActors rarely control everything in the same way. One faction may hold roads, another tax depots, another command symbolic legitimacy, and another dominate mobile force.
The control surface matrix compares actors across these different control surfaces instead of reducing them to one power score. This helps explain why formally weaker actors can still govern chokepoints, why legitimate actors may lack logistical reach, and why territory alone rarely tells the full story.
Distinguish what an actor officially owns from what it can patrol, tax, staff, and defend reliably.
Score each actor across movement, storage, institutions, legitimacy, and territorial continuity rather than collapsing them into one rank.
Pay special attention when an actor is strong on one surface but weak on another, because that is often where crises begin.
| Axis | Question | Signal |
|---|---|---|
| Territory | Where can the actor impose continuous rule? | Fortified cores, tax districts, routine patrol reach |
| Movement | Which routes can the actor protect, close, or tax? | Passes, crossings, convoy corridors, customs mouths |
| Storage | Where does the actor control buffering and inventory visibility? | Granaries, depots, docks, reserve yards |
| Institution | Which administrative or judicial systems does the actor steer? | Clerks, courts, governors, levy systems |
| Legitimacy | What part of rule depends on recognition rather than coercion alone? | Dynastic claims, civic trust, ritual authority, alliance credibility |
Most unstable political systems are not weak everywhere. They are uneven. An actor may control the capital and court ritual while another controls frontier roads or grain depots. The matrix makes these asymmetries visible enough to reason about.
That visibility is useful because political conflict often comes from trying to convert one kind of control into another. Storage becomes leverage over institutions, legitimacy becomes access to taxation, and route control becomes effective sovereignty.
Explains why actors controlling wide surfaces may still govern them unevenly.
Frontier Chokepoint LedgerShows where movement control concentrates into a few decisive frontier assets.
Surplus Capture LadderShows how storage and taxation surfaces convert into durable political leverage.
The reusable lesson is that power should be compared by control shape, not just by abstract size. Use the matrix for states, factions, guilds, alliances, insurgencies, or any setting where rule is layered and contested.
Check the prerequisite, the strongest relation role, and the next route after the reading is complete.
Start with Administrative Load and then return here once the surrounding concept stack is clear.
Use Civilization Pressure Map or the linked entries below when you want to compare this page against neighboring work.
Return to broader lenses when this model is too specific for the question you are asking.
Use this appendix when you want to continue by program branch or operating scale after the page has been read.
Explain how legitimacy, coercion, administrative reach, frontier bargaining, and elite control are structured.
Start with the pressure map, locate legitimacy and capture mechanisms, validate against a frontier or state case, then run a governance stress test.
Explain how resources, goods, labor, information, and force circulate, stall, buffer, and break.
Start from the flow architecture framework, test circulation fragility and reserve depth, compare one logistics study, then run a flow audit worksheet.
Use this scale when the strongest explanation depends on several levels staying visible together.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use prerequisites when you want the shortest path into the assumptions this page depends on.
The cumulative burden of governing, coordinating, recording, supplying, and enforcing order across a territory or institution.
Read firstSurplus Capture LadderA model for how raw surplus becomes taxable, storable, and politically controllable through successive layers of capture.
This entry still relies on generic related links. That works as a fallback, but typed relation roles would make continuation clearer.
A framework for tracking expansion, consolidation, frontier friction, and institutional fatigue across a civilizational space.
AdjacentFrontier Chokepoint LedgerA framework for tracking which passes, ports, narrows, and crossings decide political leverage at the edge of a system.
AdjacentAdministrative LoadThe cumulative burden of governing, coordinating, recording, supplying, and enforcing order across a territory or institution.
AdjacentSurplus Capture LadderA model for how raw surplus becomes taxable, storable, and politically controllable through successive layers of capture.
Models formalize behavior. Use them when you need a concrete chain, loop, stress scenario, or layered mechanism that can be tested and reused.
| Models | Reading use |
|---|---|
| Read for mechanism | A model should explain how something behaves over time or under pressure, not just identify a broad topic area. |
| Use models to pressure-test a draft | When a setting feels plausible at rest but still behaves vaguely, models provide the explicit structure needed to test it. |
| Models bridge frameworks and studies | A strong workflow often moves from broad lens to formal model to applied case reading. |
Keep these collapsed until you want an active reading exercise.
What mechanism is this model making explicit?
modelWhere does this model break or become most interesting under stress?
modelWhich study would verify whether this model survives in a complete setting?
modelThese routes are tuned to the kind of entry you are currently reading, so you can leave this page with one deliberate next move.
Return to broader lenses when this model is too specific for the question you are asking.
Return to broader lenses when this model is too specific for the question you are asking.
Move through the systems module when you want to navigate models by design intent.
Verify the model inside applied cases where multiple structures interact at once.
Use these links for corrections, missing examples, worksheet requests, or confusing sections. Each link includes the current URL, slug, kind, and Program.
Flag a factual issue, unclear claim, typo, or outdated passage.
EmailFlag a broken route, missing media asset, or relation that leads nowhere.
EmailAsk for a proof case, comparison, glossary term, or missing related entry.
EmailRequest a guide output, checklist, audit pass, or creator-facing worksheet.
EmailPoint to a section that needs a clearer explanation or stronger handoff.
Email