SYNTHETIC FLAGSHIP RECONSTRUCTION
Payment Decision Reconstruction
A read-only proof workspace for retained banking and payment transaction-decision context.
PERSISTENT RECORD SUMMARY
- Record
- RA-PAY-2026-00128
- Event
- Synthetic card-not-present payment
- Value
- USD 1,280.00
- Merchant
- Synthetic merchant MRC-204
- Recorded outcome
- Approved after step-up authentication
Review question: Can the retained authentication, authorization, risk, configuration, and exception context be reconstructed consistently?
01 / SOURCE LANDSCAPE
Owning records stay authoritative.
The proof record references retained source identities without changing source business state.
Authentication response
Source-system outcomeAuthorization response
Source-system outcomeRisk and rule context
Source factManual exception
Human-certified interpretation02 / MAPPING AND PROVENANCE
Source meaning and RecordArc structure remain distinct.
Authorized human certification governs source meaning; RecordArc-normalized values and derived relationships remain explicitly labelled.
| Source field | Proof field | Class | Authority |
|---|---|---|---|
| payment.event_id | event.identity | Source fact | Payment orchestration |
| auth.response | authentication.outcome | Source-system outcome | Authentication service |
| risk.rule_version | decisionContext.ruleVersion | RecordArc normalized | Authorized mapping |
| ops.approver_role | humanAuthority.role | Human-certified interpretation | Operations owner |
03 / RECONSTRUCTED RECORD
The retained context reconstructs consistently.
The reconstructed record matches retained source identities and chronology; it does not reproduce or validate the source decision.
{
"record": "RA-PAY-2026-00128",
"classification": "Synthetic illustration",
"recordedOutcome": "Approved after step-up authentication",
"sourceAuthority": "preserved",
"decisionExecution": "not performed",
"proofGaps": ["operations.delegation_record"]
}04 / DECISION PROOF GRAPH
Typed relationships connect evidence without flattening authority.
The graph distinguishes source events, outcomes, human interpretation, normalized values, derived relationships, and missing evidence.
- 01Payment eventlinked to next retained context
- 02Authenticationlinked to next retained context
- 03Risk contextlinked to next retained context
- 04Authorizationlinked to next retained context
- 05Human exceptionlinked to next retained context
- 06Recorded outcome
05 / PROOF CONDITIONS
Status remains dimensional and review-question specific.
No aggregate readiness percentage or universal score is produced.
Source identity
Owning systems and record identifiers are retained.
Version linkage
Rule, threshold, and configuration versions are linked.
Decision chronology
Event, decision, capture, and later-acquired times remain distinct.
Exception authority
Approval is retained; one role-delegation record is unavailable.
Outcome correctness
The recorded outcome is not rerun or validated.
06 / TEMPORAL RECORD
Event, decision, capture, and later-acquired times remain separate.
Sequence is reconstructed from retained timestamps and disclosed assumptions.
- 01Payment event captured
PAY-128 - 02Authentication challenge recorded
AUTH-44 - 03Risk response retained
RSK-771 - 04Authorization referral recorded
AUTHZ-912 - 05Operations exception approved
OPS-17 - 06Final source outcome recorded
OUT-128 - 07Later evidence capture completed
CAP-128
07 / LIMITATIONS
Proof gaps and non-goals stay visible.
The package describes what retained evidence supports and what it cannot establish.
- The scenario is synthetic and contains no customer or production data.
- RecordArc did not authenticate, authorize, score, refer, hold, release, or approve the payment.
- The underlying rule, model, and authorization logic was not re-executed.
- One delegation record is intentionally missing and remains a disclosed proof gap.
- The reconstruction does not establish legal, regulatory, audit, or operating-effectiveness sufficiency.
08 / REVIEWER PERSPECTIVES
QA and Audit are views on the same proof record.
They are not separate product modules and do not replace reviewer judgment.
QA perspective
Inspect classification completeness, chronology coverage, proof gaps, and package consistency.
Audit perspective
The retained record reconstructed consistently from the same synthetic evidence, versions, and chronology.
Control-owner perspective
Review source linkage and exceptions without asserting operating effectiveness or remediation closure.
09 / STRUCTURED PROOF PACKAGE
A deterministic synthetic package preview.
The preview keeps sources, mappings, relationships, conditions, chronology, limitations, and reviewer views inspectable together.
Review package artifact inventory
- record.json
- sources.json
- mappings.json
- proof-graph.json
- conditions.json
- timeline.json
- limitations.json