FABLE Bible: reusable story-to-production method
On this page
The supplied FABLE Competition Bible, Volume 2 is a creative reference collection containing twenty concept examples across grounded and anime styles. It is useful for how it turns a premise into an executable concept. It is not a source of verified platform capabilities, current tool pricing, eligibility rules or guaranteed outcomes.
What the Bible contributes
| Bible element | Studio control | Where to use it |
|---|---|---|
| Genre, tone and audience frame | Select the intended emotional contract before choosing images or tools | Stage 1: Shape your idea |
| Logline | State the protagonist, disruption and forward motion in one sentence | Stage 1: Brief |
| Twist or turn | Identify a planned reveal, reversal or recontextualization and seed its setup | Stage 2: Story |
| Key visual | Choose one image that expresses the promise without replacing the story | Stages 2–4: Story, canon and scene packet |
| Mood, camera and sound profile | Write a compact sensory direction that the scene packets can test | Stages 3–4: Canon and scene planning |
| Timed scene progression | Turn the story into beats with time allocated for setup, action, reaction and consequence | Stage 4: Scene packet |
| Suggested generation route | Treat the listed route as a hypothesis; preflight the actual available tools, controls and cost | Stage 5: Controlled tests |
Add this to every new brief
Copy this lightweight card before developing a script:
FORMAT / AUDIENCE:
GENRE AND EMOTIONAL PROMISE:
LOGLINE:
TURN OR PAYOFF:
KEY VISUAL:
MOOD / CAMERA / SOUND RULES:
BEGINNING → CHANGE → CONSEQUENCE:
DELIVERY AND RIGHTS CONSTRAINTS:
RISKIEST SHOT OR EFFECT:
TEST AND RETRY BUDGET:
The card is a planning aid. A creator may decide that a film has no twist, that a key visual is deliberately absent, or that silence is part of the sound rule. Record that choice rather than forcing a familiar structure onto every genre.
Feasibility before generation
For each proposed beat, ask four questions before paying for a render:
- What must the audience understand in this beat?
- Which single visible action or change proves it?
- What asset, motion, transformation, dialogue or sound dependency could fail?
- What is the cheapest controlled test, and what will change if it fails twice?
If a concept depends on multiple changes, several points of view or a long chain of precise action, split it into shots and give each one a handoff. A polished mood description is not a substitute for physical action, continuity or edit coverage.
What is intentionally not adopted
The Bible’s named engines, directors, commercial categories, scene count, scene duration and statements such as “why it wins” are example-specific creative proposals. Their availability, pricing, limits, performance and eligibility must be checked at the time of use. The workflow never infers that a tool can complete a shot, that a concept will perform well, or that a competition accepts it.
Source boundary
This map is derived from the user-supplied PDF, FABLE Competition Bible — Volume 2. It summarizes a method and does not reproduce the collection’s full concepts, scripts or prose. Keep the original PDF with the project’s private source references.