no-operation-is-truly-reversible

Status: IN

The codebase has no genuine undo or reversal: deletion is append-only metadata across all contexts (tombstones, delete markers, version entries), and failure handling escalates forward to permanent outcomes (retry-to-permanent-failure, independent-branch continuation) — both intentional removal and error recovery strictly add information rather than removing or reversing prior state.

Justifications

Deletion and failure recovery are the two operations that semantically suggest reversal, but both are implemented as forward-only state additions — the system's two "undo-like" paths are both accumulative

Depends on (SL): deletion-is-append-only-across-all-contexts, forward-only-extends-to-failure-handling

Depended on by

JSON