Months after launch, an auditor asks a team why their legal-research assistant runs on its current platform rather than an alternative. The engineers had picked it early because they had used it before. Which artifact, prepared during scoping, would have let them defend the choice?
Choose an answer to check it. Afterward, select any option to review its explanation.
The requirements record lists the functional behaviors, infrastructure constraints and the regulation behind each. Because it feeds the deployment decision, it shows the platform followed from requirements rather than from familiarity.
An eval suite is a real scoping output and shows the assistant behaves correctly, which makes it tempting. But it checks behavior, not placement; it says nothing about why one platform meets the constraints and another doesn't.
This documents familiarity, which is exactly the reason the auditor's question exposes. A defensible choice has to follow from requirements, not experience.
A benchmark looks like hard evidence, but a laptop measurement doesn't reflect the users' region and covers only one constraint. It can't explain the platform choice as a whole.
id q6affb18d0a