Committed writes survive follow-up failures with partial scheduled repair

Context

A write can commit successfully even when its later cache or scheduling work fails.

Decision

Preserve committed writes after follow-up failures and describe repair separately for each path rather than promise universal recovery.

Alternatives Considered

Hold the transaction open for every follow-up: Remote caches and functions extend transaction duration and can still fail.

Undo the committed change after a follow-up failure: Reversing a valid business change would introduce a second business failure.

Consequences

Repair depends on later successful processing. Deferred display history has no repair path. Retired-kind sweep repair applies only during seven days after retirement. Logs expose failures but do not establish durable retry or a completion deadline.