Attach the baseline to each request
The synthetic agreed baseline says: reject a second booking for an occupied room; admins may export current bookings; refunds require staff approval. No automatic refund feature is included. These are fixture terms only.
| Request | Baseline evidence | Initial classification | Next owner/action |
|---|---|---|---|
| Two bookings confirmed for the same room/time | Conflict prevention explicitly agreed | Possible defect; reproduce against baseline | Delivery lead reviews evidence |
| Make refunds automatic | Baseline requires staff approval | New behaviour/change request | Business owner decides rule and scope |
| Please run the existing admin export | Existing permitted operation | Operational request | Authorised administrator performs it |
Do not decide by the ticket title
A ticket titled “Bug: add automatic refund” asks for behaviour excluded by the baseline. Is it a defect solely because it says bug?
Show the worked answer
No. Compare the requested behaviour with the supplied baseline. Here it is a proposed change; any actual baseline failure needs a separate defect record.
Classification does not decide fees, warranty coverage or fault liability. Those require the actual agreed support terms and evidence; the sheet helps route the request.