Versions and audit trail
Every decision knows who made it.
When the auditor, a customer disputing a decision or the regulator asks about it, the answer is a query — not a reconstruction of the case.
The record of each execution keeps the input, the output, the rule that matched, the timing and the exact policy version — frozen at that moment. Publishing a new version doesn't rewrite the past.
That's what answers the auditor, the customer who disputes a decision and the regulator, without spinning up a project.
// an example of a stored decision { "outcome": "APROVA", "rule": 4, "policyVersion": "2.4.0", "decidedAt": "2026-09-20T14:22:06Z", "input": { "score": 742, "comprom": 0.31 }, "timings": { "totalMs": 352, "fetchMs": 310, "dmnMs": 9 }, "trace": [ /* the row that matched and why */ ], "traceId": "9f3ac41b…" }
What is stored
Every execution, in full
- Input
- What your system sent and, separately, the complete input after the pipeline added the fields from its sources.
- Output
- The outcome and everything that came with it: limit, queue, reason.
- Trace
- The path of the DMN table's evaluation — which rule matched and with which values.
- Version
- The identifier and number of the policy version that decided.
- Timing
- Total, data fetching and rule execution, kept apart — so you know where the time went.
Versions
The policy's history is the operation's history
Each version has its publication date. To know what applied in March, you don't have to ask anyone: it's the version published in March.
policy credito-pf · versions
| 2.5.0 | ana.souza | draft | rule 06 limit from 12× to 10× income | — |
| 2.4.0 | ana.souza | published | rule 05 flags income < 3,000 for review | Sep 20 |
| 2.3.1 | carlos.m | archived | fixes the band in rule 02 | Sep 18 |
| 2.3.0 | rita.f | archived | new rule 06 for high income | Sep 2 |
An illustrative policy history.