# Remedy Value Is Not Liquidity

## Why a service credit may compensate an AI customer without funding its recovery

AI Infra Credit · September 24, 2026 · Public companion research extension

A service failure creates at least two problems: the customer loses useful work, and somebody must finance the response. A future discount may help with the first economic loss while doing little for the second cash requirement.

Our central result is not that service credits are worthless. It is that **a remedy's face amount, usable value and cash date are separate variables**. The same nominal compensation can leave the same final cash balance and still require a different amount of bridge funding.

## 1. What the public documents actually cover

| Public source | Selected mechanism | Boundary |
| --- | --- | --- |
| [CoreWeave general terms](https://docs.coreweave.com/policies/terms-of-service) | Future covered-service bill credits, subject to notice, evidence and exclusions | The page carries a June 2022 date; application to a particular Flex Order is not established |
| [CoreWeave object-storage SLA](https://docs.coreweave.com/policies/terms-of-service/coreweave-ai-object-storage-policy) | Endpoint-specific credits, no cash refund or account transfer; the highest printed tier is 100% of the affected zone's monthly bill | Storage remedy, not a GPU payment guarantee |
| [CoreWeave Spot terms](https://docs.coreweave.com/policies/spot-tos) | The general TOS SLO does not apply | Not a conclusion that every legal remedy is excluded |
| [Lambda Cloud terms](https://lambda.ai/legal/terms-of-service#cloud-terms-of-service) | Service-scoped, noncash, nontransferable credits with a default expiry; agreed Orders prevail in a conflict | Separate conditional termination provisions are not automatic outage refunds |
| [Lambda billing documentation](https://docs.lambda.ai/public-cloud/billing/) | Describes refunds as future cloud-service credits | Operational description, not a ruling on every contractual refund right |
| [Lambda 1CC support documentation](https://docs.lambda.ai/public-cloud/1-click-clusters/support/) | Four-hour initial response for Severity 1 | Initial response is not a four-hour restoration guarantee |

The structured evidence file records the distinct notice and application clocks. A deadline measured from eligibility is not silently moved to the incident date. We have no signed customer Order, actual outage claim, approved award or bank settlement. Public terms describe possible rights and procedures; they do not establish realized recovery.

A further reading distinction matters: Lambda's combined legal page includes Website, Hardware and Cloud sections. Only the Cloud section belongs in this comparison. Its conditional termination terms preserve amounts then owed; they do not quantify all remaining future commitments. Specific rights and enforceability depend on the applicable agreement and law.

## 2. Three equal remedies, two funding needs

Use hypothetical cash units, not company invoices. The customer has an incremental liquidity buffer of 20 and must pay 40 for disruption response at period 0. Its normal operating budget already supplies the cash for ordinary invoices; those invoices have **not** been prepaid to the vendor. We isolate the extra disruption and its remedy.

There are five monthly periods, 0–4, each with a gross ordinary invoice of 20. A credit of 30 is assumed approved at period 0. It can offset 10 of otherwise cash-payable charges in each of periods 1, 2 and 3, and expires before period 4. Approval, amounts, timing and expiry are assumptions—not CoreWeave or Lambda terms.

| Hypothetical remedy | Total realized benefit | End incremental liquidity | Peak additional funding gap |
| --- | ---: | ---: | ---: |
| Future credits: 10 in periods 1, 2 and 3 | 30 | 10 | 20 |
| Cash refund of 30 at period 0, after the response bill | 30 | 10 | 20 |
| Cash refund of 30 at period 0, before the response bill | 30 | 10 | 0 |

In the credit case, issuing the award adds no cash at period 0: 20 of liquidity faces a 40 payment. Future savings eventually improve the balance, but do not retroactively fund the response.

Even a refund in the same accounting period may be too late. With cost first, liquidity falls to −20 before the refund raises it to 10. With refund first, the lowest balance is 10. A period-end-only calculation misses that difference.

Negative balances describe an unfunded requirement, not an authorized overdraft or an assumed lender commitment. Financing fees and interest would add to the requirement. The comparison does not claim that either provider owes an immediate cash refund.

## 3. Redemption capacity is a financial variable

Bring the assumed expiry forward by one period: only 20 is used, 10 expires, and end incremental liquidity falls to zero. Keep future invoices but make them ineligible: all 30 expires and realized cash benefit is zero. A large face amount does not repair a mismatch between the credit and the services the customer actually needs.

The exit scenario removes future provider invoices by assumption and likewise leaves the credit unused. It does not create a termination right or erase real fees; those conditions must come from another valid agreement or settlement.

At a 12% effective annual discount rate, the three future offsets have a conditional present value of approximately **29.43955**, versus 30 for a period-0 refund. That is a discounted scenario payoff, not fair value or a market price for the claim. The funding gap remains 20 even though most of the nominal benefit survives discounting.

If the observation horizon ends before expiry, the unused balance stays separate from expired value. In the short-horizon example, 10 has been used and 20 remains outstanding. We do not declare the remainder worthless simply because the spreadsheet stops there.

## 4. Follow both sides of the same transfer

For the provider, a granted credit is not necessarily an immediate cash payment. Under the model's full, punctual invoice-settlement assumption:

    Provider net cash transfer
      = gross otherwise-payable invoices
      − credits actually applied against those invoices
      − cash refunds actually paid

Across the five periods, gross invoices total 100. A fully redeemed credit and a cash refund both reduce net provider transfers to 70, but at different dates. Do not subtract the 30 award at issuance and then subtract it again when used.

This is a cash identity, not a revenue-recognition conclusion. It also cannot be applied to invoices already paid from a prepaid wallet as though each future credit were new cash. In that case, entitlement consumption, wallet balance and settlement need a separate bridge.

An AI operator can therefore have a contract designed to protect its immediate liquidity while its customer still needs replacement capacity today. Conversely, promising immediate cash remedies can reduce the customer's gap by putting a funding obligation on the operator. Finance has moved; it has not vanished.

## 5. Design the recovery cash path, not just the percentage

The constructive question is which remedy supports continuity at an acceptable cost for both parties.

- A faster, clearly documented claim process can shorten uncertainty, although acceptance is still not settlement.
- A valid right to offset the next payable invoice can matter more for liquidity than a larger credit usable much later. Do not assume unilateral set-off where a contract restricts it.
- Cash settlement, portability or substitution can increase flexibility, but the party funding that option must be compensated and the right must actually exist.
- An agreed working-capital reserve or facility can bridge response spending to recovery. Its draw conditions, term and cost must match the remedy's dates.
- The future credit must attach to services the customer can use without economically wasteful extra purchases.

Maximum credit percentages are not substitutes for these design choices. A financing case needs the covered product, failure definition, procedural gates, eligible fee base, redemption rules and dated cash consequences. A claim against a provider is not automatically freely transferable collateral.

For AI acceleration, the point is practical: a recovery plan that preserves access to useful compute can be worth more than a larger nominal remedy that arrives in the wrong form or at the wrong time.

## Reproduce

The companion files are service-remedy-evidence.json, service-remedy-model.mjs, verify-service-remedy.mjs and service-remedy-results.json. Run:

    node verify-service-remedy.mjs

There are nine scenarios and 23 grouped checks, including credit conservation, customer/provider transfer consistency, intraperiod funding, expiry, ineligible spend, denied claims and unknown-input rejection. No external packages, accounts or network access are required.

The program takes an assumed approved remedy amount. It does not translate uptime percentages into legal entitlements, interpolate ambiguous published threshold boundaries, estimate default risk or implement actual supplier contracts. Earlier maturity, technical-cashflow and billing baselines remain unchanged. This extension is included in the public Compute Financing Research Kit.