Link report structure and production guidance (0.8.0)

references/visual-design.md

@@ -1,15 +1,24 @@
 # Page mockups and visual materials
 
-Reuse the user's settled template, theme, route and page workflow. Define the current page's title/message, supporting evidence, content groups, notes, layout, asset roles and required native objects before generating its mockup. Review only consequential decisions that remain open; do not restart settled outline or style choices. A request to review one page does not authorize a full-deck generation run.
+Reuse the user's settled template, theme, route and page workflow. Receive the current page's title/message, evidence, content groups and notes through [content handoff](content-handoff.md), then define its layout, asset roles and required native objects before generating its mockup. Establish a minimal page brief if none is supplied. Review only consequential decisions that remain open; do not restart settled outline or style choices. A request to review one page does not authorize a full-deck generation run.
 
 When extracting style from an existing presentation or PDF, render representative pages and inspect the actual images. XML/object counts alone cannot establish density, hierarchy, ornament or spacing. Keep style references separate from strict source assets. Use existing accepted references; a rejected mockup does not remain a design baseline.
 
+## Page composition and HTML boundary
+
+Choose text, figures, diagrams and their arrangement from the current information relationship. Pure text can serve a short question, quotation or conclusion; a picture or icon needs a useful role. Do not mechanically reuse website hero sections, selling cards or dashboards as report layouts. The page's main meaning must be readable without scrolling, hovering or clicking.
+
+Make conclusions and their supporting evidence visibly correspond through proximity, a shared heading, matching labels, annotations, highlighting or a necessary connector. Use only connections that express real relationships. Preserve exact premises and key reasoning/derivation steps where the audience needs them; check progression and information burden in the actual composition. Internal item counts, maintenance IDs and authoring decisions stay in process material unless the audience needs them for the report itself.
+
+Do not use HTML/DOM/CSS to lay out report pages, including layouts later captured as screenshots, printed or converted to another format. HTML may contain a JavaScript visualization itself and its necessary runtime container. This exception does not cover surrounding titles, prose, columns or page UI; produce those through the permitted native/SVG route. A direct SVG diagram is allowed. Keep the selected route's editability claims accurate for any visualization asset.
+
 ## Mockup prompt inputs
 
 Use the host image-generation tool directly for requested raster page samples. Supply:
 
 - The selected canvas/aspect ratio, template palette, typography intent, grid and fixed content regions.
 - The exact current-page text and moderate content density, with a declared hierarchy and clear content division.
+- The intended page progression, necessary premises or key steps, and the association between conclusions and evidence.
 - Approved representative images as style references, with the current layout allowed to differ.
 - Supplied logos, figures and screenshots as strict identity/evidence assets. Preserve values, axes, labels, proportions and scientific meaning; do not synthesize substitute evidence.
 - The editable reconstruction plan: decorative pictures may remain assets, while title/body, controls, separators and diagrams must later become independent native objects as required.