# Event Density

Use this reference to decide how much story belongs in one generation.

## Density Rule

One generation should normally carry one visible beat with a changed endpoint. Long backstory, multiple locations, multiple major actions, dense dialogue, and future resolution belong in the sequence plan, not the current prompt.

## Beat Buckets

`already_happened`: do not replay.

`this_clip_only`: the current prompt may perform this.

`reserved_for_later`: do not show yet.

`do_not_show_yet`: excluded even if it explains motivation.

## Scope Firewall

Story context can inform motivation, performance, atmosphere, and pacing. It must not cause the current clip to perform future events, reveal future information, solve later problems, or skip physical handoff states.

## Splitting Triggers

Split when a request asks for several completed actions, a journey with multiple locations, several turns of dialogue, complex physical contact, product proof plus hero packshot, or a story longer than the verified active-surface duration.
