action-choreography git:20261015.220ea4bA

Immutable. This exact content never changes and is served at /api/v1/blob/0faa20e00c5e17f0.

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

At a critical transfer, work backwards from the receiving grip: where can the
hands enter while the previous support still carries weight? Check intermediate
poses, not only a plausible start and finish. Returning an object flat to a table
does not leave finger clearance everywhere. Describe the remaining support
footprint and the hand's free approach to an accessible underside in that very
pose; saying "slide underneath" is not proof of access. Resolve the path before
transferring weight, without silently adding a support prop or changing geometry.
Identify the supported region and free hand before releasing the table; cloth is a contact
layer, not an invisible lifting sling. Retain assumptions about balance or material
response as assumptions. For small contacts, establish a visible before/after
difference and its cause: lifting a cup alone need not flatten curled paper, and
reaching toward a sleeve does not prove it moved away from ink. Elaborate the
approved action without adding a new dramatic 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.

In the native handoff, each `actionPhases` row is a selected execution unit, not
one mechanical substep or one actor's Beat. Keep a continuous take's causal
sequence, concurrent partner tasks and uninterrupted speech in its `action`,
with shared `entryState`, `observable` and applicable spoken selections. State
what enables each transfer, what overlaps, and what completes the unit. Include
necessary parallel physical expression here from the participants' Beat originals;
the primary beat selection does not silence partners. Formal PERFORMANCE accepts
`beats[*].physicalExpression`, not a top-level field of that name.

Use event-relative timing or estimated local windows where they clarify execution;
never turn each window into another row. Separate a required repeated stroke from
an idle loop by its material result or dramatic purpose. Do not invent work to
fill a clip. Current contact, support and visibility conditions belong in these
action leaves; `physicalStateConstraints` holds lasting invariants, not a second
recital of the sequence. A technical split inherits the actual release state,
without restarting preparation; a film cut needs Shot/Editorial's authored boundary.

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

## Character Package ownership

Combine screenplay facts, Director intent and the packaged actionSignature. Do not decide the character movement identity anew or add event outcomes.

Use the unified read-only `CharacterRepository.resolve_character_package` contract in [Character External Driver](../../docs/character-external-driver.md). Pin characterPackageRef, characterPackageVersion and checksum. Never create or overwrite Character Core in this Skill. Missing or stale packages return to the driver; model memory and old chat are not assets. DESIGN_REVIEW access does not authorize casting or production.

## Character Embodiment ownership

Combine script action + Director intent + embodiment baseline + actionSignature. Do not invent movement identity or new action results.

Read [Embodiment contract](../../docs/character-embodiment.md). Use the unified read-only `characters.embodiment.embodiment_handoff` with exact ref/version/checksum and route. Never create or overwrite embodiment in downstream execution. Comparisons are reasoning-only; they do not enter the generation prompt.

## Still live-action professional knowledge

For opt-in STILL/LIVE_ACTION, project only the approved current body_mechanics or contact_constraints slice into existing action/contact facts. Ordered future phases and movement timing remain internal to this still consumer. Identity references cannot create an action. Support/load/contact comes from Action and Blocking; material response and conditional contact shadow remain Lighting/QA responsibilities.

Read [mapping and evidence profile](../../docs/still-professional-mapping.md) when preparing these still records. Knowledge remains LOCAL_EXPERIMENTAL until scoped A5 media evidence.


## Actor-playable screenplay handoff (Screenplay R2)

Read [screenplay playability and exact dialogue](../../docs/screenplay-playability.md). Resolve causal mechanics for the approved playable action, preserving actor/target/negation/contact. Missing action meaning returns to its owner rather than being created for model convenience.