a resident's own home, the sloped front-yard zone, Poteet, TX 78065 (Atascosa County); best-estimate location near the town center, exact address not confirmed
Split one long run into cycle-and-soak on the slope zone, a resident's own home, the sloped front-yard zone, Poteet, TX 78065 (Atascosa County).
A resident's own home, the sloped front-yard zone waters in one long continuous run, and most of it runs off the surface Read all of it
Not funded yet. Settles as earned credit, $80 proposed.
Proof it takes, the deadline, the level
- Proofbefore single-run record + runoff-onset observation + after multi-cycle program + no-runoff runtime log + GPS
- Open until2026-10-20
- Levelentry
All of it: the words, the place, the proof
A resident's own home, the sloped front-yard zone waters in one long continuous run, and most of it runs off the surface before the ground can take it in rather than soaking into the root zone -- the runoff carries mulch and topsoil to the curb every time it runs.
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. Read and record the zone's current single run time and start time before changing anything.
- 2. Watch the current run (or ask the resident) to find the point at which runoff starts reaching the bottom of the slope -- that point sets the maximum single-cycle length.
- 3. Reprogram the zone into multiple shorter cycles with a soak gap between them, so the total weekly water applied stays the same but no single cycle runs long enough to produce runoff.
- 4. Run the new program once and record: no runoff reaching the bottom of the slope during any single cycle, plus the multi-cycle program as saved on the controller.
What counts as done
- Before record of the single continuous run time and start time
- Runoff-onset observation noting the run length at which runoff began under the old program
- After record of the multi-cycle program (cycle length, number of cycles, soak gap) as saved on the controller
- Runtime log or photo series of the new program running with no runoff reaching the bottom of the slope
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_1789886661418_6ohjg9z","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_1789886661418_6ohjg9z