HandToHuman / Documentation
Work and useful resources,
callable like software.
HandToHuman is Wisent's private marketplace contract for human work, compute, and bounded residential egress. It owns the lifecycle from account and offer through delivery, reputation, and payout.
Execution is ours. A person performs a humanization or a video on this ledger, assigned with a deadline; Stado places compute and the loopback-only handtohuman-egress worker for residential egress. A disputed delivery follows dispute → resolve; verified work becomes worker balance and then payout.
Quick start
Begin with work you already wrote. The first-use journey explains the safe boundary, and both import surfaces retain a non-empty JSON request without creating an order, reserving capacity, moving money, assigning a worker, or calling a provider.
handtohuman gui --listen 127.0.0.1:0
# Open the printed loopback URL; the command never opens a browser.Graphical import
The installed binary serves an accessible local page for selecting the JSON file, destination kind, title, and optional stable draft id. It displays the fleet database name, reports every imported, unchanged, conflicting, and rejected result, and reads imported or unchanged content back from that same ledger. A retained draft can be removed unless an order names it. Read the complete GUI command and refusal contract.
The page calls the same Rust import, draft-read and draft-remove operations as the CLI. It has no order, funding, dispatch, assignment, invitation, payment, or external-execution route. The server accepts only loopback binds, exact-host requests, exact-origin mutations carrying its random session token, and capped multipart bodies.
handtohuman onboarding
handtohuman market draft-import existing-brief.json \
--kind humanization \
--title "Existing rewrite brief"The result identifies imported, unchanged, conflicting, and rejected work without echoing the brief. An identical repeat is unchanged. Inspect the retained request with market draft-show <DRAFT_ID>; only a later explicit market order-create ... --draft <DRAFT_ID> begins the order lifecycle.
The task contract
Every kind exposes the same product surface, and every rule below is enforced by the ledger rather than promised by a provider:
Typed input
The request describes the work, price, deadline, supplier requirements, and the evidence a delivery must carry.
Existing work first
A user-authored JSON request can be retained as an unfunded draft and inspected before it is attached to an order. Import never commissions or pays for work.
Direct assignment
A funded order is handed to a named supplier with a deadline. There is no listing, no application pool, and no waiting for a volunteer.
Recovery that costs the buyer nothing
Past the deadline with nothing delivered, the order is reassigned to another supplier. The escrow is not re-collected, refunded, or spent twice, and every attempt is kept.
One lifecycle
created, funded, in_progress, delivered, accepted, disputed, refunded, cancelled.
One result
The order carries its delivery, its evidence, the measured verification, and — inside a campaign — the recorded measurement a bonus was computed from.
Money that cannot leak
Funding moves buyer credit into escrow; acceptance records the platform share declared in the rate card and releases the remainder to the worker. A dispute can refund, release, or split the exact total without creating or losing cents.
No external execution provider. Humanization and UGC ran through a third-party bounty marketplace until 2026-08-31. They no longer do: the work is assigned, delivered, verified, and paid here, and nothing in this product waits on someone else's API to implement a rule we depend on.