A writing studio for long-form fiction: it fixes a Bible of the book that enters every generation, and runs six deterministic checks after each chapter, so that by chapter 30 nobody has changed name or come back from the dead.
Chapter 30, nobody back from the dead
Book Bible · characters: Elena, Tomás, Aurora
- impossible chronology
- name absent from the Bible
- copied phrase of 8+ words
- pacing off by over 30%
- sentence of 60+ words
- unsourced figure
On screen
Real screenshots of the application
What it is
Writing a sixty- to two-hundred-thousand-word novel with a model always broke at the same place: by chapter 30 the model no longer remembered what happened in chapter 3. Characters change names, the dead come back, timelines stop making sense. The alternative was a chat plus a notes document kept by hand, or a word processor with no help at all. iEscribano fixes a Bible of the book — characters, places, chronology, glossary — injected into every request in a fixed order, and after each chapter runs six mathematical checks, with no model involved, that catch contradictions before they pile up.
Who it's for
Someone writing long-form fiction in Spanish, with a GPU able to serve a 35B model locally, who is not scared of a terminal.
How it works
The Bible before the prose
Premise, tone, point of view, and the cards for characters, places and chronology. That canon is injected into every request in a fixed order: canon, chapter beats, summary of what has happened, project voice.
Outline, beats and prose
Three chained phases: a global chapter outline, per-chapter beats with the purpose of each scene, and scene-by-scene prose, streamed. “Forge the whole book” chains them and stops the moment a critical finding appears.
Six checks with no AI
After each chapter: impossible chronology, names absent from the Bible, phrases copied verbatim at eight words or more, pacing deviation above 30%, sixty-word sentences overloaded with adverbs, and unsourced figures in non-fiction.
A revision desk that rewrites
A literary inspector reviews and rewrites each scene against an objective verifier, up to two rounds. Every regeneration first stores a snapshot of the version: the current database holds 4,246 of them.
Deterministic export
EPUB, PDF, DOCX and Markdown with cover and table of contents, generated with no model involved.
Scope
Scope:
- The AI features use a local model server; the editor and the Bible always work.
- It is a personal studio, designed for one person who writes.
- It is built for Spanish: the interface, the prompts and the checks — adverbs ending in “-mente”, for instance — are designed for that language.
- The app polishes scene by scene; judgement of the whole book — its arc, its pending promises — happens in a later phase.
Frequently asked
What does the local model bring, and what does iEscribano bring?
The local model writes the draft; the book is polished afterwards with a cloud model, and at that stage the manuscript leaves the machine. What iEscribano contributes is the structure: The Bible, the deterministic checks, the version history and the pipeline that stop a two-hundred-thousand-word book from falling apart from the inside. That works with any model, today and in three years.
An important precision: writing and scene-by-scene revision happen entirely on the author's machine, but the final polish and the judgement of the complete book are done with a cloud model, and at that stage the text does leave. Fifteen novels are in progress, and the next step is to run the closing flow end to end.