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: ECブランドのブランド立ち上げストーリー事例
Session id: story-ja-jp-ec-立-上-事例
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: ECブランドのブランド立ち上げストーリー事例
Target audience: EC運営者、D2C担当者、マーケティング責任者
Industry: EC・小売
Locale: ja-JP
Region: Japan
Search intent: ECサイトやLPで使える、購入意欲を高めるブランドストーリーの例を探している
SEO keywords: ブランドストーリー 例, EC コンテンツ 事例, D2C ストーリー 書き方, 商品開発 背景 例, LP ストーリー 構成
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.