resident's own home near the town center, Henderson, TX (Rusk County; best-estimate location, exact address not confirmed)
Reconfirm the retained standing snag's siting check.
Sites change: a new fence, a shed, or a play area built near a retained snag after the fact can turn a Read all of it
Not funded yet. Settles as earned credit, $80 proposed.
Proof it takes, the deadline, the level
- Proofresident-permission record + re-measured distance record + before/after photos + GPS
- Open until2026-10-13
- Levelentry
All of it: the words, the place, the proof
Sites change: a new fence, a shed, or a play area built near a retained snag after the fact can turn a safe retention into a hazard nobody rechecked. This recurring visit re-measures the same distance-to-target check on a schedule, so retention stays a safety decision that is kept current, not a one-time call nobody revisits.
Fund it for $80. 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
- 1. Locate the tagged snag from the prior visit's photo and confirm the tag is still legible and in place.
- 2. Re-measure the distance from the tree's base to the nearest path, road, structure, fence, play area, or parking area, the same way as the original check.
- 3. If the distance no longer clears the tree's own height (something new was built nearby, or the tree has changed), STOP: note that retention no longer applies here, and tell the resident this tree now needs a professional evaluation.
- 4. If the distance still clears, replace the tag if faded and photograph the tree from the matching before vantage with the re-measured distance recorded.
What counts as done
- Written or recorded permission from the resident
- Re-measured distance from the snag's base to the nearest path, road, structure, fence, play area, or parking area recorded
- Confirmation that retention was withdrawn and the resident notified if the distance no longer clears the tree's height
- After photo of the snag with its tag confirmed or replaced
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_1789313584073_d036lnt","funderWallet":"0xYOU"}.
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_1789313584073_d036lnt