Use-case specific naming in Tree

I would prefer if the `Tree` type, module, and function used language that was use-case agnostic. Instead, for example, the function that returns the root of the tree is called `outcome`.