From 80d9ccf3832d8a5ae667758351b5d1cefb3ce178 Mon Sep 17 00:00:00 2001
From: wellspringcp <69349872+wellspringcp@users.noreply.github.com>
Date: Sat, 10 Oct 2020 17:20:02 +1100
Subject: [PATCH] Update 07-2-sovereign-war-infrastructure-apologia.md

---
 07-military/07-2-sovereign-war-infrastructure-apologia.md | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/07-military/07-2-sovereign-war-infrastructure-apologia.md b/07-military/07-2-sovereign-war-infrastructure-apologia.md
index e299594..0c78610 100644
--- a/07-military/07-2-sovereign-war-infrastructure-apologia.md
+++ b/07-military/07-2-sovereign-war-infrastructure-apologia.md
@@ -6,7 +6,3 @@ To expound further on this constraint, here are some examples of how it might be
 
 - If a dam must be built, `SovWI` should prefer to reserve and purchase the land and river-course natureses and rent them out, and put out a public tender contract for the construction and maintenance of a dam on those natureses contingent on the condition that the contract awardee will also bind itself to service-level agreement contracts and other legally binding agreements with the government to ensure the dam meets whatever parameter war-readiness requires.
 - If a telecommunications bearer backbone network must be constructed, `SovWI` should prefer a similar approach, purchasing the title to the natureses along the distance the network infrastructure will cover, and then renting them out using public tender contracts and binding the awardee to meet the service level constraints required for war-readiness.
-
-## Backbones; not fully built infrastructure
-
-This is likely to be needed when building military forts, bases and other things which cannot be contracted out to the private sector. It is limited to those products, services and infrastructure which are purely military in nature.