--- name: document-architecture description: Plan Document Studio documents by their intended form and reader task, including reports, approvals, proposals, operations guides, research briefs, existing templates and live presentations. Use for new document structures, page/section logic or changed arguments. --- # Document architecture For a new laid-out document use the [accepted guide baseline](../report-html-pptx/references/accepted-composition-default.md) to plan distinct supported narrative jobs and suitable explanation relationships across the body. Read the relevant actual guide pages; preserve current choices and do not copy its eight-page sequence. ## Select the document's logic contract In an explicitly chosen Editorial Consulting session, act as a critical strategy architect: compare the provisional author thesis against checked counterevidence and relevant **actual document precedents** before recommending substantive alternative arguments or section order. Alternatives must change a reader decision or explanation mechanism, not merely change titles. Carry only the selected direction, source/claim IDs, accepted conditions and affected sections into the canonical map; the consultation guide owns the author checkpoint. Ordinary architecture requests retain their current lightweight route. If new consulted evidence qualifies, contradicts or reframes an accepted claim, compute the **directly affected canonical section IDs**; for live narratives, inspect the necessary neighboring transitions separately. Do not reopen adjacent presentation transitions in reading reports or change unrelated already-accepted sections simply because a whole-document draft exists. Pending author thesis decisions block final manuscript acceptance, not unaffected research/copy work. First identify the document family from actual reader use and existing/accepted format, not from slide count or PPTX extension. Apply a **form-specific page/section contract**; use [editorial development](../report-html-pptx/references/editorial-story-research.md) when substantive research or content restructuring is needed. - **live presentation**: teach or persuade an audience in sequence. Use audience question → on-screen takeaway → evidence/example → prerequisite → next bridge only for live explanatory narratives; include speaking/demo time when material. - **reading report**: enable independent reading. Organize question/scope, findings, explanation, evidence/limits and navigation at section level. Pages can carry continuous prose, figures and several related facts; they need not end with a rhetorical transition. - **approval or decision**: surface requested decision, recommendation/options, decision basis, costs/risks, conditions and responsible next action. Lead with what the approver must decide; a compact approval sheet may have no cover or staged suspense. - **proposal or execution plan**: connect situation, objective, alternatives, proposed mechanism, tasks/owners, schedule, dependencies, costs, risks and measurable success conditions according to the actual request; do not force a generic three-act story. - **operations or staff guide**: organize task/trigger, prerequisites/inputs, ordered steps, examples, exceptions, handoff/checkpoint, responsible person and reference. Accuracy and findability outrank persuasion. - **research or analytical brief**: show question, definitions/method, findings, comparisons, uncertainty/limitations and interpretation so figures cannot be misunderstood. - **existing template**: preserve required field order, headings, page count constraints, tables and formal submission rules; improve meaning within the permitted slots rather than reorganizing the form. For every family, check completeness against the reader's actual task, claim/source fidelity, correct information hierarchy, units/status/qualifications, legibility and absence of redundant material. Assign a meaningful page/section role only when the artifact needs multiple distinct units. **Do not require audience_question, one takeaway, prerequisite and next_bridge on every reading-document page.** For maps use only relevant fields; a form's mandatory field can be more important than a page narrative. Create alternate sequencing only when it improves a consequential reader decision. Research is allowed to change the thesis or sequence. When a substantive new finding, corrected identification or counterexample changes an argument, revisit only affected sections and necessary transitions, while preserving accepted unaffected pages. Record what shifted and why; do not keep a broken original outline merely because pages were numbered. Stop revising when the reader decision is supported and the remaining uncertainty no longer alters the flow. Reuse the orchestrator's current brief and provisional or accepted choices. Start the usable structure from the supplied material; pending required choices permit only unaffected provisional outlining. Return only a consequential ambiguity that changes the argument, while progressing unaffected sections. Connect reader need → supported content → evidence/conditions → warranted interpretation or next action at the appropriate document/section level. This is a traceability check, not a mandatory page sequence. Distinguish fact, inference, proposal, goal and unknown. Keep critical qualifications with their claims. Exact comparisons retain period, population, unit and denominator; missing facts go to research rather than being invented for a tidy structure. Use the existing brief.sections or page map with IDs, section purpose, supported content, claim/source IDs, conditions and visual purpose. For live explanatory pages only, add audience_question, narrative_role, prior_link, next_bridge and optional time/demo/visual_motion_job. For forms and reports, use field/section order, evidence placement and cross-references instead; do not create a second slide-map database. Actual entities and relationships guide the format: comparison, sequence, ownership, object, place or proposed experience. Do not turn the map into a second manuscript or fix every section to a chart/card. Use [profiles and families](../report-html-pptx/system/design-system.md) for page roles and density. HTML is the fixed composition source; default PPTX is converted later. A supplied deck constrains layout and preserved content, not the authoring route. Keep an accepted sequence for local edits; a short approval document need not add a cover. For layout-bound architecture, reuse [expression](../report-html-pptx/references/design-expression.md). For [creative bodies](../report-html-pptx/references/body-composition.md), identify which paragraphs concern a scene, subject, local detail or activity. Give design the supported relationship and image role so it can make connected scenes, mosaics or photo narratives around substantive copy. Hand off only actual gaps to [research](../document-research/SKILL.md), the map to [writing](../document-writing/SKILL.md), and relationships to [design](../document-design/SKILL.md). Return changed IDs and affected sections. Review title/body/evidence agreement and outline-to-body alignment using [content review](../report-html-pptx/references/consulting-content-review.md) when material; this creates no extra user approval. ## Choose explanation and narrative movement Apply [expression and rhythm](../report-html-pptx/references/visual-expression-and-rhythm.md) while mapping body pages. Actively consider a factual image/annotated detail, concept illustration, process/relationship diagram, chart, timeline, case or connected prose before choosing a table. Record the actual explanation form, narrative movement and reason in the existing map; pass useful image jobs to design. Three repeated body forms/moves or table dependence require a concrete reconsideration, not arbitrary variety. Preserve logical continuity while avoiding the same background/list/effect mini-story on every page. Report page titles and subheads follow [nominal headings](../report-html-pptx/references/report-heading-style.md); claims and qualifications remain in the body.