# Mode: pyramid

Conclusion-first argumentation. State the answer, then support it with structured evidence — every claim earns its place and data is contextualized without inventing comparisons. For audiences who want the result before the process: executives, boards, investors, decision-makers.

---

## 1. Narrative skeleton

**Conclusion first**: the page title *is* the conclusion, not a label. The body develops the supporting arguments beneath it.

SCQA opening, pyramid body:

| Stage | Role | Where |
|---|---|---|
| Situation | establish shared context | opening pages |
| Complication | the tension / problem | early pages |
| Question | the implicit question to resolve | transition |
| Answer | the recommendation, developed through structured evidence; use MECE when the source supports it | body pages |

**Assertion titles** — write the finding, not the topic:

| Weak (topic) | Strong (assertion) |
|---|---|
| "Market Overview" | "Domestic market grows 23% YoY, outpacing the global average" |
| "Challenges" | "Three structural contradictions block scaled deployment" |
| "Our Solution" | "Three-phase path: Focus, Expand, Scale" |

**Contextualize data** — pair a figure with a supported comparison when that comparison changes the decision; otherwise state its direct relevance or implication. Never invent a prior period, benchmark, competitor, target, or rank to satisfy the mode.

**Structured decomposition** — when decomposing drivers, segments, or options, make branches meaningfully distinct and cover what the decision needs. Preserve real overlap or an acknowledged gap instead of fabricating a perfect MECE partition.

---

## 2. Page-structure tendencies

- Title (the conclusion) → concise takeaway → supporting evidence beneath.
- Each body page centers on a decision-relevant question and states a clear conclusion; supporting subquestions may share the page when their relationship matters.
- Decomposition pages (driver tree / MECE breakdown / 2×2 matrix) carry the analytical load.
- Source attribution on every data page.

> Page structure is a tendency, not a coordinate template. Card / tree / chart / KPI geometry lives in [`templates/charts/`](../../templates/charts/) — adapt those skeletons, do not reinvent. This mode decides *what argument each page makes*, not pixel positions.

---

## 3. Speaker-notes register

Conclusion-driven: open each page's notes with the takeaway, then support it with a compact set of facts in flowing prose. Composed, authoritative. Pair a number with a supported comparison when it materially clarifies the takeaway ("23% — nearly double the industry's 12%"); otherwise explain its implication directly. Spell percentages as words where the spoken form reads more naturally. (Common framework: [`executor-notes.md`](../executor-notes.md) §1.)

---

## 4. Page skeleton example

```
Title:    "Retention, not acquisition, now drives growth"   ← the conclusion
Takeaway: one line — "CAC up 40% YoY, yet repurchase lifted 60% of revenue growth"
Body:     supporting arguments with contextualized data
Footer:   Source: … | page #
```
