How I Write
The Constraint Narrative Framework
What This Is
This is the system I use to design and write every novel I publish.
It is a top-down narrative construction and validation framework built on constraint, consequence, and inevitability.
Stories are not discovered during drafting.
They are designed, expanded, executed, and enforced through a controlled system.
The Core Principle
All narrative operates under:
Constraint → Consequence → Irreversibility → Inevitability
Constraint defines what is possible
Consequence enforces the cost of action
Irreversibility prevents regression
Inevitability determines the outcome
The story is a system.
Once it begins, it can only move forward.
System Nature
This framework is not a flexible process.
It is a controlled system.
Each stage defines the next.
Each decision restricts what follows.
Each action removes alternative outcomes.The story is not shaped during writing.
It is executed within a system that has already been defined.
Concept Development
Every project begins with an idea.
The idea is stress-tested to determine its natural scope:
If it resolves cleanly within a single arc, it becomes a standalone
If resolution requires extended escalation, it becomes a multi-book series
If a series is required:
A macro arc is created for the full series
A complete story arc is defined for each individual book
No drafting begins until the narrative scope is fully determined.
System Construction
Once the story arc is defined, the system that governs it is built.
Lore Bible
A complete lore bible is created for the world.
This includes:
System mechanics
Rules and limitations
Costs and consequences of use
Environmental behavior
World logic and consistency
The lore bible defines how the world functions.
Series Structural Lock
A structural lock is created for the project.
A base model exists, but it is modified for each standalone or series.
This lock defines:
Narrative structure
Escalation model
Interaction between systems
Constraints unique to the story
Each project operates under its own structural system.
Once defined, the lock is absolute.
Beat Architecture
The full story is expanded into complete beats.
These are not generalized markers.
Each beat includes:
Action
Emotional shift
Irreversible change
Every beat must move the story forward in a way that cannot be undone.
Chapter Construction
Chapters are built directly from the beat structure.
Each chapter contains one irreversible beat
The number of beats determines the number of chapters
Chapters exist to execute structural movement, not to segment content
Chapter Outlining
Each chapter is fully outlined before drafting.
This includes:
Chapter title
8–12 sentence plot summary
Bullet list of all beats within the chapter
This process is completed for:
Every standalone
Every book in a series
No prose is written before this stage is complete.
Part-Level Outlining
Before drafting a chapter, it is broken into parts.
Chapters typically contain 4–7 parts, depending on beat complexity
Each part is designed to execute specific portions of the chapter
All parts are fully outlined before any drafting begins.
Each part has:
A defined purpose
A clear sequence of events
Alignment with both beat structure and chapter intent
No part is drafted until the entire chapter—at the part level—is fully structured.
Drafting Process
Drafting occurs only after full structural definition.
Each part is written according to its outline
All content must align with the lore bible
All structure must align with the structural lock
All movement must align with the beat architecture
Prose is execution.
No discovery occurs during drafting.
Chapter Assembly
Once all parts of a chapter are written:
The parts are combined into a complete chapter
Flow and continuity are verified
Validation Passes
Validation is enforced at multiple levels.
Chapter Validation
After each chapter:
The chapter is reviewed for alignment with the lore bible
Structural lock compliance is verified
Beat integrity is maintained
Inconsistencies are corrected
If necessary, sections are rewritten.
Manuscript Validation
After the full book is complete:
The entire manuscript is reviewed
Lore consistency is enforced across all chapters
Structural integrity is verified at the book level
No inconsistencies remain.
The Role of AI
AI is used as a controlled execution and validation tool.
It assists in drafting within defined constraints
It is used to verify adherence to the lore bible and structural lock
It does not define story, system, or outcome
AI operates inside the framework.
Authorship resides in system design and enforcement.
Why This Works
This framework produces consistent narrative outcomes because:
Constraint removes invalid paths before they can form
Consequence ensures every action carries forward
Irreversibility prevents regression and repetition
Structural enforcement eliminates deviation during execution
The story cannot lose coherence because coherence is enforced at every stage.
The system does not rely on revision to correct failure.
It prevents failure during construction.
What This Produces
Structured, irreversible progression
Consistent world systems
Controlled escalation across entire books and series
Narratives that move forward without regression
Outcomes that feel inevitable
What This Is Not
Discovery writing
Improvisational storytelling
Flexible or adaptive plotting
Content generation
This framework is not designed for exploration.
It is designed for control and validation.
Closing
Every story I write is governed by the same system:
Constraint defines the boundaries.
Consequence enforces movement.
Irreversibility prevents retreat.
Inevitability determines the end.
The story does not evolve during writing.
It has already been built—and is executed accordingly.
The Constraint Narrative Framework
Defined and first published: April 6, 2026