Hilmar, CA (community building, exact site not yet named)
Install cold storage.
The community food pantry at a community building in Hilmar, CA cannot accept fresh or dairy donations without cold storage. Read all of it
Not funded yet. Settles as earned credit, $90 proposed.
Proof it takes, the deadline, the level
- Proofphoto inventory + condition tag per station + GPS + ranked follow-on list
- Open until2026-10-29
- Levelentry
All of it: the words, the place, the proof
The community food pantry at a community building in Hilmar, CA cannot accept fresh or dairy donations without cold storage. Installing a reliable cooler expands what it can give out.
Fund it for $90. Proof lands onchain when it's done.
How this work is done
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- camera
- food thermometer
- water-bath canner + jars, new lids, bands
- large pots, knives, cutting boards
- tested recipe with processing times
- labels + timer
- hair covering, apron, gloves, hand-wash station
Steps
- 1. Photograph the source produce/ingredients and confirm they are sound (no spoilage) before starting.
- 2. Wash hands and sanitize surfaces and equipment; put on hair covering and clean apron.
- 3. Follow a tested recipe: wash, peel/cut, and prepare the food to the recipe's specification.
- 4. For water-bath canning of high-acid foods, fill jars to the stated headspace, remove air bubbles, wipe rims, and apply lids finger-tight.
- 5. Process for the full recipe time adjusted for altitude; for drying/fermenting, hold the specified temperature/time or brine ratio.
- 6. Cool jars undisturbed, then check every lid for a complete seal; refrigerate or discard any unsealed jar.
- 7. Label each item with contents and date; record quantity prepared and its destination (pantry/community meal).
- 8. Enter photos, recipe used, processing time/altitude, seal checks, and quantities into the proof record; sign.
What counts as done
- Photo inventory of the kitchen's current refrigeration capacity and available cold storage
- Food-safe condition tag per refrigeration unit (ready | needs repair | needs replacement)
- GPS / address confirm
- Ranked list naming the follow-on cold-storage install for each gap, with a note on any ServSafe/permitted-kitchen requirement for accepting a dairy donation stream
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_1789361193046_nuxk5j7","funderWallet":"0xYOU"}.
Open, but not claimable yet. restricted: permit-required — Regulated or permit-required work cannot be claimed on this rail yet. It stays readable; voting and pledging are free, and funding is separate from claiming.
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_1789361193046_nuxk5j7