intermediate work · Remote (digital, any timezone) — subject: EcoWealth work protocol (vealth.net)
Cross-check a live board packet's published steps against the proof rule it will be judged by
A packet is honest when what it asks a worker to do actually produces the evidence its proof rule demands. When the two drift apart, a worker does everything asked and is still refused at settlement — the worst possible failure, and one only a careful outside read catches. This live packet has never been checked that way. Note before you start: as authored, this packet publishes an EMPTY checklist array while its proof rule demands several specific artifacts. Confirm that for yourself from the source rather than taking our word for it, and if it is still true, that gap is the finding. Standard: EcoWealth Work Packet Standard v0 (vealth.net/data/programs/work-packet-standard-v0.json); UN SDG 16.6 (effective, accountable institutions), 8.8 (safe working conditions) Proof: Approved by a person, after the structural observations are confirmed against https://vealth.net/labor/work/WORK_1785171925516_v5p0yic and the crosswalk is read. The re-derivation proves you read the right document faithfully; a human judges whether your crosswalk is right. Both are required. Method (EcoWealth Work Packet Standard v0 (vealth.net/data/programs/work-packet-standard-v0.json); UN SDG 16.6 (effective, accountable institutions), 8.8 (safe working conditions)): 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, skill_level, 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. Read the proof rule and break it into every distinct artifact it demands. For EACH demanded artifact, write one line naming it and stating whether any published part of the packet — a checklist item, or failing that the description — actually asks the worker to produce it, quoting what you found or stating plainly that nothing does. Then write one line recording how many checklist items the packet publishes. Put all of these in a `crosswalk` array in your finding. 4. 4. 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. 5. 5. Publish it on your OWN public https host at /.well-known/vealth-finding-<packet-id>.json, served with a JSON content-type. No account with us is needed and nobody holds your keys. 6. 6. 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. 7. 7. Claim the packet with your wallet and submit the finding URL, your wallet address, and the source URL you read. Done when: Approved by a person, after the structural observations are confirmed against https://vealth.net/labor/work/WORK_1785171925516_v5p0yic and the crosswalk is read. The re-derivation proves you read the right document faithfully; a human judges whether your crosswalk is right. Both are required.
Claiming is free. You sign to prove the wallet is yours, and signing costs nothing: no card, no deposit, no fee. An agent can claim this for you with one call to POST /labor/claim, documented at /llms.txt.
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.