decisions/review/FABLE_PAYLOAD.md
How to run: in a Fable-5 session with read access to this repo, paste this instruction; Fable reads docs/review/STORY_REEL.md directly (no need to paste the reel in). Single context, reasoning MAX (high is an acceptable faster/cheaper fallback) — do NOT fan out; the whole-arc single-pass read is the point. Its return lands in docs/review/FINDINGS.md. The reel carries the orientation, quality standard, design vocabulary, arc map, and gate summary in its header; this payload is the reviewer's task and rubric.
---
Read docs/review/STORY_REEL.md from this repo — the complete 79-node story spine of a AAA action-forward fantasy adventure RPG — and review it for STORY QUALITY ONLY. The mechanical layer — canon consistency, hard-line compliance, formatting, pacing-mode spacing, continuity carry-forward, and the gameplay expression of the three layers — is ALREADY verified elsewhere. Do not re-check it, and do not fault the story for gameplay you cannot see. Spend all judgment on what only a reader can assess: whether this is a gripping, beautifully written story that meets the AAA-cinematic standard in the reel header and is worth 79 chapters of a player's life.
The reel opens with your orientation, the quality standard, and this game's design vocabulary (the premise; the three PLAYER TRACKS L1/L2/L3; the reveal architecture; the through-lines; the cultural-restraint context). Everything after the divider is the story in player-experienced order: each chapter's body prose verbatim, with the chapter-to-chapter transition interleaved (all transitions are authored to the same five-part form — Departure / Passage / Arrival / Transition sequence / Continuity). Hold the WHOLE arc at once; your entire value is the properties no single-chapter check can see.
Judge against the DUAL standard in the header: the AAA engagement FLOOR (would this lose a mainstream action-RPG player here?) AND the literary/thematic CEILING. Both matter. Treat the named relief chapters (Ch 27 / 52 / 57) as intended valleys, not failures — assess whether they relieve and re-set tension effectively. Judge the three layers AS THE PROSE RENDERS THEM, never faulting the game for mechanical expression absent from the text. Where you give a preference that may be wrong for this specific slow-burn, immersion-first design, say so and let the author judge. Tag every finding with chapter number(s) and severity (CRITICAL / MAJOR / MINOR); name chapters, quote the line or beat, say why. Where the whole is strong, say so plainly; do not invent problems to look useful.
1. ENGAGEMENT / TENSION CURVE. Felt rise-and-fall across all 79, judged against the AAA engagement floor. Name every SAG (flat, repetitive, momentum-losing) and RUSH (unearned escalation) — excluding the intended relief valleys, which you assess separately (do they relieve and re-set?).
2. CHAPTER-TO-CHAPTER FLOW. Using the interleaved transitions, judge each handoff: does Ch N carry momentum into Ch N+1, or does the arc lurch, reset, or go inert? Flag dead handoffs, tonal whiplash, and carry-forwards asserted but not emotionally earned — by chapter pair.
3. DOES THE PREMISE SUSTAIN 79 CHAPTERS. The spine is a journey home through immersive cultural exploration. Does that engine stay compelling for the full arc for a AAA action-RPG player, or wear thin at the midpoint? If it flags, name where it loses power and what escalation or complication would re-energize it. Does the arc have enough STRUCTURAL variety (not just new settings) to earn its length?
4. IMMERSION vs LECTURE (Layer 2). The design promise is that real cultures are learned by living inside them, never lectured. Flag any chapter where cultural or historical material is delivered as exposition/lore-dump rather than dramatized through action and experience. This is a core design tenet — be strict.
5. REVEAL ARCHITECTURE. Does the slow burn work as drama? Is the ~Ch 38 mid-reveal earned by its buildup? Is the Ch 76-77 payoff seeded richly enough across the arc, or thin anywhere? Flag reveal discipline that reads as withholding-for-its-own-sake vs genuine tension. Is Ch 65's lock-in a real turn?
6. THEMATIC THROUGH-LINES. For each major theme (finding home/belonging; the vril-bargain-that-empties; suppressed/erased knowledge; hiding vs being seen; the connectedness the game never states aloud; and any others you find), trace its strength across the arc; name where it weakens, disappears, or repeats.
7. THREE-LAYER BALANCE (as prose). Per chapter: does the narrative serve the surface story (L1 — works on action alone), seed investigable cultural depth (L2 — present but not lecturing), and keep the metaphysical undercurrent implied and pattern-based, never declared before Ch 76 (L3)? Flag L1-thin chapters (action with no resonance), L3 leaks (metaphysics too explicit early), and L3 vanishing (no undercurrent at all).
8. PROSE QUALITY & VOICE. Sentence level: vivid and cinematic, or competent-but-flat? Does the voice hold a consistent, distinctive register across all 79, or drift? Distinct from generic fantasy prose, or stock phrasing? Quote the strongest and weakest passages by chapter. Flag chapters below the arc's standard.
9. EMOTIONAL RANGE. Varied notes — wonder, dread, warmth, humor, grief, awe — or the same register (e.g. melancholy loss) too often? Map the emotional palette across the arc; flag monotony of TONE even where events vary.
10. CHARACTER & RELATIONSHIP ARCS. Do found-family, familiar bonds, the Healer's-Child mystery, and the protagonist's own interior arc cohere and pay off across the sweep? Flag any that stall, drop out, or resolve unearned.
11. REPETITION / MONOTONY. Motifs, beat-structures, boss shapes, or emotional notes recurring too often across the arc — each may be individually clean; catch the aggregate. Chapter references required.
12. OPENING & THE ENDING'S EMOTIONAL DEBT. Is the Prologue / Ch 1 / Ch 2 hook strong enough to commit a player? Does the Ch 76-77 "the antagonist is your own consciousness" reveal land as genuinely MEANINGFUL — paying the emotional debt of 77 chapters — or is it a clever twist that does not earn the feeling? Judge the Epilogue as the final note the player leaves on.
13. TOP 10 HIGHEST-LEVERAGE FIXES. Ranked by improvement-per-unit-rework, each with a chapter reference and a specific change.
---
After Fable returns: findings → docs/review/FINDINGS.md. For each window flagged SAG or MAJOR/CRITICAL, pull the full CH_NN.md (plus the flagged transitions) and send only that slice back to Fable for a deep read + fix guidance → docs/review/DEEPREADS.md. That output feeds an Opus revision pass on the source chapters. Per the reel's build discipline, ANY change to a source chapter means the reel is rebuilt (python docs/review/build_reel.py) and re-verified before the next review.