assumed-invariants-are-unenforced

Status: OUT

Critical correctness invariants exist only as developer assumptions, not as code-enforced constraints: the KV store relies on W+R>N quorum overlap without validating it, and the payment system assumes atomic balance checks despite non-atomic reads — both creating correctness guarantees that hold only when callers cooperate, with silent violations under edge conditions the code structurally permits.

Justifications

Both depth-1 conclusions identify correctness properties that documentation promises but code never checks, forming a cross-cutting pattern of unenforced invariants

Depends on (SL): kv-quorum-consistency-assumed-not-enforced, payment-toctou-double-jeopardy

Depended on by

JSON