Operational governance should surround the switch without competing with its authority.
Do not make the switch be everything
The transaction engine is authoritative for routing and transaction outcomes. Loading every dashboard, participant workflow, report, certificate operation, regulator view, and settlement download into that engine expands its blast radius and couples institutional change to a critical processing path.
Guevara documents another boundary: the switch remains the transaction authority and settlement source, while a surrounding control plane ingests operational facts and turns them into governed workflows.
Operating principleSeparate transaction authority from operational interpretation.
A control plane connects responsibilities
The public system map spans participant registry, liquidity thresholds, processed and failed transactions, regulator and board views, NSI and RTGS artifacts, certificate governance, monitoring history, reporting, downloads, and audit.
These are not fourteen random applications. They are responsibilities that share identity, permissions, participant context, operational history, and evidence. Their value comes from composition.
- Ingest facts from the switch and adjacent monitoring services.
- Normalize them around participant and settlement identities.
- Apply role, claim, and query boundaries to sensitive views.
- Expose different decision surfaces for operators, executives, participants, and regulators.
The boundary creates strategic leverage
A governed API layer lets the institution evolve reports and operating workflows without destabilizing the payment engine. It also makes the operating model inspectable: who may view, download, configure, or act is part of the architecture.
That is why the control plane is not “just dashboards.” It is where raw transaction activity becomes accountability, intervention, settlement evidence, and institutional memory.
Keep the transaction engine authoritative and narrow; build a governed control plane that converts its facts into safe institutional action.
Inspect the basis for this note.
These links point to public implementation evidence or authoritative documentation used for the claims above. The interpretation is mine; institutional code and ownership remain with their respective owners.
- 01Strategic overview
Guevara is publicly documented as a supervisory, settlement-intelligence, and operational-governance backend around—not instead of—the national switch.
Open source evidence - 02Fourteen operational subsystems
The repository records the platform surface from access control and liquidity through settlement artifacts, monitoring history, and audit.
Open source evidence