Update-seq monotonicity vs explicit key ordering for deterministic bulk loads
In repeatable CouchDB development environments, bulk-document loads via the bulk_docs endpoint assign update_seq and _rev per write, but the database does not enforce monotonic creation order across concurrent requests or clustered nodes. This behavior arises from CouchDB's document-level update_seq model, which tracks revisions per document rather than main