Literate documentation: treating docs as contracts over system behavior

I’m thinking about building a literate documentation system to address some of the gaps mentioned here.

For those who’ve run into similar issues, what gaps did I miss? And what features would you need to see to actually give something like this a try?