@eblanshey this is awesome. I’ve only just found time to read it through carefully and it is a great resources. It’s all good, but I really found the detailed explanation of how SAFE works helpful, pulling all the bits together like that (esp. as I’ve not gone into the docs at all, just been gleaning info from conversations.
Thanks very much 
I have two queries:
In point 4:
Is this so? I haven’t read the docs, it just sounds to me like the data manager might know one of the four vaults for each chunk it manages, or do all 32 of the managers for a chunk know about and manage the same four vaults holding that chunk? It may well be so, I just want to clarify. EDIT: @dirvine says you have it spot on, all 32 know about/manage the same four vaults holding a given chunk.
In point 6:
I believe the vault doesn’t earn for every successful GET. What I think happens is that all vaults holding a chunk are sent a request for the chunk. One of them will be first to deliver the chunk, so the others don’t earn even if they send it. Furthermore, I think that the one which is first gets a chance to earn Safecoin, which may not in fact succeed.
Also, we say there are four copies of each chunk, but I believe it varies and is at least four, but that its just simpler to say four. You might mention that in a footnote. Its something David mentioned [here on the forum.][1]
EDIT: @dirvine elaborates on Safecoin earning below…
[1]: What exactly happens when a particular file or safecoin address gets DOSed? - #25 by dirvine