read-correctness-is-structural-not-temporal

Status: OUT

The write-available, read-correct architecture achieves its read-correctness guarantee only for structural properties (immutable values arrive intact, synchronized structures reconcile deterministically); temporal correctness on the read path — where TOCTOU gaps and non-atomic checks are most consequential because reads must converge divergent state — remains an accepted rather than enforced property.

Justifications

The d6 architectural claim ("reads reconcile and correct") is qualified by the d5 correctness split — "read-correct" is guaranteed structurally but aspirational temporally

Depends on (SL): codebase-architecture-is-write-available-read-correct, correctness-profile-is-structurally-split

Depended on by

JSON