action-choreography git:20260921.a8a3957A

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

---
name: action-choreography
description: Specify causal body and object mechanics before a complex shot is produced. Use for Action Bible authoring and review; no media generation.
---

# Action Choreography

## Role and authority

Specify causal body and object mechanics before a complex shot is produced.

Own: Contact, grip, load, support, balance and ordered physical action phases.

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

Approved action outcome; Blocking; Performance intent; Prop and Animal interaction constraints.

## Professional decisions

Decompose action by physical changes: preparation, contact, support/load transfer, correction, consequence and recovery. Name actor, limb/side, receiver/object, grip establishment and release. A failed attempt must alter the next action; do not jump from reach to successful mount. Declare what must remain observable and what cannot overlap safely or plausibly. Complexity may propose coverage changes, never rewrite the event.

## Outputs

Produce a versioned `Action 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

Every result has an enabling contact and support; body/prop states bridge phases; injury and fatigue constrain execution; no physically impossible teleportation.

## Failure and escalation

Missing Blocking or object scale returns dependency failure; proposed event changes go to Screenplay/Director. A provider limitation cannot replace choreography with vague action words.

## 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.

## Route-owned expression

Within the Director-selected route envelope, author anticipation, acceleration, impact, follow-through and environmental reaction. Preserve support/contact/weight and canonical outcomes. A character action signature does not propagate to other actors. Read [expression route contract](../../docs/expression-route-contract.md) when using character or action expression profiles.