San Bernardino, CA
Write the emergency plan.
Write the emergency plan for a job site as it stands today in San Bernardino, CA. Read all of it
Not funded yet. Settles as earned credit, $95 proposed.
Proof it takes, the deadline, the level
- Proofthe one-page plan + photos of it posted + the changed-from-prior list
- Open until2026-11-19
- Leveladvanced
All of it: the words, the place, the proof
Write the emergency plan for a job site as it stands today in San Bernardino, CA. Most site emergency plans were written for the site as it was on day one. The exits moved, the muster point is now a laydown yard, and the nearest trauma center is not the one on the poster.
Fund it for $95. 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.
Steps
- Walk the site as it stands today with the current plan, or a blank sheet where none exists.
- Establish the plan against the ground truth: exits that actually open, a muster point that actually holds the headcount, the incident command contact chain with live names and numbers.
- Verify the response basics in place: extinguisher locations, first aid station, the route emergency services would actually drive in.
- Confirm the nearest emergency department and trauma center by current address and drive time.
- Write the plan on one page the crew can read, post it at the points the crew actually passes, and photograph each posting.
- Brief the supervisor on what changed from the prior plan.
What counts as done
- The finished one-page emergency action plan, dated
- Photos of the plan posted at each crew point, GPS inside the posting radius
- The list of what changed from the prior plan, or a note that none existed
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_1787185192938_q3ecy6r","funderWallet":"0xYOU"}.
Open, but not claimable yet. The work qualification registry could not be read (registry file not found at /home/ubuntu/ecowealth-production-20260912/data/standards/work-qualification-v0.json), so no packet's requirements can be established. The requirement is a structured fact about this kind of work, not a line of the packet's text, and an attestation does not establish it. It is not claimable 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_1787185192938_q3ecy6r