skills/ai-film-pipeline-master/references/phase-01-story-generation/cat-rel.md

# Relationship and Ensemble Dynamics

Category `rel`.

**Part 1 of 2.** 33 cards across five sections: the relationship as a unit that wants and changes, the standard pair shapes, the group as a system, the mechanics of keeping an ensemble scene legible, and three named failures.

This category treats two or more people as a single object of craft. Individual construction — want, flaw, backstory, contradiction — belongs to `char.`; here the smallest unit is the pair.

<!-- GENERATED:toc — do not edit by hand. Generated in the source package -->

## Contents

- [The Relationship as a Unit](#the-relationship-as-a-unit)
- [Pair Shapes](#pair-shapes)
- [The Group as a System](#the-group-as-a-system)
- [Writing the Ensemble Scene](#writing-the-ensemble-scene)
- [Named Failures](#named-failures)
- [Coverage](#coverage)
- [Sources](#sources)

<!-- /GENERATED:toc -->

## The Relationship as a Unit

### Count the Room, Then Find the Tilt

**Also called:** the relationship selector, the tilt question, what is actually between these two
**What it is:** The card at the head of the `rel.` shelf. It does not describe a bond. It asks the questions the shelf's own pair graph asks over and over — **how many people is this made of, which of them is ahead and who knows it, and are you writing an ordinary day or the one scene that spends it** — and hands back a named shortlist for each answer. Before any of the three it asks one thing first, because this family is **two decisions and not one**: *are you designing a bond, or are you managing a cast on the page?* The axes were not invented. They were read off the forty-eight `Yields to:` conditions the cards carry and the boundaries their `Avoid when:` lines draw, and the conditions that repeated became the questions. Every card cited here is cited by id.
**Effect on the audience:** None. This card never reaches the screen. It exists so that the bond that does reach the screen was chosen against the cast list, the power gap and the position in the story, rather than picked because it was the relationship the writer had already lived.
**Used for and where it works best:** Answer the opening fork out loud, then the three questions **in order and in one sentence each, before you open the shelf**. The opening fork is the cheap one and it is nearly always *designing a bond*; take the other branch only when the pair is already decided and the problem is traffic. Question one eliminates about half the file. Questions two and three leave a shortlist of three to six. If your honest answer to question one is *one person*, **stop — this shelf does not own that decision and five of its own exits say so**, all five pointing at `char.`. Where two answers fight for one pair, that is two relationships and one of them is `rel.misnamed_relationship`.
**Best in:** formats: all | genres: all
**Avoid when:** **You are repairing a draft rather than designing one.** This map lists no failures, by design, so a reader who already has a flat pair or a unanimous group will be walked straight past the card that names their problem — the failures are reached by the `Avoid when:` of the card you already chose, never by this one. Also **distrust question one whenever your honest answer is its first value**: twenty-six of the forty-eight bond cards live there, so on an ordinary two-hander this map has only two questions left and is doing half the work it does on a trio or a crowd. And **do not trust the shortlists to be complete on the far side of the shelf.** The pointer graph here runs almost entirely backwards — the distance, care, event and third-party cards point inward and almost nothing points out at them — so the answer this map gives you on those is a browse, not a route, and that is the shelf's own defect rather than a property of your scene.
**Example:**
> A returning soldier and the sister who stayed. Q0: designing a bond. Q1: two, and the shelf owns both. Q2: tilted, and both of them know it. Q3: the change, not the day.
> Intersection: `rel.reunion_after_separation` · `rel.register_change` · `rel.bond_across_a_time_jump`. Three cards, not sixty, and none of them is the homecoming speech that was about to be written.

---

**The axes**

**Fork zero — are you designing a bond, or managing a cast on the page?**
Asked before the axes, because this family answers two questions and not one, and the count is what says so. **Six of its cards form a closed island with zero edges to the other forty-eight**: `rel.ensemble_pilot`, `rel.ensemble_scene_legibility`, `rel.more_than_five`, `rel.pair_off_the_room`, `rel.rotating_spotlight` and `rel.pair_matrix` yield only to each other or off the shelf entirely — four of their six pair fields leave for `char.` and `dial.`. The other forty-eight are one dense component with twenty-five internal edges. Those six are not relationships. They are traffic control, and they are used at a different moment by a different pass.

**Axis 1 — How many people is this bond made of, and is every edge alive?**
Asked first, because it is the condition the shelf repeats most and the one that decides whether the shelf owns the question at all. `rel.triangle` and `rel.third_wheel` point at each other on nothing but this — *"The third edge is not live"* one way, *"The excluded position must sustain a long piece"* back. `rel.sibling_order` disqualifies itself at two people — *"Only two siblings, no parent watching"*. `rel.who_defends_whom` hands off when the count stops producing structure — *"Everyone defends everyone, map is flat"* — and `rel.group_hierarchy_display` does the same with *"The group is genuinely flat"*. `rel.ensemble_as_system` exits on *"Locked single subjective POV"*, which is the count collapsing to one.

**Axis 2 — Which of them is ahead, and who can see it?**
Seventeen conditions turn on the tilt, and they are stated as facts about standing rather than feelings about warmth. `rel.misnamed_relationship` hands over on exactly this word — *"Both people know the imbalance"* — and `rel.parasocial_bond` hands over on its mirror, *"The figure has to reciprocate"*. `rel.the_debt` collapses when the tilt is not real: *"Refusing the debt would cost nothing"*. `rel.mentor_and_student` names itself a deliberately unequal pair and exits when the inequality never moves — *"The bond never ends or reverses"*. `rel.locked_pair` exits when the tilt turns out to be a choice — *"The story is about choosing each other"*. `rel.parent_and_adult_child` leaves when the cost of the tilt is too high to pay — *"The adult must keep competence afterwards"*.

**Axis 3 — Are you writing the ordinary day, or the one scene that spends it?**
Asked last, and it carries an ordering law the other two do not. Nine conditions are about position in the story rather than about the bond: *"Pair has only three scenes, one change"* (`rel.relationship_arc`), *"No room to show the rule honoured first"* (`rel.unspoken_agreement`), *"The key change happened inside the gap"* (`rel.bond_across_a_time_jump`), *"The end must be gradual and unannounced"* (`rel.breakup_architecture`), *"The interest is the history, not the meeting"* (`rel.first_meeting`), *"The gap was never paid for"* (`rel.reunion_after_separation`), *"No peacetime version established yet"* (`rel.group_under_pressure`), *"Too late for a stranger to arrive"* (`rel.outsider_in_the_group`), *"The history must be explained, not referenced"* (`rel.reunion_ensemble`). **Read them together and they are one law: you may not stage the turn before the audience has been shown the normal.** Every card on the change side of this axis is a debt against a state card you have to have paid first.

---

**The map**

**Fork zero — which decision**

| Answer | The shortlist, by id |
| :--- | :--- |
| **Managing a cast on the page** (six) | sorted by which moment of the work — launching it: `rel.ensemble_pilot` · `rel.more_than_five`; running one crowded scene: `rel.ensemble_scene_legibility` · `rel.pair_off_the_room`; keeping it alive over length: `rel.rotating_spotlight` · `rel.pair_matrix` |
| **Designing a bond** (forty-eight) | go to Axis 1 |

**Axis 1 — how many people, and is every edge alive**

| Answer | The shortlist, by id |
| :--- | :--- |
| **Two, and the shelf owns both of them** (twenty-six) | `rel.relationship_as_protagonist` · `rel.relationship_want` · `rel.relationship_arc` · `rel.founding_event` · `rel.unspoken_agreement` · `rel.the_debt` · `rel.asymmetric_investment` · `rel.register_change` · `rel.locked_pair` · `rel.marriage_on_the_page` · `rel.parent_and_adult_child` · `rel.mentor_and_student` · `rel.professional_pair` · `rel.rivalry_as_friendship` · `rel.reunion_after_separation` · `rel.correspondence_bond` · `rel.across_a_language` · `rel.class_divided_pair` · `rel.location_bound_bond` · `rel.bond_across_a_time_jump` · `rel.caretaker_and_cared_for` · `rel.first_meeting` · `rel.breakup_architecture` · `rel.reconciliation_on_new_terms` · `rel.misnamed_relationship` · `rel.public_face` |
| **Two, and the second party cannot answer back** (four) | `rel.bond_with_the_dead` · `rel.parasocial_bond` · `rel.institutional_bond` · `rel.non_human_member` |
| **Three, and the third edge is the question** (five) | `rel.triangle` · `rel.third_wheel` · `rel.mimetic_jealousy` · `rel.co_parents` · `rel.bond_through_a_go_between` |
| **More than three, with an internal structure** (thirteen) | `rel.chosen_family` · `rel.ensemble_as_system` · `rel.group_secret` · `rel.group_under_pressure` · `rel.who_defends_whom` · `rel.outsider_in_the_group` · `rel.group_hierarchy_display` · `rel.shifting_coalition` · `rel.sibling_order` · `rel.expulsion` · `rel.succession_fight` · `rel.leader_removed` · `rel.reunion_ensemble` |

*`rel.sibling_order` sits under the fourth value and not the first on its own authority: its `Avoid when:` says position collapses at two siblings with nobody watching the comparison.*

**Axis 2 — which of them is ahead, and who can see it**

| Answer | The shortlist, by id |
| :--- | :--- |
| **Level — each can do to the other what the other can do to them** (twenty-three) | `rel.relationship_as_protagonist` · `rel.relationship_want` · `rel.relationship_arc` · `rel.unspoken_agreement` · `rel.register_change` · `rel.locked_pair` · `rel.triangle` · `rel.marriage_on_the_page` · `rel.professional_pair` · `rel.rivalry_as_friendship` · `rel.chosen_family` · `rel.ensemble_as_system` · `rel.group_secret` · `rel.shifting_coalition` · `rel.co_parents` · `rel.first_meeting` · `rel.breakup_architecture` · `rel.correspondence_bond` · `rel.location_bound_bond` · `rel.bond_across_a_time_jump` · `rel.reunion_after_separation` · `rel.public_face` · `rel.reunion_ensemble` |
| **Tilted, and both of them know it** (seventeen) | `rel.asymmetric_investment` · `rel.the_debt` · `rel.mentor_and_student` · `rel.parent_and_adult_child` · `rel.caretaker_and_cared_for` · `rel.class_divided_pair` · `rel.across_a_language` · `rel.sibling_order` · `rel.group_hierarchy_display` · `rel.who_defends_whom` · `rel.group_under_pressure` · `rel.outsider_in_the_group` · `rel.succession_fight` · `rel.expulsion` · `rel.leader_removed` · `rel.institutional_bond` · `rel.reconciliation_on_new_terms` |
| **Tilted, and only one of them knows — or only the audience does** (eight) | `rel.parasocial_bond` · `rel.misnamed_relationship` · `rel.third_wheel` · `rel.mimetic_jealousy` · `rel.bond_with_the_dead` · `rel.founding_event` · `rel.non_human_member` · `rel.bond_through_a_go_between` |

**Axis 3 — the ordinary day, or the scene that spends it**

| Answer | The shortlist, by id |
| :--- | :--- |
| **The change — it is staged, or traced, and it can only be spent once** (fourteen) | `rel.relationship_arc` · `rel.founding_event` · `rel.register_change` · `rel.mentor_and_student` · `rel.shifting_coalition` · `rel.group_under_pressure` · `rel.first_meeting` · `rel.breakup_architecture` · `rel.reconciliation_on_new_terms` · `rel.reunion_after_separation` · `rel.bond_across_a_time_jump` · `rel.expulsion` · `rel.leader_removed` · `rel.reunion_ensemble` |
| **The state — what is true on an ordinary day, and it has to survive a dozen scenes** (thirty-four) | Every other card named in the two tables above. It is named by complement on purpose: naming thirty-four ids here would make the map longer than the shelf, which is the one thing the template forbids. |

*A card appears once per axis. The answer is the intersection of the three shortlists, and it is normally three to six cards wide.*

---

**The default, and the one against it**

**The default is `rel.asymmetric_investment` holding the state, with `rel.relationship_arc` as the curve it moves along — and it is measured, not asserted.** `rel.asymmetric_investment` is the most-yielded-to card on the shelf and, unusually, it survives the test that disqualifies most most-yielded-to cards: **three cards send a reader to it and all three send them for a different reason.** `rel.mentor_and_student` sends on duration (*"The bond never ends or reverses"*), `rel.parasocial_bond` on reciprocity (*"The figure has to reciprocate"*), `rel.misnamed_relationship` on knowledge (*"Both people know the imbalance"*). Three unrelated conditions is the shape of a fallback; the same condition three times would have been an escape hatch. `rel.relationship_arc` is the only other card reached twice from working cards, and both of its conditions say the same thing — the change is spread out rather than staged — which is exactly what a default curve is. **And the contrast is on the same shelf:** `rel.reconciliation_on_new_terms` also takes two inbound edges, but both start at named failures and both fire on one condition, a rupture that did not change the terms. That is the shelf's repair bay, not its fallback, and a builder counting edges rather than conditions would have crowned it.

**The one against it is `rel.institutional_bond`.** Nothing on the shelf routes to it; its single pair field leaves the shelf altogether, for `anta.institutional`; and it is the only card here that breaks the shelf's founding assumption — that both parties can move. Every other tilted card still has two people who could, in principle, decide differently: the mentor could let go, the richer one could see the cost, the figure could reply. An institution cannot. It promises, demands, rewards and leaves, and it was never capable of the thing it asked for. That is the same asymmetry the default is built on, taken to the place where it stops being negotiable — which is why it is the more interesting answer and why nothing points at it. Its stated cost is the discipline almost every draft skips: the institution has to have given something real, early, or what you have written is a grievance rather than a tragedy. Its near cousin against the grain is `rel.non_human_member`, likewise never yielded to, likewise exiting the shelf entirely, and likewise built on a party that cannot lie, cannot leave and cannot be argued with.

---

**The unasked**

**Thirty of the fifty-four reachable cards are the target of no `Yields to:` field anywhere on this shelf.** They can be chosen but nothing ever sends you to them. By id:

`rel.relationship_as_protagonist` · `rel.the_debt` · `rel.marriage_on_the_page` · `rel.parent_and_adult_child` · `rel.sibling_order` · `rel.mentor_and_student` · `rel.rivalry_as_friendship` · `rel.group_secret` · `rel.more_than_five` · `rel.rotating_spotlight` · `rel.pair_matrix` · `rel.correspondence_bond` · `rel.across_a_language` · `rel.class_divided_pair` · `rel.location_bound_bond` · `rel.caretaker_and_cared_for` · `rel.co_parents` · `rel.institutional_bond` · `rel.parasocial_bond` · `rel.non_human_member` · `rel.first_meeting` · `rel.breakup_architecture` · `rel.misnamed_relationship` · `rel.public_face` · `rel.mimetic_jealousy` · `rel.expulsion` · `rel.succession_fight` · `rel.leader_removed` · `rel.ensemble_pilot` · `rel.reunion_ensemble`

**And the shape of that list is the finding, not its length. It is a picture of the order the shelf was written in, not of what its cards are.** Nineteen of the thirty sit in the second half of the family, which is nineteen of that half's twenty-five usable cards — and the direction of travel is entirely one-way. Nine pointer edges run from the second half back into the first; exactly one runs forward, `rel.triangle` to `rel.third_wheel`. A reader holding an early card is almost never sent to a later one, because when the early cards were written the later ones did not exist and nobody went back. **The pair graph is a record of the build, and on this shelf it has been mistaken for a map.**

The second thing the list shows is sharper. **The shelf itself names the four events every relationship line has to stage — the meeting, the rupture, the repair, the expulsion — and routes a reader to none of them.** `rel.first_meeting`, `rel.breakup_architecture` and `rel.expulsion` are all unasked, and `rel.reconciliation_on_new_terms` is reached only by two repair edges from named failures. A reader comparing two bonds is comparing two steady conditions, and an event is not an alternative to a state; the pair field cannot express it. That is why axis three is on this card, and why it is asked last rather than not at all.

The third: **the whole region where the second party cannot consent is unasked** — `rel.institutional_bond`, `rel.parasocial_bond`, `rel.non_human_member`, and alongside them `rel.co_parents`, `rel.caretaker_and_cared_for` and `rel.mimetic_jealousy`, where a third party is inside the bond without having agreed to be. The shelf treats a relationship as a thing between two people in a room who both turned up. Nothing on it routes a reader to a bond one party does not know they are in, and the nearest card that exists, `rel.parasocial_bond`, records exactly that in its own `Avoid when:` — the instant the bond becomes mutual, everything the frame bought is spent — with nothing sending anybody there to read it. **The card this shelf wants is the bond nobody consented to and nobody can end**, and the shelf currently has to reach it by browsing.

`rel.count_then_tilt`

---

### The Relationship as Protagonist

**Also called:** relational protagonism, the bond as subject, the two-hander unit
**What it is:** You treat the bond itself — not either person — as the thing that wants, suffers, changes and can die. Every scene is scored by what it does to the bond, not by what it does to him or to her.
**Effect on the audience:** They stop picking a side. Suspense stops being "will he win" and becomes "will they survive each other," which is a harder question to answer early, so they stay.
**Used for and where it works best:** Two-handers, buddy stories, marriages, partnerships — any story where both people are equally load-bearing. The craft rule: write the logline with the relationship as the grammatical subject, "a friendship that cannot survive being told the truth." If you cannot, you do not have this structure, you have a protagonist with a sidekick. Then give the bond its own beat sheet running underneath both individual arcs, and check every scene ending against it.
**Best in:** formats: feature, stage play, limited series, novella, short story | genres: drama, romance, buddy comedy, crime, literary
**Avoid when:** the climax is one person's private decision and the other is only there to witness it. Then the bond is a subject, not the subject, and forcing it produces a false ending where two people embrace over something only one of them earned.
**Example:**
> BEFORE (button scored to him): "He put the letter in his pocket and walked out alone."
> AFTER (button scored to the bond): "He put the letter in his pocket. She saw him do it. Neither of them said anything, and that was the first thing they had ever agreed to hide together."

**Yields to:** `char.protagonist_test` — Climax is one person's private decision.  
`rel.relationship_as_protagonist`

### What the Relationship Wants

**Also called:** the shared objective, the bond's want, relational want
**What it is:** The pair has a want neither holds alone — a thing they are trying to be to each other, or a state they are trying to get back to. It is separate from what each of them wants personally.
**Effect on the audience:** Gives them something to root for that is not a person, which is why partnership stories can stay tense with no villain anywhere near them.
**Used for and where it works best:** Anywhere the individual wants are compatible and the story would otherwise go slack. The craft rule: phrase it as a verb the pair performs on each other — "to be forgiven by him," "to make her need us again," "to get back to the summer before" — never as a noun like "closeness." Test it by picturing the last scene if they get it and the last scene if they do not; if the two pictures are the same, there is no want. See `char.relationship_self` for the version of a person that exists only inside a given bond — the relationship want is what that version is chasing.
**Best in:** formats: novel, series, feature, stage play | genres: drama, romance, family saga, workplace
**Avoid when:** the pair is supporting texture rather than a line. A minor duo with a fully articulated shared want starts competing with the main line for the reader's hope, and the reader will follow the smaller, warmer thing every time.
**Example:**
> "We're not going to talk about Dad tonight."
> "No."
> "Say it properly."
> "We're not going to talk about Dad tonight."
> (The want: one evening as ordinary siblings. Every interruption is now an obstacle.)

**Yields to:** `char.supporting_character_want` — A minor duo, not a main line.  
`rel.relationship_want`

### The Relationship Arc

**Also called:** relational arc, bond arc, the third arc
**What it is:** A change curve belonging to the pair — distance to closeness, closeness to rupture, dependence to equality — that runs independently of either character arc and can resolve in the opposite direction to both.
**Effect on the audience:** Endings that feel true instead of tidy. Two people can both grow and still lose each other, and the audience accepts it because they watched the third line move.
**Used for and where it works best:** Series and long novels above all, where individual arcs are slow and the relationship is what moves week to week. The craft rule: fix four stated positions — what they are at the start, the first irreversible change, the worst position, the final position — and never let two consecutive relationship scenes sit at the same position. If they do, cut one. This is the pair-scale cousin of `scene.value_turn`; the value being turned is the bond.
**Best in:** formats: series, serialised novel, feature | genres: drama, romance, crime, fantasy, family saga
**Avoid when:** the pair appears in three scenes. Three scenes buy you one change, not a curve, and staging the full arc inside them reads as whiplash.
**Example:**
> Ep 1: "Call me if you need anything." / Ep 4: "You didn't call." / Ep 7: "I didn't call because I knew you'd come anyway." / Ep 10: "I called. You didn't come."

**Yields to:** `scene.value_turn` — Pair has only three scenes, one change.  
`rel.relationship_arc`

### The Founding Event

**Also called:** the origin beat, how they met, the first thing that happened
**What it is:** The single past event that set the terms of the relationship — the favour, the injury, the rescue, the betrayal — which both people still reference and neither describes the same way.
**Effect on the audience:** Retroactive depth. One reference makes a two-scene relationship feel decades old, and the gap between their two versions is free conflict.
**Used for and where it works best:** Any relationship the story joins in progress. The craft rule: never dramatise it first. Let it be referenced twice, in disagreement, before it is shown or told — and when it finally lands, let the true version be a third version neither of them said. Keep the event small and physical (a door, a phone call, a coat) so it can be invoked in four words.
**Best in:** formats: novel, feature, series, short story | genres: crime, drama, literary, thriller, romance
**Avoid when:** you are using it to excuse a relationship you never dramatised in the present. A founding event cannot be the only evidence that two people matter to each other; it is interest on a principal you still have to deposit.
**Example:**
> "You've owed me since Rotterdam."
> "In Rotterdam I carried you."
> "You carried me because I told you where to go."

**Yields to:** `rel.unspoken_agreement` — Bond needs present evidence, not past interest.  
`rel.founding_event`

### The Unspoken Agreement

**Also called:** the treaty, the contract, the rules of the house
**What it is:** The set of rules two people run on that neither has ever said aloud — what is never mentioned, who apologises, who is permitted to be the one in trouble. The story's job is to break it.
**Effect on the audience:** They learn to read the pair like locals, then feel the violation before the characters name it. It is the cheapest way to make an audience feel expert about a relationship.
**Used for and where it works best:** Marriages, siblings, long partnerships, any bond older than the story. The craft rule: show the treaty honoured twice in dull circumstances, then break it once under pressure — and have the person who broke it not notice. The other one notices. That asymmetry is the scene. Sits well alongside `dial.talking_past`, since a treaty is usually maintained by not answering the question that was actually asked.
**Best in:** formats: stage play, novel, feature, series | genres: drama, literary, romance, family saga, comedy of manners
**Avoid when:** the audience has not had time to learn the rule. Breaking a treaty the reader never saw honoured is just a character being rude in a room.
**Example:**
> Honoured: "How was your mother?" / "Fine. Pass the salt."
> Broken, in front of guests: "How was your mother?" / "She asked about the money again. She always asks about the money." — and the pause afterwards runs four seconds long.

**Yields to:** `rel.founding_event` — No room to show the rule honoured first.  
`rel.unspoken_agreement`

### The Debt Between Them

**Also called:** the ledger, the obligation, who owes whom
**What it is:** An unsettled account — a life saved, money lent, a lie told on someone's behalf — that gives one person standing to demand and the other an obligation to comply, and that can be called in exactly once.
**Effect on the audience:** Tension with a countdown. Every scene after the debt is established carries the question of when it gets called.
**Used for and where it works best:** Crime, war, family — any story that needs a pair to stay together past the point where they would reasonably part. The craft rule: the debt must be callable for something the debtor would otherwise refuse, or it is decoration. Second rule: pay it in the scene where it is called. Deferred payment kills the device. This is a specific engine for `char.status_transaction` — the debt is standing you can spend, and spending it empties it.
**Best in:** formats: feature, novel, series, stage play | genres: crime, thriller, war, drama, western
**Avoid when:** the debtor has no scene in which refusing would be the right choice. Then calling the debt costs nothing and the audience feels nothing.
**Example:**
> "I'm asking."
> "Ask for something else."
> "I only get to ask once. You told me that. In the car, with your hand on my neck, bleeding. I'm asking."

**Yields to:** `rel.locked_pair` — Refusing the debt would cost nothing.  
`rel.the_debt`

### Asymmetric Investment

**Also called:** the unequal pair, the one-sided bond, the lopsided friendship
**What it is:** One person needs the relationship more than the other and both know it. The gap is the drama, and the story either closes it, widens it, or flips it.
**Effect on the audience:** A very specific discomfort — the reader sees the imbalance that the lesser-invested party is pretending not to see, which makes ordinary scenes painful to read.
**Used for and where it works best:** Mentorships, unrequited friendship, adult children and parents, the junior partner, fandom. The craft rule: measure investment in behaviour, not feeling — who initiates contact, who rearranges their week, who apologises first, who keeps the other's schedule in their head. Move one of those four in the back half and the relationship has changed without a single declarative line. Pair with `char.status_flip` when you want the gap to reverse rather than close.
**Best in:** formats: novel, feature, series, short story, stage play | genres: literary, drama, comedy, romance, coming of age
**Avoid when:** you intend the pair as comfort. Asymmetry cannot sit in the background as warmth; it always foregrounds itself and will contaminate the scenes you wanted to be easy.
**Example:**
> "I texted you Thursday."
> "Did you? Sorry, it's been mad."
> "It's fine. I only texted to say I'd got the job."
> "Mate! That's — that's great. Tell me Friday, I'll be at Nina's till late."

`rel.asymmetric_investment`

## Pair Shapes

### The Change of Register

**Also called:** relationship reclassification, the role switch, friends to rivals
**What it is:** The pair keeps the same two people and changes category — friends become rivals, lovers become colleagues, parent becomes dependent, teacher becomes peer. The intimacy stays; the rules do not.
**Effect on the audience:** Every established habit becomes newly loaded, so the writer gets a second relationship free out of material already paid for.
**Used for and where it works best:** Second acts, second seasons, any story with a time jump. The craft rule: do not let them renegotiate verbally. Force them through one mundane transaction under the new register — ordering food, signing a form, splitting a bill — and let the old habits misfire inside it. The misfires are the scene, and a `scene.public_scene` frame sharpens them, because neither can correct the other in front of witnesses.
**Best in:** formats: series, novel, feature, stage play | genres: drama, workplace, sports, romance, family saga
**Avoid when:** you have not shown enough of the first register. This is a payoff instrument; with no baseline it is two people in an unexplained mood.
**Example:**
> "Dad, put the card down. I've got it."
> "Don't be stupid."
> "I've got it."
> (He puts the card down. It is the first time.)

`rel.register_change`

### The Pair Who Cannot Leave

**Also called:** the locked pair, forced proximity, the bound dyad
**What it is:** Two people with every reason to separate and a structural reason they cannot — blood, money, contract, geography, a shared crime, a child. The pressure has nowhere to vent.
**Effect on the audience:** Claustrophobia plus inevitability. They read on because escape is impossible, so something has to give.
**Used for and where it works best:** The engine under most durable stage two-handers and most enduring crime duos. The craft rule: re-verify the lock in the middle of the story, not just at the start — put one credible exit door in Act Two and close it on the page. Without that, the audience quietly assumes they could leave any time and the pressure drains out. `scene.trap_scene` does this at scene scale; this is the story-scale version.
**Best in:** formats: stage play, feature, limited series, novel | genres: crime, drama, horror, black comedy, literary
**Avoid when:** the story is about choosing each other. If they cannot leave, staying is not a choice and cannot carry a romantic ending.
**Example:**
> "Then go."
> "With what? The car's in your name, the flat's in your name, and your brother's in the ground wearing my jacket."

**Yields to:** `rel.chosen_family` — The story is about choosing each other.  
`rel.locked_pair`

### The Triangle

**Also called:** the trio, three-body problem, love triangle
**What it is:** Three people where each of the three edges carries its own friction and any two can form against the third. Not one person choosing between two options — three live relationships.
**Effect on the audience:** Constant re-evaluation. A room of three is unstable in a way a room of two is not, so attention never settles.
**Used for and where it works best:** Anywhere a two-hander has gone comfortable. The whole trick: write all three edges, including the one that does not involve the protagonist — the two rivals must have a relationship with each other that would still be interesting if the third person died tomorrow. Second rule: the question is not "who will be chosen" but "who is she when she is with each of them." Write both versions of her, and let the audience choose which version they want to survive.
**Best in:** formats: novel, feature, series, stage play | genres: romance, drama, crime, YA, literary
**Avoid when:** one option is obviously correct. A triangle with a designated loser is a delay tactic, and readers resent delays more than they resent bad endings.
**Example:**
> (the edge writers forget — the two rivals, alone)
> "She does the thing with her sleeve when she's lying. You know the one."
> "I taught her that."
> "No you didn't. You think you did, and she's never corrected you. That's worse."

**Yields to:** `rel.third_wheel` — The third edge is not live.  
`rel.triangle`

### The Long Marriage on the Page

**Also called:** the veteran partnership, married shorthand, twenty-year dialogue
**What it is:** Writing a bond old enough that its communication has compressed — sentences unfinished, references reduced to single words, the real exchange happening in what gets skipped.
**Effect on the audience:** Instant credibility of duration, otherwise the hardest thing to fake. Then, when the compression fails, devastation, because they already know what fluency sounded like.
**Used for and where it works best:** Any couple or partnership older than about fifteen years. The craft rule: compression is the baseline and the drama is decompression. A long marriage in trouble starts using full sentences, first names and complete explanations — "As I was saying to you earlier, Margaret" — and that formality reads as a scream. Write three compressed exchanges before you write one decompressed one.
**Best in:** formats: stage play, novel, feature, short story | genres: drama, literary, comedy, crime
**Avoid when:** the reader needs the content of what is being discussed. Compressed dialogue is opaque by design; never route plot information through it.
**Example:**
> "Is it the—"
> "It's the Tuesday thing."
> "God."
> "I know."
> (Later, in trouble): "I am going to the appointment on Tuesday, which I have now mentioned to you twice, and I would like you to come with me."

**Yields to:** `expo.absorb_into_argument` — The scene must carry plot content.  
`rel.marriage_on_the_page`

### Parent and Adult Child

**Also called:** the grown child scene, role reversal, the returning son
**What it is:** A parent-child bond in which both parties still have access to the old script — the child's adolescent register, the parent's authority voice — and keep falling into it against their own intentions.
**Effect on the audience:** Universal recognition, and a particular vicarious shame when a competent adult is reduced to a sulk by a sentence about a coat.
**Used for and where it works best:** Homecomings, funerals, holidays, illness. The craft rule: stage the regression physically — the childhood room, the low end of the table, a chair they have outgrown — and let one parental instruction ("Don't slam it") trigger a response the character is visibly embarrassed by. The transfer of care from parent to child is the real turn, and it should be written as a chore changing hands, never as a speech.
**Best in:** formats: feature, novel, stage play, short story, series | genres: drama, literary, comedy, family saga
**Avoid when:** you need the adult to be authoritative in the following stretch of story. This dynamic strips competence, and buying it back costs scenes.
**Example:**
> "You're not wearing that."
> "I'm forty-one."
> "You're forty-one and you're not wearing that."
> (He changes. He is furious with himself in the mirror, and he changes.)

**Yields to:** `rel.register_change` — The adult must keep competence afterwards.  
`rel.parent_and_adult_child`

### Siblings and Position

**Also called:** birth order, the sibling grid, brothers and sisters
**What it is:** Sibling relationships organised by fixed positions — the responsible one, the favourite, the escapee, the one who stayed — assigned in childhood, and which the family will not let anyone resign from.
**Effect on the audience:** Fast legibility for a large group. Readers can hold four siblings in one scene if each holds a distinct position, where four friends would blur.
**Used for and where it works best:** Family sagas, inheritance plots, funerals, any ensemble needing history without exposition. The craft rule: give each sibling a duty rather than a trait — who calls the parents, who handles money, who gets phoned when something is wrong, who is protected from bad news — then start the story by having one of them refuse their duty. The sharpest sibling material is antagonism, and `sit.polti_14_rivalry_of_kin` and `sit.polti_13_enmity_of_kin` are the classical situations that name it.
**Best in:** formats: novel, series, stage play, feature | genres: family saga, drama, literary, comedy, crime
**Avoid when:** you have only two siblings and no parent in play. Position is defined by comparison; with two people and no audience for the comparison it collapses into an ordinary rivalry.
**Example:**
> "Who told Mum?"
> "Nobody told Mum."
> "Somebody always tells Mum. It's you. It's always been you."
> "Because you two never do it, and then she finds out from the bloody hospital."

**Yields to:** `sit.polti_14_rivalry_of_kin` — Only two siblings, no parent watching.  
`rel.sibling_order`

### Mentor and Student

**Also called:** master and apprentice, teacher and pupil, the succession pair
**What it is:** A deliberately unequal pair in which one transmits skill or standing to the other, and which is structurally obliged to end — by graduation, betrayal, surpassing, or death.
**Effect on the audience:** Built-in forward motion. Every lesson advances a clock toward the moment the student no longer needs the teacher.
**Used for and where it works best:** Craft stories, crime apprenticeships, sport, war, magic. The craft rule: the mentor must want something from the student — a legacy, an alibi, a witness, absolution — or this is a delivery mechanism for information rather than a relationship. Plant one wrong lesson early that the student takes as gospel; the turn is the student discovering which lesson was wrong. `char.supporting_character_want` applies with full force, because a mentor with no want of their own is furniture that talks.
**Best in:** formats: feature, series, novel, short story | genres: crime, sport, fantasy, drama, thriller, war
**Avoid when:** the student never surpasses or rejects the mentor. A mentorship that simply continues has no shape, and an ending is the only shape this bond has.
**Example:**
> "You always stand on the left of a door. Why?"
> "Because you told me to."
> "That's not an answer, that's obedience. I stand on the left because I'm deaf in the right ear. You've spent six years copying a disability."

**Yields to:** `rel.asymmetric_investment` — The bond never ends or reverses.  
`rel.mentor_and_student`

### The Professional Pair

**Also called:** partners, the working duo, the double act at work
**What it is:** Two people bound by a job, whose personal relationship is conducted entirely inside professional transactions — a case, a shift, a deal — and never in a conversation about themselves.
**Effect on the audience:** Intimacy the audience assembles for themselves, which they trust far more than any stated version of it.
**Used for and where it works best:** Procedurals, heists, medicine, war, anything episodic. The craft rule: never let them discuss the relationship. The bond is expressed entirely through division of labour — who drives, who talks to the family, who writes the report, who is trusted with the dangerous part — and you change the relationship by changing the division. One reassignment says more than a page of confession. `dial.talking_to_the_room` is the usual delivery mechanism: the personal thing gets said to a third party while the partner stands there.
**Best in:** formats: series, feature, novel | genres: crime, procedural, medical, war, thriller, workplace comedy
**Avoid when:** the story has no work in it. Strip the job and this pair has no language, which is precisely why the off-duty episode is so often the weakest one.
**Example:**
> "I'll take the mother."
> "You always take the mother."
> "You cried at the last one."
> "I'll take the mother."
> (He lets her drive instead. Neither mentions it.)

`rel.professional_pair`

### The Rivalry That Is a Friendship

**Also called:** the worthy opponent, hostile intimacy, the enemy who knows you best
**What it is:** Two antagonists who compete seriously and who are also, demonstrably, the only person who fully understands the other. The attention they pay each other is indistinguishable from affection.
**Effect on the audience:** Delicious discomfort, and a strange grief when one of them finally wins.
**Used for and where it works best:** Sport, law, crime, politics, academia. The craft rule: the rivals must want the same thing and be denied it by each other — `arc.shared_want_opponent` is the skeleton — and you convert rivalry into friendship by giving them one exclusive pleasure nobody else can supply, usually the pleasure of being taken seriously. Write one scene of open professional delight in the middle, where they enjoy each other's work, and the ending will hurt. Related but distinct: `arc.mirror_character`, where the opponent shows the protagonist what they could become.
**Best in:** formats: feature, series, novel, stage play | genres: sport, crime, legal, political, literary, comedy
**Avoid when:** the story needs a hateable antagonist. Once the audience enjoys the rival, they will not accept a clean defeat, and your triumphant ending lands as a loss.
**Example:**
> "That was a good question. The one about the ferry."
> "It was a great question."
> "It was a good question asked badly. If I'd had it, they'd have folded by lunch."
> "I know. That's why I enjoyed it."

**Yields to:** `anta.sympathetic_limit` — Story needs a defeat that lands clean.  
`rel.rivalry_as_friendship`

## The Group as a System

### Chosen Family

**Also called:** found family, family of choice, the crew
**What it is:** A group of unrelated people who take on family functions — obligation, defence, ritual, the right to criticise — by accumulated choice rather than by blood.
**Effect on the audience:** Enormous warmth with a specific ache under it, because they are watching people decide to be responsible for each other with nothing external requiring it.
**Used for and where it works best:** Crews, squads, bands, workplaces, misfit ensembles. The craft rule: prove the bond with the unglamorous and repeated, not with the rescue. Give the group one ritual (the Thursday meal, the same seat, who pays), one shared shorthand, and one member who is allowed to be difficult — then dramatise a moment where staying is genuinely costly and someone stays anyway. Choosing at no cost proves nothing.
**Best in:** formats: series, novel, feature, serialised fiction | genres: fantasy, sci-fi, crime, YA, comedy, drama
**Avoid when:** the group never disagrees. Unanimous affection is not a family, it is a mood — see `rel.everyone_agrees`.
**Example:**
> "You don't get a vote. You're not actually related to any of us."
> "I've done the Christmas washing-up eleven years running."
> "...Fine. He gets a vote."

`rel.chosen_family`

### The Ensemble as a System

**Also called:** the group as organism, network characterisation, the web
**What it is:** Designing a group so each member exists mainly as a set of relationships to the others, so that moving any one of them deforms the whole shape. The group, not the individual, is the unit of change.
**Effect on the audience:** A sense of a real world, plus a dread they cannot source — touch one person and they feel the whole net move.
**Used for and where it works best:** Ensemble series, large novels, workplace and institutional stories. The craft rule: build `char.ensemble_grid`, every pair a cell, and refuse to leave a cell empty. Then, before each act, name one cell that will change and one that will be exposed. A character's job is defined by which cells they occupy, not by a trait list. `theme.through_the_ensemble` is how you make the group argue about the idea rather than agree about it.
**Best in:** formats: series, novel, ensemble feature, stage play | genres: drama, workplace, crime, sci-fi, literary, satire
**Avoid when:** you are writing a tight single-POV subjective story. A system has to be seen from above, and a locked point of view cannot see the cells it is not in.
**Example:**
> (design note, made writable) She fires the receptionist. Now the accountant has nobody who laughs at him, the two juniors have lost their buffer, and the boss has lost the only person who told her the truth. One departure, four scenes.

**Yields to:** `rel.outsider_in_the_group` — Locked single subjective POV.  
`rel.ensemble_as_system`

### The Group with a Shared Secret

**Also called:** the conspiracy of friends, the thing we did, collective guilt
**What it is:** Every member of a group knows something the world does not, and their relationships reorganise around maintaining it — including who is trusted to hold it and who might break.
**Effect on the audience:** Every ordinary scene becomes double-layered, and any outsider entering the room creates tension with no plot movement at all.
**Used for and where it works best:** Reunions, small towns, crews after a job, families. The craft rule: rank the group by reliability and let the audience see the ranking — watch who gets looked at when a stranger asks a question. Then apply pressure to the second-weakest, not the weakest, because the weakest cracking is expected and expectation is the enemy here. The secret must cost each member something different, or they will speak with one voice.
**Best in:** formats: novel, limited series, feature, stage play | genres: crime, thriller, mystery, literary, horror
**Avoid when:** the secret is also withheld from the reader for a long stretch with no compensating pleasure. Concealment from the audience buys one reveal and costs a hundred pages of vagueness.
**Example:**
> "He was asking about the lake."
> "Who was?"
> "The new bloke. Just chat. Said the water level's down."
> Four people say nothing. Marie says, "It is down, though," and three of them look at her.

**Yields to:** `info.audience_only_secret` — Withholding from the reader costs too much.  
`rel.group_secret`

### The Group Under Pressure

**Also called:** the crucible, the siege, stress-testing the ensemble
**What it is:** Applying an external threat to a group in order to expose the real hierarchy and the real alliances, which prosperity conceals.
**Effect on the audience:** Fast, cheap characterisation — under threat people reveal in a page what would take chapters of calm.
**Used for and where it works best:** Disaster, heist gone wrong, siege, business collapse, illness. The craft rule: the pressure must force a distribution — of food, of blame, of a limited resource, of who goes first — because groups only show their structure when something has to be divided. Generalised danger produces generalised panic, which tells you nothing. Distribution produces coalitions.
**Best in:** formats: feature, limited series, novel, stage play | genres: thriller, horror, war, disaster, drama, satire
**Avoid when:** you have not established the peacetime version first. Pressure is a revealing light; with nothing established to reveal, it shows you strangers shouting.
**Example:**
> "There's four doses."
> "There's six of us."
> "Yes," says Idris, and says nothing else, and everybody understands that he has already decided which two.

**Yields to:** `rel.who_defends_whom` — No peacetime version established yet.  
`rel.group_under_pressure`

### Who Defends Whom

**Also called:** the loyalty map, defence patterns, the alliance tell
**What it is:** Establishing group structure by staging small attacks and watching who steps in — who is defended instantly, who is defended late, who is left to it, and who is defended by someone who does not even like them.
**Effect on the audience:** They map the group's politics without being told any of it, and the map feels earned because they assembled it themselves.
**Used for and where it works best:** Any group scene with more than three people, especially early, when the audience needs orienting fast. The craft rule: run the test on something trivial — a joke at someone's expense, a small factual correction — so the defence reads as loyalty rather than justice. Then, at the turn, have the usual defender stay silent. That silence is a more violent event than a betrayal scene.
**Best in:** formats: series, novel, feature, stage play | genres: drama, workplace, crime, comedy, school, war
**Avoid when:** everyone defends everyone. Universal defence flattens the map and wastes the tool.
**Example:**
> "Sorry, is Ben doing the pitch? Ben?"
> Priya: "Ben wrote the thing." (instant)
> Marcus: "...He did write it." (three beats late, looking at Priya first)
> Ben says nothing, which everyone notices, including Ben.

**Yields to:** `rel.group_hierarchy_display` — Everyone defends everyone, map is flat.  
`rel.who_defends_whom`

### The Outsider in the Group

**Also called:** the newcomer, the stranger at the table, the audience proxy
**What it is:** One person who does not know the group's rules, whose presence forces the group either to explain itself or to expose itself.
**Effect on the audience:** A licence for necessary exposition, plus a mirror — the group looks different when seen by someone who is not charmed by it.
**Used for and where it works best:** Pilots, first chapters, any moment a long-running ensemble needs refreshing. The craft rule: the outsider must want in, or want something from the group; a neutral observer generates no pressure. And the group must be genuinely wrong about something the outsider sees clearly, or the newcomer is a camera with legs. `scene.third_party_arrival` is the scene-level move; this is the sustained version.
**Best in:** formats: series, novel, feature, stage play | genres: drama, workplace, school, crime, sci-fi, comedy
**Avoid when:** you are at the climax of the group's own story. A stranger arriving late steals focus from the people the audience came for.
**Example:**
> "Why does nobody sit in that chair?"
> "We do sit in it."
> "You've all sat somewhere else."
> "It's not a thing."
> "It's clearly a thing."

**Yields to:** `rel.group_under_pressure` — Too late for a stranger to arrive.  
`rel.outsider_in_the_group`

### Displaying the Hierarchy

**Also called:** status staging, the pecking order, the seating plan
**What it is:** Making a group's rank visible through arrangement and small permissions — who sits where, who interrupts whom and survives it, who is served first, whose phone may be answered, who is allowed to end a conversation.
**Effect on the audience:** They know who runs the room within half a page, without anyone's title being spoken.
**Used for and where it works best:** Institutions, families, criminal outfits, armies, offices. The craft rule comes straight out of status work: high status blocks and permits, low status accepts and offers. So assign each character a blocking rate rather than a rank, and stage status as a seesaw — when one person's goes up, someone's goes down inside the same exchange, because status is transacted, not owned. Flip one person's rate in the third act and the room re-sorts itself with no explanation required.
**Best in:** formats: stage play, series, feature, novel | genres: political, crime, workplace, war, period drama, satire
**Avoid when:** the group's whole point is that it is flat. Staging a hierarchy in a genuinely equal group installs a leader the story did not want.
**Example:**
> "Sorry, can I just—"
> "In a minute."
> Two minutes later: "Sorry, can I just—"
> "Go on, then."
> (She now owes him the interruption. He will spend it badly.)

**Yields to:** `rel.shifting_coalition` — The group is genuinely flat.  
`rel.group_hierarchy_display`

### The Shifting Coalition

**Also called:** re-alignment, two-against-one, alliance drift
**What it is:** In a group of three or more, tracking which subset is currently allied and moving that subset across the story, so the same people keep re-pairing against each other.
**Effect on the audience:** Instability without new characters. They cannot settle, because the sides keep re-forming out of the same material.
**Used for and where it works best:** Trios, families, boardrooms, political stories, anything confined. The craft rule: a coalition needs a shared object — a plan, a secret, a resentment — and it must be visible to the excluded party, because an alliance the excluded person never notices does nothing. Rotate so each member is the excluded one at least once, and make the final exclusion the one that breaks the group. `char.load_bearing_contradiction` is what makes a member switchable: they want two things that live on opposite sides of the room.
**Best in:** formats: stage play, series, novel, feature | genres: political, drama, crime, family saga, satire, sci-fi
**Avoid when:** the coalitions rotate on nothing but mood. Unmotivated switching reads as inconsistency rather than instability, and the audience stops predicting — which means they stop engaging.
**Example:**
> Act I: "Tell her, or I will." (A and B, against C)
> Act II: "You do realise she's been telling him everything?" (A and C, about B)
> Act III: B and C in the kitchen, not speaking, both watching A through the door.

`rel.shifting_coalition`

## Writing the Ensemble Scene

### Keeping the Group Scene Legible

**Also called:** ensemble scene management, the crowded table, traffic control
**What it is:** The mechanics that let a reader follow six people in one room — voice separation, position anchoring and a controlled speaking order — so attention never has to stop and ask who said that.
**Effect on the audience:** Effortless comprehension, which reads as authorial confidence and lets the scene's content land instead of its logistics.
**Used for and where it works best:** Dinners, briefings, funerals, board meetings. The craft rules in order of return: give each speaker an identifiable pattern — line length, register, whether they ask or assert — so tags become optional; anchor three people to fixed physical positions and keep them there; never let more than three people speak consecutively before returning to a name the reader has already fixed. When a scene genuinely must be chaos, `dial.overlap` is the controlled way to do it, but chaos and legibility are a trade — buy chaos deliberately and briefly.
**Best in:** formats: feature, stage play, novel, series | genres: all
**Avoid when:** the confusion is the point — a panic, a raid, a riot. There, legibility of who is secondary to legibility of what, and you anchor to the event instead of the speakers.
**Example:**
> Six at the table, and only three need tagging.
> "No." — Dad; he always has the shortest line.
> "Well — no, hang on, because if we're saying the fourteenth, and I do think we said the fourteenth—" — Auntie Rose, who never finishes.
> "It was the fifteenth." — Ben, who only ever speaks to correct.

**Yields to:** `dial.overlap` — The confusion is the point.  
`rel.ensemble_scene_legibility`

### Writing More Than Five

**Also called:** the large ensemble, the big cast problem, the subgroup method
**What it is:** Handling casts above roughly six by refusing to treat them as one group — running two or three stable subgroups of two or three instead, and letting the full assembly happen rarely and for a reason.
**Effect on the audience:** They retain everyone, because they are only ever asked to hold three relationships at a time.
**Used for and where it works best:** Large novels, ensemble series, war stories, workplace comedy. The craft rules: assign every character a home subgroup and exactly one cross-tie into another subgroup — that cross-tie is your plotting mechanism; rotate focus deliberately instead of chasing equal screen time, since equal prominence flattens contrast and dulls conflict; and keep a screen-time grid, characters down the side, scenes or episodes across the top, so you can see who has vanished. Reserve the full-cast scene for structural turns — it is expensive, and stops being special if used weekly.
**Best in:** formats: series, novel, ensemble feature | genres: fantasy, sci-fi, war, crime, drama, workplace comedy
**Avoid when:** the piece is under about thirty pages. Below that you cannot establish six relationships, and the reader will hold none of them.
**Example:**
> (grid entry, made usable) Nadia — home: the kitchen crew. Cross-tie: the only one who speaks to Halloran upstairs. Every plot move between floors runs through her, so the week she is off shift, the story has a fault line.

**Yields to:** `char.combine_characters` — Piece is under about thirty pages.  
`rel.more_than_five`

### Pairing Off the Room

**Also called:** breaking the group, the two-shot inside the crowd, splitting the table
**What it is:** Playing a large scene as a sequence of two-person exchanges inside the crowd — stepping outside for a cigarette, a moment at the sink, one aside while the others argue.
**Effect on the audience:** Intimacy and scale at once. The group stays present as pressure while the actual drama happens between two people.
**Used for and where it works best:** Parties, weddings, wakes, office events. The craft rule: the crowd must constrain what can be said. If the two people could have had this conversation in private, the setting is wasted — the scene earns its crowd only when proximity forces euphemism, speed or silence. Give each aside a hard interrupt from the group, so it ends before it resolves.
**Best in:** formats: feature, series, novel, stage play | genres: drama, romance, crime, comedy, literary
**Avoid when:** the group itself has to make a decision. Fragmenting the room kills collective scenes; pick one or the other.
**Example:**
> By the sink, ninety seconds, both facing the window.
> "You could have told me."
> "When?"
> "Any time in four months."
> "Your mother's coming. She's coming now. Ask me later and I'll lie better."

**Yields to:** `rel.ensemble_scene_legibility` — The group must decide collectively.  
`rel.pair_off_the_room`

### Rotating the Spotlight

**Also called:** focus rotation, the featured pair, A/B/C assignment
**What it is:** Deliberately cycling which relationship carries the primary line across episodes, chapters or acts, so every pair gets a stretch at the front while the others idle in view.
**Effect on the audience:** The whole cast stays alive in memory, and the return to a neglected pair lands as a reward rather than a reminder.
**Used for and where it works best:** Series above all, and any novel with more than four viewpoint characters. The craft rule: rotate pairs, not people. Featuring a character alone produces a solo episode; featuring a pair advances a relationship arc, and relationship arcs are what serialised audiences actually follow. Enforce a minimum presence rule — no pair vanishes for more than two units — and plant one small forward beat for each idling pair per unit, so the rotation does not feel like a queue.
**Best in:** formats: series, serialised novel | genres: drama, crime, fantasy, workplace, sci-fi
**Avoid when:** you have a sprinting plot on a hard clock. Rotation implies leisure, and a twelve-hour thriller cannot pause on the secondary pair.
**Example:**
> Ep 3 front: Nadia and Halloran. One planted line for the neglected pair: "Tell Vic I'm not covering Sunday." Ep 4 opens on Vic covering Sunday.

**Yields to:** `rel.pair_off_the_room` — Hard clock, no room to pause.  
`rel.rotating_spotlight`

### The Pair Matrix

**Also called:** the relationship grid, the cell audit, the pairwise pass
**What it is:** A revision tool rather than a writing device — every character set against every other, one cell each, filled in with what that pair currently wants from each other and what they are hiding.
**Effect on the audience:** Indirect but decisive. It eliminates the flat ensemble, where six characters all relate to the lead and not to each other.
**Used for and where it works best:** The second draft, always, and before breaking a season. The craft rule: an empty cell is either a character to cut or a scene to write, and you must pick one. A cell containing only "they get on well" counts as empty. For a minor pair the cell is filled small — one directional want of the kind `char.supporting_character_want` gives, not a shared want of their own, which `rel.relationship_want` keeps for pairs that carry a line. Mark the direction of every cell too — what A wants from B is rarely what B wants from A, and the asymmetry is where your unwritten scenes are hiding. Distinct in use from `char.ensemble_grid`: that designs the group, this audits it afterwards.
**Best in:** formats: series, novel, ensemble feature, stage play | genres: all
**Avoid when:** you are drafting. Filling cells before you have heard the characters speak produces a spreadsheet with dialogue attached.
**Example:**
> Cell (Marcus → Priya): wants her to stop being right in public. Hiding: he recommended her for the job.
> Cell (Priya → Marcus): wants his access to the fourth floor. Hiding: she knows about the recommendation.
> That one cell was two scenes nobody had written.

**Yields to:** `char.ensemble_grid` — You are designing, not auditing a draft.  
`rel.pair_matrix`

## Named Failures

### The Relationship With No Want

**Also called:** the decorative bond, the flat pair
**This is a named failure, not a recommendation.**
**What it is:** Two characters established as close, appearing together repeatedly, who want nothing from each other — so their scenes carry affection but no pressure and can be cut without loss.
**Effect on the audience:** Boredom they misattribute to pacing. They start skimming any scene these two share, and eventually skim the characters themselves.
**Used for and where it works best:** Never deliberately. Diagnose it by asking what one of them is trying to get in this scene and what happens if they fail; if the answer is "nothing," you have it.
**Best in:** formats: — | genres: —
**Avoid when:** always. The real failure mode: the writer enjoys these two together and mistakes their own enjoyment for the reader's. The fix is either to give one of them a want the other resists, or to fold the scene into one that already has a want.
**Example:**
> "Morning."
> "Morning. You look tired."
> "Long night. You?"
> "Same. Coffee?"
> "Please."
> (Five lines of warmth, zero pressure. Cut it, or give one of them something to ask for.)

**Yields to:** `rel.relationship_want` — The repair for the flat pair.  
`rel.relationship_with_no_want`

### The Ensemble Where Everyone Agrees

**Also called:** the unanimous group, the harmony trap, the hive
**This is a named failure, not a recommendation.**
**What it is:** A group written as one organism with one opinion, where disagreements are cosmetic and resolved within a page, so the group has no internal politics and its members have no reason to be separate people.
**Effect on the audience:** The cast reads as one character with several faces, and they stop tracking names, because names have stopped carrying information.
**Used for and where it works best:** Never deliberately. Detect it by counting how many pages a disagreement survives; if none survives past the scene it starts in, you have it.
**Best in:** formats: — | genres: —
**Avoid when:** always, and most urgently in warm or comic ensembles, because that is where the rot sets in unnoticed. The real failure mode: the writer is protecting the group's likeability and treats disagreement as unpleasantness. The fix is not to add a contrarian — it is to give each member a different thing at stake in the same decision, so disagreement becomes structural rather than temperamental. Then let one disagreement stay unresolved across the whole story.
**Example:**
> "We go tonight."
> "Agreed."
> "Yep."
> "Whatever you think."
> (Fix: give the fourth one a reason he needs daylight, and let nobody talk him out of it.)

**Yields to:** `rel.shifting_coalition` — Structural disagreement instead of unanimity.  
`rel.everyone_agrees`

### The Friend Who Exists to Listen

**Also called:** the confidant problem, the sounding board, the best friend with no life
**This is a named failure, not a recommendation.**
**What it is:** A secondary character whose whole function is to receive the protagonist's thoughts — asking clarifying questions, offering encouragement, holding no schedule, no want and no scene of their own.
**Effect on the audience:** They feel the exposition. Confidant scenes are where readers most reliably sense the author moving furniture, because a person with no want is audibly a device.
**Used for and where it works best:** Never deliberately. Detect it by asking what this character is doing on the day the scene happens; if the answer is "being available," you have it.
**Best in:** formats: — | genres: —
**Avoid when:** always. The real failure mode is not thinness — it is that the writer needed the protagonist to say their thoughts aloud and built a person-shaped receptacle to hear them. Three fixes in descending order of quality: give the confidant a want that competes with listening, so the protagonist's crisis is inconvenient today; make them wrong about the advice and let the protagonist take it anyway; or delete them and dramatise the information instead of reporting it. See `char.supporting_character_want`.
**Example:**
> BEFORE: "So what are you going to do?" / "I don't know. That's the problem." / "You'll figure it out. You always do."
> AFTER: "So what are you going to do?" / "I don't know." / "Well, figure it out by six, because I've got Dad's hospital thing and you said you'd drive."

**Yields to:** `char.supporting_character_want` — Give the confidant a competing want.  
`rel.listener_friend`

## Coverage

33 cards. Covered here: the relationship as protagonist, the relationship want, the relationship arc, the founding event, the unspoken agreement, the debt, asymmetric investment, the change of register, the locked pair, the triangle, the long marriage, parent and adult child, siblings and position, mentor and student, the professional pair, rivalry-as-friendship, chosen family, the ensemble as a system, the group secret, the group under pressure, who defends whom, the outsider, hierarchy display, shifting coalitions, ensemble scene legibility, casts above five, pairing off the room, rotating the spotlight, the pair matrix, and three named failures.

*Build notes from when this file was drafted — targets, running totals and what remained to be written — are kept verbatim in the [coverage history](../tools/history/coverage-history.md). They were true of the draft, not of the file, so they no longer sit here as if they were measurements.*

## Sources

Researched 2026-09-17.

- [Structuring Relationship Arcs and Plots in a Series — September C. Fawkes](https://www.septembercfawkes.com/2023/01/structuring-relationship-arcs-plots-in.html)
- [Writing Relationship Arcs into Plots: Primary Principles — September C. Fawkes](https://www.septembercfawkes.com/2022/10/turning-relationship-arcs-into-plots.html)
- [How to Write Ensemble Casts in Film and TV — No Film School](https://nofilmschool.com/how-to-write-an-ensemble-cast)
- [Writing the Ensemble Cast: A Screenwriter's Guide to Balancing Multiple Characters — Creative Screenwriting](https://www.creativescreenwriting.com/cswcms/mastering-writing-the-ensemble-cast-a-screenwriters-guide-to-balancing-multiple-characters/)
- [Character Relationships and Dynamics — Fiveable, Screenwriting II](https://fiveable.me/screenwriting-ii/unit-2/character-relationships-dynamics/study-guide/KONMSYojOBDkNaVu)
- [How Writers Balance an Ensemble Cast Through Character Arc Compression and Interconnected Plotlines — Loaded Dice Films](https://www.loadeddicefilms.com/how-writers-balance-ensemble-cast/)
- [Status — The Improv Archive](https://improvarchive.org/learn-improv/concepts/status)
- [Playing With Status — The Center for Fiction](https://centerforfiction.org/writing-tools/playing-with-status/)
- [Impro: Improvisation and the Theatre, Keith Johnstone — book notes, Blas](https://blas.com/impro/)
- [The Found Family Trope — Sharon Wray, Craft of Writing](https://sharonwray.com/craft-of-writing/found-family-trope/)
- [How to Write a Found Family Arc That Feels Earned — NovelOS](https://novelos.studio/blog/found-family-arc/)
- [10 Tips for Writing Love Triangles (That Aren't Cliché) — Story Grid](https://storygrid.com/love-triangles/)
- [How to Write a Love Triangle That Doesn't Make Readers Cringe — A Thistle in the Wind](https://www.athistleinthewind.com/how-to-write-a-love-triangle/)
- [Best Three-Hander Plays — StageMilk](https://www.stagemilk.com/best-three-hander-plays/)
- [Two-Hander Screenplay Structure: When Two Characters Carry the Movie — ScreenWeaver](https://www.screenweaver.ai/blog/two-hander-screenplay-structure-guide)