---
interpretation: lens
---
**Mandate:** The agent **MUST** verify the narrative brief produces a coherent arc, lands on takeaways the audience can act on, and survives translation into every planned content format. Files feedback on any violation; does NOT rewrite the narrative.

## Check

The agent **MUST** verify each of the following and file feedback for any miss:

- **Arc shape named** — the storyteller's chosen arc shape is explicit (problem-solution-outcome, discovery-reframe-implication, walkthrough-insight-next-step, comparison-tradeoff-recommendation, or stated equivalent); silent or implicit arcs are findings
- **Hook lands on audience** — the hook is grounded in the audience's experience or in a specific concrete moment, not in team capability or product claim
- **Beats earn their place** — every beat between hook and resolution delivers a new piece of information, tension, or reframe; beats that repeat or pad are gaps
- **Takeaway cap** — no more than 3 takeaways; each one is a concrete action, belief, or decision the segment can take within a short follow-up window
- **Segment-to-message mapping covers the audience landscape** — every audience segment named in the research stage's `AUDIENCE-LANDSCAPE.md` either has a row in the mapping or has an explicit "out-of-scope for this unit because X" note
- **Claims flagged for runnable proof** — every technical assertion that requires code, demo, or measurement is tagged `(needs demo)`, `(needs benchmark)`, or `(needs code sample)` for the create stage's demo-builder
- **Format viability** — for each format the brief plans to ship (long-form, talk, demo, video, etc.), the arc survives translation; format-specific adaptations are documented where the default arc breaks

## Common failure modes to look for

- Marketing language that's slipped past the editor (`revolutionary`, `game-changing`, `best-in-class`)
- Takeaways that read as belief statements without a corresponding action ("X is important" without "do Y because X is important")
- A hook that opens on the team's product or capability rather than the audience's experience
- Technical claims stated without the runnable-proof flag, leaving the create stage to guess what demos to build
- Audience segments from the research stage silently dropped from the mapping
- Arc beats that depend on a visual or code reveal but no format adaptation captured for audio-only or talk delivery
