Anyone can start here · Any hospital or care-home facility, United States, posted and coordinated by that care organization — never claimed on this board's own say-so
Environmental hygiene verification: terminal + daily cleaning to a named standard, fluorescent-marker checked — any care organization.
Fund it for $90. Proof lands onchain when it's done.
$90 proposed
Not funded yet. Settles as earned credit, $90 proposed.
- Proofcleaning session log (room, terminal or daily, date/time, protocol followed) + fluorescent-marker check on the standardized high-touch surface set, marks placed by someone OTHER than the cleaner before the shift and checked under UV light after + pass/fail per surface recorded + red flags recorded absent or routed (facility occupational-exposure protocol / clinical staff / Adult Protective Services or the state Long-Term Care Ombudsman Program / emergency)
- Open until2026-10-19
- Levelentry
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.
Not for you? Pledge backing · free Fund this work · $90
What the work involvesThe same 47%-clean baseline Carling et al. found in 2006 is the reason hospitals still measure cleaning with fluorescent markers today: without independent verification, thoroughness cannot be assumed. This packet makes a care organization's own environmental-hygiene labor visible and checkable, wherever that organization coordinates it.
How this work is done
A documented method, so this packet comes out the same whoever does it.
Bring
- the facility's own posted cleaning/disinfection protocol (CDC/HICPAC-based) and its own required PPE
- fluorescent gel marker dots (single-use, invisible until UV light) for the standardized high-touch surface set: bed rail, call button, light switch, door handle, IV pole, bedside table, faucet handle, tray table
- a UV light/torch for post-clean checking
- the facility's own occupational-exposure protocol contact, the on-duty nursing/clinical staff contact, and — depending on state and facility type — the state Long-Term Care Ombudsman Program or Adult Protective Services line, printed for reference
- a cleaning session log (room, date/time, terminal or daily, protocol followed, pass/fail per marked surface)
Steps
- 1. Confirm with the care organization's own supervisor or infection-prevention liaison which room and which cleaning type (terminal, between patients/residents, or daily) this session covers, and follow the facility's own posted protocol — never a generic or invented one.
- 2. Before the cleaner enters, someone OTHER than the cleaner places a fluorescent gel dot on each of the standardized high-touch surfaces present in the room; this must never be the cleaner themselves.
- 3. Clean and disinfect the room to the facility's own protocol, including every marked surface, using the facility's own required PPE.
- 4. After cleaning, the same independent person (or another designated observer, never the cleaner) checks each marked surface under UV light: no visible mark or fluorescence = pass; a fully or partially intact mark = fail.
- 5. Any failed surface is re-cleaned immediately and re-checked; log the result honestly rather than marking it passed on the cleaner's own say-so.
- 6. Log the session (room, date, time, cleaning type, protocol, and pass/fail per surface); route anything not the cleaner's own to handle per the decision rules below.
What counts as done
- Room, date, time, and whether terminal or daily cleaning logged, with the named facility protocol followed
- Fluorescent-marker pass/fail recorded for each of the standardized high-touch surfaces (bed rail, call button, light switch, door handle, IV pole, bedside table, faucet handle, tray table), with marks independently placed and independently checked
- Any failed surface re-cleaned and re-checked, with the result logged (never marked passed on the cleaner's own say-so)
- Every decision-rule red flag recorded as absent or routed as the rule says
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_1788498150246_jxkpnux","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.