Leimert Park community garden, Los Angeles CA (site 1)
Ask the neighbors what they need near Leimert Park community garden, Los Angeles CA.
An intake worker at Leimert Park community garden photographs the unmet need with a phone camera and types a resident's account into a notes app, turning it into a logged need. Read all of it
Not funded yet. Settles as earned credit, $184 proposed.
Proof it takes, the deadline, the level
- Proofphoto of the full block showing absence of trees + GPS waypoint + canopy-gap measurement + community impact note (resident input) + named intake target (city forestry / aldermanic office)
- Open until2026-12-10
- Levelentry
All of it: the words, the place, the proof
Check the what the neighbors need at Leimert Park community garden, Los Angeles CA (site 1). It has never been checked before, and this check lets the people who use this place know where things stand.
Offer to pay $184. The receipt lands onchain once the proof is approved.
Safety, read before you claim
Identification and intake only, never plants, prunes, or disturbs any tree, and no roadway entry. All actual planting work routes to the city forestry program or a licensed arborist.
The full safety list for this job:
- Hazards here: traffic at curbs and driveways, uneven paving, sun and heat. Stay on the sidewalk, wear a bright top and closed-toe shoes, and carry water. Stop work and move away if a vehicle enters your space or anyone confronts you, and do not touch anything that looks like a spill, a needle or a broken fixture. No special training is needed.
How this work is done
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
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, made by the payer straight to the worker, with no Vealth fee. Paying Vealth is closed: Vealth takes no new card or wallet payment for a job. To fund a job, offer to pay the worker directly, then pay them yourself when you accept the proof, from your own wallet or by your own card or bank. From a wallet: prepare_token_offer, sign, submit_token_offer; after the proof is accepted you pay the worker on chain and the worker records it (prepare_token_settlement, or POST /labor/settle for USDC on Base). By card or bank: prepare_direct_offer, sign, submit_direct_offer; you pay the worker yourself and the worker records it with prepare_direct_settlement. Both are free, need no gas, and move no money through Vealth.
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_1794291782049_ho2h9bi