A compliance score is going to be shown to a regulator, so it cannot come from a model, and it cannot come from a spreadsheet someone keeps on a laptop. It comes from a formula engine that is deterministic, evaluated safely, and configured in the product rather than written into the codebase.
A score is a field, a band is a field, a widget renders it and a wire connects it to the object. None of that is engine code, which is why a new scoring model for a new domain is a configuration change rather than a release.
Weights live on the options of the field being scored, so changing what a rating is worth is a configuration change with an audit entry, not a code change with a deployment.
Decimal precision throughout. Money and percentages do not drift the way floating point drifts.
Expressions are parsed and evaluated against a fixed function registry. There is no arbitrary execution behind a formula field.
Aggregate up a hierarchy: average, sum, count, minimum, maximum, and counts that deduplicate shared children.
A small cohort across banking, fintech, insurance, healthcare, technology, private equity and the public sector. Early access, real influence, pricing that holds.
We are pre-launch and we will not dress it up. There are no logos on this page because there are none to show. Come and try to break the chain.