Within the live annotation and direct-edit patch flow, targeted edits are stored as first-class block-document versions and append-only edit deltas. Later targeted changes start from the latest accepted document rather than an unedited original. The stronger promise that a future document-level chat re-draft will automatically preserve every human-edited block is ratified design but is not wired in the current implementation.
What is live today
Drafts use a structured block document with block IDs, block types, roles, ordering, and touch policies. An accepted annotation patch or direct edit creates a new document version, re-renders the artifact, moves the current pointer, and records the delta.
Concurrency checks protect that history. If the draft changes underneath an inline edit, the app restores the current content and asks you to re-apply the edit instead of overwriting the newer version.
Blocked edits do not replace the document. Their refusal and safety report are recorded without applying the proposed block content.
Where to be careful
The document schema recognizes a future chat_redraft lane, and the design requires an agent to patch around human-edited blocks. No live document-level chat re-draft currently enforces that preservation rule. When exact wording must remain untouched, use inline direct edit or a block-level annotation. If you regenerate a larger block or whole artifact, review the regenerated result in full.
See DR-9, Three ways to edit a draft.