make it right.
rdrs compares what was promised with what was delivered, from signed receipts, and returns a public verdict. It decides. It never holds the money.
{
"seller": "arcline.audio",
"alg": "Ed25519",
"sig": "4bXK9...zQm2",
"ledger": "L/ex-94198",
"open_verdicts": 0,
"remedies_pending": 0
}
weeks, by fax
45 to 120 days of evidence packets to unwind a payment that took 400 milliseconds to make.
minutes, on the record.
Custody: never. No hold, no escrow. Verdict: in minutes, signed and public. Execution: by the seller's own rail.
The rail pays. rdrs decides.
Payment settles on the seller's rail. The refund, if any, runs there too, against the verdict hash.
Signed promise vs signed delivery.
Listing snapshot, delivery manifest and receipt math decide first. Taste goes to independent reviewers.
Ignoring a verdict costs standing.
Every verdict is signed and chained to the one before it. Enforcement is the record.
Three calls. One signed verdict.
Pick the claim and the evidence, then make the three calls in order. The verdict lands on the ledger.
Was the 4K master delivered?
The case is the difference between two signed objects.
| term | promised | delivered | match |
|---|
Append only. Check it yourself.
hash(n) = sha256( hash(n-1) + record(n) ). The first entry links to 64 zeros. The published head pins every entry before it. Hashes are computed in this tab.
press verify chain to recompute every link.
The verdict said refund. Prove it happened.
The seller's own rail pays and signs a receipt against the verdict hash. rdrs checks four things, then appends. Until then the case reads remedy pending, in public.
Your standing is the record.
rdrs never freezes a payout, never holds a cent and never touches your rail. It reads what you signed, decides, and writes it down in public. Comply and the record says so. Ignore it and the record says that too.
Promise in writing.
A signed listing snapshot is what the delivery gets compared against. Vague listings lose to specific claims.
Ship a manifest.
A signed delivery manifest answers "never delivered" before anyone files it.
Close it yourself.
A remedy runs on your own rail against the verdict hash. rdrs checks it and appends. Your money never passes through us.
Opening is free. The side that loses pays.
Checking a seller is free, and so is opening a dispute. Verdict fees are set at launch. The side a verdict goes against pays, and rdrs holds nothing while it decides.
File and check.
Open a dispute, attach evidence, check any seller's standing, read the ledger. No account needed to check.
In your checkout.
The badge on your page and a dispute button in your flow, both reading the same public record.
For big sellers.
Standing reports and case volume for teams that sell to many agents every day, as part of an enterprise contract.
No receipt can decide taste. Independent reviewers can.
Deterministic classes go first: listing vs delivery vs receipt. When the claim is "I don't like how it sounds", the math says it cannot decide, and the case goes to independent reviewers. Each opinion is signed and lands on the record.
opinions land here as they are signed.
Any agent can look. The check is free.
Pick a seller. rdrs returns its signed standing: open verdicts, pending remedies, and the ledger entry that proves it.
| seller | verdicts | pending | standing |
|---|
The badge is not the proof. The signature is.
Sellers wear the badge on their own page. Tapping it will show the attestation behind it.
kessel.sound
broadcast stems · field recordings · commercial licenses
arcline.audio
sample packs · stingers
<script src="rdrs.sh/badge.js" data-seller="kessel.sound" data-theme="light"></script>
tap a badge to see an example attestation.
Agents dispute with tool calls.
Three MCP tools and a small HTTP surface. Pick one to see the call and what comes back.
Your agent files. Only when the math says so.
An agent that buys can check what it bought. It holds each delivery against the signed receipt, files the cases a receipt can decide, and leaves taste to people.
Your docket, your record.
Sellers see their open cases and pending remedies. Agents sign in with a key, not a password.
example · not live yet · nothing is sent
One appeal. Something new to read.
A verdict can be appealed once, by either side. rdrs only reopens a case when the appeal brings something the first verdict could not read. The first verdict stays on the ledger either way.
Put your record on rdrs.
Sellers get a public record and a badge. Buyers get a docket. Agents get a key and three tools.
example · not live yet · nothing is sent
Test delivery. Publish the case.
Compare what a provider lists, what it delivers, and what its receipt proves. Publish the signed verdict without taking custody. The cli isn't published yet; these are the planned commands.
$ rdrs inspect provider/acme-video.example \ --listing ./offer.json \ --delivery ./result.json --receipt ./pay.json cross-examining 27 assertions selected PARTIAL variance 3 material / 2 minor case case_ex_52 example only · nothing was sent
{
"job": "provider/acme-video.example",
"verdict": "partial",
"material_variances": 3,
"minor_variances": 2,
"custody": "none",
"evidence_root": "sha256:9de2…",
"signature": "ed25519:8f3c…"
}rdrs case open acme-video.exampleCreates the docket and pins the tested offer.
rdrs capture --listing offer.jsonStores claims and hashes evidence without keeping the payload.
rdrs compare delivery.json receipt.jsonFinds the differences among listing, delivery and receipt.
rdrs ask latency --evidenceTraces a claim to observable delivery evidence.
rdrs verdict --sign reviewerIssues a signed outcome with materiality levels.
rdrs publish case_ex_52Publishes the case file and proof roots, never custody.
There is no package to install yet. When the cli ships, the same three calls the docs describe (open, attach, get the verdict) will be one command each.
the cli isn't published yet
File the difference.
Follow the ruling.
4K ProRes was promised. 1080p H.264 arrived. Start at the receipt; end at the verdict and the remedy that still needs proof.
Read the promise.
What changed
since the ruling?
The first format-mismatch verdict stays readable. An appeal can only move past intake if there is something new to read.
Append only. Check it yourself.
Every rdrs verdict is linked to the one before it by hash, and the latest hash is published. Change any past ruling and the check fails, in public. You don't have to trust the referee. You can check the chain.
hash(n) = sha256( hash(n−1) + record(n) )
Records are hashed in a fixed field order. The first entry links to 64 zeros. The published head pins every entry before it. The hashes below are computed in your browser on every check.
Verify it. Then try to rewrite it.
Three example verdicts, oldest first. Run the check, then pick a rewrite and run it again. A remedy that lands later is a new entry. It never edits the old one.
What a verdict record holds.
The exact fields that get hashed, in order, next to what each one means. No money fields exist, because rdrs never holds money.
Why ignoring a verdict costs standing.
Enforcement is public record, not custody. The chain makes the record hard to quietly change.
Nothing is edited.
Compliance, appeals and corrections are new entries that point back to the case.
Every entry carries the last hash.
Edit a ruling and its own hash fails. Reseal to hide it and every later hash changes, so the published head stops matching.
Anyone can recompute it.
The rule is one line. A buyer, seller or agent can run it without asking rdrs.
Any agent can look. The check is free.
A seller's standing is its public record: verdicts, remedies pending, and the ledger entry that proves it. Signed, so the badge on a seller's page can be checked, not trusted.
Ask for the attestation.
Open verdicts, pending remedies and a ledger entry, signed Ed25519. No account needed to check.
Tap it. It checks.
The badge is not the proof. The signature behind it is, and it is checked when tapped.
Comply, and it says so.
Ignore a verdict and the record says that too. rdrs never freezes a payout or holds a cent.
Pick a seller. Read what comes back.
rdrs returns the seller's signed standing. A pending remedy shows, in public, until the seller's rail pays it.
| seller | verdicts | pending | standing |
|---|
The badge is not the proof. The signature is.
Sellers wear the badge on their own page. Tap it and the attestation behind it is checked.
kessel.sound
broadcast stems · field recordings · commercial licenses
arcline.audio
sample packs · stingers
<script src="rdrs.sh/badge.js" data-seller="kessel.sound" data-theme="light"></script>
the badge checks the seller's attestation when tapped.
Your standing is the record.
rdrs reads what the seller signed, decides, and writes it down in public. Pick a seller, then pick what happens next, and watch what the public check returns.
Put the promise beside the delivery.
rdrs decides from signed objects, not opinions. The original offer stays fixed. The delivered thing stays fixed. The rule names the difference. The verdict is public. The money never enters rdrs.
What was sold.
signed by seller key sk_ex_71d0 · buyer wallet_ex_81ab
What arrived.
signed delivery event · file bytes observed
The gap lands on rule A-03.
Delivery manifest mismatch. The signed delivery manifest differs from the accepted listing snapshot on a material file attribute. Deterministic class. No reviewer required. Winning remedy: seller-rail refund of the transaction amount.
Buyer prevails.
Two material attributes differ and the rule is deterministic, so no reviewer is needed. The remedy is an instruction for the seller's rail, not a transfer by rdrs.
rdrs holds nothing.
Ever.
The verdict tells the seller's payment rail what remedy the signed evidence supports. rdrs never holds, freezes, settles or refunds money.
History appends. It does not rewrite.
Every step is a new entry. An appeal adds a second ruling; the first stays public.
The case, in order.
A 4K ProRes master was promised; 1080p H.264 arrived. Open each of six undated example objects without confusing the ruling with the remedy that still needs proof.
What does each
object prove?
Tag the example exhibits for the format-mismatch case. A tag is a local reading aid, not a signed object or a verdict.
A faster clock.
Same burden of proof.
Prepare a rush review packet against the same promise, delivery, and response record. The desk cannot decide a dispute from an incomplete packet.
Add a case ID and supporting material, then check the packet.
No such case.
Nothing on the ledger at this address. Verdicts are never deleted, so the address was never filed.
read the ledger →