Guarantees
The one sentence about your software that has to stay true.
OutcomeYou can write a guarantee Vraelis will hold the work to.
A guarantee is a named outcome the company depends on, written as one sentence. It is held outside the code, so a change that quietly drops it is caught rather than shipped.
Writing a good guarantee
- State an outcome, not a set of steps. "A paid customer keeps the plan they bought" travels; "call the billing endpoint" does not.
- Keep it to one sentence. If it needs two, it is probably two guarantees.
- Make it checkable against the running software, not against the agent's description of its work.
What Vraelis does with it
Vraelis crawls the deployment you connected, derives the requirements the guarantee implies and the browser journeys that would prove them, and shows you that plan. Nothing runs until you approve it, and the paid run consumes the plan exactly as approved.
Separation of dutiesThe agent that performs the work cannot approve the standard used to judge it. A person approves the guarantee and the plan that proves it.