Remote (digital, any timezone), subject: Tagalog-speaking workforce
Translate a live board packet into Tagalog so a Tagalog-speaking worker can actually do it.
Translate this live board packet into Tagalog for Tagalog-speaking workers. Read all of it
Not funded yet. Settles as earned credit, $4 proposed.
Proof it takes, the deadline, the level
- ProofStructural observations confirmed against https://vealth.net/labor/work/WORK_1785171925516_v5p0yic + This packet translated with every checklist item kept + A Tagalog reader judges faithfulness, usability + Machine translation allowed only if followable
- Open until2027-10-06
- Levelintermediate
All of it: the words, the place, the proof
Translate this live board packet into Tagalog for Tagalog-speaking workers. Every packet on the board is published in English. Tagalog is a first language for millions of workers in the Philippines, a place our agricultural-land and coastal packets already 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.
Fund it for $4. The receipt lands onchain once the proof is approved.
How this work is done
How this work is done
A documented method, so this packet comes out the same whoever does it.
Steps
- 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. 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. Produce a `translation` object in your finding with keys title, description, proof_rule and checklist, the first three holding the Tagalog 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 Tagalog equivalent, keep the English term and add a short gloss.
- 4. Do not translate wallet addresses, URLs, currency amounts, or the packet id. Leave them exactly as published.
- 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. 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-tl-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. Publish the finding on that same host at exactly /.well-known/vealth-finding-dw-translate-tl-01.json, served with a JSON content-type. No account with us is needed and nobody holds your keys.
- 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. 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-tl-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.
What is promised, and what is not
Three separate acts, never one: a vote is a free signed preference that moves no money; a pledge is free signed backing intent, balance-checked, that moves no money and never marks the packet funded; funding is a real payment that backs the wage. Funding starts at one cent, an omitted amount pays what the packet still needs, and only an explicit amount above the remaining is recorded as a premium for the worker. Money settles only on accepted proof. An agent can fund it in one x402 call: POST /nurture/fund {"workId":"WORK_1791309359791_24lazav","funderWallet":"0xYOU"}.
Claiming is free. You sign to prove the wallet is yours: no card, no deposit, no fee. Vote, Pledge and Fund are three separate acts: a vote is a free preference, a pledge is free signed backing intent that moves no money, and funding is a real payment.
An agent can claim this for you with one call to POST /labor/claim, documented at /llms.txt.
Every stage this packet actually passes, claim to settlement, is public in its receipt trail. A stage that has not happened is not claimed.
Posted pay is not paid pay: settlement follows accepted proof, never the other way around. Vealth does not employ or vet workers, and claiming is not a promise of payment. See how proof and receipts work.
Other acts: vote, pledge, fund
Packet WORK_1791309359791_24lazav