Chapter Generation and Quality Gates

A full chapter typically passes through context loading, a chapter control card, draft generation, rhythm editing, language review, narrative-authenticity review, continuity/fact review, independent final review, local patches, repeated review, and an author confirmation card.

The UI shows public task summaries, active nodes, duration, tokens, evidence, and receipts; it does not reveal a provider’s private chain of thought. Long chapters, multiple reviewers, thinking mode, and large context take longer. A highlighted active node with increasing elapsed time indicates ongoing work.

When checkpoints remain valid, retry from the failed stage rather than regenerating completed work. Continuity review retrieves evidence relevant to source-sensitive claims. Network or empty-response recovery may use a smaller request with the same evidence, but review failures must remain visible.