Rules you can read
Rules are kept as configuration your team can review, rather than buried in code.
Run business rules through traceable workflows.
Use configured rules for repeatable decisions and AI where interpretation is useful. Keep the inputs, workflow steps and review decisions available for investigation. Test changes against representative cases before a controlled release.
From trigger to trace
What happens when a case runs through a workflow, and what stays available afterwards.
Built to be relied on
Workflows are for the steps that must follow your configured rules and branches every time a case runs.
Consistent results
Configured steps follow the same logic on every run, so similar cases get similar outcomes.
Clear hand-offs
When a case needs a person, the workflow waits for their decision and continues from there.
Every run on record
Each run keeps its inputs, the steps taken and the decisions made along the way.
A controlled change process
Improving a workflow should be as controlled as running it. This is the practice we recommend.
Start from a real case
Use investigated cases to show what should change and why.
Propose the change
Describe the rule change and the reason for it, for review by the rule owner.
Test on representative cases
Run the change against a set of known cases and compare the outcomes before release.
Release with approval
Apply the change once it is approved, with the new rule version recorded.
Start with the process you repeat most.
Check it on real cases, then run it with a record of every step.
Questions, answered
How DVERSI workflows are configured, run and changed.
A configured rule applies the logic you set, so the same inputs give the same result. An AI step is used where interpretation helps, such as reading a document. Both are part of the workflow, and their results are recorded.
The workflow routes it to a person. In property risk assessment, an advisor approves within their authority or refers the case to an underwriter, who approves, approves with conditions or declines.
Yes, through authorised connections that use an open standard, the Model Context Protocol (MCP). Which systems to connect, and with what access, is agreed as part of the implementation.
We recommend proposing each change with its reason, testing it against representative cases and releasing it after approval, with the new rule version recorded.
Run your rules with a record of every step.
See how a configured workflow handles property risk assessment, then discuss your own process.