Demo state

Walk the product with seeded case files.

Switch between admissible, ambiguous, and refused examples to preview the Ovrule workspace without running a live classification request.

Built on OpenAI GPT-4o-mini · SHA-256 verifiable receipts · Open source on GitHub
Refused

What Ovrule concluded

REFUSED
Audited under: Customer Support

This action should not proceed as described. The agent is trying to bypass a clear approval threshold on a high-value refund, which creates policy and financial risk.

Risk score

84/100
LowhighHigh
Why this might be okay
  • The customer retention goal is understandable.
  • A fast response could calm the escalation.
Why this might fail
  • The refund exceeds the policy threshold by a wide margin.
  • The support agent lacks explicit authority for this class of action.
  • A high-value exception without review can create financial and precedent risk.

SAFETY

FAIL

A $5,000 unauthorized refund creates material financial and policy risk.

AUTHORIZATION

FAIL

The scenario explicitly says the agent lacks approval for refunds above the policy threshold.

CAUSAL VALIDITY

WARN

A large refund may calm the customer, but it does not justify bypassing the approval chain.

REVERSIBILITY

WARN

Refunds can sometimes be recovered, but reversal becomes difficult once funds are issued.

IMPACT SCOPE

WARN

A policy breach on a large refund can affect team norms and future exception handling.

CONSENT

PASS

The customer would accept a refund, so consent to receiving the money is not the issue.

Case core

Proposed action

Refund $5,000 to a customer after an angry escalation even though policy requires manager approval above $500.

Affected parties

Customer · customer · mediumSupport team · employee · mediumRefund policy controls · system · high

What the model used, and what it still needs

Evidence used

Escalation context

User Statement

The customer is angry and the support case has escalated.

Refund policy threshold

Policy

Refunds above $500 require explicit manager approval.

Missing information

manager approval record

Could flip decision

This would determine whether the agent can legally and operationally issue the refund.

documented loss justification

Could flip FAIL

This would show whether the refund amount is supported by the underlying harm.

Evidence still missing

Manager approval

Policy

There is no recorded approval authorizing the refund amount requested.

Damage verification

Transaction Data

The scenario does not show facts that justify a refund this large under policy.

What got recorded

Verified by Ovrule
Download the full case file

Decision history

AnnotationSupport director

2026-04-22T18:49:10.000Z

Escalate to a manager queue. The agent may prepare the refund, but it cannot authorize it.

Contestedcontest

2026-04-22T18:46:52.000Z

Support leadership says the customer relationship matters, but agrees approval still has to happen before the full refund is issued.

Createdclassifier

2026-04-22T18:42:17.208Z

Case file created from submitted scenario.

Similar past cases

Related decisions surfaced from the recent receipt register.

Not enough cases yet.