Improve developer documentation
I am under the impression that for contributors (developers) who do not already know it is still too hard to understand what gitlab-workhorse does and how it does it.
As long as you don't need to know I think it is great if gitlab-workhorse is a black box that just sits there and does stuff. But for people who do want to know we should have some way to ramp up their understanding (short of reading the code). I want contributors, developers, support engineers to be able to reason about what gitlab-workhorse does.
cc @nick.thomas