memorix docs

Guide

Reload, compare, and retry after a revision conflict

Recover safely when a stale write is rejected.

Invariants

  • Do not force overwrite without comparing meaning

This procedure requires explicit confirmation before mutating runtime.

Steps

  1. 1. Reload current revision
    Expected: Fresh envelope
  2. 2. Compare intended change to current meaning
    Expected: Decision to reapply or escalate
    Confirmation required
  3. 3. Retry write with new expected revision
    Expected: Success or escalate

Verification

  • No silent overwrite of newer fields

Download Markdown