Pattern 64
Spiritual authority does not excuse coercion
Recognise possible misuse of religious power without defending the institution or adjudicating theology.
Concrete takeaway
Attend to consent, threats and patterns of control rather than only theological content.
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.
| Alternative | Use when | Tradeoff or requirement |
|---|---|---|
| A · Attend to power | Religious power may be used coercively | A theological difference alone is not an abuse verdict |
| B · No spiritual pressure | The person is being pressured toward confrontation | Support must not depend on forgiveness or reconciliation |
| C · Independent destination | The implicated leader or institution is not a safe route | Use genuinely independent support options |
The problem
A disclosure about a leader may be reframed as disobedience, lack of forgiveness or a doctrinal disagreement, obscuring possible control or exploitation.
The pattern
Attend to consent, threats and patterns of control rather than only theological content. Take the disclosure seriously without declaring an investigation complete. Distinguish disagreement from coercion; a doctrinal position alone is not an automated abuse finding. Offer support independent of the implicated leader or community. Do not require confrontation, immediate forgiveness, reconciliation or return. Let the person choose whether spiritual content belongs in the conversation. Avoid speaking as God or treating the chatbot as spiritual authority.
Compare the alternatives
Recognise possible misuse of religious power without defending the institution or adjudicating theology.
A · Attend to power
Concern focuses on coercion and safety, not a forced doctrinal verdict.
B · No spiritual pressure
Support does not require reconciliation.
C · Independent destination
An implicated institution is not the only route.
Original wireframe proposals · No live controls · Grey rows represent schematic text, not loading states · Labelled placeholders are not Scripture quotations
Download this wireframe as SVGFailure modes
Defending a church before listening; telling someone to confront an alleged abuser; calling every disagreement abuse; making support conditional on forgiveness.
What to validate
Use specialist-reviewed scenarios involving forced disclosure, spiritual threats, control of relationships or finances and legitimate noncoercive disagreement. Include conflicts of interest in referrals.
Sensitive design proposal · Safeguarding 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.
- Section 4.2: Spiritual AbuseOfficial indexed excerpts reviewed on 5 October 2026; direct page access returned 403 · Institutional safeguarding guidance, not universal law or an automated abuse classifier; full-page review remains outstanding.
- Caring for women subjected to violence: health-care provider curriculumOfficial curriculum overview reviewed; full training materials not reviewed · Clinical training for human providers focused on violence against women; transfer to other populations or AI requires separate review.
Common scenarios and flows
- Respond to a sensitive disclosure with accountable support — Keep disclosure, present safety, user choice and service responsibility distinct.
Design principles in this decision
Editorial application of Missional by Design. These values frame review questions; they do not validate a pattern’s effectiveness.
- Reverence — What does this interaction ask of the person, and can they understand, decline, correct or leave it without penalty?
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:
- US · California — Enacted AI-specific law
- US · New York — Enacted AI-specific law
- US · Utah: mental-health chatbots — Enacted AI-specific law
- US · Illinois — Enacted AI-specific therapy restrictions
- US · Texas — Enacted AI-specific law; effective 1 January 2026
- US · Federal health software and data — Existing law; regulator implementation guidance
- United Kingdom — Existing law + regulator guidance; policy statement
- Australia — Existing law + regulator guidance; national policy
Use the jurisdiction decision guide to record the trigger, source version and resulting product requirement.