Note that this is pretty much how all "Server RDBMS" handle local storage consistency. The only difference between a "Server RDBMS" and SQLite3 is the "Server" part -- a "Server RDBMS" is nothing more than SQLite3 wrapped up with remote procedure call interface. The "database file" is still "local" to the "RDBMS" and the process for maintaining consistency between the "local database file on disk" and the "RDBMS Server process" is practically indistingushable. Generally however the "Server RDBMS" is a single process so there is no capability or provision (or need) for the "Server RDBMS" to provide consistency between multiple instances of itself.