ClearState — Pre-execution decision layer

ClearState — a pre-execution decision authorization layer.

Click any scenario below to see it in action. Each shows a real decision, the rulebook that must be true, the binary output — and, when authorized, an audit-ready record that is retrievable and deterministically reproducible.

▷ Quick tour (≈3 minutes)

First time here? Take a guided walk-through. Each tour shows Step 1 decisionability, the binary output, and — for AI / financial scenarios — how an LLM would handle the same question.

Choose scenario:

Filter by sector:

Each scenario shows: the situation · the input · the rulebook · the binary output · and, when ALLOWED, the audit-ready Authorization Record. Switch to Production above to see how this works at scale.

Input

→

ClearState

→

🔒 Execution

"ClearState stops decisions that shouldn't be made — before they are made, and shows exactly why." Every decision gets a clear yes or no — and when it's no, the exact reason and what would need to change. The decision is recorded — retrievable and reproducible.

Decision

More context — buyer, trigger, personal risk, moment of pain, consequence today

1 · Input — what we have

The facts currently available

What ClearState does not do

ClearState does not figure out who is responsible for a decision. It requires that responsibility is already defined. If no one with the right authority is named for this decision, ClearState stops it — before any rule or policy is even checked.

Rulebook — what must be true to authorize this decision

Defined in advance · cited to source

Step 1 · Decisionability Can this decision be taken at all?

Not yet evaluated — input completeness, mandate presence, responsibility assignment will be checked first.

Step 2 · Rules & mandate evaluated only if Step 1 passes

3 · Output — binary result

Binding reason · referenced documents · authorization record

Click Evaluate to check the input against the rulebook.

3-week pilot — on your historical decisions

Concrete output: what would have been allowed, what would have been blocked, and why — across your actual historical decision data. Ready-to-review Authorization Records on real cases. €7 500–15 000.

What you keep after the pilot. The deterministic, machine-readable specification of your own policies, mandates and rules — yours permanently. Historical ALLOWED / NOT ALLOWED outputs and Authorization Records are yours as documented analysis.

What ClearState retains. The decision authorization pipeline — the runtime that evaluates new decisions deterministically against the specification — is licensed by ClearState. Continued deterministic authorization on future decisions requires a license.

No lock-in. No surprise. If you choose not to license, you walk away with full ownership of the specification and the historical analysis. The pipeline does not continue running.

Why this matters — personal exposure

At scale — what the production view shows

Sample stream illustrating the pattern at scale. Click any row to expand the record inline.

⌕ Retrieve a decision by ID

Paste any Decision ID, Transaction ID or Subscription ID from an Authorization Record. The same record is retrieved by reference — what an auditor, regulator, LP or appellant would do five years from now.

This sample stream illustrates how ClearState's authorization layer would look at scale. Each row is a decision evaluated against its rulebook, with a clear yes/no answer — and, when authorized, a signed record (Authorization Record) you can retrieve later. Click any row to expand the record inline.

Show decisions for:

Top binding reasons — why decisions were blocked

Decision volume by type

Live decision stream

Time	Decision ID	Type	Subject	Outcome

Glossary

A short reference. The terms below describe what ClearState does and how it differs from tools that look adjacent — audit logs, rule engines, AI, decision support, compliance software. None of those produce an authorized decision at the moment it is taken. ClearState does.

ClearState

A pre-execution decision authorization layer. It sits between a decision being proposed and that decision being executed. It evaluates — in real time, against the customer's versioned rulebook, with the named decision-maker on record — whether the decision can be taken at all. The output is binary: ALLOWED or NOT ALLOWED. The result is captured as an Authorization Record retrievable years later.A new layer. Not an audit log, not a rule engine, not AI, not decision support, not compliance software. The category did not exist as a recognized market category a year ago.

Pre-execution authorization

Authorization happens before the decision is executed — not afterwards as a logged event, not as a recommendation that a human then signs under pressure. The Authorization Record is created at the moment of decision, not reconstructed when someone asks years later.This is the core distinction from audit logs, which register events after the fact, and from AI copilots, which recommend but do not authorize.

Decisionability

Whether a decision can be taken at all — regardless of whether it should be taken. A decision fails decisionability if required input is incomplete, the mandate is absent, or no responsibility is assigned. ClearState evaluates this first. Rules are not evaluated on a decision that is not decidable.

Mandate

A defined, versioned, owned authorization to make a category of decision within stated bounds. A mandate has a name, a version, a locked-at timestamp, an owner, an approver, and an approval date. ClearState binds every rule to a mandate at evaluation time — so that the question "who was authorized to make this call" always has an answer.

Rulebook

The customer's own policies, mandates, and rules — expressed in a form ClearState can evaluate. Versioned, locked at activation, retrievable. The rulebook is the customer's; ClearState is the layer that applies it.Most organizations discover during a pilot that what they call "rules" are prose in policy documents, undocumented exceptions, and unversioned mandates. The rulebook is the artifact that did not exist before.

Authorization Record

The retrievable record of an evaluated decision. Contains decision ID, timestamp, outcome (ALLOWED or NOT ALLOWED), authority, rulebook version, and the accountability chain. Retrievable for the retention period (typically 7 years). The record for a stopped decision is also retained — there is no version of "this never happened".

Accountability chain

The retrievable record of who owns each rule, mandate, and policy that applied to a decision. Includes mandate owner and approver, policy owner and approver, active delegation level, and the named decision-maker at the moment of decision. The accountability chain is what distinguishes a ClearState record from a rule-engine output.

Binding reason

When a decision is NOT ALLOWED, ClearState surfaces exactly one reason — the highest-priority condition that did not hold. Distinct from rule-engine error reports that list every failure. The single binding reason makes the block defensible and actionable: one thing to fix, one role responsible.

Deterministic replay

Re-evaluating the same input against the same rulebook version always produces the same outcome. Replay produces a new event (new ID, new timestamp) but identical decision content. Distinct from AI behavior, where the same input may produce different outputs across runs or model versions — which is why an AI cannot be the authorizing layer for a decision that must be defensible later.

ALLOWED / NOT ALLOWED

The two possible outcomes. Binary by design. There is no "approved with conditions", no "review pending", no third state. If conditions are not satisfied, the answer is NOT ALLOWED — accompanied by the binding reason and the role required to escalate.

Pilot

A 3-week engagement on the customer's historical decision data. Produces (1) the customer's own rulebook in machine-readable form, (2) Authorization Records on historical decisions, (3) breakdown of allowed / blocked / why. The customer keeps the rulebook permanently, regardless of whether they continue. Pilot fee €7,500–15,000, with 50% credited toward license if the customer continues.

What ClearState is not

Not an audit or logging tool — those register events after they happen. Not a rule engine — a rule engine gives an answer but no record of who was authorized to make the call. Not AI or a copilot — those recommend; they do not authorize. Not a decision support tool — those inform a person who then decides under pressure. Not compliance software — that documents policy but is not active in the moment of decision.Each of those categories gives part of what is needed. None gives the decision as a complete, defensible object at the moment it is taken.