RuleState Beta

Turn your written rules into one rulebook people can review and agree on.

RuleState reads your policies and shows what they say, what is missing and where each answer came from.

A person reviews the result. Then the rulebook is frozen — and you can use it in your own systems.

See RuleState → Talk to us →

The rules are written down. The answers are not.

Who may approve a payment? Up to what amount? Who takes over above the limit?

The answers sit in several documents, written at different times. People read them differently.

And three years later, nobody can say for sure which rules applied.

RuleState

One reviewed rulebook, with the evidence.

RuleState shows:

what the policy says
what is missing
where each answer came from

A person checks the result and confirms it. Then the rulebook is frozen: that version stays as it was, and it shows who confirmed what, and when. When the policy changes, you create a new version.

Use it in your own systems, workflows or automation. You can stop here.

See RuleState →

Use cases

Three ways companies use it.

Rules used by people today.

Payment approval. Several documents say who may approve, how much, and what happens above the limit. RuleState brings those answers into one reviewed rulebook.

Building automation or AI agents.

An AI agent prepares payments or purchases. Before you let it act, you need to know exactly what your rules allow. RuleState creates that rulebook first. Use it in your own automation. Later, ClearState can check each action before it happens.

Several companies in the same transaction.

A company, a bank and an insurer may each have rules for the same transaction. The goal is to make clear which rules from each company applied at the same time. Not available yet — talk to us if this is your case.

In development

See the use cases →

ClearState

Use the rulebook when a real decision happens.

ClearState checks the facts of a real transaction against the frozen rulebook before the action goes ahead. It keeps a record of which rules and which facts applied.

ClearState does not just stop a decision. It tells you why. A rule blocks it. Something needed is still missing. Or the rulebook does not cover the case.

You know what needs attention before the action proceeds.

That is the step after RuleState — for companies that want the rulebook to control real decisions, not only describe them.

See ClearState →

Start with one real policy.

Bring the documents for one decision — for example payment approval. One person who owns the rules reviews and confirms. You get a frozen rulebook you can use.

Plan for review time. This is a real review, not a form.

See RuleState → Talk to us →

Your documents are not stored.

The people behind ClearState.

Built across financial services, financial crime, technology and commercial execution.

Magnus Högfeldt

Payments and cross-border trade

Andreas Hobbelin

Financial crime and AML

Conrad Staudt

Technology and product

Frank Ericson

Commercial and growth

Meet the team →

We built ClearState because we could not find the layer between written policy and executable rules. Document systems could store the policy. Rules engines could run the logic. What was missing was the connection between the two as policies were interpreted, implemented and changed over time. RuleState starts there. ClearState takes the next step.