Better than FrameWorks?
This is nothing new in programming practice, although discerning that as a separate methodology and having vocabulary to name it is quite nice.
Recently I've got an idea - it is quite common that some system does indeed expose some API, but there is no documentation for it and the programmer has to wade through the source to find out the calling conventions. From the other side every mature project does have some set of tests for those APIs. How about using those tests as SeedWorks and automatically include them into the documentation?