[danabramov]

This sounds about right. I would note the atomicity of the actual screen update. We don't flush the changes until the whole tree resolves. Another thing to note is that we try to render as much of the tree as we can (e.g. if a sibling asks for a retry, we still try to render other siblings so we can collect as many requests as possible).