READ-ONLY SYNTHETIC RECORD
Inspect how retained transaction, alert, evidence, analyst, approval and outcome records reconstruct one synthetic decision.
RA-TM-2026-00417SOURCE LANDSCAPE
The topology shows what produced each retained record, what evidence remains available, and which authority stays with the source.
TX-884102ALT-7714 / TM-204ACT-09 / APR-03 / OUT-7714TM-CONTROL-2026.03MAPPING, PROVENANCE AND AUTHORITY
Four representative mappings preserve the original value, buyer-readable meaning, formal classification, and provenance state.
txn.direction_codeCRInbound transactionRecordArc normalizedSource value retained and mapping certified
alert.rule_codeTM-204Rule signal used by the recorded alertSource factDirect source reference retained
case.dispositionCLOSED_REVIEWClosed after analyst reviewSource-system outcomeOutcome and source workflow retained
merchant.category_textSPECIALTY RETAILNormalized counterparty categoryHuman-certified interpretationSource value retained; interpretation qualified
txn.direction_code = CRalert.rule_code = TM-204case.disposition = CLOSED_REVIEWmerchant.category_text = SPECIALTY RETAILRECONSTRUCTED RECORD
Original evidence remains distinct from RecordArc interpretation.
Source or derivation: Retail Payments Core 8.4
Limitation: Establishes retained transaction context, not decision correctness.
Source or derivation: TM Engine 5.7
Limitation: The retained signal is not a rerun or validation of monitoring logic.
Source or derivation: Investigation Workflow 3.2
Limitation: Detailed analyst notes beyond the retained rationale are unavailable.
Source or derivation: Investigation Workflow 3.2
Limitation: Approval authority remains human and external to RecordArc.
Source or derivation: Investigation Workflow 3.2
Limitation: The outcome is preserved without validating that it was correct.
Source or derivation: Derived from the retained synthetic record
Limitation: Later-acquired policy context remains temporally qualified.
DECISION PROOF GRAPH
Select a node to inspect its classification, provenance, upstream evidence, downstream consequence, and limitation.
SELECTED NODE
TX-884102No upstream relationship. This is the source event.
The retained transaction establishes source context, not decision correctness.
DECISION TIMELINE
Event, decision, and capture context stay distinct. Later-acquired policy context remains outside the decision-time evidence.
TX-884102TM-204ALT-7714ACT-08ACT-09APR-03OUT-7714PROOF CONDITIONS
No composite score hides missing, weak, ambiguous, or conflicting proof.
Source identities and lineage are retained.
One interpretation and the policy-time link remain qualified.Seven events and five typed relationships preserve the recorded path.
Detailed analyst notes beyond the retained rationale are unavailable.The recorded outcome and approval remain source-controlled.
The record cannot establish decision correctness or connector readiness.Four approved synthetic source profiles
Source factSynthetic profiles do not establish connector readiness.Every displayed value carries a provenance reference
RecordArc derivedLineage is limited to the retained synthetic record.One merchant-category interpretation remains ambiguous
Human-certified interpretationCertification remains pending for the ambiguous interpretation.Policy version is recorded after the alert event
Missing/unverifiableDecision-time policy applicability cannot be established.Alert, review, approval, and outcome times retained
Source factLater-acquired context remains outside the decision-time sequence.Analyst and supervisor actions retain role identifiers
Source factThe record does not replace or validate human authority.Concise analyst rationale is present; detailed notes unavailable
Missing/unverifiableUnretained reasoning cannot be inferred.All contracted graph nodes have typed edges
RecordArc derivedRelationship completeness does not establish decision correctness.Outcome and source-system status are retained
Source-system outcomeThe source outcome is preserved, not approved by RecordArc.Seven decision-time events can be ordered
RecordArc derivedChronology is limited to retained events.Later policy record conflicts with effective-time assumption
Missing/unverifiableThe governing policy at decision time remains unverifiable.VISIBLE LIMITATIONS
TM-CONTROL-2026.03The policy version was acquired later and cannot be established as decision-time evidence.
Missing/unverifiableACT-09The concise rationale is retained, but detailed analyst notes and unrecorded investigative steps are unavailable.
Missing/unverifiableComplete recordThe displayed systems and records are synthetic and do not establish a customer connector or deployment.
Synthetic illustrationOUT-7714The recorded outcome is preserved; this proof does not establish that the decision was correct.
Missing/unverifiableComplete recordThe record demonstrates the interface and cannot establish production deployment, connector readiness, or compliance.
Synthetic illustrationREVIEWER PERSPECTIVES
Investigator, supervisor, audit and assurance, and regulatory examiner views reprioritize the same synthetic facts.
INVESTIGATOR PERSPECTIVE
The evidence record is unchanged. This view changes information priority only.
PROOF PACKAGE
Artifact selection changes the structured preview. The download serializes this same canonical synthetic record.
RA-TM-2026-00417/
Source identities and approved read-only access context.
{
"record": "RA-TM-2026-00417",
"classification": "Synthetic illustration",
"artifact": {
"id": "manifest",
"filename": "source-manifest.json",
"title": "Source manifest",
"meaning": "Source identities and approved read-only access context."
},
"content": [
{
"id": "transactions",
"name": "Transaction platform",
"product": "Retail Payments Core 8.4",
"recordIdentifier": "TX-884102",
"retainedEvidence": "Transaction value, direction, currency, and event time",
"status": "Captured",
"timestamp": "2026-03-14 09:18:04Z",
"authority": "Source facts and recorded transaction state",
"provenance": "Retail Payments Core 8.4 / TX-884102",
"classification": "Source fact"
},
{
"id": "monitoring",
"name": "Monitoring engine",
"product": "TM Engine 5.7",
"recordIdentifier": "ALT-7714 / TM-204",
"retainedEvidence": "Alert state, signal identifier, and rule output",
"status": "Captured",
"timestamp": "2026-03-14 09:18:12Z",
"authority": "Alert, signal, and recorded monitoring output",
"provenance": "TM Engine 5.7 / ALT-7714 / TM-204",
"classification": "Source fact"
},
{
"id": "workflow",
"name": "Reviewer workflow",
"product": "Investigation Workflow 3.2",
"recordIdentifier": "ACT-09 / APR-03 / OUT-7714",
"retainedEvidence": "Analyst rationale, approval, and recorded outcome",
"status": "Captured",
"timestamp": "2026-03-14 09:43:51Z",
"authority": "Human judgment, approval, and source-system outcome",
"provenance": "Investigation Workflow 3.2",
"classification": "Human-certified interpretation"
},
{
"id": "policy",
"name": "Policy repository",
"product": "Control Library 2026.03",
"recordIdentifier": "TM-CONTROL-2026.03",
"retainedEvidence": "Control identifier, version, and interpretation context",
"status": "Later acquired",
"timestamp": "2026-03-17 13:05:00Z",
"authority": "Customer-controlled governing context",
"provenance": "Control Library 2026.03",
"classification": "Missing/unverifiable"
}
]
}DEMONSTRATION BOUNDARY
This record demonstrates reconstruction and proof packaging. It does not establish connector readiness, production deployment, regulator acceptance or decision correctness.