06 / Safety

Keep control of the manuscript.Know every route around it.

Local-first project data, explicit AI routes, several recovery layers, and separate production copies give different risks different answers.

Local-first, explained

Your core project lives under your control. Optional routes remain visible.

Local-first does not mean every possible workflow is offline. It means the core project is primarily controlled on your computer and external routes depend on deliberate configuration.

Core project

Write and organize on the Windows desktop.

Manuscript, planning, story knowledge, and supported project data are built around a local desktop workspace.

Local AI

Use supported engines on your machine.

Ollama and LM Studio can provide supported local inference routes when configured.

Cloud AI

Know when enabled material may leave.

A configured cloud provider may receive prompts, selected text, and context enabled for that task.

Mobile boundary

A paired bridge, not full cloud collaboration.

Mobile Sync is bounded and paired; it is not universal cloud sync or real-time co-authoring.

AI control

Assistance stays useful when the route stays visible.

RaQuill separates the manuscript, selected context, provider route, generated proposal, and author decision.

  1. 01Select contextInclude only what the supported task needs.
  2. 02Choose providerLocal or configured cloud.
  3. 03Inspect resultRead the proposal and understand its route.
  4. 04Make the callAccept, edit, reject, or ignore.

The model may suggest. The author decides.

Built around author data

Your manuscript has more than one recovery path.

Everyday save, History, snapshots, project portability, and a full-Library archive have different jobs. RaQuill keeps those roles distinct.

  1. 01AutosaveProtect current work while you write.
  2. 02Scene HistoryReview and restore earlier versions.
  3. 03SnapshotsCreate another recovery point before risk.
  4. 04Project exportMove or safeguard a complete project.
  5. 05Library vaultPassword-protected archive of the whole Library.

A manuscript DOCX is a reading or editing output—not a complete project backup.

Export is not one thing

Choose the file for the risk you are protecting against.

Reading copy, project copy, or Library archive?

A manuscript output preserves readable text. A project export carries a project. The encrypted Library archive protects the whole Library. Verify important files after creating them.

Control questions

Clear boundaries before important work.

Safety comes from knowing which layer protects what—and checking the result.

Does local-first mean offline-only?

No. Core project data is primarily controlled on your computer, while a configured cloud AI workflow may receive selected text and enabled context.

Is a manuscript export a full backup?

No. Manuscript files, project exports, History, snapshots, and the encrypted Library archive have different safety roles.

Does Book Studio overwrite Write?

No. Book Studio uses a separate production workspace and does not write production edits back to the live manuscript.

Is RaQuill real-time cloud collaboration?

No. The current product is a Windows desktop application. Mobile Sync is a bounded paired bridge, not full cloud sync or real-time collaboration.

Start small, verify the loop

Create a test project before moving important work.