The ecosystem is built one layer per element, in six bands. Under them sit the eight rules everything here obeys, and they are rules rather than preferences: a run that breaks one is a broken run.
The stack is not an engineering convenience: it is the Central Bank’s diagram, made executable. A message enters through the communication-network layer, moves through stateful actors and instrument engines, settles at the simulated Central Bank, draws on support entities, and is judged the whole way down by the control plane where the Reglamento lives.
ISO 8583 for cards, ISO 20022 for transfers and reporting, file conventions for direct debit and credit, the regional standardized account number adopted in 2010, the Central Bank’s QR standard once its instructivo is published, OpenAPI for everything modern. Institution names, BINs, routing identifiers and certificates are the Lab’s own.
The 10 seconds, the 4 minutes, the 8 minutes, the windows, the RD$79,000 cap, no charge to the beneficiary, irrevocability once settled, mandatory SGPI participation, the 10-year record: each is a rule in the control plane, cited by article and dated.
A direct credit debits one simulated bank’s Central-Bank account and credits another’s in the simulated LBTR; a chargeback reverses a settled amount; a suspicious-transaction report changes a customer’s risk state.
Every run is reproducible from its seed. Chaos and adversarial modes are switched on per run and recorded in the report.
Generated per run and coherent across registry, bureaus, banks, the electronic-payment entity and the telco. No real personal data anywhere; the generator is auditable.
A trace, per-actor ledgers, cross-actor reconciliation, and the findings report the Lab already delivers.
Stub, then stateful, then behavioural — latency, load, personality, adversaries — so a counterpart can be cheap where it does not matter and exact where it does.
So the hardware on the Lab floor can join a run instead of watching one.