A server that answers queries from a data store often stamps each answer with an id read from a sidecar (a small metadata file published beside the store), so callers know which version of the data they got. If you publish the store and the sidecar with two separate file renames, a server that starts between them pairs the new data with stale metadata, the old id, and every answer it gives names the wrong version. A row count check does not close that gap: an updated store whose totals did not change passes it.
This post covers why counts are the wrong proof, how a generation marker (the version id written inside the store itself) makes a server that starts in that gap refuse instead of serve, and how to run a drill that proves the refusal. The example is a read-only query server over a graph store, written in Python with pyoxigraph (the Python binding for the Oxigraph database).…