adding proposed web app flow docs

tat_requirements/introduction.md

@@ -263,15 +263,13 @@ simple as a record id, and some will be fairly interesting json data structures.
 
 1. The web app API does the tasks specified by the REST request and the work flow engine's directions.
 
-    * Every http request must go through the work flow engine so that the work flow is validated and
-    managed. 
+  * Every http request must go through the work flow engine so that the work flow is validated and managed.
     
-    * Every web app has a work flow, but people mostly just cobble that together with a bunch of implied
-functionality using conditionals and side-effect-full function calls. In our code, the internal API is 100%
-work flow agnostic. 
+  * Every web app has a work flow, but people mostly just cobble that together with a bunch of implied
+    functionality using conditionals and side-effect-full function calls. In our code, the internal API is
+    100% work flow agnostic.
 
-    * I can explain this in more detail, but it makes a huge improvement in the structure of the
-application.
+  * I can explain this in more detail, but it makes a huge improvement in the structure of the application.
 
 1. Create the output data object if it wasn't created by the functions doing the work.