← Back to blog

2026-06-14 · 4 min

Durable drafts and conflict policies

Fields that users edit offline need explicit conflict rules.

A durable draft is a field that should survive reload, restart, and stale remote responses.

Mark those fields with durableDraft and give them a conflict policy such as localDirtyWins.

That lets an agent know which values are safe to keep local and which ones should be replaced by remote data.

Without that metadata, generated UIs tend to overwrite user edits or keep two inconsistent copies of the same state.