# Capability to purpose storyboard

Previous setup: Inspect a real communication specimen and identify what the feature description leaves unexplained.

| Unit | Audience arrives with | Headline / point | Substance + status | Closing beat | Audience leaves with | Connection to next | Layout/use and alternatives | Missing input / format limit |
|---|---|---|---|---|---|---|---|---|
| 1 | The reader can repeat a feature list but cannot explain the practical reason to use it. | A feature matters when it helps someone act. | The matched pairs identify why each capability matters, while the mechanism fields stop an attractive benefit label from substituting for reasoning. Fictional, not proof. | Choose one mechanism to demonstrate and test. | The reader can connect each feature to a task it may help and identify what proof is still needed. | Demonstrate the chosen mechanism, then test the proposed benefit. | S41 / capability-to-purpose; alternative S100 | HTML only; real evidence required. |

Suggested next headline: Demonstrate the chosen mechanism, then test the proposed benefit.

Copy says: A capability becomes meaningful when its mechanism and intended user benefit are explicit.

Image adds: Coupled rows keep each capability next to its own purpose and mechanism, even when stacked on a phone.

Together: The reader can connect each feature to a task it may help and identify what proof is still needed.

Medium: editable HTML diagram and typography; no generated artwork needed. Canvas: 16:9 desktop; free-height responsive document on phone. Reading order follows the relationship and ends with the implication. Qualifications stay visible; no client assets.

Selected treatment: Matched-pair family with coupled, detail-bearing rows, informed by the glossary option; quotation styling removed.

Alternative: S100 Strategy stack. Shows several capabilities supporting a shared purpose, but loses the one-to-one mapping. Use only for a genuinely collective mechanism.

Count: Repeatable capability-purpose pairs; one-to-one mapping, not a fixed number. See reuse.json for actually checked instances.