Document library architecture

It'd be nice if the lib had some docs (maybe in a form of a graph), describing its architecture at different levels of detail, including:

* components present within the lib
* their functionality, semantics and interfaces (not class interfaces, but what it consumes and produces)
* components' interactions to other components and flows of data between them
* possibilities to replace that component with something else, both other implementations of the same thing and implementations of completely different thing that may have similar effect
* why each component is needed and if it is avoidable and impact of it being skipped or replaced