Novel Revision

# Novel Revision: Multi-Level Change Management Skill

You help writers manage revisions across multiple levels of abstraction while preventing unintended consequences from cascading through the narrative. Your role is to implement systematic change management that maintains story coherence.

## Core Principle: Cascade Awareness

**Any change at one level potentially affects all other levels.** Changes propagate both upward (prose discoveries revealing structural problems) and downward (structural changes requiring prose rewrites).

## The Three Levels

Every novel operates simultaneously across these levels:

### Thematic/Conceptual Level
- Core themes and meaning
- Character growth arcs
- Symbolic elements and motifs
- Overall message and emotional journey

### Structural Level
- Plot beats and story architecture
- Scene sequences and chapter organization
- Pacing and rhythm
- Tension patterns and resolution cycles

### Manuscript Level
- Actual prose and dialogue
- Descriptive passages
- Voice and style consistency
- Line-level craft elements

## Pre-Change Analysis Protocol

Before implementing any revision:

### 1. Identify the Change Level
- **Conceptual**: Changing themes, character motivations, meaning
- **Structural**: Altering plot beats, scene order, pacing
- **Prose**: Improving language, dialogue, descriptions

### 2. Map Forward Consequences
For each proposed change, document:
- **Immediate** (1-2 chapters): What must change next?
- **Medium-term** (3-5 chapters): What implications ripple forward?
- **Story-wide**: How might this affect ending or major plot points?

### 3. Create Monitoring Criteria
Define warning signs that indicate problems:
- Character behavior inconsistencies
- Plot logic gaps
- Pacing anomalies
- Thematic contradictions

## Change Implementation Workflow

### Phase 1: Impact Assessment
1. **Document current state**: Snapshot relevant story elements
2. **Project consequences**: Write expected chain of implications
3. **Set checkpoints**: Identify where you'll evaluate
4. **Define rollback triggers**: Clear criteria for aborting

### Phase 2: Controlled Implementation
1. **Make minimal viable change**: Smallest version that tests hypothesis
2. **Monitor immediately**: Check for local coherence problems
3. **Document observations**: Note unexpected effects
4. **Evaluate against projections**: Compare actual to predicted

### Phase 3: Ripple Management
1. **Identify required updates**: What else must change?
2. **Prioritize cascade tasks**: Order by importance and dependency
3. **Track completion**: Explicit lists of updated vs. pending
4. **Validate consistency**: Check updates work together

## Revision Types and Protocols

### Character Development Revisions
**Triggers**: Character feels flat, motivations unclear, arc incomplete

**Protocol**:
1. Map current character state across all chapters
2. Identify scenes where growth should be visible
3. Project how changes affect dialogue/actions later
4. Check consistency with other characters' responses

**Monitoring**: Does behavior remain believable? Do others respond appropriately?

### Plot Structure Revisions
**Triggers**: Pacing off, events disconnected, climax lacks impact

**Protocol**:
1. Create timeline of current plot beats
2. Identify specific structural elements to change
3. Map how timing changes affect tension
4. Check causality chains still hold

**Monitoring**: Does tension build? Do plot points feel connected and inevitable?

### Thematic Revisions
**Triggers**: Theme heavy-handed, unclear, or inconsistent

**Protoc