# Narrative and composition

For an opted-in reference release, read the accepted `reference-analysis.referenceSelection.plannedRelationships` and direction identity invariants. Express the accepted introduction, proof, pace, interior development and action relationships in the page/section sequence, density, media prominence and mobile transformation. Use the selected dossiers or original `reference-study-*` expansions to resolve a concrete uncertainty; do not restart discovery at every page or treat a business tag as a mandatory skeleton. Teaching facts/media never become customer facts/media.

Map every legitimate original route to a disposition. Preserve meaningful content and conversion capabilities; merging routes needs a reason, not a shorter-site quota.

Write `designContractVersion` 1. For each page, write `role`, `visitorOutcome`, and purpose, then sections with a question, message, `role`, `purpose`, opportunity and decision ids, fact IDs, media IDs, action behavior, emphasis plus `emphasisReason`, `layoutFamily`, `density`, `mediaProminence`, `repetitionRationale` when a repeat is deliberate, `mobileTransformation`, and transition. Layout names are not a mandatory sequence. Plan the homepage and a representative interior first as a complete visitor experience, not a compact study. Include each section's visitor question, message, fact/media IDs, visual emphasis, composition, transition, and action. Do not impose a universal section count or invent material to make the page longer. The interior must answer its own purpose instead of repeating the homepage.

Write storyboard version 3. Map each selected (use) media asset to a purposeful section or an explicit globalMedia header/footer placement with assetId, placement, planned routes, and reason. Only evidenced customer logos and brand artwork qualify for global placement. The storyboard owns final media-selection.json: each selected slot names its route and placement; section slots also name sectionId. A shared slot needs one selection row per route. Inventory routes are early intentions. Reopen media for changes to inspection, identity evidence, or candidate inventory.

When `launch.json` selects `composition-v1`, keep version 3 and `designContractVersion: 1`, then add `compositionContractVersion: 1` and the pinned `compositionLessonRelease`. Give each page a short `compositionIntent.organizingRelationship` and `readingSequence` of existing section IDs. For consequential sections, use stable `elementPlan` IDs with references to known facts, approved media, or the section message/action; add meaningful `relationships`, lesson applications, and `renderObservations`. Copy is written later, so do not require future copy IDs at this stage. An ordinary simple section needs no invented element or lesson count. Cross-section relationships may connect planned elements on the same route. The observations should state what a reviewer can see or test at relevant widths and states.

Plan required mobile proof and action order in the page/section sequence. If that order cannot serve the visitor, record and review a justified plan revision before implementing a different sequence.

Evaluate rhythm across scale, density, media prominence, alignment, background, and interaction. Changing grid to split is not enough if every section feels equally weighted. Repeat brand motifs while varying emphasis according to the narrative.

For people and work pages, explicitly map evidenced portraits and projects to the sections they substantiate. Explain intentional omissions of central source evidence. Keeping an image in the inventory does not by itself preserve its value to visitors; scattering unrelated originals across a page does not establish business fit.


For scroll motion, use the stage-scoped `motion.md` contract. Choose business-specific scenes and quiet intervals; preserve operator policies. Carry motionPlan v2 for every new/reauthored route (historical v1 remains compatible) from direction/storyboard to unique native/component target IDs, then inspect before/during/after normal and reduced scrolling. Temporal claims require live observations or recordings; agent review is not human preference.

Motion decision for new authoring: explicitly consider business character, useful emphasis and quiet intervals; compose the opening, development and closing of every authored route; static choices require explicit operator restrictions or connected quiet intervals. Preserve operator off and existing customer policies. Load only the selected motion-count/numeric/text/image/process/sequence recipe from agent/refs. Review actual scrolling for purpose, comprehensible pacing, immediate reading/actions, competing effects, enough stillness, intentional mobile treatment and repeated entrances. Bind scenes and statistic facts to stable compiled IDs; revise intent explicitly when it changes.


Whole-page motion responsibility: for new/reauthored routes use motionPlan v2 and read `motion-page`. Cover every authored route, including expansion/contact; locate opening, development, connected quiet intervals and closing in actual IDs. Keep essential content/actions static and readable. Representative runtime success or two colocated effects is insufficient. Inspect normal desktop/mobile full journeys and reduced/static views; critique distribution, continuity, inert stretches, competition and meaningful differences among routes with located evidence. Return actionable repairs, preserving operator off and historical records. Human preference stays unset.

When a service or action needs an icon, load `icons.md`, search and inspect the candidate. Choose by meaning, reserve the recommended size, and retain the service label. Technical illustrations and studio families need more space; compact navigation may use a simpler core symbol or text alone. Do not plan unsupported family/icon combinations.