analysis-journal

/analysis-journal — Insight Journal Manager

Records the reasoning process behind an analysis design as a structured event journal. Each event captures a discrete reasoning step — observation, hypothesis, evidence, question, decision, reflection, conclusion, or branch.

Based on Narrative Scaffolding (Huang+ IUI 2026) and Sensemaking Loop (Pirolli & Card) frameworks.

When to Use

• During active analysis: recording what you observed, decided, or discovered
• When choosing an analysis method or package (e.g., "CausalImpact を使う")
• When a new question arises during investigation
• When branching to an alternative hypothesis

When NOT to Use

• Creating a new design from scratch (→ /analysis-design)
• Structured reflection and conclusion (→ /analysis-reflection)
• Registering data sources or knowledge (→ /catalog-register)

Workflow

Step 1: Identify Target Design

If $ARGUMENTS contains a design ID (e.g., "FP-H01"), use it directly. Otherwise, call list_analysis_designs(status="analyzing") and ask user to select.

Validate with get_analysis_design(design_id).

Step 2: Load or Initialize Journal

Read .insight/designs/{design_id}_journal.yaml using the Read tool.

• If exists: load and show summary (event count, last 3 events, open questions)
• If not exists: create with initial structure using the Write tool:

metadata:
  design_id: "{design_id}"
  created_at: "{now in ISO 8601 JST}"
  updated_at: "{now in ISO 8601 JST}"
events: []

Step 3: Record Events (Interactive Loop)

Listen to user input and classify into InsightType:

User says...	InsightType	Example content
データを見たら〜 / 〜が見えた / 〜に気づいた	observe	"2026年1月以降、売上が前年比15%低下"
〜だと思う / 仮説: / 〜が原因では	hypothesize	"価格改定（+8%）が売上低下の主因"
〜で確認した / データが示す / 〜のエビデンス	evidence	"回帰分析でp<0.01の有意な負の相関"
〜が気になる / 〜を調べたい / なぜ〜	question	"季節要因を除外できているか？"
〜を使う / 〜で分析する / 手法:	decide	"CausalImpact で因果効果を推定する"
振り返ると / 見直すと / 反省点	reflect	"初期の相関分析では交絡が未考慮だった"
結論: / まとめると / 〜と言える	conclude	"価格改定は売上低下の主因と確認"
別の仮説 / 分岐したい / fork	branch	→ Step 4 (Branch Workflow)