At least two writers have noticed a relationship between literate programming and single-sourcing, and have commented on it in passing.
It is clear that you should store system information in one place and one place only, ideally in the most effective place. From the point of view of software development this concept is called normalization, in the programming world an important aspect [sic] of literate programming, and in the technical documentation world it is called single sourcing.
Scott Ambler ([Ambler])
... it is interesting to notice that the program documentation approach known as Literate Programming... can be seen as a single sourcing program documentation approach, in which both the program and the documentation are authored in an extended, aggregated language.
Kurt Nørmark ([Nørmark] p. 5)