Record the complete game accurately
Governing rules define the sport; MYOPL validates the result it stores.
MYOPL records the final points or games for each completed game or set. Its validator must recognize a legal stopping score, including sport-specific exceptions such as 7–6 in a tennis or Platform Tennis tie-break set and Badminton’s 30-point cap. It does not replace the sport’s complete governing rulebook.
Three different rule layers
| Layer | Controls | Example |
|---|---|---|
| Governing rules | How the sport is played and scored | Serve, faults, lets, interference, scoring |
| Event or local format | Which authorized match option is used | Best of three, rotation, court access |
| MYOPL result contract | Which completed values the product can store and validate | 11–9 pickleball, 7–6 tennis set, 30–29 badminton |
Current score targets
| Sport | Target | Margin or exception |
|---|---|---|
| Pickleball | 11 points | Win by 2 |
| Tennis | 6 games | Win by 2; 7–6 tie-break-set exception |
| Platform Tennis | 6 games | Win by 2; 7–6 tie-break-set exception |
| Badminton | 21 points | Win by 2; cap at 30 |
| Racquetball | 15 points | Win by 1 |
| Squash | 11 points | Win by 2 |
| Table Tennis | 11 points | Win by 2 |
Why impossible overshoots are rejected
A final score can meet a mathematical margin and still be impossible because the game should already have ended. For example, a standard first-to-11, win-by-two game cannot end 12–9: it ended when the leader first reached 11–9. Badminton cannot end 30–27 because 29–27 already created the required margin.
Validation protects data quality, but it cannot prove that the match occurred or that the listed participants are correct. Participant confirmation addresses that separate question.