How to formulate the stages of alpha and beta testing in the TOR?

Question

Law in IT

In the software development contract, the work is divided into several parts, two of which are getting alpha and beta.
The customer's lawyer asked:

- Describe exactly what is included in alpha and beta?

We work agile, the functionality of the beta is not regulated, only the goals are registered.
How to answer the question?

Answer 1

Make a table of tested functionality for each of the stages.
Lines (Records in the 1st column, if the hierarchy/"tree" - then insert it): these are the names (list) of functionality.
And 3 columns: Alpha, Beta, Release
At the intersections: "daw" or "cross" ("must be done and tested for performance" or "no", respectively)
In Alpha - few checks, in Beta - already more, in Release - all "daws".

describe exactly what is included in alpha and beta

It looks like trolling with a provocation with a 60% probability. Ask what he means and send it to the contract, because. goals - you have registered.
Direct answer :

Achievement of the functionality determined by the goals specified in the contract.

Answer 2

If you think about it, then you should ask him what is included
Because such labels vary greatly from situation to situation
Some closed alpha is stable and details are tested in it
Some open beta crashes every other time