Skip to contentCustomer remedies
Section 15 of 22
F7 records service credits and refunds separately from incident protection. An existing product rule can authorize an automatic remedy. A discretionary incident refund requires an explicit decision by the designated budget authority, which may be a member or human role. Agents can prepare the affected-request list and execute the authorized batch.
Adopting or expanding an automatic remedy rule requires a coverage check before the DAO offers the promise. Specify eligible exposure, maximum liability or an enforceable exposure limit, funded reserve, and how each new service request increases the obligation. Reserve capacity at intake where the promise requires it. Stop accepting new covered exposure when the allowance is exhausted. Previously promised remedies remain owed under their terms.
F8 establishes the funded allocation and F9 adopts changes to the promise. A budget check only when a refund comes due would be too late. The DAO cannot cure an unfunded promise by deleting its entitlement after the failure.
| Step | Work and authority | Required outcome or failure |
|---|---|---|
| R01. Identify affected requests | Controller or incident coordinator links service records to a failure and the applicable terms. | Verify request identity and avoid disclosing customer source code. Uncertain eligibility goes to the assigned decision-maker. |
| R02. Establish remedy | Controller applies an adopted objective rule, or budget authority decides the discretionary remedy. | State eligible requests, amount, service credit or asset refund, payment method, and funding source. No decision means no discretionary award. |
| R03. Reserve | Budget controller checks coverage and records one entitlement per affected request or recipient. | A budget shortage cannot erase an automatic remedy already promised under service terms. It enters funding recovery. |
| R04. Execute | Scoped service or payment executor grants credits or transfers the authorized funds. | Partial batches record each result separately. Retry cannot repay completed entries. |
| R05. Confirm and notify | Controller verifies the credit balance or transfer and notifies the affected customer. | Unknown transactions remain unconfirmed. Disputed eligibility uses a bounded challenge. |
| R06. Reconcile | Budget controller records actual cost and closes settled entries. | Due and disputed entries persist even if the incident closes. |
A service credit pays for later service. A wallet refund returns an asset under the accepted settlement terms. They are different promises. A review-fee refund for a qualifying bounty report also needs explicit eligibility and method rather than an assumed cash refund.
Free re-review after a verifier defect remains a feature to fund and activate. Estimate the inference and infrastructure cost when authorizing those credits. Containment and restoration continue while the DAO decides any discretionary compensation.