An existing fact is not everyone’s knowledge
One fact can occupy different positions: the author has established it, readers have seen it, the protagonist has told a roommate, and a colleague still knows nothing. Separate those positions before judging a line.
Oh Story’s chapter outline distinguishes character knowledge, reader knowledge and protagonist misjudgment. Character snapshots store known information; the timeline separates objective facts from reader understanding. Compare these records with prose rather than letting everyone speak from author notes.
| Distinction | Interview example |
|---|---|
| Author fact | Qin He has a local training-program interview at nine on Saturday. It has not happened. |
| Readers and Han Ning | The previous chapter shows Qin privately telling her roommate, who agrees to keep it private. |
| Tang Yu | A public group message says Qin can help at the lending station on Saturday, without a time. |
| Unsupported | Tang knows the interview, location or result; Han knows the later rota response. |
An omniscient narrator may inform readers without informing characters. Removing “she has an interview” from narration does not repair Tang’s “your nine o’clock interview.”
Trace evidence before the first unsupported line
Quote the problem line and relevant earlier passages. Was this person present? Was a message actually sent to them? What did it contain? What inference does an observed anomaly support?
Knowing someone is unavailable in the morning differs from knowing they have an interview. Hearing an interview claim differs from verifying it. A character may guess wrongly, probe or lie, but preserve the author’s intended status rather than retroactively calling an accidental leak intelligence.
Two repair paths are available: retain ignorance and ask a question supported by current knowledge, or adopt earlier disclosure with an author-chosen communication and synchronized chapters. “Han already told him” is not a harmless patch when it changes her promise of privacy and its relationship consequences.
Complete repair: agree to an afternoon shift without exposing the interview
Keep the prior facts: Qin told only Han about the interview. Tang records volunteer shifts at the lending station and has seen only the public message without a time. For this scene, the author selects Qin keeping her morning private, offering Saturday 14:00–16:00, and Tang accepting that slot. No interview result appears.
The faulty draft has Tang say, “Come after your nine o’clock interview—you wanted that training place, didn’t you?” Qin replies, “Don’t tell anyone yet.” Tang has no source, and the reply establishes an unapproved disclosure. Removing only the word interview while keeping a secrecy reply leaves the problem. A complete candidate:
Tang put the provisional rota in front of Qin. Saturday morning was still blank.
“You said in the group you could help Saturday. Can you do the morning?”
Qin looked at the blank without bringing the interview into the conversation. She remembered Han’s promise of privacy and did not intend to explain here.
“I have my own plans in the morning. I can cover two until four.”
“Two hours?” Tang moved the pen to the afternoon. “I’ll find someone else for the morning.”
“All right. I’ll do that afternoon slot.”
He wrote 14:00–16:00 and turned the provisional rota for her to see. Qin nodded. The morning remained blank.
Tang now knows Qin declines the morning and offers two afternoon hours. He has no interview information and has not yet found morning cover. Han is absent and does not automatically know their agreement. The interview and attendance remain future events; an entry is not completed participation.
Qin may remember Han because she experienced the private conversation. Tang does not hear that narration. If the book avoids inner narration, her limited answer and his response can preserve the same boundary.
Repair the affected passage and its later dependencies
Give /story-long-write, or $story-long-write in Codex, this request:
Revise only Tang’s shift conversation with Qin, using the previous private exchange and public message. Keep her private morning plans, offered 14:00–16:00 and his acceptance. Tang does not know the interview; Han has not learned this exchange. Remove the interview claim, secrecy reply and dependent reactions. Add no disclosure, overhearing or forwarded message. Preserve book style. Do not write an interview result, found morning cover or actual attendance. Leave other passages unchanged and first identify later reliance on Tang already knowing.
Review what each person actually learns. If Tang later asks about the result, check for an independently written disclosure before that question. Retain a valid source; otherwise flag the passage. Oh Story’s chapter workflow submits actual changes while complete snapshots retain unaffected location, resources and relationships. Editing a generated view cannot hide faulty prose.
Use the continuity audit for manuscript-wide evidence, or later-chapter synchronization after removing an earlier acquisition scene.
FAQ
Can a character use a secret revealed by omniscient narration?
Not automatically. Readers receiving narrated information does not mean a character heard it. Their use still needs an acquisition or inference supported by the story.
Is a correct guess always a continuity error?
No. A supported inference can be correct and still remain a guess. Check available clues, whether language turns inference into confirmation, and whether the reply actually discloses more.
Do it with the skill
Use /story-long-write, or $story-long-write in Codex, to repair premature knowledge in this conversation. Supply actual earlier acquisition and this scene’s goal. Keep valid progress; revise unsupported lines and reactions without invented overhearing, forwarding or prior disclosure. Identify later dependencies and preserve unaffected facts and style.
Read the method: Character, reader and mistaken knowledge in chapter outlines · Separate character knowledge, facts and reader understanding · Later knowledge dependencies and complete current snapshots · Style does not change information bounds or invent acquisition