RecordArc public release R21
Skip to main content

DECISION PROOF LAB

Inspect one transaction decision from source event to reviewable proof.

Follow a synthetic banking and payment decision across retained source records, mappings, ordered context, chronology, human authority, proof conditions, limitations, and reviewer perspectives.

The Lab is synthetic, read-only, and off-path. Source systems and authorized people remain authoritative.

Synthetic public demonstrationRead-only and off-pathSource authority preserved

CONTROLLED PROOF BOUNDARY

  1. 01
    Retained source contextOwning systems preserve recorded state
  2. 02
    Decision Proof LayerRead-only reconstruction and explicit limitations
  3. 03
    Authorized human reviewJudgment and approval remain human
No source decision rerunNo decision execution

FOLLOW THE PROOF

Six inspection steps keep source authority and limitations visible.

Each link opens the matching section of the complete payment reconstruction.

  1. 01

    Sources and mappings

    Inspect owning records, source identities, classifications, and certified mappings.

    Inspect sources and mappings
  2. 02

    Reconstructed record

    See the connected proof record without rerunning the underlying decision.

    Inspect reconstructed record
  3. 03

    Ordered context and provenance

    Follow retained nodes in chronology while preserving source identity, classification, and limitations.

    Inspect ordered context and provenance
  4. 04

    Proof conditions

    Inspect what is Ready, Weak, Missing, Ambiguous, or Conflicting.

    Inspect proof conditions
  5. 05

    Timeline and limitations

    Separate event, decision, capture, and later-acquired context.

    Inspect timeline and limitations
  6. 06

    Reviewer views and package

    Examine QA, Audit, control-owner perspectives, and structured package contents.

    Inspect reviewer views and package

FLAGSHIP / BANKING AND PAYMENT DECISIONS

Payment and fraud-risk decisions, reconstructed as reviewable proof.

The flagship connects retained payment, authentication, authorization, risk, configuration, human-exception, and recorded-outcome evidence. Real time describes the source payment decision environment; RecordArc remains retrospective, read-only, and off-path.

01

PAYMENT AND FRAUD-RISK DECISION CONTEXT

Payment Decision Reconstruction

One controlled record shows the full retained proof path.

Payment eventAuthentication and authorizationRisk and configuration contextHuman exception authorityRecorded source outcomeExplicit proof gaps
Current flagship synthetic proof depthSynthetic illustrationUnder development
Open Full Payment Reconstruction

WHAT THIS SYNTHETIC DEMONSTRATION SHOWS

Retained context can be inspected as a bounded proof reconstruction.

Retained synthetic context can be connected into traceable lineage, chronology, classifications, proof conditions, and explicit limitations.

WHAT THIS DOES NOT ESTABLISH

Demonstration depth is not production proof.

It does not establish decision correctness, operating effectiveness, legal or regulatory sufficiency, deployment readiness, or third-party acceptance.

FLAGSHIP PACKAGE AUTHORITY

Structured preview only

A structured synthetic package preview is inspectable. No download is offered because approved canonical proof-package authority does not yet exist for the flagship scenario.

AML PACKAGE AUTHORITY

Six-artifact deterministic preview

Six canonical synthetic artifacts form a deterministic structured preview. No local download is currently offered.

SEPARATE EXAMPLE / FINANCIAL CRIME & COMPLIANCE

AML transaction-monitoring alert decision proof.

This separate example follows an AML monitoring signal, alert, investigation evidence, analyst rationale, approval, and recorded outcome. It demonstrates proof reconstruction for AML suspicious-activity monitoring. It is distinct from the flagship payment and fraud-risk decision path.

02

FINANCIAL CRIME & COMPLIANCE / AML

Synthetic AML Transaction-Monitoring Alert Review

Public experience
Available synthetic example
Enterprise capability
Under development

Six canonical synthetic artifacts form a deterministic structured preview. No local download is currently offered.

View AML Example Overview

SCENARIO MATURITY

Public demonstration depth and enterprise availability are separate.

Each route states what can be inspected publicly and whether the corresponding enterprise capability is under development, intended, conceptual, or not currently offered.

BANKING AND PAYMENT DECISIONS

Payment Decision Reconstruction

Public experience
Full synthetic reconstruction
Enterprise status
Under development

FINANCIAL CRIME & COMPLIANCE / AML

AML Alert Decision Reconstruction

Public experience
Separate synthetic example with a six-artifact deterministic package preview
Enterprise status
Under development

FINANCIAL CRIME & COMPLIANCE

KYC/KYB Onboarding Decision Proof

Public experience
Conceptual preview
Enterprise status
Intended enterprise capability

FINANCIAL CRIME & COMPLIANCE

Sanctions Review Decision Proof

Public experience
Conceptual preview
Enterprise status
Intended enterprise capability

FINANCIAL CRIME & COMPLIANCE

SAR/STR Review Decision Proof

Public experience
Static applicability note
Enterprise status
Not currently offered

ADJACENT APPLICATION

Credit Decision Proof

Public experience
Static applicability note
Enterprise status
Not currently offered

REVIEWER PERSPECTIVE

The same record, inspected through assurance questions.

QA and Audit are reviewer perspectives on the same proof record. They are not separate application modules and do not establish operating effectiveness.

  • Are classifications complete and traceable?
  • Can chronology be reconstructed?
  • Are source and human authority preserved?
  • Are missing and ambiguous elements visible?
  • Is the structured package internally consistent?
Inspect QA and Audit reviewer perspectives

NEXT REVIEW POINT

Inspect the flagship record at full depth.

Follow retained sources, mappings, ordered context, proof conditions, chronology, limitations, reviewer perspectives, and the structured package preview.