S
SESIM
Synthetic Shadow Mode Dashboard
TRDark
Demo Environment
Live Transaction Risk

Elderly customer transfer under suspected coercion

The transaction is legitimate. The decision is not.

Recommended Action
Soft Pause + Care Call
AUPA Risk75%

Active-call authority pressure on an elderly customer

YUDA Signal36%

Hesitation present; decision autonomy beginning to degrade

Voice Stress Trend58%

Rising confirmation latency and hesitation

Behavioral Deviation85%

New high-value beneficiary anomaly vs baseline

Score Methodology

How the Decision Integrity Score is derived. Weights below are illustrative and tuned with each institution during the pilot.

DIS = 100 − weighted( AUPA · YUDA · Stress Trend · Behavioral Deviation )
AUPA RiskHigh weight

External authority & pressure pattern

YUDA SignalHigh weight

Decision autonomy & answer consistency

Stress TrendMedium weight

Stress trajectory during confirmation

Behavioral DeviationMedium weight

Beneficiary / timing anomaly vs baseline

Decision Timeline
10:42:11
Transfer initiated

Clean fraud profile; known device and normal login.

10:42:27
Call pressure detected

Customer remains on active call during transfer flow.

10:42:43
Decision drift rises

Hesitation and contradiction in confirmation answers.

10:43:02
Intervention recommended

Soft Pause + Customer-Care Callback before irreversible loss.

Explainability Panel
Engine Reason Codes
authority_pressurestress_risingbehavioral_anomaly
Customer appears legitimate; actor risk is low.
Decision-making context shows coercion pressure.
Voice stress trend rose during beneficiary confirmation.
Recommended intervention avoids exposing the customer to a coercer.
Policy Note

Use a non-blocking reconfirmation first. If pressure persists, silently escalate to fraud care operations.

Intervention Ladder

Action escalates with decision risk — friction stays proportional and hard blocks are the last resort.

70–100
Allow + Observe

Shadow-mode log only, no customer friction.

50–69
Soft Pause + Reconfirm

SMS / in-app reconfirmation on a safer channel.

30–49
Soft Pause + Care Call

Customer-care callback on a safe channel.

Active tier for this scenario
10–29
Temporary Hold

Hold transfer and notify a trusted contact.

0–9
Hard Block + Escalate

Block and route to fraud operations.

Pilot Report Preview
Example output a risk team would receive after a shadow-mode evaluation.

Synthetic demo only. No real customer data is used in this dashboard preview.

Open PDF-Ready One-Pager
Finding

Coercion-like decision risk detected despite clean fraud status.

False-positive review

Hard block not recommended; start with soft pause and safer-channel reconfirmation.

Next step

Review 3-5 anonymized or synthetic journeys with fraud, compliance, and customer care teams.

Pilot Output
Shadow-mode report for risk, compliance, and customer care teams.
Request Shadow-Mode Pilot