08 — Structure

Volume Blueprint

The per-volume implementation document that bridges system rules to chapter-level drafting — seven required sections, vocal signatures, trajectory tables, and generation sequence.

Purpose

A Volume Blueprint is a per-book implementation document. It takes the Narrative Architecture's spine, the Structural Protocol's trajectories, and the Persona Model's POV instruments, and assigns them to specific chapters — with specific content, specific values, and specific prose instructions.

The system documents define what is true. The Volume Blueprint defines what happens, in what order, through whose perception, at what pace.

The relationship is: the Persona Model defines the instrument's specifications, permanent across volumes. The Volume Blueprint defines the instrument's score for a specific composition — per-volume, evolving.


Relationship to System Documents

System DocumentWhat It ProvidesWhat the Blueprint Adds
Narrative ArchitectureSeven-beat spine, escalation compression model, uncontrollable event requirementAssignment of spine beats to specific chapters; specific uncontrollable events per chapter
Structural ProtocolNumeric trajectory principle, convergence mechanics, framework collision theoryPer-chapter trajectory values with chapter-mapped numbers
Persona ModelPOV instruments — epistemic lenses, stress responses, terminal statesPer-volume vocal signatures — how each POV's instrument sounds in this book
Story Spine ValidatorStructural validation schemaThe Blueprint is what gets validated; the schema checks the spine; the Blueprint populates it

Seven Required Sections

Every Volume Blueprint contains seven sections. No section is optional.

I. Series Position

What has happened before this book — not a summary, but a state handoff. Lists the specific conditions, counts, locations, and unresolved threads the volume inherits. Required elements: current count, current site state, technique evolution state, institutional architecture state, unresolved threads from prior volumes, what has changed since the previous volume's end.

II. Vocal Signatures

Per-POV prose instructions for this volume. See Vocal Signatures section below for the full five-field specification.

III. Chapter Map

The act structure with chapter assignments. Must include: total chapter count, total word target, POV rotation pattern, pace rule (which acts have room, which do not).

Required ColumnContent
ActWhich act (with transition labels for boundary chapters)
ChaptersChapter range
Spine BeatWhich Narrative Architecture beat(s) this act covers
Word RangePer-chapter word target

IV. Chapter-by-Chapter Entries

One entry per chapter. Each entry contains the chapter number and title (following the POV's chapter title pattern), POV, word count, spine beat, what happens (scene-level content — physical, not thematic), the uncontrollable event for this chapter, scene breaks, continuity (required for Act I and any chapter inheriting state from a prior volume), dependencies, and optional drafting notes. Entry quality rule: every entry contains what the drafter needs and nothing else.

V. Tracking Trajectories

Per-chapter values for every monotonic numeric trajectory in the volume. Each trajectory maps chapter numbers to values. Required properties per trajectory: name, POV owner, direction (ascending/descending/compressing), per-chapter values, terminal state.

Non-numeric trajectories (e.g., scar state: hurts → stops hurting → warm → different register) follow the same table format using descriptive states instead of numbers. All trajectories must satisfy the monotonic rule: no reversals without transformation.

VI. Drafting Rules

Consolidated from the system prompt and Narrative Architecture for drafter reference. Not new content — repetition of rules the drafter must have visible during drafting.

VII. Cross-Volume Notes

State handoff notes for volumes that precede or follow this one. Includes structural patterns from existing manuscripts, revision notes, and dependencies on spine generation for adjacent volumes.


Vocal Signatures

Each vocal signature extends a POV character's permanent Persona Model attributes with volume-specific prose refinement. The Persona Model says "stress response: narrow measurement." The vocal signature says "Opens with: 'The delay was [X.XX] seconds.' The measurement. Always the measurement." — specifying how that abstract attribute manifests in this book's specific drafting context.

FieldFunctionExample
Opens withThe first thing in every chapter — the signature's anchor. May evolve across the volumePrayer word count: two → one → none → gone → three
Thinks inWhat occupies the character's interiority — not thematic, but perceptual: what the body notices, what the instrument readsDelay columns, scorch pattern radii, weight differentials
Sentence shapeProse rhythm: length, structure, accumulation pattern. The sentence mirrors cognition styleShort declaratives under stress. Long lists during documentation. No metaphor.
Never doesThe absolute constraint — what this POV must not narrate, think, or articulate directlyNever names grief directly. States the number. The number is the grief.
Chapter title patternThe naming convention for this POV's chapters"The [measurement] was [value]" or "Day [N]"

Generation Sequence

Volume Blueprints are generated in order. Each step depends on the previous.

  1. Story spine first. Generate the volume's story spine using the Story Spine Validator schema. The spine provides the beats, the cast, the resolution type, the cost structure.
  2. Trajectory assignment. Take the monotonic trajectories from the Structural Protocol (or define new ones for this volume) and assign specific values to specific chapters. Validate: no reversals, terminal states reached at the correct structural position.
  3. POV rotation. Assign POVs to chapters following the rotational architecture. Deviations must be structurally motivated and documented.
  4. Chapter map. Assign spine beats to acts, acts to chapter ranges, chapter ranges to word targets. Apply the escalation compression model: Act I word counts are the highest, Act III the lowest.
  5. Chapter entries. Populate every chapter with what happens, uncontrollable event, scene breaks, continuity, dependencies, drafting notes. Uncontrollable events must escalate per the Narrative Architecture's pattern: ambient → structural → framework → irreversible.
  6. Vocal signatures. Refine the Persona Model's permanent attributes into volume-specific prose instructions. Identify what evolves across this volume.
  7. Validation. Check against all seven system invariants. Verify trajectory monotonicity. Verify every chapter has an uncontrollable event. Verify POV rotation consistency.

Validation Checklist

Before a Volume Blueprint is considered complete:


Existing Instances

VolumeBlueprint StatusNotes
Book 1 — Those We CountNot generatedRequires spine generation first. Structural patterns documented in Book 4 Blueprint's cross-volume notes
Book 2 — Those We ArmNot generatedRequires spine generation first. Manuscript exists; Blueprint is reverse-engineerable from the manuscript
Book 3 — Those Who RemainNot generatedRequires spine generation first
Book 4 — Those Who CrossComplete37 chapters, 6-POV rotation + Narem (3 insertions) + Lira (coda). 110,000–130,000 words