is there a best practice doc for ensuring concurrent state access for a stack remains valid? or is it that by using the pulumi backend this all happens under the hood?

yea the pulumi backend enforces that - if you use a different one it's your responsibility

that's right, the back end does this. (also Doom is my second favorite rapper)

ok, I'll stick with the Pulumi backend for now then