// The Policy Engine

Five gates, one verdict.

Every event walks the same five gates, in the same order, every time. Nothing is approved that cannot be explained.

// 01 The gates
Spend authority, supplier choice, commercial terms, legal capacity, delivery commitments — five gates in all, every one of them a rule lifted from an agreement you signed, and none of them a setting someone can turn off.
The order is fixed and it is not negotiable. Every event walks the gates in the same sequence, whatever the event, whoever raised it, whatever the amount. The sequence is part of the engine’s design, not a setting.
A gate can only ever narrow. Nothing downstream can restore what an earlier gate removed — which is why an approval can always be explained backwards, gate by gate, to the clause that permitted it.

Decision · Approved  · Rejected  · Escalated  · Exception

Each gate is a rule from an agreement, not a guess from a model.

// 02 Across scenarios

The same engine, every kind of event.

One happy path is a demo. The product is the engine getting the hard ones right — and writing down why.

Warranty · SimulationEscalated

A transmission fails under warranty.

AgreementOEM warranty
SLADealer response required
AuthorityRegional manager approval
PolicyWarranty routing mandatory

The engine routes the claim to the dealer, holds the spend at the authority gate, and escalates to the named approver — with the clause attached.

Roadside · SimulationApproved

A vehicle is disabled on the shoulder.

AgreementRoadside MSA
SLADispatch within 15 min
AuthorityEmergency override
PolicyNearest certified provider

The engine invokes the emergency clause you already negotiated, dispatches the nearest certified provider, and records the override on the timeline.

// See it run

Watch the engine resolve a live event.

Watch the Policy Engine How it works