# Whole-page temporal composition

Compose every authored route as one journey. Begin with its visitor task and the site's motion character, then locate opening, development, connections and ending in the actual content. Stillness connects active moments; it does not excuse an untouched remainder. Representative success does not cover contact, service, project, about or expansion routes.

New scaffolds use `motionComposition:{version:2,routes:"all-authored"}` and the supported `scrollMotion:{version:1,policy:"enabled"}`. Historical sites omit the authoring marker. A deliberate reauthor of an existing route can select `motionComposition:{version:2,routes:["/route"]}`; other routes remain historical. Managed upgrade changes knowledge, never customer policy. Explicit operator off, OS reduced motion and no-JS/failure states remain authoritative. System-generated cookie/error/redirect pages stay static and are not omitted authored coverage. Do not call a customer contact/legal page a utility to bypass the responsibility.

Extend the existing `motionPlan` to version 2, retaining its scene contract. Add `routes:[{route,task,character,normal,mobile,reduced,ending,available:["primary-message","contact-action"],beats:[{sectionId,role,change,scenes:["accent-id"],transition}]}]`. Beat IDs follow storyboard sections and actual output in document order. Roles are opening/development/closing, or whole for a genuinely single-beat short page. Every scene belongs to its real beat. Quiet beats use `scenes:[]` and `connects:["earlier-active-target","later-active-target"]`; explain the continuity. `available` identifies essential messages/actions/forms that remain immediately readable and operable. Counts also carry supplied fact references and exact final text. Never fabricate a statistic or image to fill a beat.

Opening: keep identity, h1, LCP image and action visible. A secondary rule, graphic or supporting visual can introduce the character. Initially visible text/sequence entrances are deliberately static safeguards: choose an appropriate supporting draw/progress accent rather than claiming those skipped entrances run.

Development: express useful evidence. Use a verified count, selected phrase, authentic image/caption, process accent or another existing primitive only when content warrants it. Relate direction, cadence or a shared accent across sections. Keep ordinary paragraphs, specifications and service/legal detail readable. Do not force a sticky story onto short content.

Ending: resolve a supporting accent or brief visual sequence near the next action, with the action available throughout. Never animate form fields, move a submit button, delay labels or make a contact page artificially long. A short page can have one coherent accent across its brief opening/ending; it needs no animation quota.

Positive text-led example: a visible offer with a secondary ledger rule establishes precise continuity; a later scope comparison changes emphasis; a still detail interval connects to a closing margin accent beside an immediately usable inquiry. On the service interior, use the actual ordered work/process relationship instead of repeating the homepage phrase-plus-rule pair. On contact, a small supporting accent resolves the same identity beside static fields.

Positive image-led example: a quiet authentic project hero with a supporting accent; later project/caption movement clarifies a material or spatial relationship; the project list stays readable; a closing image detail or simple rule connects to the inquiry. The interior can follow project evidence at its own cadence, not duplicate the homepage arrangement.

Negative examples: two effects in one section with all remaining sections called quiet; fade-up every section; adding ornaments at fixed percentages; unsupported counts; introducing empty spacer sections to meet coverage; competing large image/text motion; hiding primary headings/actions; using a static mobile treatment for every active moment. None establishes good choreography.

Watch every route from first view to ending in normal desktop/mobile, then reduced/static readability. Full journey evidence must include the quiet middle at readable traversal speed, ordered section/scene positions, actual changing scene states and source/output/scenario hashes. Target checkpoints alone are insufficient. Recordings are review evidence, separate from performance runs. Concentration flags detect incompleteness, never establish aesthetic quality or a numeric motion score.

Critique every route with located checkpoints: opening-to-ending contribution; distribution/connections; business-specific rhythm; competition/inert stretches; differences among routes; immediate reading/navigation/action in mobile/reduced views. Return an actionable repair for a concentrated or inert plan even when runtime tests pass. Record findings as agent assessment, with human preference unset.