continuity

Coherence and logic checks (continuity)

The real cause of a long work's collapse is not being unable to keep writing, it iscontradictions before and after, a messy timeline, setting drift—this is especially true when AI writes long works: 50 chapters are normal, at 100 chapters it starts to collapse, by 300 chapters it has completely lost its memory. This skill is the "logic defense line" of a long work, and pairs with memory(memory): the archive is responsible forrecording, and this skill is responsible forchecking。

When to use

• Writing a long work, checking logic once every chapter / few chapters
• Afraid that "later on the setting collapses / characters drift / foreshadowing is forgotten"
• Checking the timeline (whether "three days later" "two months later" is actually messy)
• Checking whether resources / injuries / identities / power levels match up from beginning to end
• Doing a full coherence health check at the end of each volume
• And review difference:review isreader retentionperspective (hooks / payoff moments / making readers keep reading); this skill isauthor backstageperspective (settings do not contradict, logic can be self-consistent)

How to check (seven logic chains + timeline / world state)

Checking chapter by chapter against the archive (01_人物.md / 03_伏笔追踪.md / 07_时间线.md / power-level table / emotional trajectory), see references/continuity-check.md：

1. Reasonableness of character behavior — does the behavior have motivation? Does it conflict with the character setting? (A wanted criminal will not go shopping for steamed buns)
2. Plot causal chain — is the new setting foreshadowed? Are the pits dug recorded in the foreshadowing table? (Prevent "suddenly popping up / dug but not filled")
3. Resource changes — money / props / troops can only increase or decrease according to the plot (prevent "last chapter could not afford food, next chapter pulls out one hundred thousand spirit stones")
4. Identity exposure status — maintain the "list of people in the know": who knows the protagonist's true identity / strength / alternate identity (the lifeline of the pretending to be weak to eat the tiger genre)
5. Injury / status persistence — severe injury / poisoning / seclusion must persist, and must be fulfilled when it expires (prevent "dying → next chapter fighting three hundred rounds")
6. Power level / rank consistency — check against the power-level table; if there is no improvement, do not fight evenly across tiers
7. Emotion / relationship continuity — check against the emotional trajectory; jumps need transitions (prevent "just broke up → next chapter laughing happily")
8. Timeline + world state — every "after X time" can be converted into a point on the timeline; parallel lines converging do not contradict; deadlines are fulfilled when reached; for strong-setting genres also checkworld state(was the North City they went to already destroyed in the previous chapter, see world skill)

Workflow

1. First read the archive (if no archive has been built, first use memory to initialize, at minimum there must be character status, foreshadowing table, timeline, power-level table).
2. Read the chapters to be checked, go through the six chains + timeline one by one.
3. Producecoherence health check report(format see below), locate contradictions to paragraph / chapter + give fixes.
4. Reminder to write this chapter's changes (character status/resources/timeline/people in the know)back into the archive, otherwise the next chapter will keep drifting.

Output: Coherence Check Report

【连贯性体检 · 第 N 章 / 第 X 卷】
时间线：本章 = Day__ ｜跨度 __ ｜与主线 一致/冲突
六条逻辑链：行为/因果/资源/身份/伤势/战力 —— 逐条 ✓/✗ + 问题定位
矛盾清单：① 第_段 与 第_章/档案 冲突 → 改法（改本章/回改前文/补一句交代）
待兑现：到期未兑现的期限/伏笔（毒/闭关/约定）
档案待更新：人物状态/资源/时间线/知情人 哪些要写回

Principles

• Pinpoint to the paragraph/chapter, specify which chapter/which archive entry it conflicts with, don't be vague.
• Every contradiction must be givenan executable fix。
• Sort by severity: main plot/combat power/identity are hard flaws to fix first; secondary emotional lines left blank are not a flaw (see references/human-texture.md"Not closed-loop ≠ bad ending").
• After checking, must remindto write back to the archive— this is the closed loop that prevents amnesia.

Coordinate with

• Memory/Archive/Timeline/Combat Power Table → memory（references/project-memory.md）
• Reader retention five-dimension diagnosis → review
• Fix contradiction chapters → expand rewrite; foreshadowing payoff → review dimension 3.