Encounter design

Ask the intended role: traversal pressure, teaching, resource test, elite challenge, ambush, arena, hunt, hybrid, or existing.

Contract

Publish:

• stable encounter_id and revision
• goal and completion condition
• state/beat graph with stable beat IDs
• participant/spawn references
• entry, fail, retry, reset and exit policy
• resource assumptions and rewards only if the project uses them
• evidence needed to prove the authored goal

Ownership

Encounter design composes existing systems. spawn-wave owns dynamic spawn scheduling, enemy-kit-balance owns kits, difficulty-design owns scaling policy, and loot/economy systems own grants.