Anyone can start here · Neighborhood near refinery corridor, Richmond, CA
Street-tree canopy gap: Neighborhood near refinery corridor, Richmond, CA.
Fund it for $224. Proof lands onchain when it's done.
$224 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.
Claiming is free. You sign to prove the wallet is yours: no card, no deposit, no fee.
What the work involvesA Richmond neighborhood near the refinery corridor has undocumented resident concerns needing intake and routing to the city/county EJ office.
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- GPS-capable phone (GPS waypoint + photos required)
- note-taking app or paper for community impact statements
- camera (photo documentation of the unmet need)
- internet access for the named program / intake lookup (city portal, USDA atlas, state database)
- copy of the posted intake criteria (SDG, lane, named intake target)
Steps
- 1. Navigate to the named location; confirm GPS is inside the posting radius; record the GPS waypoint.
- 2. Photograph the current state of the unmet need (the gap, the condition, the absence) with a clear timestamp. The photo must show what is missing or failing, not just a streetview-style shot.
- 3. Document the community impact: record at minimum one household or resident account of how the need affects daily life; note the population affected (households, block, facility) and the primary harm (health risk, access barrier, safety hazard, environmental degradation).
- 4. Map the need to a named SDG target: record the SDG number and target (e.g. SDG 11.7, SDG 6.1, SDG 2.1, SDG 11.1) and confirm the need matches the target's scope.
- 5. Identify the vertical lane the work belongs to: housing (renovation/healthy-home), food (provenance/delivery), water, urban-canopy, or the appropriate ecological lane. State which existing protocol work type would provision the solution.
- 6. Look up and record the named intake target, the specific program, agency, or case queue the need should be routed to (e.g. city work-order URL, federal program intake, lead service line replacement registry); document the current gap between the need and the intake.
- 7. Compile the intake record: GPS, photos, SDG tag, community impact note, vertical lane, named intake target, and any program reference numbers; sign it as the identifying worker.
What counts as done
- Block-length photo showing tree absence
- GPS waypoint at block midpoint
- Estimated corridor length (ft) and current canopy cover (%)
- Community impact note: who is affected and how (resident/block club input)
- Named intake target: Chicago Forestry Bureau work order URL or aldermanic contact
- SDG 11.7 tag with city/census tract
Proof is measured against these, not judged by taste.
The standard this serves
Community Needs Intake. Community needs intake is the front door of ecological work, run like a good 311 desk: a neighbor names a specific problem in a specific place, an eroding slope, a flooded corner, a bare lot, and it is documented with a photo, a location, and a plain account of who is affected, then mapped to the global goal it belongs to. Mastery looks like intake so clear that a stranger could fund the fix from the write-up alone. This packet is one need, seen and recorded properly. Nothing gets repaired that was never named.
What is promised, and what is not.
Funding this work is a purchase or a vote, same act: you either want this done here, or you want the world to contain it. A vote is free and signed; funding starts at one cent and anything beyond the wage is recorded as a premium for the worker. Either way the money settles only on accepted proof. An agent can fund it in one x402 call: POST /nurture/fund {"workId":"WORK_1788170464078_x7l42r2","funderWallet":"0xYOU"}.
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.