Consistency And Coordination

Atlox does not apply one consistency mode to an entire application. It derives coordination from the observations and guarantees of each operation.

Coherent snapshots

One admitted invocation reads a coherent logical snapshot plus its own preceding writes. A query, authorization decision, and state transition therefore agree about the world they are changing.

The physical engine may use locking, optimistic validation, ownership, or another protocol. Those choices do not alter source-level value semantics.

Coordinate only where required

Some operations commute and can execute independently. Others must serialize because they protect an invariant or one authority boundary.

The compiler can avoid coordination only when the operation and invariant semantics prove that it is safe. Availability is not obtained by silently weakening correctness.

Replication

Replicas and client caches are maintained projections. A replica may be stale according to an explicit policy, but it is not a competing source of truth.

Local-first or multi-authority domains require merge laws and conflict meaning. Atlox can support those capabilities without forcing every ordinary field into an open-world knowledge model.