Link report structure and production guidance (0.8.0)

references/page-collaboration.md

@@ -4,7 +4,7 @@ Use one coordinator and one active writer per page. The coordinator owns narrati
 
 ## Freeze and assign
 
-Agree audience, deck argument, page order and review cadence. Define stable IDs and a brief per page: one message, evidence, data/units, capacity, transition and notes. Assign only pages authorized to proceed. Under `interactive-page`, review gates still apply; parallel workers do not authorize future pages or a batch.
+Consume the agreed audience, deck argument, page order and review cadence through [content handoff](content-handoff.md). Define stable IDs and a brief per page: its task, intended understanding, evidence, data/units, necessary premises and key steps, progression, conclusion-to-evidence associations, capacity, transition and content/notes/appendix allocation. Express these in the existing brief as relevant to the task; no new compiler schema or mandatory page-by-page time budget is needed. Report structure may come from the optional `report-structure` Skill or the user's own plan. Assign only pages authorized to proceed. Under `interactive-page`, review gates still apply; parallel workers do not authorize future pages or a batch.
 
 Freeze one template/version/theme, manifest and style input hashes, roster, fonts, glossary, shared data/assets. Use the project tools for the template snapshot and builder. Give each worker the same baseline, a visual reference when available, page brief and write allowlist. Read library examples from the selected template. Route shared changes to the coordinator before implementation.
 
@@ -27,7 +27,7 @@ For separate worktrees/devices, return an assigned source diff or directory arch
 
 Deliver source/content/notes, private assets and a packet recording ID, owner, revision, baseline hashes, layout, purpose, origin, source/asset hashes, preview renderer/hash, native objects, picture exceptions and unresolved issues. State source/static, native structure, SVG render, actual PowerPoint render, editing and projection individually; unavailable checks stay `not-run` with a reason. A PNG does not prove editability. Ready means ready for integration review.
 
-Source, content and notes must agree. Update table/chart metadata with data; preserve evidence labels, numbers and units. Match fonts, grid, fixed body area and palette; remove placeholders/example text. Keep resources within the assigned page directory.
+Source, content and notes must agree. Update table/chart metadata with data; preserve evidence labels, numbers, units, necessary premises and key steps. Check actual reading order and the visual association between conclusions and evidence. Match fonts, grid, fixed body area and palette; remove placeholders/example text. Keep resources within the assigned page directory.
 
 ## Integrate and revise
 
@@ -37,7 +37,9 @@ Source, content and notes must agree. Update table/chart metadata with data; pre
 4. Review the integrated deck for narrative, terminology, units, title rhythm, density, figure scale, repeated icons and navigation state. Render it: per-page static checks cannot establish visual consistency. Shared-style changes require affected pages to rebase and rerender.
 5. Keep the agreed user acceptance granularity. Record accepted/revision-needed with evidence, then proceed to the next authorized pages. Pack after locks/integration pass. Another device supplies declared dependencies/fonts and runs its own application checks.
 
-Reauthor or repair only affected pages; integrated export still compiles the completed SVG set together. Reuse unchanged page content and valid prior checks. For shared changes identify affected pages before repeating checks. Author completion, integrated render and user acceptance remain separate states.
+Reauthor or repair only affected pages; integrated export still compiles the completed SVG set together. If content allocation or order changes, synchronize stable IDs and destinations, page numbers, references and notes with the plan, including links across split arguments. Reuse unchanged page content and valid prior checks. For shared changes identify affected pages before repeating checks. Author completion, integrated render and user acceptance remain separate states.
+
+Use independent review when it can resolve a meaningful understanding gap; it is not a fixed multi-Agent pipeline. Save new reference implementations only from actual received or produced material, with source, method and the scope of acceptance. Template geometry feedback stays with the template maintainer; report-logic examples and rule learning stay with the structure maintainer.
 
 ## Research basis