Expand the database section to competing paradigms

Our problem domain specifically covers *all* of these paradigms. Some of our data is naturally graphs (e.g. social networks, economic networks); some is tabular (summary stats about economic activity); much is in maps; and still others sits most naturally in objects.

Generally there are ways to fudge any paradigm inside of any other paradigm; e.g. a graph can be stored in SQL with two tables, "edges. I think our approach should allow the model writers to use whatever is natural **for them**, and that we should make heavy use of converters to make actually working with the data fluid.