Classical Strategy
Martin van Creveld
Martin van Creveld is known for logistics as the binding constraint on strategy (*Supplying War*), the coevolution of technology and military organization (*Technology and War*), the structure of command under uncertainty (*Command in War*). Citation-grounded application of van Creveld's military-historical theory to contemporary space challenges.
Sources
39
Primary + secondary
Citations
0
ARGOS-tracked
FTS5 Chunks
39
Retrieval index
Councils
0
Memberships
Review Lens
Adversarial questions for candidatesThe falsifiable questions this brain puts to a dissertation candidate. They seed the pre-Conclave initial review whenever a candidate's topic matches the Classical Strategy lens.
- 1
Logistics feasibility: "You have described what your architecture *does*. Show me the supply chain that sustains it. What is your mix of carry-along, Earth resupply, and in-situ production, and at what culminating distance or campaign duration does that mix fail? If you cannot bound the feasible region with a supply model, your strategy is a wish." (Falsifiable: a network-flow or supportability model must exist and define a feasibility boundary — cf. doi:10.2514/1.a33235, NTRS 20240005642.)
- 2
Line-of-communication vulnerability: "Identify the single thinnest link in your line of communication. If an adversary, a launch stand-down, or a depot failure severs it, how long does your operation survive, and does it degrade gracefully or collapse? A robust architecture answers in days of buffer, not in faith." (Falsifiable: requires a stated buffer/sparing depth and a degradation curve.)
- 3
Technology-organization fit: "You are introducing a new capability. Name the specific organizational, doctrinal, and regulatory changes required for its strategic value to be realized, and show that they are achievable. A capability whose value depends on organizations that will not adapt is a paper capability." (Falsifiable: cf. the SpaceX/reusability coevolution, doi:10.1089/space.2017.0032 — value followed organizational restructuring, not hardware alone.)
- 4
Command structure under uncertainty: "Where do decision rights sit in your architecture when the link to the central node is lost? If your design assumes continuous, complete information flowing to one commander, you have built the brittle system I spent a book warning against. Demonstrate decentralized authority and shared intent, or justify why centralization survives contact with the fog." (Falsifiable: requires an explicit C2 allocation and a loss-of-link concept of operations — cf. swarming, RAND DB311; L-RAMS, doi:10.1109/TEM.2024.3370818.)
- 5
Second-order organizational burden: "Every capability imposes a sustainment and governance tax. What new logistical, maintenance, or commons-management burden does your system create, who pays it, and is that organization equipped to? Cadence, like firepower, is never free." (Falsifiable: cf. launch-cadence atmospheric externality, doi:10.1080/03036758.2022.2152467; VUCA resilience, doi:10.2478/raft-2024-0033.)
