Autosave and the Ready mark

There is no Save button in the editor and no way to force a save. That is fine once you know what the editor tells you and when, and it is worth knowing exactly, because "did that last sentence save?" is the question that sends people looking for a button that is not there.

When saving happens

The editor saves itself about five seconds after you stop typing. It also saves when you leave the canvas and when you open History, so ordinary use rarely leaves anything behind.

On an existing document, the only confirmation is the word Saved, which fades in at the bottom right of the writing surface for a couple of seconds after each successful save. Nothing changes on screen while a save is in flight. If a save cannot be written you get Save failed in that same corner plus an error toast naming the reason. Your typing stays on screen and goes out again on the next save.

The brand new canvas is different

A canvas you reached from a type tile has not created anything yet, so its header carries a status of its own:

• Nothing at all while you have unsaved typing. The absence of the tick is the signal, not an oversight.
• Saving… with a spinner while a save is in flight. On a new canvas, this is the save that creates the document.
• Saved with a tick once everything you typed is on the server.
• Not saved with a warning icon after a failure. It outranks everything else and stays until a save succeeds, so later keystrokes do not hide it.

The document does not exist until you type real text. An empty canvas creates nothing, and closing the tab there leaves no trace. Adding blank sequence steps does not count as text either. If a save is somehow attempted with nothing in the document you will see Add some text before this is saved.

Once in a while a save comes back reporting that the document changed since the revision it expected. That means the same document was edited somewhere else, another tab or another person. The toast says so, and your draft deliberately stays unsaved rather than writing over the other copy. Open the document fresh in one place and reconcile the two by hand.

What the Ready mark is

Mark as ready flags the text currently in the document as the version you intend to send. It is a mark you make for yourself and the people you share a workspace with. It does not send anything, does not lock the document against editing, and is not a verdict from any check.

You can set it in two places: the button in the panel beside your draft, next to Copy with all feedback, and the item in the document's three-dot menu. Once set, the button reads Ready and its tooltip reads Unmark, and a toast confirms with Marked ready. Removing it says Back to a working draft.

A small READY badge then appears beside the document's name everywhere it is listed: the sidebar, the Documents list, and any project list it belongs to.

What it does not mean

A Ready badge on wording nobody has looked at would be worse than no badge at all. If you changed a draft you had marked and kept the change, look it over and mark it again.

A few more things about the mark:

• While the toggle is in flight the button shows a spinner and cannot be pressed. If the server refuses, a toast tells you and nothing changes.
• On an archived document, Mark as ready is hidden. An archived document can be unmarked but never marked.
• Ready is independent of Quality Check and Simulation. You can mark a draft that has never been checked, and a checked draft is not marked for you.