RISK-1: The bureau feed can again make scores stale
This page shows how the risk works, what it would cost, and what your company decided.
Owner: Erik Lindqvist, Head of Credit Risk. Next check: 11 Nov 2026.
How the risk works
When a feed batch from the bureau is empty, the bureau agent returns stale scores. Stale scores raise the risk score, and a higher risk score makes a denial more likely.
Auga is very sure of each step. See the findings.
What it would cost
If nothing changes, the loss is about €983,804 a day. The prices are illustrative, so do not quote this figure. See the Value sheet.
Decision and control
| Now | |
|---|---|
| Decision | Reduce the risk |
| Control | The Bureau agent's data handling is held at a lower stage. |
| Planned change | Return the bureau feed to 3.2 |
| Decided by | Erik Lindqvist, on 4 Nov 2026 |
When Auga opens an incident
If the share of failed runs from the bureau agent is above 30% in one period, Auga opens an incident. Auga also checks on 11 Nov 2026 whether its prediction still holds: an empty feed batch makes scores stale one period later.
History
| When | What happened | Who |
|---|---|---|
| 4 Nov 2026 15:30 | The risk was added after incident INC-1. | Erik Lindqvist |
| 4 Nov 2026 15:31 | Erik Lindqvist decided to reduce the risk. | Erik Lindqvist |
This page is a sketch. Nothing on it is built, and all names and figures are invented.
Send evidence
Auga puts the evidence about this risk into one signed package. A receiver can check the package without Auga.
The package holds
- What happened, with the figures.
- The affected runs, under pseudonyms.
- The cause chain, with the grade of each finding.
- Who decided what, and when.
- The stages before and after.
- What Auga cannot say.
Receivers
The GRC system, the ticketing system, the model provider, or a supervisor. See the receivers in Connections.
Now
This prototype sends nothing. Each package that Auga sends would be recorded in the ledger.