book-genesis-codex

A book manuscript pipeline structures drafting into intake, foundation, architecture, drafting, adversarial audit, scoring, and editorial packaging phases. It enforces file-backed state persistence via PROJECT_STATE.yaml, requiring audit completion before advancing.

Adversarial evaluation in LLM book production applies structural criticism before scoring to catch over-explanation, repetition, weak character voice differentiation, and structural failures, blocking pipeline progression until the manuscript passes this quality gate.

Automated book production pipelines support fiction, memoir, nonfiction, and hybrid long-form book production. They manage durable project state and phase-by-phase artifacts across these genres to ensure consistent manuscript drafting.

Manuscript drafting pipelines generate production-ready editorial assets including loglines, back-cover blurbs, synopses, cover briefs, formatting notes, and query strategies as final delivery artifacts after scoring.

Book generation pipelines block progression to enforce evidence-required quality gating. A Genesis Score evaluates the manuscript using floor and threshold gates, ensuring adversarial audit completion and structural validation occur before revision readiness.