BlaezMost unfinished arcs share a diagnosis: the writer knows the vibe (“she learns to trust”) but not the machine — what she wants, what she believes that is wrong, what costs make her choose differently. The arc lives in a journal entry. The draft never cashes it.
A story bible fixes that when it is not a scrapbook. Character records with arc fields, linked relationships, and named motivations give you a ledger: deposits in scenes, balance visible at the end.
The minimum arc kit (four lines)
For each major character, store four lines you will still understand in month nine:
- Want — visible goal (get the job, save the sibling, win the case)
- Need — what growth actually requires (tell the truth, share control, forgive)
- Lie / wound — the belief that makes want feel safe (“If I need anyone, I lose”)
- Choice — the late-book decision that proves change (or tragic refusal)
That is the arc. Everything else — backstory, aesthetics, favorite food — supports readability, not change. If your bible has pages of traits and blank arc fields, continuity will be pretty and transformation will be missing.
An arc is a series of choices with prices. Motivation is why the price hurts.
Arc fields in the bible — not in a separate doc
When arc lives beside the manuscript, revision stays honest:
- Update the lie when you realize act two softened it
- Update the choice when the ending pivots
- Jump from the character card to appearances and read every scene they touch
Scatter arc notes in Google Docs and the draft will drift. One entry per character, same file as scenes — that is what story bible means in practice.
Motivations: name the fuel
Motivation is not “she’s complicated.” List two or three engines:
- External — money, status, survival, duty
- Relational — approval, rivalry, protection, belonging
- Internal — guilt, pride, curiosity, shame
In each act, one engine should dominate a scene. When dialogue feels interchangeable, the motivation field is empty — see dialogue that sounds like your character for tagging voice once motivations are clear.
Relationships: arcs collide
People change in relation to other people. In the bible, link relationships explicitly:
- Protagonist ↔ mentor (trust curve)
- Protagonist ↔ rival (respect curve)
- Protagonist ↔ love interest (vulnerability curve)
For each link, one line: what this relationship costs the protagonist to maintain the lie. “Mara and Jon: she performs competence; he offers help; accepting help = admitting the lie.”
Relationship arcs are often how internal arcs become visible. A trust beat is a scene, not a paragraph about backstory.
Map beats to scenes — same habit as plotlines
Treat the internal arc as a plotline with payments:
- Act one: lie works (short-term win)
- Act two: lie costs (midpoint complicates)
- Act three: choice (need wins or loses on purpose)
Link each beat to a scene container. If “accepts help” has no scene, the arc is a wish. This pairs with plotline tracking: internal arc is often its own colored thread.
Finishable arcs vs. infinite depth
You do not need a therapist’s file. You need enough structure to write the next scene:
- Primary POV — full four-line kit + three motivations + key relationships
- Secondary with arc — want, lie, one relationship, one choice
- Functional cast — role + one trait for voice; no arc unless they earn one
Adding arc fields to every named extra is how bibles become mausoleums. Be stingy; be clear.
Revision pass: arc audit (20 minutes per lead)
- Read arc fields aloud. Still true?
- Scan appearances in order. Mark first scene the lie is tested, first scene it costs, last scene it resolves
- If any column is empty, outline one scene to fill it — do not “fix” with interior monologue
- Check relationship links: did any bond go static for 80 pages?
- Update bible fields to match the draft you intend to keep
Continuity errors break trust; unfinished arcs break meaning. Both live in the bible — see the cost of inconsistent characters for the continuity side of the same coin.
When the arc should not finish
Tragedy and static protagonists are valid. The bible still helps: write the choice refused as the ending beat. “Need” listed but never chosen is a tragedy arc — if you meant it. If you did not, the audit above will embarrass you early, which is cheaper than a rewrite from scratch.
FAQ
Flat arc heroes?
A flat arc protagonist changes the world, not themselves. Bible the world’s lie and the hero’s fixed truth; track how scenes apply pressure anyway.
Ensemble casts?
One arc gets primary color on the grid. Others get at most one turn each. More is a series problem, not a single-volume problem.
Pantsers?
Fill arc fields after the first draft — retroactively. The audit still works; you are naming what you already wrote so act three can pay it off.
Arcs in the same file as the draft
BlaezForge character records hold traits, arc notes, relationships, and appearances in one project — linked to scenes and plotlines so the bible and the manuscript cannot drift into different apps. Finish the arc in the book, not in a sidebar you stopped opening.