At the outdoor bed site / national (home and small-farm wine cap wood-chip beds)
Home/small-farm wine cap (Stropharia rugosoannulata) outdoor bed cultivation audit — national.
Inspect your outdoor wine cap bed for colonization progress and volunteer fungi, never for edibility. Read all of it
Not funded yet. Settles as earned credit, $120 proposed.
Proof it takes, the deadline, the level
- ProofBed layered per source spawn rate, coverage depth + Chips or straw pre-soaked before layering + Colonization progress checked against expected fruiting window + Any non-Stropharia fruiting body flagged unidentified, never eaten + No edibility determination made regardless of mature-ID literature
- Open until2026-12-23
- Levelentry
All of it: the words, the place, the proof
Inspect your outdoor wine cap bed for colonization progress and volunteer fungi, never for edibility. Wine cap grows in an open, soil-contact wood-chip bed instead of an enclosed substrate block, the opposite technique from this standard's oyster/shiitake/lion's mane definitions, so the audit tracks bed construction and colonization rather than searching for the same indoor contamination signs.
Fund it for $120. 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
- The grow area (fruiting chamber, monotub, or shiitake log yard) with good lighting
- Camera for photographing any suspect growth before disturbing it
- Nitrile gloves and an N95 dust mask for inspection near suspect substrate
- A sealed disposal bag for discarded contaminated substrate
- A grow log with prior audit dates and environmental settings
Steps
- 1. Inspect the substrate and fruiting surfaces without unnecessary disturbance; record temperature, humidity, and fresh-air-exchange (FAE) conditions at the time of audit.
- 2. Look for green mold: green-sporulating patches on grain spawn or substrate, most common where FAE is poor or substrate was under-sterilized (Trichoderma spp., the documented dominant green-mold pathogen on cultivated mushroom substrate).
- 3. Look for cobweb mold: a fast-spreading, fine gray-white mycelial mat that can overgrow pins and casing within days (Cladobotryum spp.).
- 4. Look for bacterial blotch: brown-to-tan slimy or sunken lesions on cap surfaces, typically worsened by excess surface moisture (Pseudomonas tolaasii).
- 5. Photograph any suspect growth before touching it, for the grow log.
- 6. Isolate affected substrate or blocks immediately, moving them out of the shared grow space to prevent airborne spore or mycelial spread to clean substrate.
- 7. DISCARD the contaminated substrate. Never salvage it, cut out the affected area and continue fruiting, or harvest any mushroom from a contaminated block for food.
- 8. Review sterile/sanitary technique against the source protocol — substrate pasteurization/sterilization parameters, spawn-handling cleanliness, FAE and humidity control, and surface sanitation between batches — and record the specific gap identified, if any.
- 9. Log the audit date, findings, disposal action, and technique-review outcome against the prior audit.
What counts as done
- Bed construction recorded against the source protocol: chips/straw pre-soaked, spawn layered at the documented rate (roughly one 5.5 lb bag per 30-50 sq ft, 4-6 inches deep), and coverage depth measured
- Colonization progress (white mycelial webbing through the chip layer) checked and dated against the expected 2-6 month fruiting window from inoculation
- Bed moisture and mulched-area integration (shade, existing garden/orchard mulch) recorded, since an outdoor bed has no enclosed humidity control to fall back on
- Any fruiting body that is NOT a mature, clearly burgundy-capped Stropharia recorded as unidentified volunteer fungus and photographed, never assumed to be the cultivated species
- No edibility, culinary, or medicinal claim recorded anywhere in the audit, regardless of how distinctive published identification literature describes the mature species
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_1790264090014_1akd7we","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_1790264090014_1akd7we