Criteria-led reading
The manuscript is read through stable editorial criteria so feedback is not a random chat response or a matter of taste alone. The same core language lets authors compare reports across drafts.
Methodology
RevisionGrade evaluates manuscripts through stable criteria, evidence-backed diagnosis, and revision restraint. The goal is not generic feedback. The goal is to identify what the manuscript asks the reader to believe, where that trust holds, and where it breaks.
Method standard
The manuscript is not judged by vibes.
The report should explain why a finding matters.
Revision follows diagnosis; it does not replace it.
Reading principles
The methodology keeps the product from becoming a generic critique engine. It reads through stable editorial dimensions, requires evidence, respects long-form behavior, and avoids unnecessary rewriting.
The manuscript is read through stable editorial criteria so feedback is not a random chat response or a matter of taste alone. The same core language lets authors compare reports across drafts.
Major findings should be traceable to the submitted pages and explained in terms the author can act on. A score without evidence is a verdict, not a diagnosis.
Novel-length work requires attention to recurrence, payoff, pacing over distance, character behavior, escalation, closure, and cumulative reader experience.
A recommendation is not automatically an instruction to rewrite. Some passages should be repaired; others should be protected, preserved, clarified, or left alone.
Evaluation modes
RevisionGrade should not pretend a chapter can prove what only a full manuscript can show. Evaluation mode controls what the report can responsibly diagnose.
Under 25,000 words
Core story diagnosis
Evaluates the submitted pages against the 13 story criteria only. Designed for openings, chapters, excerpts, short stories, and shorter works where full manuscript continuity cannot yet be judged.
25,000+ words
Manuscript-scale readiness
Adds manuscript-scale analysis: continuity, recurrence, setup/payoff, pacing over distance, character behavior, structural readiness, and cumulative reader experience.
Complex long-form manuscripts
Deep architecture review
A deeper architecture audit for manuscripts that need layered evidence views, manuscript-scale continuity, proprietary repair governance, dialogue and speech protection, and deeper structural analysis where appropriate.
Thirteen Story Criteria
The 13 criteria give every report a common vocabulary. Short-form evaluations use these criteria only; long-form and multi-layer evaluations build on them where manuscript length supports deeper claims.
Whether the central idea is clear, compelling, and strong enough to sustain the promised story experience.
Whether the story generates pressure, escalation, consequence, curiosity, and forward motion.
Whether characters behave with coherence, agency, contradiction, development, and emotional credibility.
Whether the prose creates a distinct, controlled, and appropriate narrative presence without accidental flattening.
Whether scenes are built around action, tension, change, stakes, and consequence rather than static explanation.
Whether speech reveals character, pressure, relationship, subtext, rhythm, and scene movement.
Whether the manuscript develops meaning through dramatic pressure instead of lecture, repetition, or abstraction.
Whether setting, context, culture, rules, history, and environment create a credible story world.
Whether momentum, compression, expansion, turns, and recovery beats are proportioned to reader attention.
Whether the line-level writing is precise, intentional, readable, and aligned with the manuscript’s voice.
Whether the emotional and stylistic register remains coherent, deliberate, and appropriate to the material.
Whether the manuscript resolves, withholds, or complicates its central promises in a satisfying way.
Whether the manuscript can be positioned clearly for a likely readership, category, shelf, or submission path.
Evidence model
The report should not merely name a weakness. It should explain what was observed, where it appears, how it affects the reader, and what kind of revision decision follows.
What the manuscript is doing on the page: repeated behavior, missing pressure, unstable voice, over-explanation, payoff drift, or a strong craft choice.
Where the observation appears: passage, chapter, scene, pattern, structural span, report section, or long-form layer.
Why the issue matters: confusion, loss of trust, reduced pressure, emotional flattening, promise drift, or increased engagement.
What kind of intervention is warranted: preserve, clarify, compress, restructure, escalate, defer, or repair in Revise.
What makes the diagnosis different
Generic critique tells the author to improve. RevisionGrade should identify the story behavior that causes the reader effect.
Generic feedback
“Increase tension.”
Evidence-backed diagnosis
The river scene states the emotional contradiction instead of dramatizing it; the reader receives explanation where hesitation, silence, or action would create pressure.
Generic feedback
“Make the protagonist more active.”
Evidence-backed diagnosis
Across the midpoint sequence, the protagonist observes consequences but rarely makes a choice that changes the scene’s direction, weakening perceived agency.
Generic feedback
“The pacing is slow.”
Evidence-backed diagnosis
Chapters 12–14 hold conversation without a consequence-bearing turn, creating a pressure plateau before the next major reversal.
Evaluate → Revise bridge
Evaluation identifies the weakness. Revise turns the weakness into a governed repair opportunity: evidence, diagnosis, options, voice risk, and explicit author decision.
01
The submitted word count and project type determine whether the report is short-form, long-form, or long-form multi-layer.
02
The manuscript is evaluated through the 13 story criteria so the diagnostic language remains stable.
03
Major conclusions should connect to manuscript evidence, confidence, severity, and reader effect.
04
Findings can become governed repair opportunities in Revise, where the author chooses what changes.
Method boundaries
The methodology is strongest when it says what the system can diagnose and what it should not pretend to know.
Next step
Methodology explains how the system reads. Reliability explains why the author remains protected. Revise turns findings into controlled repair decisions instead of blind rewriting.