Deterministic
The default. Everything reproducible from the seed, so a supervisor’s team or a bank’s vendor can replay exactly what you ran.
Runs, reports and certification
A run is six steps, and it ends in a report that says what was tested and under which assumptions. The report is evidence for a request to the Central Bank and nothing more - never a substitute for its no objection.
How a run works
A run is the unit of work, and the report is the deliverable. It says what was tested — scenarios, seed, fidelity tiers, modes, rule-catalogue version — because a pass is a pass on that run.
SeedOne number fixes the synthetic population, the clock and every random decision. The same seed replays the same run.
ScenarioOrdered messages across actors, expected states at each step, and the variants to exercise. Scenarios are written in YAML and published.
TraceEvery message in and out of every actor, signed and time-stamped, in one ordered record.
LedgersPer-actor books: balances, positions, current accounts at the simulated Central Bank, card settlement.
ReconciliationThe ledgers are matched across actors. A break is a finding, not a footnote.
ReportFindings against the rule catalogue, article by article — and, where a team asks for it, in the shape of an Art. 83 dossier.
Three modes
Chaos
An administrator goes down mid-cycle, the LBTR queue stalls, a message is corrupted, a reconciliation breaks. The question is not whether your application survives, but how it degrades.
Adversarial
The synthetic population includes account takeover, mule networks, synthetic identity, card testing and social engineering at the machine. The run scores detection.