the Concow Road residential corridor, Concow (Yankee Hill area), Butte County, CA
Fell and remove a documented fire-killed tree threatening a Concow Road driveway (licensed crew).
The documented queue names the tree; this job drops it. Read all of it
Not funded yet. Settles as earned credit, $540 proposed.
Proof it takes, the deadline, the level
- Proofbefore/during/after photos + GPS + license note
- Open until2026-10-28
- Leveladvanced
All of it: the words, the place, the proof
The documented queue names the tree; this job drops it. Fire-killed snags are the region's real post-fire trade -- chainsaw and rigging work for a licensed, insured tree contractor, paid at a premium because the hazard is real.
Fund it for $540. 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
- the tree-risk assessment on file + the land manager's or owner's removal authorization + any local tree-removal permit
- ANSI Z133 crew: qualified arborist plus a second qualified person in view at all times
- saws maintained to spec, felling wedges, rigging and lowering gear rated for the load
- chainsaw chaps, helmet with face and hearing protection, gloves and boots
- drop-zone control: cones, tape, signage and a spotter for the public edge
- camera + GPS phone
Steps
- 1. ASSESS: photograph the tree and the target area, and confirm the written risk assessment, the removal authorization and any permit before a saw comes out of the truck.
- 2. Walk the site for overhead conductors, structures, and the public edge; if a conductor is within the fall or rigging path, stop and route to the utility.
- 3. Establish and control the drop zone with cones, tape and a spotter, and hold a documented pre-cut briefing covering the plan, the escape routes and the abort signal.
- 4. Remove the tree by the planned method (sectional rigging or directional felling), with a second qualified person in view for every cut.
- 5. Process and remove the material to the agreed disposal route, and cut the stump to the specified height or grind it if the packet calls for it.
- 6. VERIFY: photograph the cleared site from the before vantage, confirm no hanger is left in an adjacent tree, and log the disposal route and the crew of record in the proof record.
What counts as done
- Before photo of the standing tree and its threat line
- After photo of the stump and cleared lay
- Disposal note: where the wood was bucked/staged
- Contractor license number recorded (CSLB C-61/D-49)
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_1789302190936_cfd719x","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_1789302190936_cfd719x