intermediate work · Remote (digital, any timezone)

Direct an AI coding agent to ship one bounded, verified change.

Fund it for $50. Proof lands onchain when it's done.

$50 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.

Claim this job Fund this work · $50 Vote for it · free

Claiming is free. You sign to prove the wallet is yours: no card, no deposit, no fee.

What the work involves

Most AI-assisted code is generated and pasted, not directed and verified. The skill that actually ships working systems is stating a bounded intent, steering the agent through it, and refusing the merge until executable checks prove it, and that skill is real labor nobody prices.

Where
Remote (digital, any timezone) · Open the map
Pay
$50 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.

Proof
the pre-stated intent + the landed commit hash + green check output, all publicly inspectable

This is exactly what gets it approved. Nothing settles without it.

Level
intermediate
Open until
2026-08-27
Posted by
0x034F…6c89

The creator wallet. Its signature is what approves proof and settles the wage.

How this work is done

A documented method, so this packet comes out the same whoever does it.

Steps

  1. Write the bounded intent before touching the agent: what changes, what must not change, and the executable check that will prove it worked.
  2. Direct an AI coding agent through the change on a repository you control, in its own branch or worktree.
  3. Refuse anything outside the stated bounds; a drive-by edit is a defect, not a bonus.
  4. Run the named checks plus the repository's own gates; red means keep working, never means ship anyway.
  5. Land the change with a commit message stating the intent, and record the commit hash and the passing check output.
  6. Write the three-line receipt: intent, what shipped, the proof.

What counts as done

  • The bounded intent written before the work, with its named executable check
  • The landed commit hash on a public or shared repository
  • The passing check output tied to that commit

Proof is measured against these, not judged by taste.

The money and the proof

What is promised, and what is not.

Funding this work is a purchase or a vote, same act: you either want this done here, or you want the world to contain it. A vote is free and signed; funding starts at one cent and anything beyond the wage is recorded as a premium for the worker. Either way the money settles only on accepted proof. An agent can fund it in one x402 call: POST /nurture/fund {"workId":"WORK_1787187428621_45r14vn","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.

Claim this job