Correctness

mvSQLite is beta software, but data reliability is taken seriously. While I can't guarantee that every component is bug-free, I'm giving a tiered correctness expectation:

• Tier 0: FoundationDB. It is rock-solid, and even if everything else goes wrong you can still get your data back via FDB's continuous backup. I have confidence this will practically never break, as long as you configure the cluster properly.
• Tier 1: mvstore. It is reasonably tested under different configurations, with simulated extreme cases, and with fault injection. It is unlikely that data will get corrupted in this layer.
• Tier 2: mvsqlite-{preload,fuse}. Automatic testing coverage is low for client libraries, and there may be more bugs here than in other components of the system. However, if something goes wrong you can still check out a known-good snapshot from the past (this is a mvstore mechanism), so it is very unlikely that bugs in this layer will cause data loss.