Anyone can start here · Community Kitchen El Centro Ca Ladder B34 Entry
Verify one delivery of ingredients to the community kitchen, El Centro, CA
Fund it for $360. Proof lands onchain when it's done.
$360 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.
Claiming is free. You sign to prove the wallet is yours: no card, no deposit, no fee.
What the work involvesThe community kitchen in El Centro, CA buys blind off a distributor list while Imperial Valley fields sit minutes away. Start with one verified delivery: named producer, harvest date, and cold-chain log to the kitchen door.
How this work is done
A documented method, so this packet comes out the same whoever does it. Typically 120–240 minutes. Method of record: Michelin-grade ingredient provenance + delivery verification (green-star-grade sourcing criteria; named-source verification + time/temperature chain of custody + receipt grading confirmed by the receiving kitchen)
Bring
- camera
- instant-read / infrared thermometer (chain-of-custody temperature checks)
- insulated transport totes / cold chain appropriate to the ingredient
- tablet/clipboard with the sourcing spec + receipt-grading sheet
- GPS-capable phone (source, transit, and delivery waypoints)
Steps
- 1. Write the sourcing spec WITH the receiving kitchen (community kitchen, school, pantry fresh-program, or institution): the ingredient, the standard it must meet (peak-season, named source, variety, harvest window, condition at receipt), the quantity, and the delivery window. The spec is the claim being provisioned, real food at a named standard, delivered.
- 2. Verify at the source in person: photograph the farm/boat/producer, record the grower/captain/maker's name, the harvest/landing date, the variety/breed/catch, and the growing/handling practice; confirm the lot you will transport is the lot you inspected.
- 3. Grade the ingredient at pickup against the spec's Michelin-grade criteria, freshness indicators appropriate to the ingredient (eyes/gills/firmness for fish, turgor/aroma for produce, date and handling for dairy/grain), seasonality honesty, and variety specificity; reject-or-accept against the spec, recording the call.
- 4. Hold the chain of custody in transit: record time out of source cold storage, transport method + temperature checks at pickup and delivery (cold chain ≤4°C / frozen ≤-18°C where applicable, per the receiving kitchen's spec), GPS waypoints source → kitchen.
- 5. Deliver into the kitchen's receiving process: the kitchen's manager (or certified food-protection manager) inspects, temperature-checks, and accepts/rejects; record their acceptance, receipt grading, and what the kitchen will make with it.
- 6. Package the provenance record: source identity + harvest date + practice, grading at pickup and receipt, the custody log, and photos at all three points; sign. Real (a named source, a real delivery), Proven (photo+GPS+temperature log+kitchen acceptance signature), One-of-one (this lot, this kitchen, these meals).
If it does not match the plan
- Ingredient fails the spec at pickup (freshness indicators, wrong variety, off-season substitution) -> reject at source, record why, and re-source; never deliver a downgraded lot against a Michelin-grade spec.
- Cold chain broken in transit (temperature above the spec's limit at any check) -> flag to the receiving kitchen BEFORE handoff; the kitchen's certified food-protection manager makes the accept/reject call, never the courier.
- Any food-safety concern at source or receipt (contamination risk, unapproved processing, recall overlap) -> route to the receiving kitchen's manager / local health department; the packet documents provenance, it never overrides food-safety authority.
- Source cannot evidence its claim (no harvest date, vague origin, resold lot) -> do not certify provenance; record the gap and source elsewhere: an unverifiable claim is not delivered as verified.
What counts as done
- Sourcing spec approved by the receiving kitchen before pickup
- Source verification photos: producer, the actual lot, harvest/landing date, variety, practice
- Time + temperature custody log at pickup and delivery with GPS waypoints source → kitchen
- Receipt grading + the receiving kitchen's signed acceptance
- GPS / address confirm at delivery
Proof is measured against these, not judged by taste.
The standard this serves
Michelin Craft, Ingredient Provenance. Provenance means knowing exactly where food comes from: which field, which boat, which week. The best kitchens can name the farm behind every plate, and the Michelin Guide notices when they can. Wine people have a word for what this protects, terroir, the taste of one particular place. Mastery means growers you know by name and records you can stand behind. It starts with a single honest entry: this crop, this plot, this date, these hands. A packet like this one writes that first line of the ledger.
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_1785976438835_sjhkiy2","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.