# Guarantees

> **Historical. This product is retired.** This page describes the earlier browser-testing product and is kept only as history. Its service, API, console and accounts are closed: do not run the install commands or call the endpoints shown here.

A claim saved so it can be checked again.

- **Outcome:** You can keep a claim and check it again later against the same approved meaning.
- **Does not do:** A guarantee is not checked on a schedule. A person, a CI job or an assistant starts each run.

A guarantee is a claim you save in the console so it can be checked again: the same sentence, held outside the code, with the plan a person approved for it. It is useful for the things that have to keep working as the app changes, such as sign-in, checkout, or one customer never seeing another's data.

## Writing a claim worth keeping

1. State an outcome, not a set of steps. "A paid customer keeps the plan they bought" travels; "call the billing endpoint" does not.
2. Keep it to one sentence. If it needs two, it is probably two claims.
3. Make it checkable on the running app, not against someone's description of their work.

> **Separation of duties.** Whoever did the work cannot approve the standard used to judge it. A person approves the plan behind every guarantee, and an API key cannot.

---

Vraelis documentation, Earlier references. https://docs.vraelis.com/guarantees