Anyone can start here · public streets, canal paths and city parks, Phoenix, Maricopa County, AZ
Build the water right and permit public record baseline for City of Phoenix Water Services, Phoenix, AZ.
Fund it for $80. Proof lands onchain when it's done.
$80 proposed
This packet is not funded yet, so this figure is a proposed price and not money waiting in escrow. If a buyer funds it, approved proof settles that price onchain. If nobody funds it, approved proof earns provable credit toward the work instead of cash — recorded, and readable any time at vealth.net/labor/credit/(your wallet). You see which before you claim, never after.
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.
What the work involvesCity of Phoenix Water Services draws from Colorado River water through the Central Arizona Project, Salt and Verde river water through SRP, and Phoenix AMA groundwater. Before anyone argues about how much is fair, write down what the public record actually says: the water rights, permits or contracts on file, the volume each one allows, the agency that issued it, and the current status of the source under Arizona Department of Water Resources, Phoenix Active Management Area, with Bureau of Reclamation Colorado River operations setting the river year. Every field carries its citation or is marked not found, and nothing is estimated in anyone's favor. the state's 2023 Phoenix AMA groundwater model found unmet demand at the 100 year assured supply horizon and new groundwater based subdivision certificates were paused, so every gallon in this valley now carries a public argument.
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- laptop with a spreadsheet
- the state or district water rights and withdrawal registry, open in a browser
- the utility's published monthly or annual water reports
- USGS National Water Information System site pages for the local gauges and monitoring wells
- a hashing tool for the anchor step
- GPS phone and camera for the one bank or gauge photo
Steps
- 1. Name the system and the source exactly as the agency names them, then list every record type that could exist for it: water right, permit, contract, registered withdrawal, diversion order, compact allocation.
- 2. Search each registry for the system by name and by any parent utility or district, and record for every hit the issuing agency, the filing reference, the allowed volume in the record's own units, and the date of the version read. Where a search returns nothing, write not found and write down the search that was run.
- 3. Pull the volume actually taken for the reporting period and LABEL each figure at the point of entry: utility report, agency registry, owner meter, or no data. Never convert units without showing the conversion in the sheet, and never fill a gap with an average.
- 4. Pull the published record for every public gauge and monitoring well within reach, keep the full series rather than the last reading, and state a trend per site with its slope and the period the slope was computed over.
- 5. Set allowed volume, taken volume and the same period one year earlier side by side, and write one plain sentence saying which way the place is going and which figure in the sheet is the weakest.
- 6. Publish the sheet and the sentence in full, hash the published file, and anchor the hash via vealth.net/anchor before handing it to anyone.
What counts as done
- A table of every water right, permit, contract or registered withdrawal found for the system, each with its issuing agency and filing reference or URL, or marked not found with the search described
- The allowed annual volume on each record as written, in the record's own units, never converted without showing the conversion
- The governing rule cited by name: the plan, stage, cap or compact the agency applies to this system, with the date of the version read
- The baseline published in full and its content hash anchored via vealth.net/anchor
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_1788298586303_tm1nhvr","funderWallet":"0xYOU"}.
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.