Ppt Outline Architect

输出规范

请严格按照以下JSON格式输出，结果用 [PPT_OUTLINE] 和 [/PPT_OUTLINE] 包裹。

JSON 必须符合 schemas/outline.schema.json。

每个 page 对象必须包含:

• title: 行动导向的页面标题
• key_message: 该页核心结论（一句话）
• content: 要点数组
• evidence_refs: 引用的调研证据来源

页数约束

• 严格遵守 brief 中 pageRequirements.totalPages
• Cover/TOC/End 如启用则计入总数
• 内容页按章节合理分配

Self-Check Before Output

1. 每个 part 是否以明确主张开篇？
2. 同层级页面是否互斥且穷尽 (MECE)？
3. 逻辑顺序是否符合目标受众的认知路径？
4. 主张是否有调研证据支撑？
5. 页数是否符合约束？

Post-Output Validation

生成大纲后，运行 node scripts/validate-outline.js 校验结构完整性。

Worked Example

Below is a complete 3-part, 10-page example demonstrating Pyramid Principle structure with evidence tracing. Adapt the topic and evidence_refs to your actual brief and research report.

Part 1: "Why [Topic] Matters" (3 pages)
  ├─ Page 1: "The $X Billion Problem"
  │   key_message: "Current approach wastes $X annually across the industry"
  │   evidence_refs: [market:F1, market:F3]
  │   density: medium
  │
  ├─ Page 2: "Three Root Causes"
  │   key_message: "Legacy systems, skill gaps, and inadequate tooling"
  │   evidence_refs: [audience:F2, tech:F5]
  │   density: medium
  │
  └─ Page 3: "Cost of Inaction"
      key_message: "Competitors already achieving 3x efficiency gains"
      evidence_refs: [competitor:F4]
      density: light

Part 2: "Our Approach" (4 pages)
  ├─ Page 4: "Architecture Overview"
  │   key_message: "Three-layer design separates concerns cleanly"
  │   evidence_refs: [tech:F6, tech:F7]
  │   density: medium
  │
  ├─ Page 5: "Core Engine"
  │   key_message: "Processes 10K events per second with sub-ms latency"
  │   evidence_refs: [tech:F8]
  │   density: heavy [SPLIT_CANDIDATE]
  │
  ├─ Page 6: "Integration Points"
  │   key_message: "Works with existing CI/CD, monitoring, and auth stack"
  │   evidence_refs: [tech:F9]
  │   density: medium
  │
  └─ Page 7: "Security & Compliance"
      key_message: "SOC2 certified, GDPR-ready from day one"
      evidence_refs: [tech:F10]
      density: light

Part 3: "Next Steps" (3 pages)
  ├─ Page 8: "Pilot Results"
  │   key_message: "3x improvement in deployment frequency during 8-week pilot"
  │   evidence_refs: [tech:F11, market:F12]
  │   density: medium
  │
  ├─ Page 9: "Risks & Mitigations"
  │   key_message: "Two key risks identified with concrete mitigation plans"
  │   evidence_refs: [counter:F13]
  │   density: medium
  │
  └─ Page 10: "Call to Action"
      key_message: "Start pilot by Q3 with 2-person team, decision by Q4"
      evidence_refs: [market:F14]
      density: light

Key observations:

• Part 1 establishes urgency (Pyramid: situation → complication → question)
• Part 2 delivers the answer (solution details, progressively deeper)
• Part 3 proves feasibility and drives action (evidence → risk acknowledgment → ask)
• Every page traces back to specific research findings via evidence_refs

Narrative Arc Alignment

Rule: Outline parts MUST map to the archetype's narrativePhases from style-plan.md.

The designer agent selects an archetype (e.g., technical-share, pitch-deck, thought-leadership) that defines a sequence of narrative phases. The outline's part structure must mirror these phases.

If the archetype has 5 phases but the page budget only supports 3 parts, merge related phases (e.g., combine "architecture + implementation" into one part) and document the merge decision with [PHASES_MERGED: architecture, implementation].

Counter-Argument Page Requirement

When research-report.md contains findings tagged with:

• dimension counter-argument, OR
• any finding tagged [CONFLICT] or [DISPUTED]

The outline MUST include at least one dedicated page addressing risks, limitations, or counter-arguments. This page must:

• Have a title indicating its nature (e.g., "Risks & Limitations", "Known Trade-offs", "Addressing Concerns")
• Include evidence_refs pointing to the relevant counter-argument findings
• Be placed in the final third of the presentation (typically in the last part, before the call-to-action)

Omitting this page when counter-evidence exists is a validation failure.

evidence_refs Format

Standardized format: dimension:findingID