Skip to main content
The Decision Console at /decisions/:id is where compliance analysts make every non-trivial decision. Three regions: the subject of the case, the evidence collected for it, and the actions available to the reviewer.

​
Evidence sources

The evidence region composes from whatever the workflow run wrote during execution. One card per provider type — analysts see provider names and outcomes, not internal variable names.
The terminal review outcome, the reject labels (if any), the liveness + face-match indicators, the document metadata. Pivot link to the vendor’s applicant timeline.
Sanctions / PEP / watchlist / adverse-media hits with match scores and locale-prioritised sources.
Risk score, exposure signals (sanctions, mixer, darknet, stolen coins), counterparty entity name, deep-link to the provider’s investigation tool.
Registry status, address history, related parties, lawsuits / debts / protests, digital footprint.
Resolved counterpart name + document + institution from the rail’s registry (e.g. PIX DICT).
Tax-authority confirmation of identity / corporate status (e.g. Receita Federal in Brazil).
Each AI node’s structured output rendered with model name + temperature + reasoning. Reasoning is the model’s justification — useful for analyst trust, not authoritative.
Linked diagram showing which nodes the run traversed. Click any node to inspect its inputs/outputs for this run.

​
Actions available to the analyst

​
Prior cases

The right rail surfaces decisions on the same subject in the last 90 days. The lookup keys are:
  • customer_id
  • tax_id
  • wallet_address
  • counterpart_document
Pattern detection: if the same counterpart has been cleared three times in a row, the system suggests allowlisting.

​
Role gating

reported_to_regulator is never reversible — the regulator copy is canonical.