read-path-is-architectures-critical-surface

Status: OUT

The codebase's core contract — irrevocable writes with reconciling reads — places the read path under significant responsibility, and temporal correctness gaps (documented and accepted limitations) are likely to concentrate where reads must reconcile divergent state, since the forward-only constraint prevents reads from requesting write corrections.

Justifications

Irrevocable writes shift all reconciliation to reads, which is exactly where known temporal gaps (TOCTOU, atomicity) are most dangerous

Depends on (SL): writes-commit-irrevocably-reads-reconcile, temporal-correctness-gaps-are-known-and-accepted

Depended on by

JSON