skills/novel-story-telling/references/drama.md

# Dramatic Story Design

## Contents

1. Genre engine
2. Relationship model
3. Recommended flow
4. Escalation and scene design
5. Reveals and resolutions
6. Continuity ledgers
7. Failure modes
8. Research basis

## Genre Engine

Build drama from legitimate but incompatible needs. Make the central conflict costly to state, avoid, or resolve. Silence, evasion, and bad choices require credible feared consequences; otherwise conflict becomes a preventable misunderstanding.

Treat relationship change as plot, not commentary around plot. A changed alliance, trust level, dependency, obligation, or boundary can carry the same structural force as an external victory.

## Relationship Model

For each important directional bond, define:

- what A wants from B;
- what A believes B wants;
- what A fears losing;
- the old bargain sustaining the relationship;
- the need A cannot admit;
- the fact A misreads;
- A's current leverage and dependency;
- the action A considers unforgivable;
- the conduct that repair would require.

Model both directions separately. Affection can be mutual while power, trust, knowledge, and dependency remain asymmetric.

## Recommended Flow

1. **Relational equilibrium:** show the explicit or implicit bargain holding people together.
2. **Pressure:** introduce a need the old bargain cannot satisfy.
3. **Defensible wrong choice:** let a character protect something valuable through a tactic that creates harm.
4. **Failed repair:** make apologies, concealment, bargaining, or control worsen the underlying problem.
5. **Boundary crossing:** commit an act that cannot be forgotten even if forgiven.
6. **Recognition:** let a character understand self, other, or past differently.
7. **Reversal:** let that knowledge change power, fortune, alliance, or available choice.
8. **Irreversible choice:** force a real cost in belonging, status, safety, identity, money, or future.
9. **Resolution:** use changed conduct, separation, sacrifice, renegotiation, or tragic repetition.
10. **Aftermath:** demonstrate the new relationship state through behavior.

## Escalation And Scene Design

### Escalation ladder

Use flexibly:

1. indirect request;
2. explicit request;
3. refusal or evasion;
4. leverage or ultimatum;
5. boundary violation;
6. third-party involvement;
7. public consequence;
8. betrayal or irreversible action;
9. recognition;
10. costly decision.

Increase one or two dimensions at a time: intimacy, publicity, dependency, time, material consequence, moral cost, or irreversibility.

### Scene contract

- Give every participant an immediate objective.
- Make simultaneous satisfaction impossible.
- Begin with tactics consistent with history and status.
- Make at least one tactic fail and change.
- Give dialogue a surface topic and contested subtext.
- Use action, refusal, or disclosure to change the relationship.
- Exit with a new wound, alliance, obligation, secret, boundary, or power balance.

A loud argument is not automatically escalation. A quiet refusal, withheld ritual, changed form of address, or practical act of care may produce the larger turn.

### Tactic palette

Use request, reassurance, deflection, humor, status display, withdrawal, confession, bargaining, accusation, triangulation, gift, threat, care, public claim, silence, or sacrifice. Avoid letting every character argue with the same vocabulary and rhythm.

## Reveals And Resolutions

Reveal a secret when it changes a choice, alliance, or interpretation. Seed through avoidance patterns, asymmetric reactions, missing rituals, inconsistent stories, or disproportionate care.

Track:

- who knows;
- who suspects;
- who knows that another person knows;
- what evidence could prove the fact;
- what disclosure would cost.

After a reveal, show changed conduct before introducing another major turn.

Resolution patterns:

- apology plus proportionate reparative action;
- renegotiated boundary or responsibility;
- voluntary sacrifice without coercive debt;
- public truth replacing private manipulation;
- separation accepted as growth;
- mutual recognition without reconciliation;
- redistribution of care, money, inheritance, labor, or authority;
- tragic repetition caused by a final refusal to change.

Explanation alone is not repair. Show what changes in access, habit, risk, status, and future choices.

## Continuity Ledgers

### Relationship edge

```yaml
from:
to:
affinity:
trust:
intimacy:
dependency:
resentment:
power:
public_status:
private_status:
last_change:
cause:
```

Also maintain:

- promises with exact wording, witness, deadline, breach, and repair;
- secrets with holders, affected people, evidence, suspicion, reveal condition, and consequence;
- conflicts with stated issue, underlying need, tactic history, temporary settlement, and residue;
- emotional carryover between scenes;
- shared resources, care duties, financial ties, and authority.

## Failure Modes

- Conflict survives only through implausible non-communication.
- Repeated arguments change no leverage or consequence.
- Every character expresses emotion identically.
- Twists replace causal choices.
- Instant forgiveness erases accumulated harm.
- Spectacle appears without relational groundwork.
- Recognition is spoken but does not alter conduct.
- Secondary characters exist only to give advice.
- A practical dependency disappears when inconvenient.
- The aftermath states a new bond without showing it.

## Research Basis

- Aristotle, [Poetics](https://classics.mit.edu/Aristotle/poetics.2.2.html), especially complication, unraveling, reversal, and recognition.
- Mohamed Ahmed et al., [Relational arcs as narrative structure](https://www.cambridge.org/core/journals/computational-humanities-research/article/relational-arcs-as-narrative-structure-dynamics-distribution-and-diachronic-change-in-fiction/37947D31A93A7FA276BC3E6BA67C5DFD).

Use the dramatic concepts as adaptable tools. The operational model above is synthesis for long-form prose continuity.