Scenario
ClearState stops decisions that shouldn't be made — before they are made, and shows exactly why.Before an action is executed, ClearState checks if it's allowed under current rules and limits. If not, it stops it and shows the exact reason.

For:
What goes wrong today
What ClearState does
or press T for tour
ClearState — Pre-execution decision layer
Showing a single scenario ·
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.
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.
Step 1 / 8
About ClearState
What ClearState is

ClearState is a pre-execution decision authorization layer. Before a regulated decision is taken, ClearState evaluates whether it can be defended — against the customer's own mandates, policies, and ownership structure — and produces a clear yes/no result with a retrievable record.

It is not a risk engine, a scoring system, or a compliance checker. The output is binary: the decision is authorized, or it is blocked with one specific reason.

What it was built for

ClearState was originally built for invoice substitution — a graph-based novation mechanic that allows a payable to be substituted before settlement, deterministically and with a verifiable authorization chain. The pre-execution authorization layer (the architecture you see in the scenarios) was developed as the gate that makes substitution safe at scale.

The same architecture — Step 1 decisionability, Step 2 rules & mandate, signed Authorization Records, deterministic replay — applies to any regulated decision where authorization must be defensible at the moment of decision rather than reconstructed afterwards.

Patent

The graph-based substitution mechanic is covered by patent application SE 2515467-5, filed December 2025 by VND Scandinavia AB (Stockholm, Sweden) through Zacco Sweden AB.

Current status
Architecture
Built and integrated for the originating substitution use case.
Patent
Filed Dec 2025 (SE 2515467-5).
Rollout
Insurer underwriting and SPV structure under review. Live operation expected within ~6 months pending insurer sign-off.
Other domains
Six application scenarios in active prospect dialogue (financial services, public sector, customs, AIFM).
Pilot offer
3-week pilot on customer's historical decisions. €7,500–15,000.
Customs case · 2026–2028 window

Regulatory trigger. The EU customs reform on low-value consignments takes effect 1 July 2026. The duty-free threshold for parcels under €150 is removed; a flat duty of €3 per tariff line is introduced as a transitional measure through 2026–2028, ahead of the EU Customs Data Hub. Parcels that previously cleared as simplified, duty-free entries now require formal declarations with payable customs debt.

What this creates. The reform reshapes the economics of high-volume cross-border e-commerce flows from non-EU marketplaces into the EU. Parcels that previously cleared duty-free now generate formal declarations and customs debt at scale. Each declaration consumes a customs broker's deferment guarantee — a finite envelope sized for current volumes, not for the volumes the reform will route through it. The capital required to scale the envelope is not on the broker's balance sheet. Without verifiable pre-submission control, the portfolio is uninsurable on commercial terms.

Architecture. The flow does not need a better tool. It needs an architecture in which control, financing, and risk transfer are held by parties priced to bear them. Six parties: marketplace operator (generates volume), data partner (structures declaration data), control layer (ClearState — authorizes each declaration before submission), customs broker (operates the flow without absorbing the customs debt on its balance sheet), financing partner (provides capital backing the deferment guarantee), credit insurer (covers credit risk against verifiable pre-submission control).

What each party gains. The marketplace operator continues to operate at scale under the new regulation. The customs broker captures volume revenue without taking proportional balance sheet risk — operator, not risk bearer. The control and data layers capture a share of the value created. The financing partner earns priced return on capital extended against an observable, capped exposure. The credit insurer earns premium on a risk that is controlled at origination — each underlying exposure gated against policy terms before it enters the book.

What the control layer adds. Without verifiable pre-submission control, this architecture does not exist. The financing partner cannot price a volume that may or may not stay within capacity. The credit insurer cannot underwrite a portfolio that cannot be reconstructed at claim time. ClearState authorizes each declaration in real time against mandate, capacity, and external coverage conditions — simultaneously, at the moment of submission — locks the rulebook by version, produces a signed Authorization Record per decision, and blocks non-compliant declarations before submission, non-overrideable.

Status. Architecture defined. Control layer built and patented (SE 2515467-5). First customs broker engaged as operating partner; operational rulebook being specified jointly. Engagement with credit insurer for policy terms and pricing is the next step, followed by financing partner engagement on guarantee capital structured against the same controlled flow. Onboarding of marketplace operator under bankable, insurable terms is targeted ahead of 1 July 2026. Replication across additional brokers and operators within the 2026–2028 window.

The Customs Deferment Gate scenario in this demo (scenario 04) shows the control layer in operation — a single declaration evaluated against mandate, capacity, and credit insurer conditions at the moment of submission.

Operating entity

VND Scandinavia AB · Stockholm, Sweden. Patent counsel: Zacco Sweden AB. Contact: info@clearstatenetwork.com.

Glossary
ClearState's internal terminology. Used here for technical audiences (architects, engineers, patent counsel). External communication uses Plain mode — switch via the Plain / Technical toggle in the top bar.
SP1Substitution Point 1
The patent-protected pre-processing layer that prepares an incoming decision request for evaluation. Normalizes inputs, applies referential substitutions, and enforces input completeness before passing the decision to REM.Patent: SE 2515467-5 covers the SP1 substitution mechanic specifically.
REMRisk & Exposure Mapping
The decisionability gate. Determines whether a decision can be taken at all — independent of whether it should be taken. Verifies input completeness, mandate presence, and explicit responsibility assignment.Plain mode label: "Decisionability". REM fails → STOP. No rules are evaluated.
RILRisk Instruction Layer
The rule and mandate evaluation layer. Forces every rule to be specified in binary, machine-readable form before activation. If a rule cannot be specified binarily, that is the customer's responsibility to resolve before RIL can run.The forcing function is itself a commercial value proposition — most policies are not yet binary.
CRSLClear Risk State Layer
The verified, signed authorization gate. The only layer that authorizes execution. Output is binary: EDGABLE or NOT EDGABLE. Produces the Authorization Record.Plain mode label: "Output". Nothing executes downstream without CRSL authorization.
Decisionability
Whether a decision can be taken at all — regardless of whether it should be taken. Decisionability fails if input is incomplete, mandate is absent, or responsibility is undefined. Distinct from "permissibility", which is a Step 2 / RIL question.
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 (function and role), an approver, and an approval date. ClearState binds every rule to a mandate at evaluation time.
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 chain is what distinguishes ClearState from a rule engine.
Deterministic replay
The property that re-evaluating the same input against the same rulebook version always produces the same output, with the same input hash. Replay produces a new event (new ID, new timestamp) but identical decision content. Distinct from LLM behavior where same input may produce different outputs across runs or model versions.
Binding reason
When a decision is NOT ALLOWED, ClearState surfaces exactly one reason — the highest-priority failed condition. Distinct from rule-engine error reports that list all failures. The single binding reason makes the block defensible and actionable.
Authorization Record
The signed, retrievable record of an ALLOWED decision. Contains decision ID, timestamp, outcome, authority, rulebook version, input hash, and accountability chain. Retrievable by reference for the retention period (typically 7 years). The block event for NOT ALLOWED is also retrievable.
EDGABLE / NOT EDGABLE
The internal binary outcome from CRSL. EDGABLE = decision authorized to execute. NOT EDGABLE = decision not authorized; execution is blocked.Plain mode labels: "ALLOWED" / "NOT ALLOWED".
Pilot
A 3-week engagement on the customer's historical decision data. Produces: (1) the RIL specification of the customer's own policies, (2) Authorization Records on historical decisions, (3) breakdown of allowed / blocked / why. Pilot fee €7 500–15 000, with 50% credited toward license if the customer continues.
Keyboard shortcuts
P toggle presenter mode
E evaluate scenario
R verify determinism (replay)
L show LLM contrast
13 switch example (Customs / Pre-Trade / LP)
G open glossary (REM / RIL / CRSL)
Esc back / close panels
? toggle this help
click anywhere to dismiss