{"id":"reads-bear-full-correctness-burden","text":"Reads bear the full correctness burden: they absorb lazy computation and active repair to converge state, and must interpret metadata-as-deletion (tombstones, delete markers, soft-deleted records) to present a correct view — making the read path the primary site of system complexity across the codebase.","truth_value":"IN","source":"","source_url":"","source_hash":"","justifications":[{"type":"SL","antecedents":["read-path-absorbs-consistency-and-computation-cost","deletion-is-metadata-in-replicated-systems"],"outlist":[],"label":"Both depth-2 conclusions shift complexity to reads — one for computation/convergence, the other for deletion semantics — together establishing reads as the locus of correctness"}],"dependents":["read-cost-scales-with-system-complexity"],"metadata":{"last_reviewed":"2026-06-06T06:26:57","review_result":"insufficient"},"created_at":"","updated_at":"","reviewed_at":"","verified_at":"","retracted_at":"","explanation":{"steps":[{"node":"reads-bear-full-correctness-burden","truth_value":"IN","reason":"SL justification valid","antecedents":["read-path-absorbs-consistency-and-computation-cost","deletion-is-metadata-in-replicated-systems"],"label":"Both depth-2 conclusions shift complexity to reads — one for computation/convergence, the other for deletion semantics — together establishing reads as the locus of correctness"},{"node":"read-path-absorbs-consistency-and-computation-cost","truth_value":"IN","reason":"SL justification valid","antecedents":["lazy-read-time-evaluation-trades-write-simplicity-for-read-cost","kv-read-path-is-self-healing"],"label":"lazy eval (autocomplete decay, URL expiration, payment balance) defers computation to reads; KV read repair defers convergence to reads — the combined pattern reveals a systematic bias toward read-path complexity across the repo"},{"node":"lazy-read-time-evaluation-trades-write-simplicity-for-read-cost","truth_value":"IN","reason":"SL justification valid","antecedents":["autocomplete-decay-is-read-time","url-shortener-expiration-lazy","payment-balance-never-cached"],"label":"Three independent systems chose lazy evaluation, suggesting write-simplicity is the dominant concern in pedagogical implementations"},{"node":"autocomplete-decay-is-read-time","truth_value":"IN","reason":"premise"},{"node":"url-shortener-expiration-lazy","truth_value":"IN","reason":"premise"},{"node":"payment-balance-never-cached","truth_value":"IN","reason":"premise"},{"node":"kv-read-path-is-self-healing","truth_value":"IN","reason":"SL justification valid","antecedents":["kv-read-repair-on-get","kv-node-stores-sibling-versions"],"label":"Read repair + sibling detection make the read path an active consistency mechanism, not just a query"},{"node":"kv-read-repair-on-get","truth_value":"IN","reason":"premise"},{"node":"kv-node-stores-sibling-versions","truth_value":"IN","reason":"premise"},{"node":"deletion-is-metadata-in-replicated-systems","truth_value":"IN","reason":"SL justification valid","antecedents":["soft-delete-prevents-distributed-resurrection","append-only-versioning-makes-restore-non-destructive"],"label":"both depth-1 conclusions independently arrive at the same principle — never physically destroy data — but for complementary reasons (anti-resurrection vs non-destructive restore); combined they show this is a fundamental constraint of any system that replicates or versions state"},{"node":"soft-delete-prevents-distributed-resurrection","truth_value":"IN","reason":"SL justification valid","antecedents":["kv-store-deletes-use-tombstones","s3-delete-marker-hides-not-removes"],"label":"Both systems independently arrived at write-over-delete to prevent resurrection from unsynchronized replicas"},{"node":"kv-store-deletes-use-tombstones","truth_value":"IN","reason":"premise"},{"node":"s3-delete-marker-hides-not-removes","truth_value":"IN","reason":"premise"},{"node":"append-only-versioning-makes-restore-non-destructive","truth_value":"IN","reason":"SL justification valid","antecedents":["s3-version-list-append-only","gdrive-restore-creates-new-version"],"label":"Append-only version lists make restore a forward operation, not a rollback"},{"node":"s3-version-list-append-only","truth_value":"IN","reason":"premise"},{"node":"gdrive-restore-creates-new-version","truth_value":"IN","reason":"premise"}]}}