A model for explaining how courier time, relay density, verification delay, and command visibility reshape coordination, legitimacy, and operational response.
A system changes shape when messages, verification, and response do not travel at the same speed as the events they must govern.
Read when
Use this when a concrete mechanism in Capability Regimes needs to behave coherently instead of only sounding plausible.
IntermediateRead next
Read Administrative Load first, then return here once the surrounding concept stack is clear.
Systems rarely operate at the speed of the map. They operate at the speed of message movement, verification, and release authority. The communication latency regime makes those delays explicit.
This is useful because delayed communication changes more than convenience. It changes who can improvise, how much legitimacy a center retains, and whether reserves or repairs arrive in time to matter.
The regime becomes especially important when transport and command no longer share the same tempo. Supplies may still move, but if decisions lag behind them the system starts acting on stale pictures of itself.
Four layers inside a communication latency regime.
Axis
Question
Signal
Courier speed
How fast can orders and reports move between key nodes?
Relay horses, signal towers, packet routes, secure channels, jump-gate relays
Verification delay
How long until information is trusted enough to act on?
Double reporting, seals, bureaucracy review, sensor confirmation, witness lag
Release authority
Who can spend reserves or redirect force without waiting?
Delegated governors, local commanders, reserve keys, emergency mandates
Coordination drift
What mismatch appears while actors are waiting on the same event?
Duplicated effort, stale orders, delayed relief, rumor authority, local bargaining
Use the model when a state, faction, or platform claims wide reach but seems strangely slow or brittle in practice. The fastest check is whether crisis pace is faster than message pace. If it is, local actors start governing by improvisation, stockpiles are released too late, and legitimacy becomes uneven.
The reusable lesson is that control depends on response time, not only on territorial claim. Model communication latency whenever you need to explain why a large system governs unevenly, releases aid late, or fractures into local initiative under stress.
Continuation map
Leave this page through one clear next step.
Check the prerequisite, the strongest relation role, and the next route after the reading is complete.
Before this entry
2 prerequisites to read first
Start with Administrative Load and then return here once the surrounding concept stack is clear.
Read firstRelation map
3 typed paths across 2 continuation roles
These entries clarify the footing underneath the current node before you move outward again. Start with Administrative Corridor when you want the clearest next role.
Foundation 2 · Apply 1Next move
Open Frameworks
Return to broader lenses when this model is too specific for the question you are asking.
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.
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.
