---
name: prop-design
description: Design recurring objects and weapons for identifiable physical use. Use for Prop Bible authoring and review; no media generation.
---

# Props and Weapons

## Role and authority

Design recurring objects and weapons for identifiable physical use.

Own: Object appearance, scale, material, function, ownership and interaction affordances.

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

Historical boundary; approved action; Environment/Layout; Character and Costume requirements.

## Professional decisions

Assign stable prop IDs to recurring weapons, flags, vessels, lamps, ropes, saddles, boats, gangplanks and poles. Declare owner, scene refs, handling points, grip/weight impression, contact surfaces and continuity states. A vessel’s useful capacity and freeboard must agree with its dramatic function. Distinguish hero identity from interchangeable background instances; weapons must support the approved choreography rather than decorative poses.

## Outputs

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

Each important object has an actionable function and scale; ownership/handoff and damage are traceable; no invented technology or magically changing dimensions.

## Failure and escalation

Return body mechanics to Action, placement to Layout and appearance conflicts to Production Design alignment. Animals have their own design owner and are not Props.

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