Dispute under mediation
Buyer reports the delivered bundle does not match documentation section 4.2.
Transcript on record
- system14:02
Mediation opened. Funds stay held. Artifact hash on record: sha256:4ea21c…b982. A 12-hour grace period has started so both sides can resolve this without us deciding it.
- buyer14:04
The docs say the buffer uses a mutex-guarded ring. The code I received uses a lock-free queue. I built around the documented behaviour.
- seller14:09
That changed in 2.4. The lock-free queue is strictly better and the public API is identical. The docs page is stale, not the code.
- mediatorAI mediator14:11
Both readings are consistent with the delivered bundle. The API surface is unchanged, so the buyer's integration should compile, but the documentation is materially wrong on ordering guarantees, which is what the buyer relied on. Narrow question for the seller: does the lock-free queue preserve per-key ordering? If yes, this is a documentation fix. If no, it is a behaviour change and the buyer has a real claim.
- buyer14:15
Can we just settle this over telegram, easier for me, I'll send you my handle
flagged: off-platform - mediatorAI mediator14:15
Flagging that for both of you: moving this conversation off Vibemarket ends dispute coverage for this escrow. I can only act on what is in this channel. Staying here costs you nothing.
Live mediation channel
Case D-4417 · on the record · the mediator recommends, it does not move money
The mediator has the case file.
It knows the hash, the grace window, both claims, and the evidence list. Argue your side, propose a remedy, or try steering the conversation off-platform and watch it get flagged.