Pattern 21

Narration style has provenance

Distinguish an audio edition from an adaptation or generated retelling.

Research-informed design proposal

Concrete takeaway

Identify the text basis, narrator or synthetic voice, adaptation status and relevant rights.

Choose an approach

These are editorial decision conditions to validate. Some alternatives are successive states or can be combined; they are not always exclusive choices.

AlternativeUse whenTradeoff or requirement
A · Verbatim readingVerified edition text is read verbatimThe recording must match the displayed edition
B · Dramatized editionThe edition is performed or dramatizedPerformance needs a label distinct from commentary
C · RetellingThe audio retells the passageA retelling is not the original Bible wording

The problem

Music, dramatisation or synthetic voices can change perceived meaning and authority without telling listeners what kind of content they hear.

The pattern

Identify the text basis, narrator or synthetic voice, adaptation status and relevant rights. Keep verbatim audio, dramatized edition and retelling separately selectable. Do not use voice likeness without the required permission.

Compare the alternatives

Distinguish an audio edition from an adaptation or generated retelling.

A · Verbatim reading

Audio and reading · Example interface
‹   Passage context · Schematic text   ⋯
8
9
10
Audio Bible · Verbatim edition
Source
Translation, publisher and narrator.
Listen to this edition

The audio edition and narrator are named.

B · Dramatized edition

Audio and reading · Example interface
‹   Passage context · Schematic text   ⋯
8
9
10
Dramatized audio edition
Production information
Voices, music and edition basis.
Read the production notes

Production choices are transparent.

C · Retelling

Audio and reading · Example interface
‹   Passage context · Schematic text   ⋯
8
9
10
Adapted retelling, not a verbatim Bible reading.
Basis and creator
Original passage and adaptation details.
Open the original passage

An adaptation is labelled before listening.

Original wireframe proposals · No live controls · Grey rows represent schematic text, not loading states · Labelled placeholders are not Scripture quotations

Download this wireframe as SVG

Failure modes

A generated retelling labelled Scripture; unnamed editorial additions; impersonating a trusted religious figure; unsupported claims that a voice is human.

What to validate

Can listeners identify content type and origin before playback, including on audio-only surfaces? Does switching styles preserve accurate labels?

Evidence status

Research-informed design proposal. These visual alternatives have not been tested with users in this atlas. Source findings, documented behaviour and this proposed adaptation are different kinds of evidence.

Sources and adaptation

This card is an original design synthesis. The following sources inform its content distinctions, interaction approach or review requirements; they do not validate the whole pattern.

Common scenarios and flows

Examples in use

Attributed app evidence with dates and review limits. A screenshot illustrates an implementation; it does not establish that the proposal works for every audience.

Explore the growing app-example collection

Design principles in this decision

Editorial application of Missional by Design. These values frame review questions; they do not validate a pattern’s effectiveness.

Compare alternatives using the task and evidence above. Record competing needs instead of treating a principle as an automatic verdict.

Regional applicability

Design review questions · 5 October 2026. These prompts identify possible triggers; they do not classify this pattern or every faith app as a regulated service.

Does generated text, audio or media leave the app? Decide which origin information remains understandable in playback, download and sharing, and which file metadata the applicable role requires.

Start with EU and Germany, then review the relevant market:

Use the jurisdiction decision guide to record the trigger, source version and resulting product requirement.