a number with no parts
When the score cannot be decomposed, the review becomes a conversation about trust.
Nova reads your screening profiles, rules, customers and monitoring schedules, and comes back with suggestions that carry their own evidence. It proposes; your team approves, rejects or defers. It never changes a setting on its own.
Nova reads the scan, states what it found and what it could not confirm, and proposes the next step. Nothing is applied until you say so.
Screening profiles and monitoring rules are set once, at go-live, by people who are no longer in the room. They are then left alone because nobody can prove in advance what a change would do.
When the score cannot be decomposed, the review becomes a conversation about trust.
Parameters set at go-live stay there, because changing them is unmeasured risk.
The rationale for a threshold lives in a meeting nobody minuted.
Deterministic detectors walk your screening profiles, rule firings, dispositions, customer scores and monitoring schedules. No model decides anything at this stage — these are countable facts about your own data.
A finding only matters if it is out of line. Nova compares each signal against your own baseline and against anonymised sector benchmarks, and drops the ones that are ordinary.
What was found, why it was flagged, which records prove it, how confident Nova is and what it would do to your false-positive volume. Everything an approver needs, on one card.
Nova stops here. An approval opens a draft rule or a pending setting change for your normal review path; a rejection carries its reason back so the same suggestion does not return unchanged.
No second tool and no copy-paste. Nova opens beside the case with the context already loaded, and hands the decision back to the analyst.
Every contribution shown with its module, its weight and its source.
Findings link back to the record rather than restating it.
A suggested value with the measured effect on volume, never applied on its own.
What was proposed, by whom it was accepted or rejected, and when.
Source text is retained alongside any translation.
No separate tool: the answer sits next to the decision it informs.
Approve, reject or defer — and every one of those is written down. Rejections carry the reason back to Nova so the same suggestion does not return unchanged.
No suggestions for this product right now.
An approved suggestion opens as a draft rule or a pending setting change, with the evidence attached. It still goes through your normal change process.
Nova has write access to drafts, never to live configuration.
Rejections take a short note. It is stored against the finding, so the next reviewer sees why it was turned down and Nova stops surfacing the same thing.
Feedback is the only way a suggestion engine stops being noise after the first month.
Not now is a valid answer. The finding comes back later instead of sitting in the queue as a permanent unread item.
Alert fatigue applies to suggestions too, so Nova tracks what has been seen and when.
Each analysis run, each finding it produced and each decision your team made is stored and exports with the regulator pack.
An auditor asking why a threshold moved gets the finding, the evidence, the approver and the date.
Only where you let it. Every action is a node you place yourself, and you can leave a rule in dry run indefinitely.
Confidence is a number you can branch on. Most teams auto-close above a high threshold, route the middle band to an operator and escalate the rest.
Every execution writes a log entry: which rule, which node, what it saw, what it changed, and whether it applied, simulated, skipped or failed.
Set the rule to draft and it stops immediately. The log stays, so an auditor can still read what happened while it was on.
We run it against a sample of your screening and monitoring history and walk through what it found.