Live progress
The engine working through your request in real time — planner, retrieval, gates — not a spinner.
One domain, shown end to end — a delivery service's refund & dispute decisions — so you can watch the engine reason, cite its sources, and escalate when it can't be sure.
A refund is the perfect stress test for grounded decisioning: it has to combine a specific order with the company's policy, get the money exactly right, refuse to be gamed, and stay explainable after the fact. Handle this reliably, and the same engine handles claims, invoices, or eligibility too.
A full walkthrough — a real customer message in, a grounded decision out, every step visible.
You send a plain customer message; the engine returns a decision tied to the exact order and policy it used — or routes it to a human.
Messages it handles
The last one never touches the model. Fraud, chargebacks, and legal threats are routed straight to a human before any AI call.
What comes back
A partial refund of $6.50 has been approved for the missing item.
Not a black box — the parts that usually stay hidden are the whole point here.
The engine working through your request in real time — planner, retrieval, gates — not a spinner.
The decision plus the exact policy and order it cites, so you can check the reasoning yourself.
Partial vs. full refunds derived from the order — never a number the model guessed.
The edge cases it catches and the abuse patterns it refuses, even when the message is convincing.
High-risk requests — fraud, legal threats — routed straight to a human, before any AI runs.
The delivery domain is just one pack. The engine is the product — bring your records and rules.