First-depth synthetic demo

AML Alert Decision Replay

Replay why an AML alert was closed, escalated, or overridden by tracing evidence, policy versions, AI/rule influence, analyst action, approval history, and audit-ready evidence output.

Head of AML OperationsCompliance AssuranceInternal Audit

Back to Decision Proof Lab Book Private Demo

Decision Proof Layer

Evidence context5 synthetic records

Policy and obligationHigh-risk corridor review

Model or rule traceSynthetic AML Risk Model v2.3

Human approvalSenior analyst

Proof readinessReady, weak, and missing

Replay and outputAnalyst review required

Synthetic examples only. No customer data.

Read-only. No writeback or case mutation.

No production or autonomous decisioning.

No auto-disposition or source-system replacement.

No filing automation, compliance guarantee, or regulator approval.

Humans retain ownership and authorization.

Synthetic scenario

Synthetic decision scenario

AML operations and compliance assurance need to prove why the alert moved to enhanced review and what evidence supported the decision. The scenario is generic and uses synthetic data only.

Synthetic AML alert intake

Source event

Unusual cross-border transaction pattern created an AML alert in a synthetic alert queue.

Escalation rationale

Decision being proved

Why the alert was escalated for enhanced review instead of closed.

Role-based ownership

Decision owner

AML operations and compliance assurance.

Synthetic outcome

Outcome

Escalated for enhanced review with a synthetic proof pack prepared.

Synthetic assumptions

Generic synthetic queue metadata is used instead of real alert identifiers.
Counterparty, geography, and customer-risk references are abstract categories.
The source event is read-only and remains separate from source case systems.

Capture

Evidence and source context

Synthetic alert, transaction-pattern, risk, and reviewer context is shown without real customers, accounts, geography, or production connectors.

Alert context

Synthetic alert event

Synthetic alert category, queue label, priority, and review trigger.

Synthetic alert queue snapshot

Captured as source-context metadata with no live connector.

Synthetic evidence

Risk context

Customer risk profile

Synthetic risk-tier context and relevant profile attributes.

Generic risk profile summary

Linked to the decision record as a synthetic evidence input.

Synthetic evidence

Pattern summary

Transaction pattern summary

Synthetic transaction indicators represented as generic categories.

Synthetic transaction-pattern rollup

Preserves the category-level reason the alert required review.

Synthetic evidence

Context indicators

Counterparty and geography indicators

Generic counterparty type and region-category indicators without real geography.

Synthetic indicator bundle

Shows how contextual indicators are attached without real data.

Synthetic evidence

Human rationale

Analyst notes

Generic review rationale written by a synthetic analyst role.

Read-only rationale entry

Captured as rendered text in the replay record.

Synthetic evidence

Review history

Prior review context

Synthetic prior review context showing whether similar alerts were reviewed.

Synthetic review-context snapshot

Links historical context without exposing real case history.

Synthetic evidence

Govern

Policy and obligation trace

Synthetic policy versions show how criteria, evidence standards, and escalation conditions can be attached to a replayable decision without making a compliance guarantee.

AML-Triage-vSynthetic-03

AML Escalation Policy v3.2

Enhanced review obligation

Alert triage criteria

Decision criteria

Determine whether evidence supports closure, escalation, or further review.

Required evidence

Alert context, transaction pattern, customer-risk context, and analyst rationale.

Escalation condition

Enhanced review is required when risk context and pattern indicators remain unresolved.

Review standard

Document rationale, supporting evidence, and review owner before final disposition.

Escalation-Threshold-vSynthetic-02

Enhanced Review Obligation

Second-line review

Escalation threshold

Decision criteria

Identify when a second review is required before closure or escalation.

Required evidence

Risk-tier context, pattern summary, and any override rationale.

Escalation condition

Escalate when evidence does not support immediate closure.

Review standard

Preserve reviewer approval, rationale, and policy version in the decision record.

Review-Control-vSynthetic-01

Alert Closure Evidence Standard

Evidence sufficiency

Review documentation control

Decision criteria

Require rationale, supporting evidence, and approval trace for disposition.

Required evidence

Decision record, evidence lineage, approval chain, and replay timeline.

Escalation condition

If required evidence is incomplete, route for enhanced review.

Review standard

Create an audit-ready evidence pack from rendered synthetic content only.

Govern

AI/rule trace

AI/rule trace is synthetic and illustrative. No live model inference is performed.

No AI runtime. No production decisioning.

This section is static explanatory content. It does not run AI, score live records, or make a production decision.

Synthetic AML Risk Model v2.3

Synthetic signals

Synthetic alert risk score
Synthetic rule trigger category
Synthetic feature/rationale summary
Synthetic model version label

Human review required

Feature group examples

Pattern categoryRisk context categoryReview history categoryQueue priority category

A human reviewer must inspect evidence and record rationale before escalation.

Human accountability

Approval and override chain

Role-based review is captured without real names. The page shows who reviewed the synthetic decision, what action they took, and whether an override was recorded.

Review step 01

Analyst review

Evaluates evidence and records disposition rationale.

Rationale

Pattern and risk context require enhanced review before closure.

No override recorded

Review step 02

Senior AML reviewer

Reviews rationale and supporting evidence.

Rationale

Escalation is supported by unresolved risk and policy criteria.

No override recorded

Review step 03

Compliance assurance sample

Samples the decision for evidence sufficiency and control trace.

Rationale

Evidence pack contains policy, rationale, approval, and replay markers.

Assurance sample only

Review step 04

Final escalation decision

Records enhanced review outcome and evidence pack generation.

Rationale

Decision is defensible because evidence, policy, trace, and approvals are linked.

Escalated for enhanced review

Assess

Proof readiness and proof gaps

The synthetic record is replay-ready while making its intentionally absent production evidence explicit.

Ready

Source evidence context

5 synthetic evidence records retain source and decision-time context.

Ready

Policy and trace versions

2 governing control record and Synthetic AML Risk Model v2.3 are attached to the replay.

Ready

Human accountability

Senior analyst remains the recorded decision checkpoint.

Weak

Prior-review rationale depth

The synthetic prior-review context is summarized rather than sourced from a complete case history.

Missing

Production source verification

Intentionally absent from the public lab because it contains no live connectors or customer data.

Prove

Replay timeline

The replay reconstructs the synthetic alert decision from source event through proof-pack output. It does not operate a case workflow.

Alert generated

Synthetic AML alert intake is captured with source context.

Source event

Evidence attached

Alert context, pattern summary, and risk context are linked.

Evidence lineage

Policy matched

Alert triage and escalation criteria are associated with the review.

Policy trace

Rule/AI trace recorded

Synthetic score, rule trigger, and rationale summary are preserved where applicable.

AI/rule trace

Analyst rationale captured

Analyst review records why enhanced review is required.

Human rationale

Reviewer approval added

Senior review confirms the escalation decision is supported.

Approval chain

Escalation decision recorded

The final synthetic decision is recorded with approval context.

Decision record

Evidence pack generated

A synthetic audit-ready evidence pack is assembled from the replay record.

Evidence pack

Evidence output

Evidence pack output

The page shows what a static synthetic evidence pack can contain. The JSON control creates a deterministic local file in this browser; it makes no backend call and performs no regulatory submission.

Decision record

A rendered record of the synthetic alert outcome and decision owner.

Evidence lineage

Source-context links showing what evidence supported escalation.

Policy trace

Policy versions, criteria, and review standard attached to the decision.

AI/rule trace

Synthetic signal, score placeholder, and rule rationale where applicable.

Approval chain

Role-based review sequence, rationale, and override status.

Replay timeline

Ordered reconstruction of how the synthetic decision happened.

Audit summary

Concise summary for QA, assurance, and internal audit review.

Buyer value

What this proves

The walkthrough shows how evidence, governing context, model and rule influence, and human rationale can support replay of an AML alert decision.

Why the AML decision happened

The page ties the escalation decision to evidence, policy criteria, and human rationale.

What evidence supported escalation

Evidence cards show which context was available at the time of review.

Which policy version applied

Policy trace cards preserve version labels and review standards.

Whether AI/rules influenced the decision

Synthetic signal and rule-trace content explains influence without running a model.

Who approved the decision

Role-based approval history records accountability without real names.

Whether it can be replayed for audit

The timeline and evidence pack show the decision can be reconstructed and defended.

Doctrine boundary

What this does not prove

The synthetic walkthrough demonstrates proof structure, not operational authority, customer deployment, or a regulated outcome.

AML disposition

The walkthrough does not close, escalate, or otherwise dispose of an AML alert.

Production operation

The public walkthrough uses synthetic content and does not connect to or operate a production system.

Decision authority

RecordArc does not approve, reject, clear, escalate, or dispose of the underlying decision.

Source-system control

The walkthrough performs no writeback, case mutation, workflow execution, or source-system replacement.

Compliance outcome

The proof record does not guarantee compliance or imply regulator approval.

Customer implementation

The synthetic example is not evidence of customer data, deployment, adoption, or production readiness.

More synthetic workflows

Back to Decision Proof Lab

Synthetic walkthrough