Preparing the current spcent route.
The page shell is online. Shared content and route data are still being assembled.
The page shell is online. Shared content and route data are still being assembled.
The usable interval in which a pressured line, district, or campaign can still rotate people, reserves, or command attention before fatigue and exposure harden into structural loss.
A rotation window is the span of time in which a pressured force, garrison, convoy chain, or defended district can still cycle personnel, reserves, or command attention before exhaustion becomes harder to reverse than the original pressure.
The term matters because many systems do not fail the moment they are attacked or overtasked. They fail when the interval for orderly relief becomes too short to keep pace with burn rate.
Campaigns, sieges, and frontier systems often look sustainable right up until their rotation window closes. Supplies may still exist. Reinforcements may still exist. But if rest, repair, and reserve substitution cannot arrive inside the remaining interval, the system begins consuming itself faster than it can recover.
That is why rotation windows are often more decisive than raw stock totals. A force with modest reserves but a durable rotation window may outlast a richer force that cannot cycle its burden in time.
| Axis | Question | Signal |
|---|---|---|
| Burn rate | How quickly does the active line exhaust people, matériel, or command capacity? | Casualty tempo, sleep debt, ammo burn, repair queue, decision backlog |
| Relief timing | How long does it take replacement capacity to arrive and take over? | Reserve travel, convoy protection, road repair, docking slot, handoff lag |
| Exposure cost | What happens while the handoff is being attempted? | Open flank, overloaded checkpoint, convoy visibility, weakened district patrol, delayed escort |
| Closure point | At what point does missed rotation stop being recoverable? | Runaway fatigue, abandoned posts, discipline breakdown, attrition spiral, permanent retreat |
A rotation window is not just the existence of reserves somewhere in the theater. It is the usable interval in which relief, rest, repair, and substitution can still arrive before fatigue becomes harder to reverse than the original pressure.
If a line still looks defensible on paper but can no longer rotate crews, reserves, or command focus before fatigue compounds, its rotation window has closed.
The main signs are missed handoffs, rising sleep debt, skipped repairs, overloaded reserve travel, and decisions that are now being made too late to prevent cumulative burn.
A fleet may still have escorts and fuel, yet lose its rotation window if damaged ships, exhausted crews, and command staff cannot cycle out before the next pursuit contact arrives.
Places rotation inside the larger question of projection, holding burden, relief timing, and operational decay.
Exhaustion Rotation CycleTurns the term into a reusable mechanism for testing when relief, rest, and reserve substitution can still keep pace with burn.
Battlestar Galactica Fleet Survival LogisticsApplies the term to a moving survival system where every damaged ship, escort task, and crew cycle narrows the remaining rotation window.
Read what should come before it, what relation role matters next, and where this page should hand you off after the local graph is clear.
Start with Force Projection Window and then return here once the surrounding concept stack is clear.
These entries clarify the footing underneath the current node before you move outward again. Start with Operations Pressure Framework when you want the clearest next role.
Many glossary abstractions become richer when viewed inside the spatial module.
5 handoff nodes stay inside Conflict And Operations. 4 handoff nodes share Regional.
Detail pages now expose the branch and scale of their surrounding graph before showing raw prerequisite and relation shelves, so continuation can stay taxonomy-led instead of adjacency-led.
Explain campaigns, sustainment, force projection, defensive depth, and operational windows as structural systems.
Start with sustainment and projection models, identify the theater cycle, validate through an operational case, then run an operations stress test.
Use this scale when the region is the main leverage unit for settlement, extraction, governance, or conflict.
Use this scale when the whole world model or planetary constraint pattern should stay visible at once.
Use prerequisites when you want the shortest path into the assumptions this page depends on.
A model for how far and how long force can be projected effectively before supply, delay, terrain, and recovery costs collapse performance.
A model for how supply, reserve depth, reinforcement timing, route security, and recovery windows determine whether force projection remains real or collapses after contact.
These groups explain why each neighboring node matters, whether it stabilizes the concept, operationalizes it, proves it, or pushes the lane further.
Use foundation relations when this node depends on a concept, term, or framing layer that should be explicit before you branch further.
A framework for reading campaigns, patrol regimes, relief pushes, and theater control through projection, sustainment, tempo, recovery, and control burden rather than battle moments alone.
Use operationalizing relations when you want the current abstraction rendered as a cleaner model, loop, or structural device.
A model for how operational tempo, unit fatigue, reserve cycling, relief timing, and recovery depth determine whether a force stays coherent over repeated pressure or degrades into local crisis management.
Use applied relations when the next useful move is to see the current pattern survive inside a study or assembled world.
A fiction study of how moving civilian survival, escort pressure, repair scarcity, and relief timing turn Battlestar Galactica into a logistics-and-rotation system rather than a fleet combat story alone.
These entries still matter, but they currently rely on generic adjacency instead of typed continuation semantics.
A model for how far and how long force can be projected effectively before supply, delay, terrain, and recovery costs collapse performance.
Glossary entries define Spcent's shared vocabulary. They are conceptual anchors designed to stabilize how an abstraction is used across pages and modules.
A glossary term should lock down what a phrase means so later reading is not burdened by ambiguity.
When you know the concept but not yet the best framework or model, start here and then move outward through related nodes.
A useful definition points toward the frameworks, models, and studies that actually use the term in context.
Keep these collapsed until you want to turn the page into an active reading exercise.
What question becomes easier once this term is precisely defined?
Which entries in the graph are using this abstraction operationally rather than only naming it?
Do I need a framework, model, or study next to see this concept in action?
These routes are tuned to the kind of entry you are currently reading, so you can leave this page with one deliberate next move.
Many glossary abstractions become richer when viewed inside the spatial module.
Many glossary abstractions become richer when viewed inside the spatial module.
Cross-layer moveMove into frameworks when you want a planning lens built on top of the term.
Cross-layer moveSearch across the graph to find every place the concept currently appears.