To scenes

Turn BEATS.md and NARRATION.md into SCENES.md. A scene is a small event in a world, not a container for information.

Process

1. Read both inputs, the applicable design truth, and references/hyperframes-capability-envelope.md. Recompute the beats and narration artifact digests; continue only when the narration's source_digest matches the current beats and both stored artifact digests match their files. The envelope constrains feasibility without prescribing implementation. Treat narration as revisable evidence, not a locked timeline.
2. Find a physical or spatial expression for each abstract beat: give the concept a body, put it in a world, and cause a visible state change.
3. Group beats that belong to one continuous event; split a beat when its explanation requires distinct visual events.
4. Design the film as a whole: establish a continuity object or motion, vary worlds and shot scales, place visual peaks, and name the rhythm.
5. Flag narration sentences whose order, length, or duplication fights the visual event. Revise NARRATION.md only after preserving the originating beat's claim and job. After any revision, recompute its artifact_digest and revalidate its beats and article lineage before using it as a source.
6. Write SCENES.md using references/scene-format.md. Read that file before drafting or auditing scenes, and record the current beats and narration digests.
7. Classify every scene's feasibility using the capability envelope, naming dependencies and fallbacks where required.
8. Run the scene audit in the format reference. If narration changes after scenes exist, revise every affected scene, refresh source_narration_digest, recompute the scenes artifact_digest, and repeat the audit before completion.

SCENES.md is complete when every beat has a feasible visual event, the film has deliberate variation and continuity, and a storyboard artist can choose shots without inventing the direction.