Overwintering colony-loss tracking (Bee Informed Partnership methodology) — apiary / national.

Track colony losses using the Bee Informed Partnership's own denominator and season boundaries. Read all of it

Not funded yet. Settles as earned credit, $110 proposed.

Claim this job

Proof it takes, the deadline, the level

ProofColony counts taken at season boundaries using BIP's own colony/at-risk definitions + Summer, winter, and annual loss rates calculated separately + Operation's own size band compared to BIP's current published national result + Suspected cause routed out, never self-diagnosed
Open until2027-03-21
Levelentry

All of it: the words, the place, the proof

Track colony losses using the Bee Informed Partnership's own denominator and season boundaries. A keeper who only knows their own dead-out count has no way to tell an ordinary year from a warning sign, because there is no single fixed 'normal' loss number — BIP's own national survey shows the honest benchmark moves every year and differs by operation size. Using the SAME at-risk denominator and season windows BIP uses turns a private hunch into a number that lines up against the published national result for the same size of operation, catching a worsening pattern before it becomes chronic.

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

Where: On-site at the apiary / national (managed honey bee colonies). Open the map
Pay: $110 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: Colony counts taken at season boundaries using BIP's own colony/at-risk definitions + Summer, winter, and annual loss rates calculated separately + Operation's own size band compared to BIP's current published national result + Suspected cause routed out, never self-diagnosed
This is exactly what gets it approved. Nothing settles without it.
Level: entry: anyone can start here
Open until: 2027-03-21
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.

Bring

The operation's own hive/yard records showing colony count at the season start (April 1)
A record of any colonies made (splits), acquired (packages, swarms, nucs), or given away/sold during the season, per BIP's own colony and at-risk definitions
The current BIP National Colony Loss and Management Survey published results for the matching operation-size band (backyard 50 or fewer / sideline 51-500 / commercial more than 500), from beeinformed.org or apiaryinspectors.org
A dated loss-tracking log or spreadsheet the keeper maintains across seasons

Steps

1. At the season boundary (April 1 for annual/summer-start, October 1 for winter-start), count every colony currently in the operation using BIP's own colony definition: a full-sized colony, a nuc, a newly created split, or a newly installed package or swarm all count; a mating nuc does not.
2. Record every colony made (split) or acquired (package, swarm, purchased nuc) during the season, and every colony sold or given away, per BIP's own 'colonies at risk' rule: at-risk colonies are the viable colonies present plus new colonies made or acquired, MINUS colonies sold or parted with — a sold colony is never counted as a loss.
3. At the season's end, count colonies that failed to survive as a discrete, queenright unit (dead-outs, unrecoverable queenless/laying-worker colonies, or colonies too weak to continue and combined into another hive) as the season's losses.
4. Calculate the loss rate as losses divided by colonies-at-risk for that season, expressed as a percentage, separately for summer (April 1-October 1), winter (October 1-April 1), and the full annual cycle (April 1-April 1) — never a single blended number.
5. Classify the operation into BIP's own size band (backyard: 50 or fewer colonies; sideline: 51-500; commercial: more than 500) and compare the season's measured rate against BIP's most recently published national result for that SAME band — record the comparison as a number-to-number benchmark, never a pass/fail verdict.
6. Where a suspected proximate cause is visible (disease signs, a suspected pesticide kill, widespread queen failure), route the observation to the state apiarist, extension apiculturist, or a diagnostic lab per this kingdom's existing routing law; the loss-rate number itself never stands in for a diagnosis.
7. During BIP's live survey window (April 1-30 each year), optionally submit the operation's own counts to the current National Colony Loss and Management Survey at beeinformed.org so the data joins the national dataset, exactly as the survey is designed to be completed.
8. Log the season's rate, band comparison, and any routed findings in the operation's running record, and set the next season-boundary count date.

What counts as done

Colony counts taken at each BIP season boundary (April 1 and October 1) using BIP's own colony definition, with sold or given-away colonies excluded from the at-risk denominator
Summer (Apr 1-Oct 1), winter (Oct 1-Apr 1), and annual (Apr 1-Apr 1) loss rates each calculated and dated separately, never blended into one number
Operation classified into BIP's own size band (backyard/sideline/commercial) and the season's rate compared against BIP's most recently published national result for that band, recorded as a comparison only
Any suspected disease, pest, or pesticide cause behind a loss routed to the state apiarist, extension apiculturist, or a diagnostic lab, never self-diagnosed from the loss rate alone

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_1790037190050_amo316t","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

Vote for it, free Pledge backing, free Fund this work, $110

Packet WORK_1790037190050_amo316t