The problem
A writer’s first fear is losing words. It is not abstract at Kwark: in September 2026 a phone opening a light project card saved its placeholder over ten real pages of a screenplay. The founder made data loss priority one. At the same time, the writer is often on a train or a set with bad signal, and the same project is open on a laptop and a phone.
They need three things: the work is saved without thinking about it, it is never overwritten by another device, and they can tell, at a glance and in words, where it is.
Kwark’s answer
Save as you write, on the device first
Every change is written to the device at once and queued for the cloud. The queue runs in order and keeps a change until the cloud confirms it; a failed upload backs off and retries (up to every five minutes) and is never dropped after an arbitrary number of tries. A change a person had no right to make (view-only access) stays on their device and is not reported as a failure, because it was never theirs to save.
Cmd+S says Saved (Decision 0014)
Writers press Cmd+S out of habit. It used to make a snapshot each time, which cluttered history and reassured nobody. Now Cmd+S (Ctrl+S) shows “Saved. Your script saves as you write.” A deliberate restore point is Keep a restore point, Shift+Cmd+S, in the File menu.
Revision stamps and conflict protection
Every screenplay save carries a stamp: a revision number, the time, the device and the session. Two checks use it.
- On the device, a save refuses to replace a newer revision written by another session.
- In the cloud, the screenplay is written inside a transaction that compares revisions. If the cloud is newer, the upload stops, this device’s version goes to the recovery store, the cloud copy is adopted, and the editor shows the conflict banner.
A project whose screenplay has not reached this device (cloud unreachable, nothing local) opens read-only and never saves, so a blank cannot overwrite the real script.
The honest limit, recorded in the memory note on conflict protection: a device still running an older app writes without a stamp and can still overwrite. The protection is in the app, not in the rules.
One word, in the corner (Decision 0013)
The state is told first, calmly, and only when it is worth telling.
| State | Words | Colour | Shown |
|---|---|---|---|
| Loading | Loading… | Quiet | While opening |
| Up to date | Up to date | Quiet | Briefly, then steps back |
| Edited | Edited | Quiet | While typing |
| Saving | Saving… | Quiet | During upload |
| Saved | Saved | Ok | Briefly (about 2.6 seconds), then steps back |
| Offline | Saved on this device | Warn, with the word | Until the cloud has it |
| Not downloaded | Not downloaded, and a banner | Warn | Until it downloads; the page is read-only |
| Conflict | Changed elsewhere, and a banner | Danger | Until the writer chooses |
| Failed | Not saved | Danger | Until it saves |
Outside the editor the account panel says Safe, Safe here, waiting to reach the cloud, or Safe on this device (offline by choice), with Retry, Backup and Work offline or Reconnect. On Home, a story still only on the device carries Not synced yet (or Only on this device for a guest). Characters and locations say Saved on this device after a local write, which makes no cloud claim.
Anatomy
| Part | Means | The person does |
|---|---|---|
| Sync word | Where the work is now | Nothing, usually |
| Conflict banner | Two sessions changed the screenplay | Chooses Load the newer version or Keep mine |
| Not downloaded banner | The script is not on this device; nothing will save | Try again |
| Recovery banner | Unsaved edits from an earlier visit were found | Restore them or Discard |
| Cmd+S toast | Reassurance; nothing new happened | Keeps writing |
Rules
- Must write to the device before the cloud, and keep every queued change until the cloud confirms it.
- Must stamp screenplay saves with a revision and refuse to replace a newer one.
- Must open a project read-only when its screenplay has not reached the device.
- Must keep the writer’s version whenever two copies disagree. Loading the newer one saves theirs as a restore point first.
- Never say “failed”, “sync error” or raw Firebase text. Say the state and that the work is safe.
- Never show a permanent bar for ordinary saving. “Saving 1 change” is the normal state of a writing app, not news.
- Never carry the state by colour alone; every state has its word.
- Always let Cmd+S answer “Saved”. Never make it create a snapshot.
- Always offer a way to take the work away when the cloud cannot be reached (Backup).
Phone and desktop
The same states and words everywhere. On a phone the sync word sits where it cannot be covered by the floating button; banners span the width under the one-line header and their actions wrap below the sentence. On desktop the word sits at the corner of the page. On a phone, a failure is one line: what went wrong and how to fix it.
Writing
- “Saved. Your script saves as you write.”
- “Saved on this device · sign in to keep it everywhere”
- “Working offline · changes stay on this device”
- “This screenplay was changed in another session. Your edits are kept on this device and have not overwritten it. Loading the newer version saves yours as a snapshot first.”
- “This screenplay has not downloaded to this device. Nothing will be saved until it does, so the copy elsewhere stays exactly as it is.”
- “Could not save. Your words are kept on this device.”
Accessibility
- The sync word is in a polite live region, so a screen reader hears “Saved on this device” without being interrupted.
- Banners use
role="status"; their actions are real buttons, reachable by Tab, in reading order after the sentence. - A state that settles away must not take focus or move the page.
Saved on this device, in amber with the word, and a Retry button in the account panel.
A red cloud with a line through it and “Sync failed”, or a pulsing dot with no label.
Cmd+S shows “Saved. Your script saves as you write.” and nothing else changes.
Cmd+S makes a new snapshot every time and fills the history.
Demo
<div class="kw-banner kw-banner--warn" role="status" style="width:100%;flex-wrap:wrap"><span style="flex:1;min-width:220px"><strong>This screenplay was changed in another session.</strong> Your edits are kept on this device and have not overwritten it. Loading the newer version saves yours as a snapshot first.</span><span style="display:flex;gap:8px"><button class="kw-button kw-button--sm" type="button">Load the newer version</button><button class="kw-button kw-button--sm" type="button">Keep mine</button></span></div>
<div class="kw-banner" role="status" style="width:100%;flex-wrap:wrap"><span style="flex:1;min-width:220px"><strong>Unsaved edits from 16 Nov, 21:40 were found on this device.</strong></span><span style="display:flex;gap:8px"><button class="kw-button kw-button--sm" type="button">Restore them</button><button class="kw-button kw-button--sm kw-button--quiet" type="button">Discard</button></span></div>
<div class="kw-card" style="display:grid;gap:8px;width:100%;max-width:340px"><span style="display:flex;gap:6px;align-items:center;font-weight:500">Safe here, waiting to reach the cloud</span><span class="kw-row__meta">3 changes only on this device</span><span style="display:flex;gap:8px"><button class="kw-button kw-button--sm" type="button">Retry</button><button class="kw-button kw-button--sm kw-button--quiet" type="button">Backup</button><button class="kw-button kw-button--sm kw-button--quiet" type="button">Work offline</button></span></div>
<span class="kw-badge kw-badge--warn" aria-live="polite">Saved on this device</span>
Related
Errors, Collaboration, Loading, Banner, Toast.
AI readiness test
Task. Add autosave to the budget, which today saves the whole record on a button.
Give the agent. This page, Review and quality (free tier), the memory note on conflict protection.
Constraint. No new rules deploy without the founder.
A reliable answer
- Writes to the device first and queues for the cloud
- Uses field-path writes, not a whole-record overwrite, and states reads and writes per edit
- Protects against a second editor overwriting (a stamp or per-field writes) and keeps both copies on conflict
- Uses the sync words from this page, with no “failed”