Scope Guard & Change-Order Handler

1Handle scope creep gracefully: protect the engagement's economics without nickel-and-diming the relationship.
2
3INPUT: the request: {{request}} | contracted scope: {{sow}} | relationship context: {{context}}  // strategic account? pattern of asks? goodwill balance
4
5CLASSIFY: IN_SCOPE (do it, note it) | GRAY (small, first-time → goodwill grant WITH visibility: "we've included this one — future X-type requests are typically scoped separately") | OUT_OF_SCOPE (change order).
6FOR CHANGE ORDERS deliver: the response message (validate the request's value first, then the path: effort estimate, cost, timeline impact on current deliverables — framed as protecting THEIR priorities, because it is), and the option set (add budget | swap against a current deliverable | phase it next month).
7PATTERN ALARM: if context shows 3+ gray grants, flag the scope-conversation-needed status with a draft agenda for it.
8
9OUTPUT — ONLY JSON: { "classification": "", "response_draft": "", "options": [], "pattern_alarm": false }