What handling disputes on delivered work says about Mission

On a Thursday evening in Lyon, a homeowner logs into WEVONE Mission to reject a €680 electrical panel upgrade four minutes before the 72-hour auto-settlement timer expires. The buyer attaches a single out-of-focus photograph of a switchboard and writes two words: "Still trips."

Traditional service marketplaces handle this with blunt instruments. Either a human support agent skim-reads a chat transcript three days later and splits the escrow, or the platform quietly sides with whichever party holds the highest lifetime transaction volume. Both approaches erode long-term trust. Handling disputes over delivered work is not a peripheral customer service feature; it is the stress test that reveals whether a platform's underlying protocol actually understands local physical work.

The Asymmetry of Service Verification

Physical and localized service delivery within WEVONE's Mission universe lacks the clean determinism of digital software tasks. When a remote developer pushes a code commit, automated test suites and git hashes provide objective verification of completion. When an electrician rewires a distribution board, a gardener clears a terrace, or an artisan restores a timber door, completion exists in a contested space between technical scope and human perception.

Most gig platforms attempt to solve this asymmetry by imposing punitive review policies on independent workers while treating buyer claims as inherently valid. WEVONE rejects this imbalance. Mission approaches service delivery through a deterministic state machine anchored by transactional escrow, timestamped verification media, and Mia's context memory.

Anatomy of the Dispute Window: The 72-Hour Ledger

When a provider marks a Mission task as delivered, funds do not immediately enter their wallet, nor do they sit in unmonitored limbo. They enter a locked 72-hour evaluation window enforced by WEVONE's transactional escrow protocol.

During this 72-hour window, three distinct execution paths exist:

1. Explicit Acceptance: The buyer confirms satisfaction, immediately releasing escrowed funds to the provider's wallet.
2. Silent Expiration: The 72-hour timer elapses without buyer intervention, triggering an automated protocol release to the provider.
3. Formal Dispute: The buyer flags non-compliance, pausing the settlement clock and initiating Mia’s dispute intake pipeline.

Rather than treating a dispute as an unstructured complaint, Mission treats it as a protocol exception requiring evidence payloads. When a buyer initiates a dispute, Mia automatically ingests four distinct data artifacts: the original scope contract signed at booking, the full event transcript, the timestamped media submitted by the provider at delivery, and the precise technical delta claimed by the buyer.

A Worked Example: The Lyon Panel Upgrade

Consider the late-night dispute in Lyon. Under a traditional freelance platform, the buyer's vague "Still trips" comment would initiate an indeterminate email chain, freezing the electrician's funds for weeks.

On Mission, Mia's context memory immediately cross-referenced the original contract parameters. The signed scope stated: "Installation of a dedicated 20A circuit for an induction stove and replacement of the primary safety switch." Upon marking the job complete, the electrician had uploaded three high-resolution images: the labeled breaker panel, a digital multimeter reading showing 230V across the new circuit, and a signed physical completion slip.

Mia’s vision parsing evaluated the buyer’s out-of-focus photo against the provider’s baseline delivery media. The photo submitted by the buyer showed a tripped 10A breaker dedicated to hallway lighting—a circuit entirely untouched by the electrician’s documented work scope.

Within 90 seconds, Mia synthesized the findings for both parties: the reported fault occurred on an unserviced circuit outside the agreed contract bounds. The buyer was presented with two programmatic choices: release the €680 escrow for the verified scope, or trigger a separate Mission request for the hallway lighting fault at an automated diagnostic rate. The buyer released the escrow four minutes later.

Reputation as a Two-Sided Ledger

Disputes reveal whether a marketplace values fairness over short-term conversion metrics. Standard platforms treat buyer churn as catastrophic and provider churn as acceptable, resulting in systems where buyers face zero friction for bad-faith claims.

WEVONE structures reputation across all universes—including Mission, Tutus, and Nest—as a two-sided ledger tied to the user's Trust profile and Contribution Score.

If a buyer consistently initiates late-stage disputes that fail evidentiary verification, Mia flags the behavioral pattern. The buyer's Trust score drops, which dynamically increases their required upfront deposit ratios for future Mission bookings or restricts access to highly rated service providers.

Conversely, service providers who maintain a pristine record of scope compliance earn shortened escrow clearance windows. A provider with an exemplary Trust history sees their default dispute hold drop from 72 hours down to 24 hours. Systemic honesty creates liquidity.

What is Live vs. What Remains a Bet

We must be explicit about the boundaries of our current implementation.

FACT: WEVONE’s transactional escrow, strict 72-hour state timers, metadata inspection, and Mia’s baseline scope-matching algorithms are currently shipped and operating in beta across active European test markets.

AMBITION: Fully autonomous resolution for purely subjective or qualitative service disputes remains an open engineering problem, not a solved science.

When a dispute centers on subjective judgment—for instance, a client asserting that a freshly painted wall "lacks the depth of tone promised in the color chip"—data logs and photo EXIF metadata cannot deliver a definitive answer. Software that pretends to measure subjective human delight is lying.

For these edge cases, Mia does not issue unilateral binding decisions. Instead, she compiles an audited evidentiary dossier containing the scope agreement, delivery logs, and baseline dispute synthesis, then routes the file to a human community arbitrator. The long-term bet is that structured data intake reduces human arbitration time by over 80%, keeping platform overhead low without sacrificing human fairness when data hits its natural limit.

Disputes on delivered work are not platform failures to be swept under a rug. They are the exact moment a platform proves whether its infrastructure is built on marketing promises or verifiable protocol mechanics.