Hey man, no harm and no offense but rant follows.
Can you imagine asking how a part of a brain achieves X or how part of an ant allows it to do Y? What I mean is decentralised systems like SAFE will use a lot of interrelated modules to achieve “stuff”. Then somebody says I want to know how it does X and then we have to say well X is done by … which means you need to explain almost the whole system to see each part, but folk want a part as a stand alone module with a sentence to describe that module. Many questions are like this (in my mind), “how do you do (this buzzword)?” and to be honest they are almost impossible to answer in a single sentence succinctly. Kinda like why is the earth the 3rd rock from the sun? then all hell breaks loose as there is no simple answer without a huge amount of info.
As for SLD, I don’t know what that is, I could google, but I am almost certain it’s the latest, inked docs. xml, UML or some similar, " we can describe complex stuff simply". Well IMO we cannot.
OK so saying all of that, rust has a truly brilliant feature and that is the documentation system. Each crate has a docs repo, all published ones are on docs.rs AFAIK, that is where we document each code piece. So I think if questions are not able to be answered there then we perhaps should look at updating that. It’s a start, but I have spent thousands of man hours documenting stuff, our patents for example are on occasion 120 pages long (as opposed to normal 4-5 pages) and I bet nobody has read them, certainly nobody who wants to know how/why (I include our own Engineers), then papers, wow a load, and again same, then wikie, again, primer, again and so on.
IMO folk want docs in their own personal preferred style and then I bet they still don’t read them, especially for large complex systems