Loading this page.
Preparing content, navigation, and supporting references for this route.
Preparing content, navigation, and supporting references for this route.
A model for how far and how long force can be projected effectively before supply, delay, terrain, and recovery costs collapse performance.
Use this when a concrete mechanism in Conflict And Operations needs to behave coherently instead of only sounding plausible.
IntermediateRead Corridor first, then return here once the surrounding concept stack is clear.
CorridorForce projection is not binary. It happens inside a window defined by time, distance, route reliability, and recovery capacity.
Outside that window, the same army or organization may still move, but it no longer converts movement into durable combat effectiveness. The model is therefore about sustained useful pressure, not just about raw ability to arrive somewhere once.
Ask how route length, escorts, and interruptions reduce the force before it even arrives.
Track how long supplies, replacement depth, and command coherence can keep pressure active.
Identify whether depots, hospitals, repair chains, or reserve nodes can reopen the window after losses.
| Axis | Question | Signal |
|---|---|---|
| Distance | How far can force travel before it loses coherence? | Route length, escort need, transit friction, reinforcement lag |
| Duration | How long can pressure be sustained? | Food, ammunition, rest cycles, replacement depth |
| Terrain | How much does the map compress or degrade force? | Passes, rivers, mud season, chokepoints, enclosure |
| Recovery | How quickly can force restore its ability to act? | Depot depth, secure fallback nodes, command continuity, medical or repair capacity |
Projection windows usually close gradually before they close catastrophically. Convoy drag increases, reinforcement takes longer, terrain starts dictating timing, and the system shifts from pressure to mere presence. When that tipping point is missed, actors mistake movement for real control.
This is why routes and depots matter more than abstract range. The farther force travels from its buffer chain, the more the window shrinks from both ends: arrival gets harder and recovery gets slower.
The reusable lesson is that military or policing reach should be evaluated as a sustainment window rather than a radius on paper. This makes the model useful for campaigns, frontier governance, convoy warfare, and any system where pressure must be maintained instead of merely declared.
Check the prerequisite, the strongest relation role, and the next route after the reading is complete.
Start with Corridor and then return here once the surrounding concept stack is clear.
Use Frontier Chokepoint Ledger 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 topology, region graphs, corridors, map abstraction, and scale determine movement and leverage.
Start in Spatial, reduce the map into region graph and corridor logic, test topology under disruption, then return through a spatial design guide.
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.
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.
Use this scale when routes, relays, buffers, and linked nodes matter more than territorial bulk.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use this scale when the strongest explanation depends on several levels staying visible together.
Use prerequisites when you want the shortest path into the assumptions this page depends on.
A durable movement spine where terrain, settlement, exchange, and repeated transit align strongly enough to guide long-run circulation.
Read firstStorage NodeA location where flow is buffered, accumulated, protected, measured, or redirected strongly enough to change who can control the wider system.
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 which passes, ports, narrows, and crossings decide political leverage at the edge of a system.
AdjacentTopology Stress TestA model for testing how a spatial layout behaves under congestion, disruption, seasonal shifts, and asymmetric pressure.
AdjacentSettlement Corridor StackA layered model for understanding how roads, rivers, passes, and market towns align into durable spatial corridors.
AdjacentStorage NodeA location where flow is buffered, accumulated, protected, measured, or redirected strongly enough to change who can control the wider system.
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