Records are normalized under declared parse rules, not guessed through silent coercion.
Colombia rail
If the issue is already live, order matters.
Spanish-first operational triage for Colombia-facing pressure, public surface correction, chronology handling, and private evidence packaging. Structure first. Delivery second. No noise added to the record.
What stabilizes first
Public surface, chronology, conflict, package.
The first pass establishes what is breaking, where the time pressure is real, what records can be trusted, and how the next controlled packet should be formed.
BFIE layer
Bank Forensic Integrity Engine (BFIE)
BFIE is the computation-integrity layer used when financial records arrive inconsistent, incomplete, or in conflict. It keeps the handling deterministic, flags ambiguity instead of hiding it, and packages outputs for later verification.
Repeated identifiers with conflicting values are surfaced as conflicts instead of being overwritten.
Where timing cannot be lawfully completed, the ambiguity stays visible and propagates downstream.
Outputs travel with verification material so a later reviewer can re-check what was handled.
Initial intake
What enters first.
Notice type, notification date, remaining time, available records, preferred language, and immediate operational pressure. The output is a break map, an evidence order, and the next controlled step.