Refresh DICT infraction from BACEN
Fetches the infraction’s current record from BACEN (getInfractionReport) and projects the counterparty-determined outcome onto the local row verbatim: no computation, no interpretation. No scheduler runs this — the operator triggers it explicitly.
Parámetros de ruta
Respuesta
OK
Persisted local DICT infraction record
When the DICT 8.4 §20.3 seven-day analysis window closes (RFC 3339, UTC), counted from bacenCreationTime. Absent while BACEN's creation instant has not been observed — an unknown anchor is not a deadline, and a local clock would put the deadline later than the one BACEN counts.
"2026-06-21T12:00:00Z"
When THIS deployment first observed a notification created elsewhere (RFC 3339, UTC). Read against analysisDeadlineAt it separates an operator who did not act on a notification held for six days from a rail that discovered it minutes ago already six days old — a blocked feed or a deployment that was down. Absent for a notification this rail itself reported.
"2026-06-20T09:00:00Z"
MED tracking-graph layer of the disputed transaction (DICT 8.5 TransactionDepth): 1 for the root transaction, 2 for the second layer, and so on. Absent when BACEN has not stated a layer — notably for notifications answered before the 2026-10-26 vigencia.
x >= 11

