Evidence & the audit trail.
The design goal is to make a decision inspectable without inventing missing evidence. This chapter explains which fields may be present, what a bounded pack can prove, and where current coverage must be checked.
The Decision Record, field by field
- Outcome pill — approve / step-up / manual review / block / report, with semantic color
- Risk score and band where recorded; a reconstructable label is a claim to validate, not an assurance by itself
- Engine and policy versions where recorded; model version is Not applicable for rules-only flows, while the current ML chip is a stub
- Rules fired, labels, thresholds, actuals and weights only to the extent the producing engine recorded them
- Input snapshot fields such as amount, channel, geo, device and list hits where captured and permitted
- Correlation and case identifiers where propagated across the relevant services
- Timeline events for actors, time and rationale where the workflow emits them; not a universal signed history
- Evidence-pack export on supported, authorized surfaces; not every object exposes this action
The evidence pack, section by section
| Section | Contents |
|---|---|
| Identity evidence | Available KYC/KYB results, screening hits and review notes; UBO links only if supplied outside the current GATE UI |
| Risk rationale | Recorded score, rules, thresholds, features and snapshot; PULSE rationale may be partial |
| Payment trail | Recorded route path and responses; SWITCH does not imply live PSPs or complete fallback data |
| Tax snapshot | Captured VAT/GST inputs, rates and rate-basis date; filing suitability requires review |
| Case timeline | Available alerts, notes, attachments, approvals and disposition events for the selected workflow |
Exporting an evidence pack
Start from the object
Use Export evidence pack only where the authorized object surface exposes it; an absent action may require another approved collection route.
Scope it
Choose only available sections, dates and recipients. The appropriate scope is purpose- and authority-specific; more data is not automatically better.
Generate
Inspect the generated pack for expected source records, versions, timestamps, correlation IDs, manifest and hashes. Missing material remains a limitation.
Deliver
Use an approved download, dispute attachment or scoped Evidence Portal grant only after verifying authorization, expiry and access-event coverage.
Verification — trust, then check
Where implemented, a hash chain can reveal changes within the recorded chain and a manifest can verify included files. Neither proves that every event was emitted, that nothing was omitted before sealing, or that storage is universally append-only or WORM. Test regeneration and verification for the exact pack rather than promising byte-for-byte identity.
Giving an authorized reviewer access
An Evidence Portal grant can provide scoped, time-bound read access where the workflow is configured. Verify the exact packs, timelines, expiry behavior and access events before use. The current surface is not proof of complete regulator access, complete logging or legal sufficiency.
Retention rules, jurisdiction overrides, legal holds and WORM options are conditional controls. Confirm the applicable workflow, storage class, authority and event coverage. Do not claim that every deletion is prevented or logged unless the scoped implementation proves it.
Want the complete manual as a PDF? Leave us your email and we'll send it over.
Request the manual