When a novel’s authoritative spelling cannot be decided immediately, send the issue to a decision queue instead of turning a search result into a replacement command. Attach an owner, possible evidence, response date, dependency, and decision condition to each character-name, place-name, or title case. Editing can then continue outside the affected scope. Completion here does not mean that every spelling has been changed. It means that every accept, exception, or hold request states who can decide it and what evidence is needed.
Start the queue after discovery
Search operations, match counts, replacement, and verification of old and new forms belong to STUDIO-035 and STUDIO-298. This article begins after one unresolved occurrence has already been found.
Use columns for case ID, term and context anchor, requested decision, owner, possible evidence, response date, dependency, and state. Do not add an approved-form or replacement-count column. The queue must not invent the answer before the decision exists.
Split the same term into separate case IDs when its contexts have different decision reasons or dependencies. A dialogue nickname and a formal narrative name must not be closed by one answer merely because their strings are related. The queue lists decision units, not just words.
Treat accept, exception, and hold as requests
The three queue types describe the answer being requested, not a text change already made.
- Accept: confirm the authoritative form from a character sheet, prior volume, or other source.
- Exception: approve why dialogue, quotation, or period spelling should differ from the standard form.
- Hold: identify missing evidence or decision authority before either answer is possible.
Moving a case into Accept does not edit the manuscript. Only a resolved answer with evidence can be handed to a separate correction step.
Assign three proper-name cases
| Case | Term and anchor | Requested decision | Owner | Possible evidence | Due | Dependency | State |
|---|---|---|---|---|---|---|---|
| N-01 | Character name, C02 dialogue | Accept | Continuity editor | Character sheet | Aug 14 | Colophon name | Inquiry sent |
| N-02 | Place name, C05 narration | Hold | Author | Map note | Aug 16 | C05 approval | Awaiting answer |
| N-03 | Title, C03 quotation | Exception | Editor | Quoted source | Aug 13 | None | Inquiry sent |
The names and dates are illustrative. The point is to give cases with different unresolved causes different next actions.
Stop only the dependent scope
If N-02 affects C05 approval, pause the affected C05 sentence and any navigation or description that repeats that place name. Unrelated C08 editing can continue. The dependency field defines how far an unresolved decision reaches.
A case with no dependency can be researched without stopping the manuscript. If it must be decided before publication, keep it in the prepublication decision list. The queue makes a hold visible while narrowing its impact.
Close an answer with evidence and conditions
When the character sheet confirms N-01, record the source and reviewer and mark the case resolved. When the quoted source supports the unusual title in N-03, resolve it as an intentional exception. If evidence for N-02 remains missing after its due date, do not convert it to Accept; assign another decision owner or request another source.
Hand a resolved row to the correction owner with case ID, answer, evidence, reviewer, and decision date. This article does not apply the change or reconcile counts. Queue resolution and manuscript correction remain separate operations.
Limit Rune Studio search to intake
Rune Studio documentation confirms a feature scope covering Japanese long-form editing, project organization, search, vertical preview, and EPUB output in one workspace. This article uses search only as an intake point that exposes a context anchor for a queue case.
Search does not decide authoritative spelling, exceptions, owners, or deadlines. The queue is an editorial practice, not an automatic product feature. The three-case workflow is an example rather than a completed Stage 4 product test.
Finish with owners and decision conditions
Before handing off the queue, confirm that every row has an owner, possible evidence, due date, dependency, and decision condition. An unanswered row can still be managed when those five fields state what happens next. A row containing only a term and context has no owner and cannot progress.
A useful novel editor does not simply remove search results. It helps the editor find a context that can be assigned. The conclusion is not replacement completion. It is a queue in which every accept, exception, and hold case has an owner and decision condition, allowing unaffected editing to continue.
Start today with the one proper name that is hardest to decide and register it as N-01. Write who can answer, what evidence is needed, when it is due, and which chapter depends on it. The next editorial action is then visible even before the answer arrives.
