---
skill_id: gf-pc-settlement-dispute-playbook
evaluation: free
quality: agent-decision-grade
functional: true
price_usd_full: 4.99
price_label: $4.99 / unlock
kind: good
category: Commerce
challenge: https://lvlltd.com/api/pay?skill=gf-pc-settlement-dispute-playbook
outline: https://lvlltd.com/skills/gf-pc-settlement-dispute-playbook/outline.json
runtime_after_unlock: src/index.js createSkill
standards: x402, ERC-7857
completion_pass: functional-v1
---

# Free sample — Settlement Dispute Playbook

**Skill ID:** `gf-pc-settlement-dispute-playbook`  
**Unlock:** $4.99 / unlock USDC on Base via x402  
**What you get after pay:** runnable sealed pack (`createSkill().run`) + workbook + templates  

## Summary

Structured dispute intake, evidence packs, and resolution paths for agent-mediated USDC settlements that fail, partial-pay, or double-charge.

Operational playbook for classifying settlement disputes on agent marketplaces—underpay, overpay, delayed confirm, wrong memo, and double-submit—plus evidence checklists and buyer/seller message skeletons that stay factual without promising outcomes.

## When to use

- On-chain or x402 settlement amounts do not match the sealed order total and support needs a shared classification
- Buyers report unlock stuck after payment and you must separate rail delay from non-delivery claims
- Ops wants a single evidence pack template before escalating to rail partner or counsel review

## Decision-grade outline (free)

1. Tag each open case with dispute class, order_id, settle_ref, and unlock state so triage queues stay machine-sortable
2. Assemble a minimal evidence pack: receipt fields, chain memo, unlock timestamp, and policy version shown at purchase
3. Draft buyer-facing status notes that restate what settled, what remains open, and the next checkpoint time without blame language
4. Route partial-pay and double-submit paths to distinct recomputation sheets so nets and refunds never share the same form
5. Log resolution codes and handoff owners so closed cases remain auditable for partner fee and GMV reconciliation later

## Capabilities

- Dispute class taxonomy for agent USDC settlements
- Minimal evidence-pack field checklist
- Buyer and seller status message skeletons
- Partial-pay and double-submit routing sheets
- Resolution codes for audit and GMV adjust logs

## Artifacts after unlock

- `settlement-dispute-taxonomy.md`
- `evidence-pack-checklist.json`
- `dispute-status-message-skeletons.md`
- `resolution-code-matrix.csv`

## Detailed description

Settlement Dispute Playbook is a sealed operational kit for marketplaces and agent sellers who settle digital goods and sealed unlocks in Base USDC, including flows that use x402 challenges. When amounts, memos, or confirm timing diverge from the order, support often invents ad hoc language and mixed evidence dumps. This pack locks a dispute taxonomy—underpay, overpay, delayed confirm, wrong memo, double-submit, unlock-stuck—and maps each class to a minimal evidence pack: order identifiers, settle references, unlock timestamps, and the policy version the buyer saw at purchase. Message skeletons restate facts for buyer and seller channels without assigning legal blame or inventing chargeback outcomes. Partial-pay and double-submit paths use separate recomputation sheets so refunds and net adjustments stay consistent with partner fee math. Resolution codes feed later GMV and fee reconciliation so finance is not reverse-engineering chat logs. Free outline eval is available on lvlltd.com before purchase so you can match the taxonomy to your logging stack. Full unlock settles via x402 Base USDC. The material is process and documentation craft only—not legal, financial, tax, or investment advice—and it makes no revenue, recovery-rate, or dispute-win guarantees. Adapt codes and escalation paths with your own compliance and counsel owners; keep PII out of evidence packs beyond order and settle identifiers you already control.

## Functional runtime (paid)

After verified payment the sealed pack includes:

| Path | Role |
|------|------|
| `src/index.js` | `createSkill`, `run`, `plan`, `checklist` |
| `src/runbook.js` | Outline-driven steps with done_when |
| `src/tools.js` | Tool schemas for agent registries |
| `WORKBOOK.md` | Human/operator procedure |
| `templates/` | Checklist + artifact shells |
| `schemas/output.schema.json` | Result contract |

### Agent snippet (after unlock)

```js
import { createSkill } from "./src/index.js";
const skill = createSkill({ tenantId: "ops", agentId: "buyer" });
const result = await skill.run({
  goal: "Execute Settlement Dispute Playbook for my catalog",
  context: { skill_id: "gf-pc-settlement-dispute-playbook" },
  dry_run: false,
});
// result.ok, result.steps, result.artifacts
```

## Pay path

1. Free: this sample + outline.json  
2. `GET https://lvlltd.com/api/pay?skill=gf-pc-settlement-dispute-playbook` → HTTP 402  
3. Transfer `maxAmountRequired` USDC to `payTo` on Base  
4. `POST /api/pay` with `X-PAYMENT: {"txHash":"0x…","skill":"gf-pc-settlement-dispute-playbook"}`  
5. Write `sealed_pack.files` to disk or use install-unlocked-pack.mjs  
6. Re-redeem anytime with the same verified txHash  

## Honesty

- No revenue, conversion, or uptime guarantees  
- Not legal, tax, medical, or investment advice  
- Crypto transfers are irreversible  
- Confirmed unlocks only for proof strips (/api/proof)  

*Public `/sealed/gf-pc-settlement-dispute-playbook/` is teaser-only. Full `src/` is paywalled under locked sealed delivery.*