anchor.diff:  Mocking must be done in the context of a specification, and creates a scope for all sub-outlines. Generally
   you want to isolate mocking to a specific behavior:
   
  -```
  +[source]
  +----
  +(:require
  +  [untangled-spec.core :refer [specification behavior when-mocking assertions])
  +
   ;; source file
   (defn my-function [x y] (launch-rockets!))
   ;; spec file
  
positive.code: On occasion you'd like to mock things that use callbacks. Chains of callbacks can be a challenge to test, especially
  when you're trying to simulate timing issues.
  
  ```
  (def a (atom 0))
  
  (specification "Some Thing"
  
negative.code:       ;;actual test
        (assertions
          (my-function 3 5) => true))))
  ----
  
  Basically, you include triples (a form, arrow, form), followed by the code & tests to execute.
  
  