Create the initial commands to act as framework for the project
TG-1 #in-progress
Architecture
I am using a Command pattern to denote all of the things that can be done from the initial program loop. Ultimately I envision these as being completely stateless items that will act on the current game state in predictable and repeatable ways.
I have an open question about what persistence mechanism I'm going to use. I am currently leaning toward the Unix everything-is-a-file philosophy, using yml or json or some other mostly-human-readable format in order to facilitate easy understanding of what's happening as well as portability of the game state into other systems.