Thanks for pointing this out Andrew.
As of the time of writing, this pattern is not GraphQL spec compliant.
This is a pattern that our team has found successful for code organisation and schema consistency.
I was not aware of the sequential execution guarantee issue, I will look more into it. Thanks!