If `|` is going to be used as a separator we need to enforce that sort of behavior elsewhere. There needs to be a guard against a valid but unusual hierarchy value being read and completely exploding. For instance, in the above situation where `/` was being used as a field separator, `|` could be forseeably used instead with a non-filesystem based backend. Generally the use of `|` is just too magical for my comfort.