Evaluator Context · Controlled Data Intake
INPUT — Synthetic Transaction
The demonstrator begins with a controlled synthetic transaction representing a simulated event from Bank A, Mobile Money B or FinTech C. This stage establishes a reproducible assessment starting point and makes clear that the EOI portal is using synthetic evidence rather than production customer data.
INPUT — Synthetic Transaction
Expanded evaluator context
Professional interpretation
Purpose in the demonstrator
This stage gives the evaluator a clear view of what enters the TRUST pipeline. It defines the institution, scenario and selected synthetic transaction used for the end-to-end replay.
Operational meaning
Source systemsBank A, Mobile Money B and FinTech C simulated ecosystems.
Scenario controlNormal, new device, unusual corridor, high velocity and insufficient metadata patterns.
ReproducibilityEach selected input maps to a validated controlled artifact.
Inputs and outputs
| Element | Meaning in this demonstrator |
|---|---|
| Institution | Selected simulated payment ecosystem feeding the demonstrator. |
| Scenario | Controlled risk pattern used to challenge the trust pipeline. |
| Transaction ID | Validated synthetic reference enabling deterministic replay. |
| Output | A selected assessment path ready for normalization and downstream processing. |
Evaluator questions this page answers
- What exact transaction is being assessed?
- Is the data synthetic, controlled and reproducible?
- Which institution and scenario generated the assessment?
- How does the portal avoid implying production data use?
How this stage fits in the end-to-end chain
1. INPUTControlled synthetic transaction chosen by the evaluator.
2. NORMALIZEInstitution-specific structure converted to the canonical model.
3. FEATURESContext evidence derived from normalized metadata.
4. CONTINUATIONAI, explainability, policy and audit consume the same transaction lineage.
Governance and interpretation notes
This page is an evaluator-facing contextual explanation of the demonstrator stage. It explains the business role, the technical contribution, the governance boundary and the expected interpretation of the displayed output. It is designed to make the demonstration credible, understandable and professionally reviewable without exposing raw internal JSON on-screen.