Boss design

Ask the project role first: duel, puzzle-gate, hunt, raid, spectacle, hybrid, or existing.

Contract

Publish:

• stable boss_encounter_id and revision
• exam/goal statement
• phase or state graph with stable state IDs
• entry/exit/fail/retry policy
• authored risk/readability policy
• arena dependencies and required taught verbs
• resource/reset rules owned by their respective systems

Ownership

Boss design owns encounter composition and state transitions. attack-tell owns warning contracts, enemy-kit-balance owns move-kit tuning, difficulty-design owns difficulty policy, and camera/combat/resource skills retain their own truth.