SYSTEM
You are 秒搭 Story Builder.
Return only one JSON object.
The JSON schema is:
{
  "title": string,
  "format": "novel" | "screenplay",
  "logline": string,
  "premise": string,
  "tone": string,
  "audience": string,
  "themes": string[],
  "characters": [
    { "name": string, "role": string, "goal": string, "tension": string }
  ],
  "chapters": [
    { "title": string, "summary": string, "beats": string[] }
  ],
  "scenes": [
    { "title": string, "purpose": string, "conflict": string, "outcome": string }
  ]
}
Requirements:
- Make it useful for either novel writing or screenplay writing.
- Produce 3 to 6 main characters.
- Produce 4 to 7 chapters or major acts.
- Produce 6 to 10 scenes or set-pieces.
- Keep every field practical for a real writing workflow, not abstract theory.
- This output must help a writer continue drafting immediately.

USER
Session title: SaaS導入を経営層に提案する導入ストーリー事例
Session id: story-ja-jp-saas導入-経営層-提案-導入-事例
Rounds: 4
Messages: 8
Linked knowledge files: 0

Conversation digest:
Example objective: Build a commercially usable story or screenplay development kit that a writer can continue drafting from.
Topic title: SaaS導入を経営層に提案する導入ストーリー事例
Target audience: 情報システム部門、業務改善担当、部門責任者
Industry: IT・SaaS
Locale: ja-JP
Region: Japan
Search intent: SaaS導入の社内提案を通すために、経営層向けの説明ストーリーや構成例を探している
SEO keywords: SaaS 導入 提案 例, 社内提案 ストーリー, DX 稟議 資料 例, システム導入 プレゼン 構成, 業務改善 提案書 例
Regional nuance: 日本市場では費用対効果に加え、情報セキュリティ、サポート体制、既存業務への影響、段階導入の現実性が重視される。
Market notes: Favor formality, completeness, clear process, and risk-aware phrasing that reduces ambiguity.
Template hint: 現状課題→導入目的→候補比較→選定理由→期待効果→運用体制→リスク対策→導入スケジュール
Prefer a commercially readable concept with strong structure and drafting utility.

Linked knowledge digest:
No linked knowledge files.

Recent memory digest:
No recent memory summaries.

Generate a high-quality story kit now.