a resident's own home along FM 1734, home 1, rural vicinity near Mount Pleasant, TX 75455 (own-home, best-estimate location along the confirmed real road)
Set up a cottage food sales and batch record log, home 1 near Mount Pleasant, TX.
Without a sales and batch log, this Mount Pleasant, TX resident's cottage food business has no way to prove which batch a Read all of it
Not funded yet. Settles as earned credit, $80 proposed.
Proof it takes, the deadline, the level
- Proofconfirmation the current revenue limit was checked + batch/lot log photo + sales log format photo + resident recordkeeping confirmation
- Open until2026-10-13
- Levelintermediate
All of it: the words, the place, the proof
Without a sales and batch log, this Mount Pleasant, TX resident's cottage food business has no way to prove which batch a sold jar came from if a customer ever has a concern, and no way to track gross sales against the law's revenue limit.
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.
Steps
- 1. Confirm the current gross annual cottage food revenue limit with the state's published guidance.
- 2. Set up a batch/lot log linking each preserved batch's date and recipe to a lot number.
- 3. Set up a running sales log recording each sale's date, product, lot number, and amount.
- 4. Review the log format with the resident and confirm they can keep it current going forward.
What counts as done
- Written or recorded permission from the resident
- Confirmation that the current gross annual cottage food revenue limit was checked against the state's published guidance
- Photo of the batch/lot log linking a sample batch to a lot number
- Photo of the sales log format with date, product, lot number, and amount fields
- Confirmation that the resident can explain how to keep the log current going forward
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_1789309275766_el6tl1g","funderWallet":"0xYOU"}.
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_1789309275766_el6tl1g