UAT Scenarios

Turn what a change is meant to do, and what the code actually does, into a repeatable set of UAT artifacts that a tester can run end to end.

1. Input contract

All three are required. If any of them is missing, ask for it before doing anything else and stop:

Input	What it is	Example
Intent	One or two sentences: what the feature is for, from the business side	"Lead partners can defer an accepted offer to next year and resume it later"
Pseudo-specification	The rules in plain language: triggers, conditions, outputs, systems involved	"When status X is set in system A and the record is in state Y, call API Z; then write the result back to A"
Changes	The branch (default: current branch vs the main branch) or an explicit list of commits/files	`feature/x` vs `main`

If an example of an existing UAT artifact to use as a style example is given, match its columns, tone and level of detail.