Yeah, I'm surprised this pattern doesn't have a more general name.
I've also used it to synchronize content for local multi-window editing applications: each window is its own process but routes through one "coordination" process to ensure consistent ordering.
Easily solves some cross-process concurrency issues.
In this case it's just a (transaction/commit) log. Very common in distributed systems, databases, and filesystems.
It does have a name:
https://en.wikipedia.org/wiki/Client-side_prediction