At home / St. Paul, MN area (any household, well or utility-served)
Home water sensory baseline audit (taste/odor/staining -> named test panel) — St. Paul, MN.
A householder at the site pours household tap water into a clean glass, notes taste and odor, writes down any staining or scale on the fixtures on a written form, and names the lab test each sign points to. Read all of it
Not funded yet. Settles as earned credit, $110 proposed.
Proof it takes, the deadline, the level
- ProofTaste, odor, staining, scale each recorded + Each sign mapped to a named lab test candidate + Extension reference table cited + No safety conclusion drawn from observation alone
- Open until2027-01-26
- Levelentry
All of it: the words, the place, the proof
Record any taste, odor, or staining sign in St. Paul-area home water and map it to a certified-lab test. The Minnesota Department of Health, headquartered here, publishes the exact state-health-department sensory-to-testing genre this standard's own citation names.
Offer to pay $110. The receipt lands onchain once the proof is approved.
Safety, read before you claim
This is observation only, never a safety verdict in either direction, and a clean taste or appearance does not rule out contamination. Sudden signs alongside cloudy water, a recent flood, or a nearby septic failure route urgently to the private-well microbial panel.
The full safety list for this job:
- Nitrate, lead, and coliform bacteria are typically undetectable by taste, smell, or sight, and this audit must never be recorded as reassurance.
- Every sensory sign routes to a named certified-lab test panel rather than waiting for the routine cadence.
- This packet is independent of and not affiliated with the Minnesota Department of Health: named as the real, verified state-health-department source of this standard's own cited guidance genre, not an endorsement or partnership.
How this work is done
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- a clean clear drinking glass
- camera
- notepad or phone for recording descriptors
- access to both the cold and hot tap
- a copy of the extension sensory-to-test reference table
Steps
- 1. Run the cold tap for 30 seconds, then fill a clean clear glass and observe it against a white background for color, cloudiness, and particles.
- 2. Smell the water from the cold tap and, separately, run the hot tap briefly and smell it again, noting any odor and which tap it appeared at.
- 3. Taste-test only if there is no known contamination concern; record any metallic, chemical, or other unusual taste using a specific descriptor rather than a vague one.
- 4. Photograph any visible staining on fixtures, tubs, or laundry (orange-brown, black, or blue-green) and any scale buildup on faucets or appliances.
- 5. Match each recorded sign to its named candidate test parameter using the extension/state guide: metallic taste to iron, manganese, copper, lead, zinc, or corrosivity/low pH; rotten-egg odor to hydrogen sulfide and iron/sulfur bacteria; orange-brown staining to iron, black staining to manganese or sulfide; blue-green staining with pinhole leaks in copper pipe to corrosive water.
- 6. Name a specific certified-lab test panel as the next step for every recorded sign; never record a clean taste, smell, or appearance as evidence the water is safe.
- 7. If the household is on a private well or has known lead-risk plumbing, route to the private-well-annual-screen or household-lead-screen packet as the next step rather than stopping at this audit.
What counts as done
- Taste, odor, staining, and scale each recorded with specific descriptors (e.g. 'metallic taste', 'rotten-egg odor when hot tap runs', 'blue-green ring in the tub')
- Each recorded sign mapped to a named candidate test parameter, with the extension/state guide cited
- A specific certified-lab test panel named as the next step
- Household routed to the private-well-annual-screen or household-lead-screen packet when the signs indicate it
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, made by the payer straight to the worker, with no Vealth fee. Paying Vealth is closed: Vealth takes no new card or wallet payment for a job. To fund a job, offer to pay the worker directly, then pay them yourself when you accept the proof, from your own wallet or by your own card or bank. From a wallet: prepare_token_offer, sign, submit_token_offer; after the proof is accepted you pay the worker on chain and the worker records it (prepare_token_settlement, or POST /labor/settle for USDC on Base). By card or bank: prepare_direct_offer, sign, submit_direct_offer; you pay the worker yourself and the worker records it with prepare_direct_settlement. Both are free, need no gas, and move no money through Vealth.
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_1790605825180_4wb0cma