Finding one unconvertible character is the beginning of control, not proof that the file is clean. Saving should remain blocked until the starting count is recorded, every replacement has evidence and a named human approver, and the same scan returns zero. Rune Studio can expose risky characters and block autosave while they remain. Semantic replacement decisions stay with people, and the clean result is saved under a separate name with its zero-result record.
Open the release record with a starting count
Scan a copy and record the number of unconvertible characters, file identifier, target encoding, and time. Without a baseline, a later reduction or new warning cannot be explained.
A three-item example using a name variant, emoji, and circled number illustrates the table only. It is not a measured Rune Studio result.
Map every warning to readable context
For each warning, record chapter, paragraph, original character, and surrounding phrase. A count alone does not tell an approver which occurrence should change.
Visible highlighting is a locator. Convert it into a human-readable evidence row before making any replacement.
Require a named approver and source
Use author confirmation for a character name, a dictionary for a standard term, or the original publication for a quotation. Record the approver's name or role on the row.
Leave uncertain characters pending. Visual similarity is not semantic authority, especially for names and intentional symbols.
Close one approved row at a time
Apply only approved replacements to the copy. Check the original, replacement, and location before closing each row, and record who made the change.
If a new warning appears, add a new row. The record follows current risk rather than defending the original estimate.
Run the identical scan until it returns zero
Repeat the same test after all approved changes. Record an actual zero-result count instead of relying on the absence of a visible red mark.
If the result is not zero, saving remains blocked. Add the remaining positions and repeat approval rather than overriding the gate.
Release a separately named copy
Connect the starting count, approved-row count, zero-result rescan, and output name in one release entry. Save a distinct file such as clean-02.txt and reopen it for representative checks.
Keep the original protected. The next workflow receives the clean copy together with the evidence that allowed saving to resume.
Divide responsibility between Rune Studio and people
Rune Studio documents encoding detection, visible unconvertible-character warnings, and autosave blocking while risk remains. Those functions provide detection and a protective gate.
A designated human approver chooses the semantically correct replacement. The product does not infer authorial intent, and the article does not claim that it does.
Conclusion: make zero the save authorization
Create columns for the starting count, location, replacement evidence, approver, and repeated result. Process the copied manuscript one approved row at a time.
Saving becomes safe for this workflow only when the repeated scan records zero and the clean copy is separately identified. A first warning is an inventory entry, not completion.
