Create Pricing-Exception Escalation Rules

#CONTEXT:
Create review-only pricing exception escalation rules from supplied approved policy. The output is a decision-support draft, not authority to approve, price, contract, communicate, or change a system.

#INPUTS:
- Approved price book, units, currency, and effective dates: [APPROVED PRICE BOOK]
- Current approved pricing exception policy and documented stop conditions: [PRICING EXCEPTION POLICY]
- Named discount approvers and their explicit limits: [DISCOUNT AUTHORITY]
- Approved tax rules and tax-review owner: [TAX RULES]
- Approved payment and quote-validity terms: [PAYMENT TERMS]
- Delivery prerequisites, capacity facts, and third-party dependencies: [DELIVERY DEPENDENCIES]
- Named escalation owners by commercial domain: [ESCALATION OWNERS]

#INSTRUCTIONS:
1. Inventory the supplied authority. Separate approved rules, conflicts, expired policy, missing owners, and Unknown items.
2. Do not invent, infer, or fabricate prices, terms, taxes, discounts, SLA commitments, approval limits, exceptions, owners, or delivery facts.
3. Missing price, tax, or payment term data must stop price generation. Mark the decision Unknown and require the missing authoritative evidence.
4. Create a decision row for requests involving price-book mismatch, discount, scope deviation, tax uncertainty, payment-term change, validity-period change, delivery dependency, or SLA request only when supplied rules support that row.
5. For each row, state the trigger, evidence required, permitted recommendation, prohibited action, named human owner, and escalation path. Unknown authority means Stop and escalate; it never means implied approval.
6. Identify overlapping or contradictory authority and keep the affected decision unresolved until named owners reconcile it.
7. Include a proposed audit record containing the request, evidence, recommendation, owner, decision, and decision date. It is a draft schema, not a live record update.
8. Add separately labeled assumptions. Each assumption must cite the supplied basis or remain Unknown; it cannot expand or replace approved authority.
9. Use only authorized quote data and authorized customer data in an approved AI workspace or approved AI vendor. Minimize the data and redact or omit unnecessary personal, sensitive, or confidential data. Follow company retention and vendor policy.
10. Do not deliver, send, publish, bill, charge, sign, accept, promise, update a live system, apply or offer a discount, waive a fee, or make a pricing decision. A named human owner must approve customer delivery, every price or discount exception, every payment or legal commitment, every external send or sending action, and every live system or record change before action.
11. This prompt is decision support, not professional financial, tax, or legal advice. A qualified financial, tax, or legal professional must verify every applicable conclusion against current authoritative sources and cite those sources before approval or use.

#RESPONSE FORMAT:
## Authority evidence and Unknowns
| Commercial domain | Supplied authority | Limit | Status | Conflict or missing evidence |
|---|---|---|---|---|

## Pricing-exception escalation decision table
| Exception trigger | Evidence required | Permitted recommendation | Prohibited action | Named human owner | Escalation path | Stop condition |
|---|---|---|---|---|---|---|

## Unresolved authority conflicts
- Conflict — affected decisions — owners needed

## Assumptions — separately labeled
- Assumption — supplied basis or Unknown — evidence needed

## Draft audit-record fields
- Request identifier
- Evidence references
- Recommendation
- Named owner and decision
- Decision date

## Human approval checklist
- Authority source and effective date verified
- Exception decision separately approved
- Customer delivery, external sending, payment, legal commitments, and live changes separately approved