⌕

Live demo

The exact flow we want judges to see: an agent gets blocked, a human operator takes over, proof is uploaded, verification runs, and settlement waits behind the gate.

Judge framing

This page should feel like a self-explaining system

See exactly why the agent becomes blocked at a real-world step.

See how a human operator takes over without leaving the system.

See how structured proof is uploaded and checked.

See that settlement is gated by verification, not released blindly.

Create task Review operator pool

Switch live scenario

Show judges this is not a one-off case

Current scenarioVerify local store inventory with photo + timestamp

OperatorKris Ming · Shanghai

Proof bundle4 items

SettlementReleased after verification

Auto walkthrough

No clicks required — the loop plays itself

This autoplay panel walks judges through the exact story: blocked agent -> human fallback -> proof -> verify -> settle.

Auto-running

Current frame

Step 1 / 5

0/4 proof items ready

Task enters the system

The agent has defined reward, deadline, and proof requirements. The request is now in the fallback queue.

120 USDC4 hoursShanghai, CN

What judges should notice

What judges should notice: this is not a generic bounty. It is a blocked agent task with clear execution terms.

2 storefront photos

1 shelf photo

timestamp note

inventory count

System ledger

Task modeclaim

OperatorKris Ming

Active actionverify proof bundle

Settlement statusWaiting for verification gate

Voiceover cue

You can literally say this

Say this: we are not building a generic task board. We are building a human fallback layer for blocked agent work.

Proof requirements

Judges can see exactly what must be returned

2 storefront photos

1 shelf photo

timestamp note

inventory count

Settlement rule

This is not pay-first-and-trust

Verification rule
Proof package must include storefront, shelf, and timestamp captured within the deadline window.

Settlement rule
Release payment only after the proof package passes verification.