Forms of address

A preferred name is not the whole relationship

One character may permit a childhood nickname from a friend in private while requiring a surname in a rehearsal room. A single nickname field cannot represent that boundary. Enter directed rules: speaker, listener, context, permitted form, and a chapter interval. Reversing the speaker and listener can produce a different answer. That asymmetry is often the point of the scene.

Make the transition observable

The chapter interval represents an authored relationship event. It is not a score that automatically measures intimacy. If a private form becomes welcome after a reconciliation, start its permission at the chapter where the change is earned. If the story later restores distance, end that interval. Do not let a character use an intimate form early simply because the author knows the eventual relationship.

Understand wildcard priority

An asterisk matches any speaker, listener or context. More specific rules take priority over general ones. Two equally specific rules producing different forms are a conflict, not a chance to pick whichever sounds best. Resolve the contradiction by narrowing the context, changing the dates or explicitly choosing the intended rule. A wildcard is convenient, but an overbroad wildcard can accidentally authorize private address for everyone.

Fictional example: the rehearsal room

A stage manager calls a friend by a private nickname during a public rehearsal. The friend asks for the professional surname in that room. Backstage, the nickname is welcome again. The scene does not require a new legal identity or a stronger nickname. It requires recognizing the audience and the speaker’s obligation to respect a boundary.

What a different address would do

If the private name were welcome everywhere, the correction would seem arbitrary. If only the stage manager could use it, the same word could establish a special relationship in a different scene. Record the actual rule rather than assigning one universal emotional meaning to a form. A deliberate violation may be important characterization. The tool’s conflict warning identifies the mismatch; the author decides whether to repair the dialogue or portray the violation and its consequence.

Move from the graph back to dialogue

Read the exchange aloud after resolving the form. Repeated vocatives may make a scene stiff even when every permission is technically correct. Sometimes the right revision is to omit a name and let action or a response identify the listener. Language-specific honorifics and kin terms need contextual evidence and review. This worksheet applies your declared policy; it does not establish that a chosen term is culturally natural.

Represent the event that permits the change

An interval alone can state when a form is valid, but a relationship event explains why that interval is earned. Add an event ID, chapter and active state to the milestone table. A permission can reference that event in its seventh column. Until the event occurs, the dependent form is inactive. Cancelling the event invalidates that permission without requiring you to erase the rule from your private plan.

For example, enter reunion | 3 | active. Add a | b | private | Sela | 0 | 99 | reunion to the permissions. At chapter two, the event does not yet authorize the form. At chapter four, it does. Change the event state to cancelled and the same private form becomes unavailable again. A wildcard public rule may still supply another form; that is a separate permission, not a fallback to presumed intimacy.

Deleting a referenced event produces a visible issue. The tool does not invent an equivalent emotional milestone to keep the scene working. This is especially useful in revision, when a reconciliation scene moves or disappears but later dialogue retains a private nickname. Replaying the timeline can locate the resulting gap before an editor has to discover it by memory.

Audit what the characters actually say

The dialogue table records chapter, speaker, listener, context and the actual form used. An optional reason marks an intentional violation. This does not turn a violation into permission. It distinguishes a continuity mistake from a deliberate act the story needs to portray. The expected form and the supplied form remain visible for review.

Use the same directed IDs throughout. If the speaker is allowed to call a colleague Sela, the colleague does not automatically gain access to that speaker’s childhood name. Nor does an actor’s knowledge become a character’s knowledge. Before interpreting the audit, identify whose voice the line represents: direct dialogue, quoted dialogue, a rehearsal annotation or narration. The worksheet models the direct exchange you enter; it does not infer these layers from a manuscript.

If two equally specific active permissions disagree, solve the rule conflict first. A public scene and a private scene may legitimately differ. Two contradictory rules for the same pair, context and time need narrower conditions or an explicit choice. Do not let arbitrary row order decide what the character is supposedly allowed to say.

Original fictional scene: the room and the corridor

The stage manager counted heads, then called a private nickname across the rehearsal room. Sela looked up before she could stop herself. Three people smiled. One repeated the name while writing it beside her role.

“Morrow in here,” she said.

The manager thought she was asking him to speak louder. He repeated the nickname, carefully this time.

“No. In this room, use Morrow.”

The pianist took his hands off the keys. It was an awkward place to pause: everyone was ready, the scene had a difficult entrance, and the manager was the only person who knew that nickname from before the company existed.

He crossed it out on the roster. “Morrow. From the doorway, then.”

They rehearsed the entrance. She missed the first cue. On the second attempt, he called Morrow clearly enough for the whole room, and she came through on time.

Afterward, in the corridor, he asked whether she wanted him never to use the old form again.

“Not never,” she said. “Not as an announcement.”

He looked through the open door at the roster. Someone had copied the correction. The nickname was still visible under a single line of ink.

“I should replace that page.”

“Yes.”

When they were alone at the prop cupboard, he used the private form as a question rather than a call. She answered. That did not cancel the correction he still needed to make in the room.

The scene is fictional. It demonstrates an audience boundary and a practical consequence: the roster must be corrected, not merely the speaker’s feelings soothed. It does not prescribe how every person should respond to a private or former name.

Why a universal nickname field fails here

Both uses come from the same speaker and address the same listener. The difference is context. A single preferred-nickname value would either authorize the public call incorrectly or forbid the welcome private exchange. The directed context rule preserves both facts without turning the name into a universal sign of intimacy.

The roster also changes the scale of the mistake. A private word has become a production reference that other people may repeat. If the manager only apologizes in the corridor, the public record still distributes the form. The repair therefore includes a concrete action. In your own scene, look for the artifact, group assumption or repeated practice that carries a name beyond the original exchange.

If Sela instead wanted the old form abandoned entirely, the private ending would contradict her stated boundary. End the permission rather than use a tender final line to override the character’s choice. If she welcomed the public nickname but disliked the manager’s tone, a context ban would misdescribe the problem. The tool cannot choose the emotional interpretation; it can expose the inconsistency between that interpretation and the permissions you record.

Use omission as an editorial option

Correct address does not mean every sentence should contain a name. A repeated vocative can make dialogue sound instructional. After resolving the permission, read the exchange without the name. Can a response, gaze or action identify the listener? If yes, omission may preserve the relationship while improving rhythm. The tool does not score name frequency or claim that more vocatives make a scene more emotional.

A full-name reprimand is another context rule, not a new identity. It may contrast with an ordinary short form, but the contrast needs a baseline established in the work. Likewise, a title may be appropriate during a ceremony while a personal name is used elsewhere. Record what the story has taught rather than assuming a reader will assign the same emotional meaning to a form in every language.

For language-specific honorifics and kin terms, keep a source or reviewer note outside the permission itself. A consistent but culturally unsupported policy can still be wrong for a realistic setting. The worksheet checks that you follow your stated policy; it cannot certify that the policy is natural or historically appropriate.

Handoff and revision questions

Export the address style sheet with the selected speaker and listener. The timeline helps a collaborator see how the relationship develops, while the dialogue audit identifies actual occurrences needing attention. A private style sheet can contain future milestones. Do not present it as a spoiler-free reader glossary unless you have removed the undisclosed events.

When an event changes, ask which later forms depend on it, which contexts remain valid, and whether any recorded violation was intentional. Keep cancelled events in the author’s planning record if they explain an abandoned version, but do not treat them as active story facts. A missing milestone should create review work rather than silently increase familiarity.

Finally, check the correction scene itself. Does the person requesting a boundary retain agency? Does the other person alter behavior? Do later public records match the change? Those questions make the name useful in character writing. The graph is successful when it supports a coherent scene, not when it produces the most elaborate collection of possible nicknames.

Can an intentional insult pass the permission audit?

It can be recorded as intentional, but it is still not a permitted form. The audit keeps the actual wording, expected form and stated reason visible. That lets an editor check whether the scene portrays the violation and its consequence rather than accidentally endorsing it as the normal relationship. Annotation explains the exception in the manuscript; it does not rewrite the character’s boundary.

Why does deleting a milestone affect later dialogue?

A permission linked to that event depends on the relationship transition actually occurring. Removing or cancelling the event invalidates the dependent form. This is useful when a revision removes a reconciliation but leaves intimate address in later chapters. Add a new earned transition or revise the dialogue. Do not let the tool invent an emotional event merely to keep the planned vocabulary.

Does the public/private field establish cultural formality?

No. Context labels are authored categories in your project. A particular honorific, title or kin term still needs language- and situation-specific review if presented realistically. The graph checks consistency with your supplied policy, not universal politeness. Two speakers can also have different permissions in the same context, so avoid turning one formal label into a rule for every relationship.

Should narration use the same form as dialogue?

Not automatically. A narrator’s knowledge and narrative distance can differ from a speaker’s permissions. Model a separate context or observer where necessary rather than assume a universal preferred name. Read the actual passage after resolving the rule. A correct vocative repeated too often can still sound stiff, and an omitted name can sometimes preserve both clarity and the intended relationship.