The document answers, so you are not the bottleneck.
A recipient with a question at 9pm does not email you and wait. They ask on the page, and the assistant answers from the document itself. It has no authority to negotiate, so it never concedes anything you did not write.
It answers from the document, not from the internet
The assistant reads the document in front of the recipient and answers out of it. Scope, dates, what a clause means, what is included. If the answer is not in the document, it does not invent one.
A change request is a request, not a change
Ask for something different and it becomes a request rather than an edit. You see it on Home and in the document's Activity tab, with a drafted reply and the proposed replacement block. One click approves or answers it.
An approved change is a new version, and the hash moves
Accepting on a sent document nobody has signed creates a new version and moves the content hash, so a stale page must reload before it can be signed. The recipient is told by email. On a signed or closed document the assistant replies but changes nothing.
The playbook bounds what it will concede
Settings carries a playbook in free text. The reviewer and the reply assistant both obey it, so "never discount past 10%" or "payment terms are not negotiable" hold whether you are at your desk or not.
What it is not: It is not a chatbot bolted to the page. It cannot agree to anything, change a price, or commit you to a date. Every change goes through you.