Your rules.
Traceable results.
Your calculations, checked and recorded from input to result.
Month-to-month. Built for the long term.
Version 1 · 1 September
Illustrative values, not regulatory rates.
Use the rule that applies to this record.
How the calculation is preserved
- Choose the applicable rule. Use the activity date and agreed criteria to select the relevant rule version. The illustrative rates here are fictional and do not represent a regulation.
- Calculate with code. Once the input and rate are resolved, multiplication, unit conversion, and threshold checks are deterministic steps. An AI suggestion does not replace the calculation.
- Keep the evidence. Save the inputs, source references, rule version, intermediate values, and result. A later correction creates a distinguishable result so the original remains explainable.
Make the logic
part of the system.
We work through the interpretation with the people who know the requirements.
- 1
Define the rule.
Resolve units, dates, scope, and edge cases.
- 2
Check the inputs.
Catch missing values and inconsistent records.
- 3
Calculate clearly.
Apply exact logic and retain the evidence.
- 4
Manage revisions.
Test new rules and preserve earlier results.
When requirements change
A new requirement.
A recorded update.
Monitor agreed sources for changes, then assess what applies before changing a calculation.
Who approves a rule change
Your specialist confirms interpretation and effective dates. We implement and test the agreed change.
Identify the change
Keep the source notice and flag the affected work.
Check both versions
Test new cases and compare earlier results.
Release with history
Record the effective date and retain the prior rule.
Know how the
answer was reached.
Exact calculations. Visible assumptions. A review trail.
Where do deterministic rules and AI belong?
Use code for exact arithmetic and explicit conditions. An AI step may suggest a classification or extract a value from a document. Check that suggestion against allowed values and supporting sources before using it in a calculation. Unresolved interpretations need human judgment.
Can you keep up with new regulations?
We can build monitoring for agreed sources and route relevant changes for review. Your specialist determines applicability and interpretation. We then update, test, and version the process. Monitoring does not guarantee that every change will be found or that a business is compliant.
Can we reproduce a result from before a rule changed?
The workflow can retain the original inputs, calculation version, and output so earlier results can be explained or reproduced. This is calculation history. Database point-in-time recovery is a separate capability with its own retention and infrastructure requirements.
What happens when a rule has an exception?
Route the case to our team with the relevant evidence. We work with you to resolve it, decide whether the rule needs to change, and add a test for the new condition. Keep the exception and the resulting decision connected to the record.
Bring us the logic
your team relies on.
David and the team build, operate, and improve the work with you.
From $6,000/month for one agreed area of work.