Create a Service-Recovery Plan

#CONTEXT:
Create a draft service-recovery plan for internal human review. Use only the supplied evidence, approved policy, severity, owner authority, resolution options, and constraints. Do not execute the plan.

#INPUTS:
- Verified incident facts, timeline, and evidence references: [INCIDENT FACTS]
- Customer-reported and verified operational impact: [CUSTOMER IMPACT]
- Current applicable policy with source and effective date: [APPLICABLE POLICY]
- Human-reviewed severity level and supporting reason: [SEVERITY]
- Current owners, responsibilities, and authority: [CURRENT OWNERSHIP]
- Resolution options explicitly approved for consideration: [APPROVED RESOLUTION OPTIONS]
- Capacity, legal, financial, technical, and timing constraints: [RECOVERY CONSTRAINTS]

#INSTRUCTIONS:
1. Build a source-of-truth table separating verified facts, reported statements, conflicts, expired inputs, and Unknown items.
2. Do not invent, infer, or fabricate policy, eligibility, customer facts, outcomes, root cause, dates, capacity, approvals, fault, or liability.
3. Draft a service-recovery action plan in four lanes: containment, fact verification, approved customer-response preparation, and corrective follow-through.
4. For every proposed step, state the evidence basis, named owner, dependency, target proposed for owner approval, stop condition, and verification evidence. Do not convert a proposal into a promise.
5. Include only supplied approved resolution options. Recommend escalation when an option, owner, authority, timing, or eligibility fact is missing or conflicting.
6. Do not issue, apply, process, or promise a refund, reimbursement, credit, compensation, retention offer, discount, concession, exception, or guarantee.
7. Draft customer-response talking points only when supported by verified facts and supplied policy. Do not admit fault or liability, and do not characterize legal responsibility.
8. Do not send, publish, contact, notify, route, assign, close, resolve, or update any live ticket, account, record, or system.
9. Use only authorized support 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. A named human owner must approve every refund, credit, or compensation decision before action. A named human owner and legal counsel must approve every admission of fault or liability before action. A named human owner must approve every retention offer, discount, or policy exception before action. A named human owner must approve every external communication, sending action, or customer contact before action. A named human owner must approve every ticket, system, account, or record change or mutation before action.

#RESPONSE FORMAT:
## Evidence, conflicts, and Unknowns
| Item | Status | Supplied source | Conflict or missing evidence |
|---|---|---|---|

## Draft service-recovery action plan
| Lane | Proposed step | Evidence basis | Named owner | Dependency | Proposed target | Stop condition | Verification |
|---|---|---|---|---|---|---|---|

## Customer-response talking points for review
- Verified acknowledgment
- Supported next step
- Prohibited or unresolved statement

## Human decisions and approvals
- Decision — named owner — evidence required — approval state