WEBVTT

00:00:00.299 --> 00:00:01.963
Begin by deciding what needs editing

00:00:02.432 --> 00:00:04.181
If the problem is story structure

00:00:04.693 --> 00:00:05.376
missing motivation

00:00:05.973 --> 00:00:06.955
or the order of events

00:00:07.552 --> 00:00:09.685
use Dev Edit to build a revision plan first

00:00:10.217 --> 00:00:13.460
Ruthless Editor is the browser app for reviewing proposed line

00:00:13.545 --> 00:00:15.465
edits and assembling changes you accept

00:00:16.182 --> 00:00:19.766
This walkthrough uses prepared fictional material in actual workspace

00:00:19.851 --> 00:00:20.278
references

00:00:20.790 --> 00:00:23.051
so you can learn the decisions without exposing a private

00:00:23.137 --> 00:00:23.649
manuscript

00:00:24.280 --> 00:00:27.480
Import a chapter or supported manuscript file and check the

00:00:27.523 --> 00:00:29.187
extracted text before analysis

00:00:29.784 --> 00:00:30.894
Describe the intended meaning

00:00:31.448 --> 00:00:31.960
point of view

00:00:32.515 --> 00:00:33.539
tense and voice

00:00:34.051 --> 00:00:36.568
Add phrases or repetitions that should be protected

00:00:37.276 --> 00:00:38.556
Keep an unchanged source copy

00:00:39.367 --> 00:00:43.122
Scanned PDFs need text extraction before this workflow and imported

00:00:43.164 --> 00:00:45.554
text should not be treated as a promise to preserve

00:00:45.639 --> 00:00:48.740
the original page layout Open one proposal and read its

00:00:48.868 --> 00:00:50.148
original passage in context

00:00:50.788 --> 00:00:53.306
The source check helps locate the text the suggestion is

00:00:53.391 --> 00:00:53.562
about

00:00:54.074 --> 00:00:56.975
It does not establish that the model's editorial judgment is

00:00:57.018 --> 00:00:57.188
right

00:00:57.852 --> 00:00:59.601
Ask what the passage is doing for the scene

00:01:00.156 --> 00:01:01.564
what the proposed replacement changes

00:01:02.161 --> 00:01:04.721
and whether a deliberate voice choice is being mistaken for

00:01:04.764 --> 00:01:05.105
a mistake

00:01:05.788 --> 00:01:07.068
Compare the replacement with the original

00:01:07.886 --> 00:01:10.105
Accept it when it serves the book reject it when

00:01:10.147 --> 00:01:12.622
it does not or revise the wording before accepting

00:01:13.219 --> 00:01:16.121
Work in manageable groups and reread the surrounding sentences

00:01:16.955 --> 00:01:19.259
The goal is an edited chapter you can account for

00:01:19.685 --> 00:01:22.544
rather than a collection of smoother lines that quietly change

00:01:22.672 --> 00:01:22.928
character

00:01:23.525 --> 00:01:23.696
meaning

00:01:24.208 --> 00:01:24.763
or continuity

00:01:25.488 --> 00:01:28.816
After deciding on the proposals review the assembled text against

00:01:28.901 --> 00:01:29.200
your source

00:01:29.951 --> 00:01:30.889
Look for missing material

00:01:31.529 --> 00:01:32.126
shifted meaning

00:01:32.724 --> 00:01:33.577
repeated new phrasing

00:01:34.217 --> 00:01:36.222
and changes to names or intentional wording

00:01:37.161 --> 00:01:40.318
Use the workspace's decision and recovery controls when you need

00:01:40.361 --> 00:01:41.300
to reconsider a change

00:01:42.049 --> 00:01:45.121
Keep notes about unresolved story problems instead of forcing a

00:01:45.164 --> 00:01:46.487
sentence level tool to solve them

00:01:47.041 --> 00:01:49.900
Export the draft containing your accepted edits and keep the

00:01:49.943 --> 00:01:50.882
original alongside it

00:01:51.391 --> 00:01:54.463
Save a portable project backup before changing browsers or devices

00:01:55.786 --> 00:01:59.412
For a reusable workflow inside an AI assistant compare Chapter

00:01:59.455 --> 00:02:01.674
by Chapter Edit or Final Fiction Edit instead

00:02:02.399 --> 00:02:04.532
Those are downloadable skills with their own setup

00:02:05.104 --> 00:02:06.213
Your completion check is simple

00:02:06.853 --> 00:02:08.517
the chapter still means what you intended

00:02:08.987 --> 00:02:10.352
and you can trace the edits you chose