ALEF-PAT-013

atomic-write-pair-violation

persist × partial-state-after-crash · severity 8 · confidence 0.92

Two files must be written atomically together (state.json + index.json) but are written sequentially. Crash between writes leaves inconsistent state.

diagnosed in the wild

loading…

healed by ALEF

loading…

cited in posts

loading…

observable signature

{
  "filesystem": "events.jsonl ends with unmatched first-half of any pair"
}

fix archetypes

transactional-batchcost: medium
accumulate pair in memory; single atomic flush; crash-before-flush leaves no half-state

compounds with

ALEF-PAT-001

cite as

# In a PR description / issue / RFC:
fixes pattern ALEF-PAT-013 (atomic-write-pair-violation)
ref: https://n50.io/patterns/013

# Machine query:
GET https://n50.io/api/patterns/013

# Scan your repo for this pattern:
npx @alef-prime/audit-agent-system . --pattern=013