Pattern 63
Take a disclosure seriously without requiring a label
Support safety and choice even when the person is unsure whether an experience was abuse.
Concrete takeaway
Listen without blame or pressure for a detailed account.
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 · Uncertain experience | The person is unsure how to name an experience | Support must not depend on accepting an abuse label |
| B · Present safety | It may be unsafe to continue the conversation | Avoid collecting unnecessary identifying detail |
| C · Independent support | The person wants help beyond the relationship | Check independence and safe contact methods |
The problem
A user may describe fear, coercion, control or harm without calling it abuse. Demanding proof or delivering a confident verdict can both undermine support.
The pattern
Listen without blame or pressure for a detailed account. Acknowledge concerning behaviour and ask what the person needs now. Clarify immediate safety where relevant; support does not depend on agreement with an abuse label. Offer independent specialist help and user-led next steps rather than investigating or prescribing confrontation. Include sexual, physical, emotional, financial, technological and spiritual contexts. Do not route automatically to a partner, parent or religious leader who may be implicated. Protect disclosure and explain real data handling.
Compare the alternatives
Support safety and choice even when the person is unsure whether an experience was abuse.
A · Uncertain experience
The person can explore concern without adopting a label.
B · Present safety
Safety questions do not become a demand for the full story.
C · Independent support
Support can sit outside the relationship or institution involved.
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
Minimising harm; interrogating for proof; declaring facts conclusively; automatic reconciliation advice; sharing the account with the person or institution involved.
What to validate
Safeguarding reviewers and survivor-informed research should cover uncertainty, coercive control, sexual assault, historical experiences, unsafe households and institutional conflicts.
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.
- 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.
- Technology-Facilitated AbuseOfficial resource reviewed on 5 October 2026 · US service context; device-specific advice needs specialist review.
- Concept of Trauma and Guidance for a Trauma-Informed ApproachPrinciples checked; full PDF access limited · An organisational approach, not a validated AI script. The full guide needs deeper review before claiming implementation fidelity.
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.