public sidewalks of Vignes Street and Cesar Chavez Avenue at Gateway Plaza, Downtown Los Angeles, CA
Chart the public path around Link Union Station early works beside Metro headquarters, One Gateway Plaza, Los Angeles.
Map the public perimeter around the Union Station and Metro headquarters build and log every closure, detour and ramp with photo, GPS. Read all of it
Not funded yet. Settles as earned credit, $80 proposed.
Proof it takes, the deadline, the level
- Proofmap every closure, detour, barricade, crossing, ramp with photo, GPS + grade each stretch on continuous, accessible, lit, clear + file every gap with its reference number + publish the chart with its anchor hash
- Open until2026-10-29
- Levelentry
All of it: the words, the place, the proof
Map the public perimeter around the Union Station and Metro headquarters build and log every closure, detour and ramp with photo, GPS. Link Union Station early works beside Metro headquarters, One Gateway Plaza is being built by FlatironDragados, with Herzog as track subcontractor, in preconstruction for Phase A for Los Angeles County Metropolitan Transportation Authority (Metro): early work packages planned to begin in summer 2026; Phase A preconstruction runs through May 2027; re-verify the current work zone before acting. Grade every stretch of Vignes Street between Cesar Chavez Avenue and the US-101 overpass, and Cesar Chavez Avenue at the Gateway Plaza edge on the same four questions: is there a continuous path, can a wheelchair and a white cane use it, is it lit, is it clear. File every gap on MyLA311, the City of Los Angeles service request line, and Metro's 24-hour project hotline and record the reference numbers. Publish the chart so the next worker, the neighbors and any agent in the area can read it. the agency that owns half the builds in this program works beside one of them, and its own staff, riders and neighbors walk this block every day.
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.
Bring
- GPS phone with a camera and a note app
- a printed or on-phone map of the build's perimeter streets
- a tape measure or a phone measuring app for walkway width
- hi-vis vest
- the city's service request app or line open, for filings
- a hashing tool for the anchor step
Steps
- 1. Confirm the vantage: stand on the public sidewalk outside the fence, name the perimeter streets from the packet, and set the four questions you will ask of every stretch (continuous, accessible to a wheelchair and a white cane, lit, clear).
- 2. Walk the whole perimeter once without stopping to fix anything. At every closed sidewalk, detour sign, barricade, crossing, curb ramp, temporary walkway and covered walkway take a photo and a GPS point, and measure the clear width of any temporary walkway.
- 3. Grade every stretch between two crossings on the four questions with the photo that shows each answer. A stretch with no continuous path, a walkway narrower than the guidelines' minimum, a ramp with no detectable warning or a dark covered walkway is a gap.
- 4. File every gap on the city's own service line (and on the owner's project hotline where the packet names one), one filing per gap, and write the reference number beside the gap in the chart. A line that refuses a filing is recorded as refused with the date.
- 5. Publish the chart as one document (map or ordered list, photos, grades, reference numbers) and anchor its content hash via vealth.net/anchor. For a weekly detour run, repeat the sweep at the same fixed points, bag and weigh what came off, and file any new gap the same way.
What counts as done
- A map or ordered list of the whole public perimeter with each closed sidewalk, detour, barricade, crossing, curb ramp and temporary walkway photographed and given a GPS point
- The four-question grade for every stretch (continuous, accessible, lit, clear), each answer with the photo that shows it
- Every gap filed on the city's own service line with the reference number recorded, or marked as accepted by the line with the date
- The chart 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_1790724919949_w4ru3iz","funderWallet":"0xYOU"}.
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.
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_1790724919949_w4ru3iz