Revision and Issues
Revising a book means tracking concerns — "fix the pacing in chapter 3," "Olga's motivation is weak here," "rewrite this dialogue." Instead of scattering those across paper, chat messages to yourself, and memory, Writer Studio gives them a single visible home, connected to your manuscript. This is a writing aid, not a project-management tool: no due dates, assignees, priorities, or boards.
Issues
An issue (Russian: «замечание») is a concern you write down and attach to part of your book. It is just free text — that is enough.
- Attach an issue to a scene, chapter, part, the book, or a story entity (a character, location, or plotline).
- Add it in one action from wherever you are — the editor, the structure tree, or an entity card.
- Each issue points back to its anchor, so you can jump straight to the thing it is about.
Revision notes
A revision note is a lighter thought on the same anchors — something that is not yet a concern. When a note turns into a real concern, convert it to an issue without retyping.
Scene status
A scene's status tracks where the scene stands as the draft matures. Status is unset by default and shows nothing — if you never use statuses, you never see them.
When you do use it, set one status per scene from a small fixed set:
| Status | Meaning |
|---|---|
| Outline | Planned, not yet written |
| Draft | Written, raw |
| Revision | Being revised |
| Final | Done |
A scene has exactly one status or none — never several — and you can clear it back to unset at any time. A set status shows in the structure tree and near the editor, kept visually distinct from tag colors. Status is a label, not a gate: it changes nothing about your text.
In the Explorer you can filter the tree by status — for example, show only scenes in "revision" — and the matching scenes stay inside their chapters and parts so you keep your bearings. Per-status counts appear alongside the filter («revision — 7»), giving you a quick survey of where the draft stands without any dashboards or percentages.
One home for everything unresolved
The Issues panel shows every open issue and note across the project in one list. Filter it by anchor (a chapter, an entity) or by type, and select any item to jump to where it lives.
Filters follow your structure: filtering by a chapter shows items anchored to that chapter and its scenes; items on a part, the book, or an entity show up under their own filters.
Resolving issues
You control the lifecycle. Nothing closes an issue on its own — not the app, not the AI.
| Action | Result |
|---|---|
| Resolve | Marks the issue done and removes it from the active view |
| Dismiss | Sets it aside without losing it |
| Defer | Snoozes it from the active view for now |
| Reopen | Brings a resolved or dismissed issue back, with its text intact |
A typical pass: open an item, jump to its scene, fix the text as a normal edit, then mark the item resolved.
Resolving an issue and accepting a change are different things: accept/reject applies to AI suggestions (proposed changes to your text), not to issues. An issue is something you decide is handled — see AI Assistant.
Review passes
Group related issues under a named review pass — a "dialogue pass" or an "Olga pass" — so you can revise one dimension at a time. A pass's progress is simply the lifecycle of its items; finishing a pass changes nothing else.
Where revision lives
Issues, notes, and scene statuses are your content. They travel with the project folder, survive a database rebuild, and are covered by Backup and whole-project restore. Trashing a scene hides its issues from the default view without deleting them; restoring the scene brings them back (see Safety).
Language and spelling findings from Proofreading land in this same Issues home, clearly marked by where they came from — never a second list.
See also: Metadata | Proofreading | Search | Safety