It's actually a tri-state variable.  The value theoretically could be `nil` if `init` function on the service weren't invoked by the time this line is reached -- although practically this shouldn't happen.  The value would only get set to true or false if the value were set from the return from the `thrown-with-msg?` call in the `init` function.  Arguably, I could have just initialized the atom to false and only assert that the value is reset to true at the end.  This was just a sanity check to see that my `init` implementation in my service was being used.