An AI worker is not a chat window
The difference is not how well it writes. It is whether the work has a matter attached to it, and whether what comes back is finished work you can read.
The argument
A chat window is a good way to ask a question. It is a poor way to run a matter, and the reason is structural rather than a matter of quality.
A window waits for you. It holds what you paste into it and forgets the rest. The work of assembling the context, deciding when something is due, and carrying the answer back into the file stays with the lawyer, which is most of the labour and all of the risk of forgetting.
The interesting question about legal AI is therefore not how well it writes a paragraph. It is whether the work is attached to a case, and what it is allowed to do once it is.
The mechanism
A worker runs on a matter rather than in a window. It is started by a trigger or a schedule, not by somebody remembering to open a tab, and it comes back when there is something to show.
What it has in front of it is the case, not a paste. The documents on the matter, the parties, the phase the matter is in and what that phase still owes are what the worker reads, so the answer is about this file rather than about legal work in general.
What comes back is a draft written to the firm's own Standard, learned from the firm's own documents, and the options that belong to it: use it, hold it, or set a follow-up so it is chased on time.
Then it stops. It does not send, file or serve anything: the work is handed back inside the product, as a draft or a redline, with a card naming what it did and what it could not settle. A worker that acted on its own would be a faster way to make the same mistake.
That is also the honest reason a worker is more useful than a window rather than merely different. The window cannot chase anything, because nothing told it to, and it cannot stop safely at a gate, because it was never holding anything that was going anywhere.
What it does not do
It does not run without a matter. A worker with no case attached has nothing to read, and the product is not a general assistant with a legal accent.
It does not act on its own authority. It sends nothing: no email, no message, no filing. Every result is handed back into the product as a draft or a redline, which is a property of how actions are built rather than a default we chose.
It does not replace the reading. A draft that arrives finished still arrives for a lawyer to read, and reading it is the work rather than a formality at the end of it.
It is not a claim about any other product. This describes how Volares is built. What a given tool elsewhere does is a question for that tool's own documentation.