Pattern 36

Support without spiritual pressure

Respond to difficult topics with choice, humility and appropriate support.

Sensitive design proposal · Specialist review required

Concrete takeaway

Acknowledge the concern without imposing an explanation.

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 · Acknowledge painA disclosure is painfulListening must not impose a spiritual explanation
B · Preserve controlThe person needs control over disclosureSupport should not depend on more personal detail
C · Repeated certainty seekingRepeated certainty seeking is distressingSpecialist review is required and ordinary doubt must remain distinct

The problem

Grief, abuse, guilt or repeated moral reassurance can trigger harmful spiritual explanations or confident clinical assumptions.

The pattern

Acknowledge the concern without imposing an explanation. Make Scripture and prayer optional. Preserve control after religious harm, offer independent help and avoid promises of absolute moral certainty. Repeated reassurance requires specialist-informed handling rather than diagnosis from a chat.

Compare the alternatives

Respond to difficult topics with choice, humility and appropriate support.

A · Acknowledge pain

Assistant · Example interface
This sounds painful. You do not have to find an explanation right now.
Talk without a Bible passage
Choose a passage
Pause

A spiritual interpretation is not imposed.

B · Preserve control

Assistant · Example interface
You can decide what you want to share.
Independent support options
Help me organise my thoughts
End the conversation

Support is independent and disclosure is voluntary.

C · Repeated certainty seeking

Assistant · Example interface
We are returning to the same distressing question.
I cannot promise absolute moral certainty.
Talk about the distress
Explore qualified support

Illustrative wording requires specialist review.

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

Explaining loss as God’s plan; pressuring reconciliation with an abusive community; pathologising identity or doubt; endless certainty promises.

Bible and faith considerations

These are illustrative routing and dialogue proposals, not treatment instructions. Do not diagnose OCD, conduct exposure therapy or classify an identity as illness.

What to validate

Use expert-reviewed synthetic multi-turn cases covering grief, religious harm, shame, identity and reassurance. Evaluate correction, refusal and long-term repetition, not only the first answer.

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.