The problem
Most feedback on a written document is small: a word, a number, a sentence that should say something slightly different. Describing that in a comment and waiting for the agent to make the change is slower than making it yourself. But if you edit a copy, the agent's source file and your copy drift apart, and the next version undoes your fix.
How it works with Onlay
Publish with editing on:
onlay push proposal.html --edit collaborative
Readers click a paragraph, change it, and click away. That is an edit, and it means "keep this". Several people can edit at once and see who is in which paragraph. Editors sign in, so every change has a name.
Your agent runs onlay pull proposal.html and gets each edit as the published text and the reader's replacement, with the lines of the source file it came from:
- Revenue grew 12% in Q3, driven mostly by new customers.
+ Revenue grew 12% in Q3, driven mostly by expansion in existing accounts.
from: Mia
source: v1 line 24, as pushed
It applies the edit to the source and pushes. The push checks what happened: if the old wording is gone, the edit was taken; if it is still there, the reader is told in a thread that it was not, and the agent can explain why.
The other editing modes
--edit fork: anyone can make a private copy and change it freely. Their copy stays theirs and never reaches you.--edit invited: only the people you invite by email can edit.--edit none, the default: readers comment but do not change the text.
When something else fits better
If many people will write the document together over weeks, use a shared editor built for that. Onlay keeps your agent's file as the source, with readers' edits flowing back into it.