the public library's front-bed irrigation controller, Poteet, TX 78065 (Atascosa County); best-estimate location near the town center, exact address not confirmed
Reprogram the controller off its stuck seasonal schedule, the public library's front-bed irrigation controller, Poteet, TX 78065 (Atascosa County).
The public library's front-bed irrigation controller is still running the summer program -- same run times, same days -- weeks after the Read all of it
Not funded yet. Settles as earned credit, $80 proposed.
Proof it takes, the deadline, the level
- Proofbefore program record + after program record + saved-confirmation photo + GPS
- Open until2026-10-20
- Levelentry
All of it: the words, the place, the proof
The public library's front-bed irrigation controller is still running the summer program -- same run times, same days -- weeks after the season that called for it ended, because nobody has touched the controller since. The zones are getting watered on a schedule the current season's rainfall and temperature no longer call for.
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 controller's CURRENT program exactly as it is running today -- every zone's run time, start time, and active days -- before changing anything.
- 2. Pull the manufacturer's seasonal-adjust guidance (or the controller's own seasonal-adjust dial/menu) and compute the correct run times for the current season.
- 3. Enter the new program into the controller zone by zone, confirming each entry on the controller's own display before moving to the next.
- 4. Record the controller's NEW program in full, matched field-by-field against the before record, and confirm the display shows the change saved, not just entered.
What counts as done
- Full before-program record (every zone's run time, start time, active days) as found
- Full after-program record in the same format, matched field-by-field against the before record
- Confirmation the controller display shows the new program saved, not just displayed
- Photo of the controller's seasonal-adjust setting or menu at its new value
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_1789886609235_egqqqwr","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_1789886609235_egqqqwr