## 1. Inventory policy and evidence scope

Read POL1/POL2 and five requests. List conditions, visible fields and gaps. Use uploaded material only, without inbox/Stripe reads, final approval/rejection or financial action.

Expected: A policy/request index.
Check: Every outcome is human-review material, not approval.

## 2. Check payment identity, state and minor units

Normalize paid_minor/refunded_minor with currency and raw values. Keep missing payment_id unknown; do not match by guessed name/email. List evidence needed without reading card numbers or keys.

Expected: Payment fields and gaps.
Check: 10000 cents displaysUSD100; R04 identity is not invented.

## 3. Review previous refunds before a new recommendation

Check prior refund states. R03 has succeeded 20 and R05 succeeded 100. Calculate R03 balance 80 labeled not an approved amount. Send unknown status to human review; generate no execution request.

Expected: A history/duplication table.
Check: No second refund for R05; R03 balance is not approved.

## 4. Prepare human guidance and a minimal draft

Compare all five requests to POL1/POL2. List differences/gaps without a final decision. Draft only R04’s request for order identity and usage. Do not promise refunds, send email or cancel subscriptions.

Expected: A checklist and local draft.
Check: All five are accounted for without invented orders or executed money.

## 5. Run a small read-only real review

Verify <Stripe account/support queue> and read-only capability. Review at most 3 requests using exact payment ids and necessary fields/history. Deliver a human checklist only. Do not create refunds/cancellations or send messages. Stop at unmatched identity.

Expected: A dated read-only review or blocker.
Check: Money, subscription and email state remain unchanged.

## 6. Track repeated requests and changing states

Draft a refund-review Skill with policy version, request/payment ids, currency, history, gaps, human decision and recheck. Default to read-only files. Do not convert review approval into automatic refund permission or create financial Routines.

Expected: A traceable review method.
Check: Reruns recognize the same request; humans retain financial execution.