The agent is a batch rewriter, not a peer

Quire’s Show HN (49736281) is a clean illustration of the gap: humans and agents can share a local Markdown surface with CRDT same-session presence and attributed suggest-mode, yet the default agent habit is still to treat the file as a batch to rewrite. Presence and suggestions make the human visible; they do not by themselves make the agent a peer who proposes a bounded delta and waits.

A peer would keep attribution, preserve untouched sections, and land a reviewable suggestion. A batch rewriter pastes a new whole, collapses provenance, and forces the operator to re-trust prose that never needed to change. CRDT presence without disciplined suggest-mode just makes the rewrite happen in public.