adding mines

microservices/LocationsApi/README.md

@@ -28,26 +28,28 @@ locations are unowned `Open` records until claimed by a player.
 
 Player resource state is stored server-side in the `PlayerResources` collection.
 New players start with 100 gold. A player's headquarters generates 10 gold per
-minute. Log Camps generate wood. Generation is applied lazily when the resource
-record is read.
+minute. Log Camps generate wood and Mines generate ore. Generation is applied
+lazily when the resource record is read.
 
 ## Units
 
 Unit training is stored server-side in the `UnitTraining` collection. The first
 unit type is `Scout`, which costs 50 gold and takes 60 seconds to train.
 Finished training is completed lazily when unit state is read. Claiming an
-unclaimed visible location consumes one completed Scout.
+unclaimed visible location consumes one completed Scout by deleting that Scout's
+training record.
 
 ## Buildings
 
-Buildings are stored on location records. The first building type is `LogCamp`,
-which can be built on controlled Forest territory, takes 60 seconds to build,
-and adds 5 wood per minute to the owning player's resource generation after it
-finishes. Each location has one building slot; a building under construction
-occupies that slot.
+Buildings are stored on location records. `LogCamp` can be built on controlled
+Forest territory, takes 60 seconds to build, and adds 5 wood per minute after it
+finishes. `Mine` can be built on controlled Ore territory, takes 60 seconds to
+build, and adds 5 ore per minute after it finishes. Each location has one
+building slot; a building under construction occupies that slot.
 
 Timer settings are stored in the MongoDB `GameSettings` collection and are
 seeded on first read:
 
 - `ScoutTrainingSeconds`
 - `LogCampBuildSeconds`
+- `MineBuildSeconds`