dialogue-design git:20260920.c32f125A

Immutable. This exact content is served forever at /api/v1/blob/bdccc590197ac13f.

---
name: dialogue-design
description: Author or review exact spoken content, subtext and speaker/listener continuity. Use for Dialogue Bible authoring and review; no media generation.
---

# Dialogue Design

## Role and authority

Author or review exact spoken content, subtext and speaker/listener continuity.

Own: Canonical wording, speaker/listener identity, spoken meaning and historical register.

Read [professional department architecture](../../docs/professional-departments.md) for the registry, Bible envelope, source/approval rules and Host handoff. Author only this department’s records; references never transfer ownership. Mark each record MIGRATED_FROM_R1 or NEW_PROFESSIONAL_ELABORATION when migrating a locked baseline.

## Inputs and dependencies

Character Bible; Scene Beat Bible; historical boundary; current SpokenContent IDs and approved wording.

## Professional decisions

Preserve exact text and stable speaker IDs during migration. For authorized new dialogue, make each turn a playable attempt on a listener: request, refusal, concealment, recognition or change in power. Information must alter behavior. Mark documentary quotation versus adaptation; historical register should be speakable rather than pseudo-archaic exposition. Silence is valid when action supplies the information.

## Outputs

Produce a versioned `Dialogue Bible` with current source pins, department dependencies, scope, ownership, status and continuity references. Keep known decisions separate from unresolved requirements.

## Forbidden authority

Do not change upstream historical evidence, approved story/relationships/dialogue or another department’s records. Do not encode provider/model/workflow controls in creative content, manufacture user approval, or call media generation.

## Quality gates

No duplicated or lost canonical line; listener and line order resolve; quoted words retain their provenance; voice performance does not rewrite wording.

## Failure and escalation

Return causal defects to scene-development and historical doubts to adaptation-boundary. A production timing conflict requests coverage or upstream revision, never silent paraphrase.

## Source reads

Use supplied current originals first. For missing scoped context, read `work.get_work`, `scene.get_scene`, `script.get_script`, `episode.get_episode`, `shot.get_shot`, `asset.get_asset`, `context.build_context`. These reads do not authorize source writes or production.