Pattern 37

Safety follows the conversation context

Distinguish a historical text question from an immediate personal safety concern.

Sensitive design proposal · Specialist review required

Concrete takeaway

Differentiate textual discussion, distressing personal experiences and immediate danger.

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 · Textual questionThe question is about a historical textA false crisis route disrupts legitimate study
B · Distressing beliefA personal belief is distressing or dangerousValidate distress without confirming the unsafe claim
C · Immediate dangerThere is immediate personal dangerBrief verified human-help routes take priority

The problem

Keywords about death, violence or divine commands can occur in Bible study, fiction, past experience or a current emergency. The right route depends on context.

The pattern

Differentiate textual discussion, distressing personal experiences and immediate danger. Acknowledge emotions without affirming unverified dangerous claims. Prioritise brief, locally verified human-help information for immediate danger and state actual monitoring limitations.

Compare the alternatives

Distinguish a historical text question from an immediate personal safety concern.

A · Textual question

Assistant · Example interface
Question about a biblical narrative
You are asking about violence described in this passage.
Read the literary context
Explore sourced interpretations

Historical analysis is not automatically a current emergency.

B · Distressing belief

Assistant · Example interface
This experience seems very distressing.
I cannot establish that this is a divine instruction.
Explore appropriate human support

Acknowledge distress without endorsing an unsafe claim.

C · Immediate danger

Assistant · Example interface
Germany · Local example
In immediate danger, contact emergency services: 112.
Call 112
If possible, involve a trusted person.
No live human monitoring is promised.

A local example is clearly labelled and kept brief.

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 crisis card for every historical question; validating a harmful divine command; lengthy exegesis before urgent help; invented contact information.

Bible and faith considerations

Emergency numbers differ by jurisdiction. This Germany example must be replaced with verified local guidance for each deployment.

What to validate

Have qualified reviewers assess multi-turn synthetic cases, indirect phrasing, ambiguity and false positives. Maintain contact accuracy by location and audience. Do not claim perfect detection.

Evidence status

Sensitive design proposal · Specialist review required. 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

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.

Could functionality, marketing or reasonable expectations make this a companion or mental-health service? Define the human role, health claims, escalation capability and locally verified support route before selecting dialogue UI.

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.