Translate a live board packet into French so a French-speaking worker can actually do it.

Every packet on the board is published in English. French is the working language across much of West and Central Africa, including places our water and forest packets name. A worker who cannot read the checklist cannot claim the work, and a worker who half-reads a proof rule does the job and is refused at settlement. That is not a translation nicety; it is the difference between the board being open to them and closed.

Where

Remote (digital, any timezone), subject: French-speaking workforce · Open the map

Pay

$4 proposed

This packet is not funded yet, so this figure is a proposed price and not money waiting in escrow. If a buyer funds it, approved proof settles that price onchain. If nobody funds it, approved proof earns provable credit toward the work instead of cash — recorded, and readable any time at vealth.net/labor/credit/(your wallet). You see which before you claim, never after.

Proof

Approved by a person who reads French, after the structural observations are confirmed against https://vealth.net/labor/work/WORK_1785171925516_v5p0yic. The re-derivation proves you translated THIS packet and kept every checklist item; only a French reader can judge whether the translation is faithful and usable. Machine translation is allowed: a translation nobody could follow is not.

This is exactly what gets it approved. Nothing settles without it.

Level

intermediate

Open until

2026-09-29

Posted by

0x034F…6c89

The creator wallet. Its signature is what approves proof and settles the wage.

How this work is done

A documented method, so this packet comes out the same whoever does it.

Steps

1. 1. GET https://vealth.net/labor/work/WORK_1785171925516_v5p0yic exactly once, with no query string and no credentials. Read the response; change nothing.
2. 2. Derive each observation this packet names (http_status, is_json, valid_json, definition_id, work_type, checklist_count, proof_rule) as a pure function of that one response, using the source_derivation_vocabulary at the top of this library. Report what you actually observed, never what you expected.
3. 3. Produce a `translation` object in your finding with keys title, description, proof_rule and checklist, the first three holding the French text, and checklist an array with exactly as many items as the source publishes, in source order (an empty array if the source publishes none). Translate meaning, not words: if a term has no French equivalent, keep the English term and add a short gloss.
4. 4. Do not translate wallet addresses, URLs, currency amounts, or the packet id. Leave them exactly as published.
5. 5. Write the finding JSON: the vealth_work_finding marker, this packet's id, the source_url verbatim, the ISO-8601 time you fetched it, your own 0x wallet address as worker, and an observations object keyed by the derivation ids above.
6. 6. CLAIM BEFORE YOU PUBLISH. POST /labor/claim with your wallet and `targetUrl` set to your host ROOT (for example https://your-host, with no path). `targetUrl` is REQUIRED: it is what the machine verifier probes, and a claim without it can only be settled by human review. We check /.well-known/vealth-finding-dw-translate-fr-01.json on your host at claim time and it MUST NOT be serving the finding yet, because this packet pays for work done AFTER claiming (a surface that already exists at claim time is refused). Signing the claim makes it free.
7. 7. Publish the finding on that same host at exactly /.well-known/vealth-finding-dw-translate-fr-01.json, served with a JSON content-type. No account with us is needed and nobody holds your keys.
8. 8. Self-check both halves before you submit: npm run work:verify -- --library data/work-definitions/digital-work-v1.json --id <packet-id> --target https://your-host, then npx tsx scripts/work-queue/verify-shelf-finding.ts --library data/work-definitions/digital-work-v1.json --id <packet-id> --target https://your-host.
9. 9. Submit your proof: POST /labor/work/<workId>/complete with your claimId, your wallet address, and the finding URL. Signing the request makes this free too. The worker path costs you nothing end to end.

What counts as done

• The public https URL of your published finding (your host + /.well-known/vealth-finding-dw-translate-fr-01.json)
• The 0x wallet address recorded inside the finding as `worker`, the same wallet that claims and is paid
• The exact source URL you read, recorded in the finding as `source_url`: https://vealth.net/labor/work/WORK_1785171925516_v5p0yic
• The observations object, with one entry per derivation id named in this packet

Proof is measured against these, not judged by taste.