the city park's irrigation controller, Poteet, TX 78065 (Atascosa County); best-estimate location near the town center, exact address not confirmed
Install a rain/freeze shutoff sensor and prove it interrupts the cycle, the city park's irrigation controller, Poteet, TX 78065 (Atascosa County).
The city park's irrigation controller runs its full schedule no matter what happened overnight -- rain that already soaked the ground, or Read all of it
Not funded yet. Settles as earned credit, $140 proposed.
Proof it takes, the deadline, the level
- Proofsensor wiring photo + triggered bench-test showing cycle interrupt + reset confirmation + GPS
- Open until2026-10-20
- Levelintermediate
All of it: the words, the place, the proof
The city park's irrigation controller runs its full schedule no matter what happened overnight -- rain that already soaked the ground, or a hard freeze -- because there is no shutoff sensor wired in to interrupt it. Every cycle that runs into already-saturated or frozen ground is water the schedule should have skipped.
Fund it for $140. 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. Power the controller off at its disconnect, then mount the rain/freeze sensor at an open, unobstructed spot per the manufacturer's siting spec, clear of the eave line and any sprinkler spray.
- 2. Wire the sensor into the controller's dedicated sensor-bypass terminal, never the load side, and confirm the wiring matches the controller's own terminal diagram.
- 3. Restore power, then run the bench test: trigger the sensor (saturate the rain sensor's absorbent disks with water, or hold the freeze sensor below its rated cutoff with an ice pack) and start a scheduled zone from the controller.
- 4. Record the controller's screen showing the run was skipped or interrupted while the sensor is triggered, then release the sensor and confirm the same zone runs normally once it resets.
What counts as done
- Before photo of the controller's sensor terminal with no sensor wired in
- Wiring photo showing the sensor connected to the dedicated sensor-bypass terminal, not the load side
- Bench-test photo series showing the triggered sensor and the controller's screen reading a skipped or interrupted cycle
- Photo/reading of the same zone running normally once the sensor resets, confirming the bypass works in both states
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_1789886593056_2hw4lzy","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_1789886593056_2hw4lzy