mutation-pipeline-is-atomic-snapshot

OUT derived (depth 2)

Every network mutation follows an atomic snapshot pipeline: API context management ensures load/save atomicity with write-flag gating, while storage performs full-replace persistence — no partial state is ever visible between operations.

Summary

When something changes in the network, the entire process from loading data through saving it back works as a single indivisible operation — no other part of the system can ever see a half-finished update. This comes from the API layer locking down access during mutations and the storage layer always saving a complete snapshot rather than patching individual pieces. Since this claim is currently retracted, one or both of those underlying guarantees may not fully hold.

Justifications

SL — API atomicity and snapshot storage together guarantee no partial-write visibility

Antecedents (all must be IN):

  • api-layer-ensures-atomic-isolated-mutations — The API layer enforces mutation safety through four mechanisms: context-managed load/save, per-function transaction scope, write-flag gating to prevent unintended persistence, and dict-only returns that prevent callers from holding live network references.
  • persistence-is-snapshot-not-incremental — The storage layer operates as a full snapshot: save replaces all rows, load trusts stored values without re-propagation, and the dependents index is rebuilt from scratch

Dependents

These beliefs depend on this one:

Details