Policy the operation cannot exceed
Acta decides what should happen. Writ decides whether it is allowed to happen, against limits you wrote and the model cannot change.
Acta decides what should happen. Writ decides whether it is allowed to happen.
The limit it checks is one you wrote, not the model.
The four checks between a proposal and a refund
Four values are checked before any refund runs.
Writ reads them from their source. None comes from the model.
The rule stops living in six documents
The rule stops living in six documents
Today your refund rule is copied into PDFs, macros and prompts, and the copies drift apart. In Writ it lives in one place, so changing it changes every action.
One rule, in one place, read by every action.
Outside policy does not mean escalated to you
A request your policy forbids is refused, with the alternatives the same rule allows. Only a case no rule covers reaches your helpdesk.
That’s day 45, past the 30-day refund window on this order. You can still exchange it for the same size in our returns portal, or I can put the full $80 on store credit. Which works?
Outside policy does not mean escalated to you
A request your policy forbids is refused, with the alternatives the same rule allows. Only a case no rule covers reaches your helpdesk.
A request your policy forbids is refused, with the alternatives the same rule allows.
Refused is not escalated. Only a case no rule covers reaches your helpdesk.
Why was this refund allowed?
Why this refund was allowed, 243 days later
A log records what happened. This records why it was allowed to happen — the question finance, compliance, your operators and an investigation all ask later.
Why this refund was allowed, 243 days later
A log records what happened. This records why it was allowed to happen.
Why was this refund allowed?