dispute-respond
Prepare a governed dispute response artifact from a linked charge receipt.
- License 许可
- MIT
- 所属仓库
- ZachDreamZ/runx
- 最近更新
- 2026-07-17
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- dispute-respond
- runx
- { "category": "payments" }
- description
- Prepare a governed dispute response artifact from a linked charge receipt.
02 资源文件 2
- 参考文档fixtures/dispute-respond-prepares-evidence.yaml1.1 KB
- 参考文档X.yaml1.4 KB
03 SKILL.md 正文
Dispute Respond
Prepare a profile-local dispute response artifact for a counterparty-initiated payment dispute.
This skill attaches the linked sealed charge receipt, prior refund receipts, and provider evidence, then selects a response posture. It does not settle the dispute or produce a rail closure receipt.
What this skill does
- Bind the dispute to a charge. Match the dispute event to the original sealed charge receipt and the provider-side charge identity.
- Collect linked receipts. Attach prior refund, verification, reversal, or recovery receipts so the response does not hide previous action.
- Classify the posture. Recommend
accept,contest,refund_already_sent,needs_more_evidence, oroperator_reviewfrom the evidence and operator posture. - Prepare the response artifact. Emit the evidence packet a rail adapter or operator can submit: receipt refs, provider evidence refs, redactions, timeline, posture, and open questions.
- Stop on ambiguity. Return
needs_agentwhen the dispute id, linked charge receipt, prior refunds, evidence posture, or submission authority is unclear.
It does not submit the response to Stripe, x402, MPP, or another rail; it does not issue a refund; and it does not mark a dispute closed.
When to use this skill
- A provider receives a chargeback, payment dispute, or counterparty complaint tied to a runx-sealed charge.
- An operator wants a defensible response packet before deciding whether to contest or accept the dispute.
- A future rail-specific dispute adapter needs the normalized evidence and posture before submission.
When not to use this skill
- To silently refund a disputed charge. Disputes and refunds are separate governed actions with separate receipts.
- To respond without a sealed original charge receipt.
- To fabricate product, delivery, identity, or consent evidence that is not already present in receipts, provider logs, or operator-supplied refs.
- To close the rail dispute. This skill prepares the artifact; a rail-specific action submits and later records closure.
Procedure
- Validate that
dispute_eventandoriginal_receipt_refare present. - Resolve the original sealed charge receipt. Confirm it matches the dispute amount, currency, provider, counterparty, operation, and settlement family when those fields are available.
- Resolve
prior_refund_receipt_refsand record whether any refund fully or partially covers the disputed amount. - Normalize provider evidence refs into a timeline: price, challenge, verification, service delivery, user consent, prior support contact, refund, and recovery events.
- Apply
operator_postureonly as a preference. Evidence still controls the final posture; a contest request without evidence returnsneeds_agent. - Redact raw secrets and personal data that do not need to be submitted.
- Emit
dispute_response,dispute_evidence,linked_receipts,posture,open_questions, and a submission readiness decision.
Edge cases and stop conditions
- Missing or unsealed original receipt: return
needs_agent; do not prepare a contest packet. - Dispute does not match the receipt: return
needs_agentwith the mismatched fields. - Prior refund exists: do not recommend a silent second refund. Set posture
refund_already_sentoroperator_reviewand cite the refund receipt. - Evidence is stale or unauthenticated: include it as low confidence or
return
needs_agentwhen it is required for the posture. - Operator wants to contest with no delivery or consent evidence: return
needs_agent; do not fabricate narrative. - PII or credentials in evidence: redact before output and list each redaction.
- Rail submission authority absent: prepare the local artifact only and
return
needs_agentfor submission.
Output schema (dispute_response_artifact)
decision: ready | needs_agent
dispute_response:
dispute_id: string
posture: accept | contest | refund_already_sent | needs_more_evidence | operator_review
amount: string | null
currency: string | null
counterparty: string | null
settlement_family: string | null
dispute_evidence:
timeline:
- at: string
kind: price | challenge | verify | delivery | refund | support | recovery | dispute
ref: string
summary: string
redactions:
- field: string
reason: string
linked_receipts:
original_charge: string
verification: [string]
refunds: [string]
recoveries: [string]
open_questions: [string]
recommendation: string
A ready decision means the artifact is complete for review or downstream rail
submission. It does not mean the dispute has been submitted or closed.
Worked example
A Stripe test-mode dispute dp_test_01 references charge receipt rcpt_charge.
The receipt proves the caller accepted challenge ch_test_01 for 0.08 USD,
verification receipt rcpt_verify sealed, and the provider delivery log ref
shows the paid result was returned. No refund receipts exist. The skill returns
decision: ready, posture contest, linked receipts, redacted evidence refs,
and a recommendation to submit the packet through the Stripe dispute adapter.
If refund receipt rcpt_refund already covers the full disputed amount, the
skill returns posture refund_already_sent, cites the refund receipt, and
warns against an untracked second refund.
Inputs
dispute_event(required): provider-initiated dispute or chargeback event.original_receipt_ref(required): linked sealed charge receipt reference.prior_refund_receipt_refs(optional): prior refund receipts.evidence_refs(optional): provider evidence references.operator_posture(optional): requested response posture.
04 同仓库更多 Skills
zapier-handoff
Validate a runx execution context and hand off a governed payload to a Zapier Catch Hook with scoped auth, idempotency, and receipt expectations.
x402-pay
Execute a governed x402 payment by delegating to the canonical spend flow with the x402 runtime path selected.
work-plan
Decompose a build objective into governed runx execution steps.
web-fetch
Fetch and extract one web source within an explicit allowlist, returning the content by digest with full provenance.
weather-forecast
Normalize provider weather evidence into an action-safe forecast packet with provenance, uncertainty, and stop conditions for downstream agents.
vuln-triage
Triage dependency or ecosystem vulnerability risk into remediation and advisory packets, grounding on verified CVE evidence when it is supplied.