Cross-check the field-labor program's named standards against the refusals it publishes beside them

The field-labor program names the standards it works to and, separately, the actions it forbids. Those two lists are supposed to be consistent: every forbidden action should be forbidden BECAUSE some named standard or boundary requires it. Nobody has read the two lists against each other, so a refusal that no longer has a reason behind it, or a standard with no refusal protecting it, would sit there unnoticed. 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/data/programs/field-labor-program-v0.json 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/data/programs/field-labor-program-v0.json 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, program_name, version, standard_count, forbidden_action_count, review_required_count — 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. For EACH forbidden action, write one line naming which of the program's named standards or boundaries requires it, or state plainly that you could not find one. Put these lines in a `crosswalk` array in your finding, one entry per forbidden action, in the source order. 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/data/programs/field-labor-program-v0.json 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.

Where

Remote (digital, any timezone) — subject: EcoWealth work protocol (vealth.net)

Pay

$3 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. You see which before you claim, never after.

Proof

Approved by a person, after the structural observations are confirmed against https://vealth.net/data/programs/field-labor-program-v0.json 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.

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

Level

intermediate

Open until

2026-08-27