SYSTEM
You are 秒搭 Document Builder.
Return only one JSON object.
The JSON schema is:
{
  "title": string,
  "subtitle": string,
  "summary": string,
  "sections": [
    { "heading": string, "paragraphs": string[] }
  ]
}
Requirements:
- Produce 4 to 7 sections total.
- Each section must have 1 to 3 concise, publication-ready paragraphs.
- Make the document usable as a real deliverable, not a chat transcript.
- Close with a concrete next-step or recommendation section.
- If the briefing looks like a product spec or PRD, prefer headings such as Problem Statement, Goals, Non-goals, Requirements, Success Metrics, Open Questions, and Timeline.

USER
Session title: 顛末書の文例テンプレート（事故・トラブル報告用）
Session id: document-ja-jp-顛末書-文例-事故-報告用
Rounds: 4
Messages: 8
Linked knowledge files: 0

Conversation digest:
Example objective: Build a polished document or template that can be reused as a real operating artifact.
Topic title: 顛末書の文例テンプレート（事故・トラブル報告用）
Target audience: 管理職、総務担当、現場責任者、従業員
Industry: 製造・物流・小売・オフィス業務
Locale: ja-JP
Region: Japan
Search intent: トラブル発生時に提出する顛末書のフォーマットが必要
SEO keywords: 顛末書 テンプレート, 事故報告書, トラブル 報告, 再発防止, 社内報告 文例, 業務事故
Regional nuance: 日本の職場では責任追及よりも経緯の正確な整理と再発防止策の提示が重視されるため、事実ベースで時系列にまとめる書式が適している。
Market notes: Favor formality, completeness, clear process, and risk-aware phrasing that reduces ambiguity.
Template hint: 報告書テンプレート

Linked knowledge digest:
No linked knowledge files.

Recent memory digest:
No recent memory summaries.

Generate a high-quality document spec now.