Asking for a change in words is easy to imagine and hard to do safely, because the easy way is to let the model touch the file. Here the request becomes a specification, and the engine does the writing.
The request becomes a specification
The model understands; the engine writes
You say what should change: a stale number, a section title, a term spelled two ways. What comes out of the conversation is not a file but a description of what changes, on which elements, against which version. The engine executes it, alters those elements, and records each one it changed. Why the two layers are separate is in the conversation is with the AI.
Editing inherits the refusal
A request the engine cannot resolve fails, instead of being guessed
If the model misreads you, the result is a wrong specification you can read and reject, not a document silently broken. Translation already works this way: segments go out delimited, the count that returns is compared with the count that left, and a mismatch fails the step (differentials). An edit inherits the same rule: a request that does not resolve to a concrete element has to fail.
What exists today, and the gap
The door that takes a described change exists and refuses; the path from your sentence to it does not
Since 2026-07-30 the agent has four operations that assemble a change element by element: list what is editable, open a draft, send each line (element, paragraph, content type, text), and execute. Title, body and table cell accept writing; image, field, chart label, comment and geometry are locked, and a line pointing at them fails. A draft no longer editable fails. An empty recipe fails.
The gap: you must name each element by its internal identity, read from the map first. What is not built is the step from your sentence to that line. So you cannot yet ask for a change in plain words. The full set is in capabilities; the doors are in interfaces.
Where this stands today
A direction, with the gap named
The screen has its own gap, in web editor. What a new document is assembled from is in co-creation with AI.
The state, dated. Measured on 2026-09-02, in the development environment, not in production. The four operations above were read from the product itself, with the refusal of locked elements built in. No operation was found that takes a request in your own words and resolves which element it names. The write step is declared among the engine's steps, and its execution log is empty across all four formats.
Why no number. This capability has a written decision, but not yet a measurement someone outside can repeat.
Whatever is requested, executed or refused stays on record: the fifth verb, trust.